WordPress.org

1. Chucky-GFX
   Member
   Posted 3 years ago #

   Hello there,
   i have a problem with my pages. If i want to edit them i get the message "You are not allowed to edit this page."
   I have a site in german and copied the whole database and the folders.
   Then i created new tables. with the prefix 'wp_eng'. First i had the problem with the false permissions, so i cant enter the wp-admin panel. After i fixed that i've now the problem that i cant edit the old posts. Anyone a idea how to fix that?

2. stvwlf
   Member
   Posted 3 years ago #

   When you put more than one blog in a single database, it is still seen as two different blogs. You have two WP installations? It won't work otherwise.

   Most likely you do not have administrator privileges on the second blog. That would give you the "not allowed" messages.

3. Chucky-GFX
   Member
   Posted 3 years ago #

   The second blog is a full copy of the first... the only difference is other folder and an other database with the prefix wp_eng_ for english.

   I have the privilegies of an admin...but i can't use them.

4. Chucky-GFX
   Member
   Posted 3 years ago #

   i solved the problem . wp_options ...there is a field with wp_user_roles...that must be named as wp_eng_user_roles. Not that easy to copy a blog ;D

5. cantemusdomino
   Member
   Posted 3 years ago #

   I have encountered the same problem with both administrator accounts on the same installation. Existing pages are off-limits for administrators, as "You are not allowed to edit this page" appears in lieu of the editing fields.

   Additionally, administrators have the ability to post new pages, but not to publish them - a [Submit for Review] button replaces the [Publish] button; new pages cannot clear a review process if the administrators don't have the capability to do so.

   Lastly, administrators lack the ability to delete pages; every attempt is met with a "You are not allowed to delete this page" alert.

   The installation in question has a database prefix of wp_xxxxxxx_, and the fix given above does not seem to have any positive or negative effect. Another contributing factor to this headache may be the non-linear upgrade that was made from 2.0.x to 2.6.0.

   Plugins have been deactivated with no effect on the lack of page editing capabilities. Under the hood, the wp_xxxxxxx_user_meta information checks out - both administrators have the correct data assigned to them.

6. nsanden
   Member
   Posted 3 years ago #

   I have exactly the same problem as you cantemusdomino. My tables also have non-defualt prefixes. Did you ever figure it out?

7. nsanden
   Member
   Posted 3 years ago #

   Okay, I think i have it fixed, finally!

   I think the problem was too many upgrades. We must of started with wordpress 1.x and upgraded 10 times since then.

   The fix was to change the wp_user_roles option_value to:

   a:5:{s:13:"administrator";a:2:{s:4:"name";s:23:"Administrator|User role";s:12:"capabilities";a:51:{s:13:"switch_themes";b:1;s:11:"edit_themes";b:1;s:16:"activate_plugins";b:1;s:12:"edit_plugins";b:1;s:10:"edit_users";b:1;s:10:"edit_files";b:1;s:14:"manage_options";b:1;s:17:"moderate_comments";b:1;s:17:"manage_categories";b:1;s:12:"manage_links";b:1;s:12:"upload_files";b:1;s:6:"import";b:1;s:15:"unfiltered_html";b:1;s:10:"edit_posts";b:1;s:17:"edit_others_posts";b:1;s:20:"edit_published_posts";b:1;s:13:"publish_posts";b:1;s:10:"edit_pages";b:1;s:4:"read";b:1;s:8:"level_10";b:1;s:7:"level_9";b:1;s:7:"level_8";b:1;s:7:"level_7";b:1;s:7:"level_6";b:1;s:7:"level_5";b:1;s:7:"level_4";b:1;s:7:"level_3";b:1;s:7:"level_2";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:17:"edit_others_pages";b:1;s:20:"edit_published_pages";b:1;s:13:"publish_pages";b:1;s:12:"delete_pages";b:1;s:19:"delete_others_pages";b:1;s:22:"delete_published_pages";b:1;s:12:"delete_posts";b:1;s:19:"delete_others_posts";b:1;s:22:"delete_published_posts";b:1;s:20:"delete_private_posts";b:1;s:18:"edit_private_posts";b:1;s:18:"read_private_posts";b:1;s:20:"delete_private_pages";b:1;s:18:"edit_private_pages";b:1;s:18:"read_private_pages";b:1;s:12:"delete_users";b:1;s:12:"create_users";b:1;s:17:"unfiltered_upload";b:1;s:14:"edit_dashboard";b:1;s:14:"update_plugins";b:1;s:14:"delete_plugins";b:1;}}s:6:"editor";a:2:{s:4:"name";s:16:"Editor|User role";s:12:"capabilities";a:34:{s:17:"moderate_comments";b:1;s:17:"manage_categories";b:1;s:12:"manage_links";b:1;s:12:"upload_files";b:1;s:15:"unfiltered_html";b:1;s:10:"edit_posts";b:1;s:17:"edit_others_posts";b:1;s:20:"edit_published_posts";b:1;s:13:"publish_posts";b:1;s:10:"edit_pages";b:1;s:4:"read";b:1;s:7:"level_7";b:1;s:7:"level_6";b:1;s:7:"level_5";b:1;s:7:"level_4";b:1;s:7:"level_3";b:1;s:7:"level_2";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:17:"edit_others_pages";b:1;s:20:"edit_published_pages";b:1;s:13:"publish_pages";b:1;s:12:"delete_pages";b:1;s:19:"delete_others_pages";b:1;s:22:"delete_published_pages";b:1;s:12:"delete_posts";b:1;s:19:"delete_others_posts";b:1;s:22:"delete_published_posts";b:1;s:20:"delete_private_posts";b:1;s:18:"edit_private_posts";b:1;s:18:"read_private_posts";b:1;s:20:"delete_private_pages";b:1;s:18:"edit_private_pages";b:1;s:18:"read_private_pages";b:1;}}s:6:"author";a:2:{s:4:"name";s:16:"Author|User role";s:12:"capabilities";a:10:{s:12:"upload_files";b:1;s:10:"edit_posts";b:1;s:20:"edit_published_posts";b:1;s:13:"publish_posts";b:1;s:4:"read";b:1;s:7:"level_2";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:12:"delete_posts";b:1;s:22:"delete_published_posts";b:1;}}s:11:"contributor";a:2:{s:4:"name";s:21:"Contributor|User role";s:12:"capabilities";a:5:{s:10:"edit_posts";b:1;s:4:"read";b:1;s:7:"level_1";b:1;s:7:"level_0";b:1;s:12:"delete_posts";b:1;}}s:10:"subscriber";a:2:{s:4:"name";s:20:"Subscriber|User role";s:12:"capabilities";a:2:{s:4:"read";b:1;s:7:"level_0";b:1;}}}

8. cantemusdomino
   Member
   Posted 3 years ago #

   nsanden: That did it! You are a genius and a philanthropist.

   On the particular installation in question there were two fields named "wp_[xxxx_]user_roles" so I changed the values in both. Not sure what deleting one of them would do, so I'm leaving it alone.

   The field in question may be found in the wp_[xxxx_]options table for those less familiar with mucking around in the backend.

9. mjayas
   Member
   Posted 3 years ago #

   Thanks for the fix, nsanden, and for the additional tips, cantemusdomino!

   In case it's helpful for others, my wp_[xxxx_]options table had a row with option_name of "wp_user_roles", and a second row towards the bottom of the table with option_name "wp_[xxxx_]user_roles". I first changed the former row, but that didn't fix the problem. After changing the latter, it worked perfectly.

   (Tip for newbies like me: the rows mentioned above didn't appear on the first page of rows displayed in my MySQL admin tool; I had to click through a couple of pages to find them, and even still, they weren't near each other.)

   So, to summarize the fix:

   1. Go to the wp_[xxxx_]options table (where 'xxxx' is your table prefix)
   2. View all the data in that table
   3. Find the row with the option_name wp_[xxxx_]user_roles
   4. Edit that row, and replace the option_value for that row with what nsanden indicates above
   5. Save the changes to the row, and you should be all set.

Topic Closed

This topic has been closed to new replies.