When adding a new user I am able to set the user up with all relevent details and the ui indicates that the user is saved correctly but the user tree never updates. The user data seems to be saved correctly in the user tables with the exception of the field 'defaulttoliveediting' is set to 1 instead of 0.
There is an error in the log table but all it says is: 'return:users/EditUser.aspx?id=93'
Even though the user data seems to be in the tables I am not able to log into the back end with the new user details.
Can anyone give me a steer on how I proceed from here to resolve this issue?
Reloading the nodes makes no difference, the user never appears in the list.
More related information;
When selecting the 'Content' node as the start node in content, the name of the node returns as 'SYSTEM DATA: umbraco master root' instead of Content. It is still stored in the db as -1 and when the user details panel reloads it is called Content again.
Yes I have inspected them and the request/response looks the same as my development platform.
I have just noticed that by default all the restricted access tickboxes are ticked when I create a user which means they are automatically disabled/in canvas edit mode and dont have Umbraco access. Creating a new user with these unticked works as expected.
Have also found out that since 4.7 disabled users no longer appear in the user list as they used to, sorry for the confusion.
Thanks for your time though (even though I wasted it, sorry again), its always nice to have another persons ideas in these situations.
I think the disabled by default issue may stem from the fact I had to migrate from MySQL to MSSQL mid project and a missed default setting.
Hmmm. Out of curiosity I've glanced over the code and realised that the tree is really supposed not to show disabled users. It looks like a very strange decision since it's absolutely unclear how to enable a disabled user back without going into the database...
New users dont appear in the user tree
When adding a new user I am able to set the user up with all relevent details and the ui indicates that the user is saved correctly but the user tree never updates. The user data seems to be saved correctly in the user tables with the exception of the field 'defaulttoliveediting' is set to 1 instead of 0.
There is an error in the log table but all it says is: 'return:users/EditUser.aspx?id=93'
Even though the user data seems to be in the tables I am not able to log into the back end with the new user details.
Can anyone give me a steer on how I proceed from here to resolve this issue?
Many thanks
Simon
Hi. It happens sometimes. Personally I don't bother about it and just use the "reload nodes" context menu item.
Reloading the nodes makes no difference, the user never appears in the list.
More related information;
When selecting the 'Content' node as the start node in content, the name of the node returns as 'SYSTEM DATA: umbraco master root' instead of Content. It is still stored in the db as -1 and when the user details panel reloads it is called Content again.
Any help appreciated.
Have you tried to inspect http requests with FireBug or Chrome's developer tools?
Yes I have inspected them and the request/response looks the same as my development platform.
I have just noticed that by default all the restricted access tickboxes are ticked when I create a user which means they are automatically disabled/in canvas edit mode and dont have Umbraco access. Creating a new user with these unticked works as expected.
Have also found out that since 4.7 disabled users no longer appear in the user list as they used to, sorry for the confusion.
Thanks for your time though (even though I wasted it, sorry again), its always nice to have another persons ideas in these situations.
I think the disabled by default issue may stem from the fact I had to migrate from MySQL to MSSQL mid project and a missed default setting.
Hmmm. Out of curiosity I've glanced over the code and realised that the tree is really supposed not to show disabled users. It looks like a very strange decision since it's absolutely unclear how to enable a disabled user back without going into the database...
is working on a reply...