• Resolved cmendlacct

    (@cmendlacct)


    I tried to install this plugin and got the following error.

    Plugin could not be activated because it triggered a fatal error.
    Parse error: syntax error, unexpected end of file in C:\inetpub\wwwroot\myweb\wp-content\plugins\memphis-documents-library\mdocs-rights.php on line 128

    memphis Documents was Version 3.0.2
    This is running on an intranet on IIS.

    Everything else on the site seems to be working OK.

    I’d appreciate any thoughts

    https://www.ads-software.com/plugins/memphis-documents-library/

Viewing 6 replies - 1 through 6 (of 6 total)
  • I’m having the same issue after upgrading from 2.6 to 3.0.2 it completely killed my WordPress 4.2 installation (error 500). After disabling all the plugins and upgrading WP to 4.3 I started upgrading and activating all the plugins and once I go to Memphis Documents Library I get the same error as above. I’m running on Bitnami stack with Apache so it is not only related to IIS but also Apache.

    Any ideas anyone?

    I solved it.

    To fix this go to the \plugins\memphis-documents-library\mdocs-rights.php file and open it in editor. On line 125 you will see this:
    <?
    replace the above with this:
    <?php

    Save the file and try to activate the plugin again. It worked for me.

    Thread Starter cmendlacct

    (@cmendlacct)

    Wikig – THANKS –

    that worked perfectly.

    chris

    Plugin Author bhaldie

    (@bhaldie)

    sorry for the late reply I’ve been hard are work on other issues. I’ve made the fix that was recommended and will be added to the next update.

    Thanks for the hard work ??

    I get same error. If I uninstall and redownload I assume new version has this fixed. But will my old doc library still be there and connected after reinstall?

    Plugin Author bhaldie

    (@bhaldie)

    You shouldn’t need to uninstall, an updated should fixe the issue work.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Plugin could not be activated because it triggered a fatal error.’ is closed to new replies.