How often have you tried to visit the element14 Community, and instead seen an 'oops!' page?

I’m voting almost every time to highlight this issue that I’ve encountered several times, specifically when editing a draft of one of my RoadTest reviews.

When making multiple changes between the HTML view and the standard text editor, I frequently get the “Oops” message. In all cases when this happens, my access to the community is temporarily blocked for a period of time (which I’m not sure how long it lasts).

I’m reporting this as constructive feedback. Overall, my experience with the platform has been very positive, and I hope this helps identify an area where the page could be improved.

I’m really happy to be part of the community and appreciate all the work behind it.

Thanks!

AngelSoto said:

I’m voting almost every time to highlight this issue that I’ve encountered several times, specifically when editing a draft of one of my RoadTest reviews.

Hey AngelSoto ,

To be clear, this is not the same as "content under review", are you certain that you're seeing "Oops!" explicitly?

Hi cstanton 

Yes, I’m sure, it is the same “Oops!” message, like the one shown in chloro’s screenshot.

Hi,

Just for future reference, I was able to identify the root cause of the “Oops!” behaviour I reported earlier with the help of the maintenance team.

In my case, it was triggered while editing a RoadTest draft that contained a large number of image references pointing to non-existent paths (coming from externally generated HTML). This resulted in multiple 404 responses in a short time, which in turn activated the platform’s protection mechanisms and temporarily blocked my access.

After their explanation, the behaviour makes sense from a backend/protection perspective, so it’s not really a failure but more a side effect of how the system handles repeated errors.

I’ve adjusted my workflow accordingly (uploading images individually instead of referencing them externally), and the issue is no longer occurring.

Hope this helps add some context in case others run into something similar.

Thanks!

Hi,

Just for future reference, I was able to identify the root cause of the “Oops!” behaviour I reported earlier with the help of the maintenance team.

In my case, it was triggered while editing a RoadTest draft that contained a large number of image references pointing to non-existent paths (coming from externally generated HTML). This resulted in multiple 404 responses in a short time, which in turn activated the platform’s protection mechanisms and temporarily blocked my access.

After their explanation, the behaviour makes sense from a backend/protection perspective, so it’s not really a failure but more a side effect of how the system handles repeated errors.

I’ve adjusted my workflow accordingly (uploading images individually instead of referencing them externally), and the issue is no longer occurring.

Hope this helps add some context in case others run into something similar.

Thanks!