I have a Umbraco v 7.1.4 site that is completely protected by Role Based Protection.
Given that I am logged into the site as a Member (font end)
And logged in as a User/Administrator (back office)
Then some functions stop working in the back office
The uBlogsy Tag nodes stop showing and saving.
The Contour forms picker data type won't show any forms.
The accounts have different user names and emails.
I'm forced to log out as a member, use two browsers, or use a "private" browser window.
I think the best approach is to report it as a bug on the isse tracker and add as much details as you can in order to reproduce.
Does the /app_data/logs file reveal anything marked with ERROR or WARNING that could be related?
You could perhaps try doing an upgrade to 7.1.8 and see if the issue might already have been fixed in this latest version. If you do se please remember to keep a backup of the database and the files.
Before I commit to starting a bug report I will wait for 7.2 to release. After I've upgraded to 7.2 if the problem persists I will create a bug report with the logs that correspond to the issue. Indeed, several errors are reported in logs & browser console when this happens.
Members & Users conflict
I have a Umbraco v 7.1.4 site that is completely protected by Role Based Protection.
Given that I am logged into the site as a Member (font end)
And logged in as a User/Administrator (back office)
Then some functions stop working in the back office
The uBlogsy Tag nodes stop showing and saving.
The Contour forms picker data type won't show any forms.
The accounts have different user names and emails.
I'm forced to log out as a member, use two browsers, or use a "private" browser window.
What can I do to fix this, or is it a bug?
Hi Ed
I think the best approach is to report it as a bug on the isse tracker and add as much details as you can in order to reproduce.
Does the /app_data/logs file reveal anything marked with ERROR or WARNING that could be related?
You could perhaps try doing an upgrade to 7.1.8 and see if the issue might already have been fixed in this latest version. If you do se please remember to keep a backup of the database and the files.
Cheers, Jan
Jan,
Thanks, I'll do that.
Before I commit to starting a bug report I will wait for 7.2 to release. After I've upgraded to 7.2 if the problem persists I will create a bug report with the logs that correspond to the issue. Indeed, several errors are reported in logs & browser console when this happens.
Regards, Ed
is working on a reply...