WordPress.org

Support

Support » Plugins and Hacks » [Plugin: Tweetable] Canot access permissions error

[Plugin: Tweetable] Canot access permissions error

Viewing 15 replies - 1 through 15 (of 20 total)
  • redwallhp
    Member

    @redwallhp

    Are you an administrator on the blog? And have you run through the setup yet?

    dirkhillbrecht
    Member

    @dirkhillbrecht

    I have exactly the same problem with a freshly installed Tweetable 1.0.8 on an up-to-date 2.8.1 German WordPress installation. Own server, so no access problems. Problem is that I even cannot start the setup process, as soon as I click on any menu items in the new “Twitter” menu in the sidebar, I get “You are not allowed to access this page” (or, more precisely, the German version of this error message).

    I’m a bit stuck. 🙁

    I get the same error with permission. Running WP 2.8.1.

    Thanks

    shawnsandy05
    Member

    @shawnsandy05

    yes i am the admin

    redwallhp
    Member

    @redwallhp

    I think the significant part in this case is in admin_menus.php:

    $main_menu_permission = get_option('tweetable_main_menu_permission');
    
    if ($main_menu_permission == '') {
    	add_option('tweetable_main_menu_permission', 'edit_themes');
    	$main_menu_permission = 'edit_themes';
    }

    Does anyone want to try replacing if ($main_menu_permission == '') with if (empty($main_menu_permission)) ?

    Just tried it, no joy.

    dirkhillbrecht
    Member

    @dirkhillbrecht

    @redwallhp: Already looked at that. Is not the problem as the installation of the module fills the wp_options table with tweetable_main_menu_permission=edit_themes. So that condition is never matched, anyway.

    On Twitter, I got confirmation from other people that this behaviour seems to be general. Perhaps you should make a fresh 2.8.1 install on your own and trace the module’s behaviour in that. I’m pretty sure that it’s a minor glitch and has something to do with the special situation of the module before setup starts.

    Ashutosh
    Member

    @ashubetta

    I’m yet another user with this problem. Waiting for a solution… 🙂

    redwallhp
    Member

    @redwallhp

    Perhaps you should make a fresh 2.8.1 install on your own and trace the module’s behaviour in that. I’m pretty sure that it’s a minor glitch and has something to do with the special situation of the module before setup starts.

    That was going to be my next step. The trouble is, it doesn’t seem to affect everyone. If any of you have any unique features to your server setup or WordPress installation, be sure to mention any that might cause problems. New PHP releases, funky WP plugins, Windows servers, things like that.

    redwallhp
    Member

    @redwallhp

    Just tagged 1.0.9. It should fix the problem.

    http://wordpress.org/extend/plugins/tweetable/

    Apparently WP 2.8.1 added some “security” features… 🙂

    dirkhillbrecht
    Member

    @dirkhillbrecht

    Looks much better now! 🙂 Installation procedure starts now, but I must admit that I’m too tired to perform installation. Has to wait until tomorrow European time…

    Thank you!

    redwallhp
    Member

    @redwallhp

    That’s good. I was afraid something else would blow up now that I made changes. 🙂

    I’ve just updated tweetable to 1.1.0 on WordPress 2.8.1 and can’t change the Twitter account in the tweetable settings page (we want to use a new twitter account).
    If I click on the ‘change’ link I get the message

    You do not have sufficient permissions to access this page.

    redwallhp
    Member

    @redwallhp

    Just tagged version 1.1.1. (Will be available for download within 15 minutes.) It should fix it.

    I had missed a bit of logic that adds-in the installer page when you click the link. WordPress 2.8.1 changed some things, which are great for security, but make for some re-coding headaches. 🙂

    no, just upgraded to 1.1.1 and still the same

Viewing 15 replies - 1 through 15 (of 20 total)
  • The topic ‘[Plugin: Tweetable] Canot access permissions error’ is closed to new replies.