Removing “page is protected by password” in unprotected pages
-
Hi William,
Can you please share with us the Project Name and the Preview URL of your project in the Brizy Cloud Dashboard so we can further check the issue?

Best regards,
Ariel H.0 -
Certainly. There are a few of them doing this at the moment.
In the Workspace “William Mincy” the following websites are showing this behavior:
* William Mincy - https://www.w*****ncy.com/
In the Workspace “|meta| the following websites are showing this behavior:
* HalfMeta - https://ha****a.com
* Other Realities - https://www.h****ta.com/In all of these cases the websites have been published for a while and I have not added a protected area. Additionally, when I go into the cloud editor I don’t find any element in the page that would let me remove this. All have been published for a while now and should not have this on the sites.
So the help I need is in understanding what this is and in removing it from my sites. Additionally I’d like to know why this was added to already published websites that I did not edit. Having elements added without my permission or knowledge really makes me uneasy in moving more sites to the platform as I’d planned in the new year, so hoping this is just a fluke and not a larger issue.
0 -
Hi William,
Thank you for your cooperation.
I’ve created a private ticket so one of my colleagues can look into this issue. You should hear back from them soon.
Sorry for the inconvenience.
Best regards,
Ariel H.0 -
Thanks, but I’m not sure how I follow up on the issue from here. Will someone be messaging on this thread or will they be sending me an email?
0 -
Hello William,
Kindly check the hello@......stries.com inbox for an email from support@brizy.io. My colleague Basharat has replied to you.
This is an unusual issue. After our developers investigate, Basharat will contact you with an update on resolving the issue.
0 -
The issue appears to now be resolved, thanks. However what was the cause of the problem?
0 -
Hi William,
Thank you for the update and for bringing this to our attention. It appears to have been a backend glitch.
If you have any further questions, feel free to reach out.
Best regards,
Ariel H.0
Please sign in to leave a comment.
Comments
7 comments