• manuroc

    (@manuroc)


    PHP Fatal error: Uncaught Error: __clone method called on non-object in /wp-content/plugins/translatepress-multilingual/includes/class-url-converter.php:428

    I’m getting the above error as soon as I add a 2nd language in TranslatePress. Having just 1 language active and everything works fine. When a 2nd language is added, the whole website crashes on every page with the above error.

    I don’t recall it happening in the past, so could it be due to a recent update?

    Thank you in advance for any advice on this matter.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Anca

    (@ancavictoria)

    Hello,

    Thank you for reporting this to us!

    I have notified the development team, and it will be resolved shortly.

    Could you please let me know if WP_CACHE is set to false and if TRP_DEBUG is set to true?
    If so, until we resolve the issue, you can try to set WP_CACHE to true and TRP_DEBUG to false to prevent the error from appearing.

    I will notify you as soon as the fix is available.

    Kind regards,

    Anca

    Hello, also encountered this error. Disabling the “SQLite Object Cache” plugin seems to resolve the issue in our case, consider disabling your object cache temporarily as a possible workaround.

    WP_CACHE and TRP_DEBUG are not present in wp-config, PHP 8.2

    I can confirm the issue comes from a conflict with the plugin:

    SQLite Object Cache – WordPress plugin | www.remarpro.com

    Disabling the plugin and removing the file .ht.object-cache.sqlite from wp-content folder fixes the issue. This occurs with the latest version of both plugins 1.5.1 for sqlite and 2.9.5 for translatepress.

    I am not sure which plugin introduced the functionality breaking change.

    Thread Starter manuroc

    (@manuroc)

    Thanks for catching this! I would have never guessed it was coming from that plugin….

    There’s a test build of SQLite Object Cache available at https://github.com/OllieJones/sqlite-object-cache/issues/71 that appears to have resolved the issue, if you’d like to test it before the update hits the plugin directory. Otherwise, it should be safe to re-enable the plugin once version 1.5.3 is available.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.