Destructor conflict with SQLite Object Cache

  • OllieJones

    (@olliejones)


    3 weeks, 3 days ago

    Hello, I’m the author of SQLite Object Cache. A mutual user has reported this defect to me. https://github.com/OllieJones/sqlite-object-cache/issues/119

    SQLite Object Cache needs to use __destruct() to both keep its SQLite session open as long as possible, and to avoid a session leak.

    And your Loco Translate relies on __destruct() to use set_transient to persist an instance of your Loco_gettext_Metadata class. But php calls my __destruct() before yours. There’s more detail in the github ticket linked above.

    Is it possible for you to persist your data from a shutdown handler rather than relying on the destructor? Thanks.

Viewing 1 replies (of 1 total)
  • Plugin Author Tim W

    (@timwhitlock)

    2 weeks, 6 days ago

    Sorry for the delay. I was on holiday.

    The lazy persistence code you’re referring to was written in 2019. I don’t recall why I architected it this way, but a shutdown handler is something I could look at if I had the time, but I’m afraid I don’t. My priorities for this plugin are essential maintenance at this point. That means tracking breaking changes in WordPress and PHP versions, and avoiding plugin closure by applying security fixes. Unfortunately, ensuring against conflicts with all other tenants of the WordPress APIs is not something I can prioritise unless it’s affecting a lot of users.

    I can see you closed your Github issue. Does this mean it’s a non-issue now?

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.