• Resolved ginmi

    (@ginmi)


    WordPress refuses to activate the plugin because it triggers a FATAL ERROR:

    Fatal error: Cannot redeclare GuzzleHttp\uri_template() (previously declared in /public_html/xxx/wp-content/plugins/comet-cache-pro/src/vendor/guzzlehttp/guzzle/src/functions.php:17) in /public_html/xxx/wp-content/plugins/amazon-polly/vendor/aws/GuzzleHttp/functions.php on line 31

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor tstachlewski

    (@tstachlewski)

    Hi @ginmi
    Could you test it again, with the latest plugin version? (1.0.5)? We were working on fixing this problem, so now it should be OK.

    Cheers,

    Thread Starter ginmi

    (@ginmi)

    Tried activating on a test site and the plugin generated an error 500 as soon as it’s activated.

    Clearly the plugin is not yet ready for a production site.

    Plugin Contributor tstachlewski

    (@tstachlewski)

    Hi @ginmi,
    A lot o people already use the plugin. The error message 500 is quite generic, and can be caused by many reasons, depending on your environment configuration. Could you please share with us a bit more details?

    Cheers,

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Conflicts with my caching plugin’ is closed to new replies.