The problem
The problem is that when an administrator or super user (the only users in our portal/site) edits a tab, The 'Edit Page' permission for the 'All users' is set (a lock.gif icon is displayed). This does not happend with a clean install of DNN, but after we create a new portal based on our custom template.


My questions:
1. Where does the Page edit screen' permission grid gets its defaults from?
2. How can the installation of a custom template influence tab-permissions so the page edit screen forces 'All Users' to have edit rights, which cannot be undone.


What I've tried:
I've tried a lot, but what I mainly tried is remove alle permissions for the tabpermissions and modulepermissions table that give explicit edit rights to the all 'All Users' role (role id -1). After that i execute an 'iisreset' so the cache is cleared. The edit panel is then gone for anonymous users, but the problem re-arises when the page edit screen is openened (lock icon is present) and saved (all users have edit rights again).


Thank you in advance for any insight in this matter. If you require more information please ask.


Other information:
DNN version: 5.05
The site is hosted with Windows Server 2008 and IIS 7.5. The application is runnings under it's own application pool. Regional settings for the machine are set to nl-NL and within DNN the dutch regional language pack is used (nl-NL). As a database we use SQL server 2008. DNN is installed via the Microsoft Web Installer.
Furthermore, a custom template is used when the portal was newly created. All other portals where removed.

Thank you for your fast reply Sebastian The ID's in the Portals table where indeed not correct. I've amended them, restarted the application and permissions are back to normal now. I wish I postded the question earlier :-) Thanks again!

Using DNN 5.6.1, using a portal template to create a new site, I encountered the same problem.

So, although finding this post extremely helpfull, I'm wondering if this is going to be solved in a future release?
Or do I edit my portal template somehow to prevent this? (or both  )

Thanks,