Support » Plugin: User Access Manager » [Plugin: User Access Manager] Parse error: syntax error, unexpected T_DNUMBER, expecting ',&#03

Viewing 7 replies - 1 through 7 (of 7 total)
  • changed line 32; as prompted in the admin section updated the database to UAM; roles have no affiliations, adding affiliation will not save. Noticed after update that 4 tables were dropped; all in relation to UAM

    At this point the plugin still doesn’t work but at least my site is back up; going to attempt a complete uninstall and reinstall of the plugin, will post results once done

    completly wiped the files from the server and then logged into db and dropped the tables that were associated with the UAM

    from wp menu, searched for and installed UAM plugin, edited line 32 of the file that was having the original issue

    protected $uamVersion = 1.9;

    after this one modification the plugin worked as it should; i think if the plugin has the version number changed to a x.x as opposed to an x.x.x then that should resolve the issue.

    FYI, for those who download this now as a new plugin are advised they can’t activate it due to the error, thank you WP Error handling!!!

    WP error handling is rather nice!

    I think maybe version 1.0.3 is back on the horizon and make this one beta

    well it seems to work outside of the x.x.x version number. mind you my needs for this plugin are limited so perhaps there are other issues that i’m not running into

    Plugin Author GM_Alex

    (@gm_alex)

    Fixed in version 1.1.1.1

    Plugin Author GM_Alex

    (@gm_alex)

    BTW Thanks to Samuel for answering the many same threads. 😉

    It would have been enought to put ” ” around the version number on line 32 and 33 so that it looks like

    protected $uamVersion = “1.1.1”;
    protected $uamDbVersion = “1.2”;

    Then everything works fine. Great plugin by the way!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘[Plugin: User Access Manager] Parse error: syntax error, unexpected T_DNUMBER, expecting ',&#03’ is closed to new replies.