Support » Plugin: Connections Business Directory » [Plugin: Connections] Plugin could not be activated because it triggered a fatal error.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author shazahm1

    (@shazahm1hotmailcom)

    Can you please provide the exact steps you followed when installing Connections and what the error message was?

    I uploaded the plugin, clicked activate and got this exact error after about 2-3 minutes:

    “Plugin could not be activated because it triggered a fatal error.”

    I ran the top command on my linux server and when I try to activate the plugin the CPU is sitting at 99%,

    I checked the database and it looks like a whole load of tables have been created, so something is happening but the install never completes.

    [Wed Dec 28 01:37:32 2011] [error] [client 127.0.0.1] PHP Warning: readdir() expects parameter 1 to be resource, boolean given in /var/www/web/web.com/wp-content/plugins/connections/includes/class.template.php on line 113, referer: https://web.com/wp-admin/plugins.php

    I just checked my Apache logs, as soon as I click activate plugin the logs are flooded continuously with this error message.

    Plugin Author shazahm1

    (@shazahm1hotmailcom)

    Thanks very much for the debug info. This helped me identify the exact issue. There is a scenario where FALSE will be passed to readdir(). I’ll fix this and issue an update. Curious though, that this causes a CPU spike, that must be a PHP deficiency.

    After some more testing it seems the CPU issue is a generic Amazon EC2 “feature” called CPU steal, it happens when a process is consuming more than the allocated CPU cycles.

    Anyway, happy to help and I look forward to the update and will test it once again once available.

    Plugin Author shazahm1

    (@shazahm1hotmailcom)

    Could you give this version a run to see if it addresses this issue?

    http://downloads.wordpress.org/plugin/connections.zip

    Either way, I’ll be releasing it in the next day or so because it addresses a few other small bugs.

    Note to future forum readers, this link is to the dev version of the plugin, at any given point, it may be critically broken. Please do not install unless requested.

    Activated successfully, no errors reported.

    Thats great thank you Steven, Ill be testing it further over the next few hours and will let you know if any problems.

    Thanks again for resolving this quickly, looking forward to implementing it.

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