I'm having some troubles with the access.config and protected pages. From what I understand, everything about which pages should be protected is saved in the access.config file. I have two installions, which both refer to the same DB. A dev and a production setup. When I copy the access.config from dev to production, the protected pages doesn't get updated. If I edit the settings in Umbraco on the production setup, the access.config gets overwritten and only the new entries are added.
It seems like there is some kind of cache on the config-file, or something like that? Isn't it suppose to work if I copy the file from one setup to another? All of the information in the access.config looks ok, it's the same Node IDs etc.
after you deploy the access.config, do you bump the app pool? It might get loaded into memory when the app initializes which might explain why after the file is deployed it makes no difference
Nope, I haven't tried that. I'm working for a customer and I don't have directly access to the IIS. But why should that be necessary, when everything works fine if I edit the permissions settings in Umbraco? I thought all that happend was, that the changes were added to the access.config-file. I read that nothing were added to the DB etc.
I'm thinking about this from a .NET frame of mind rather than an Umbraco frame of mind, but it sounds like when you make a change in Umbraco, it updates the values in memory then serializes that data to the file. Which would explain why when you deploy then change the settings in Umbraco the file is overwritten.
I don't know whether this is actually whats going on, but it seems like thats whats happening...
Caching on Access.Config (or?)
Hey!
I'm having some troubles with the access.config and protected pages. From what I understand, everything about which pages should be protected is saved in the access.config file. I have two installions, which both refer to the same DB. A dev and a production setup. When I copy the access.config from dev to production, the protected pages doesn't get updated. If I edit the settings in Umbraco on the production setup, the access.config gets overwritten and only the new entries are added.
It seems like there is some kind of cache on the config-file, or something like that? Isn't it suppose to work if I copy the file from one setup to another? All of the information in the access.config looks ok, it's the same Node IDs etc.
Kind regards,
Berntsen
Can't edit for some reason. I'm running 4.7, upgraded from 4.5. And the access.config is located in App_Data.
after you deploy the access.config, do you bump the app pool? It might get loaded into memory when the app initializes which might explain why after the file is deployed it makes no difference
Hi elspiko!
Nope, I haven't tried that. I'm working for a customer and I don't have directly access to the IIS. But why should that be necessary, when everything works fine if I edit the permissions settings in Umbraco? I thought all that happend was, that the changes were added to the access.config-file. I read that nothing were added to the DB etc.
Thanks for your reply. :)
/Berntsen
I'm thinking about this from a .NET frame of mind rather than an Umbraco frame of mind, but it sounds like when you make a change in Umbraco, it updates the values in memory then serializes that data to the file. Which would explain why when you deploy then change the settings in Umbraco the file is overwritten.
I don't know whether this is actually whats going on, but it seems like thats whats happening...
Rich
Yes, and thanks for your reply! I'll try to test it on my local setup and see what I'll find. Will post my findings later. :)
Hi, Berntsen.
Did you find solutioin for save information not only in file, but in database too?
Thanks.
How to raad Access.Config in my code (c#)?
is working on a reply...