![]() ![]() Report your findings here by editing your question if you don't understand the output of DNA. Remember to give give the anonymous and authenticated user roles permission to "Access developer information" to use DNA to debug access problems for these roles. DNA will display a block telling you exactly what permissions are enforced and where they come from. ![]() Use the DNA module (part of Devel) to debug node access problems. (There will be a link to this page on the Status reports page if Drupal thinks you need to do it.) ![]() To execute a database update, append the path update.php to you site's base URL. If you've just installed a new module, make sure that you've executed a database update. Repair the Sessions table: Use phpMyAdmin or a similar tool, choose your Drupal database, check the box next to the table, and find the "With selected" drop-down near the bottom of the page. Rebuild permissions: append the path: admin/reports/status/rebuild to your site's base URL, or navigate to Administration → Reports → Status report and look for the link "Rebuild permissions". If you've got drush installed (always a good thing to have around), a quick way to clean all caches on the server is drush cc all. If you use Views, clear Views' cache: Administration → Structure → Views → Settings Advanced → Clear Views' cache. To clear the server cache, navigate to Administration → Configuration → Development → Performance → Clear all caches. To clear your browser's cache, hold down Shift and reload the page. Note that you need to both clear your browser's cache and the Drupal cache on the server. Things to try when you get inexplicable "Access denied" when non-admins try to view nodes and you're sure every role has the permission "View published content":Ĭlear all caches. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |