Plugin messes wptexturize by running too early

  • Resolved JayFry

    (@jayfry)


    2 months, 2 weeks ago

    Hi!

    I disabled wptexturize feature on my site by adding this code in functions.php:

    add_filter('run_wptexturize', '__return_false');

    Turned out this code isn’t working because of your plugin. I have 50 different plugins on my site and your the only one the messes it. Reason – code in your plugin runs earlier than code in my functions.php.

    function boot() in woo-product-feed-pro/bootstrap/app.php adds action to ‘setup_theme‘ to run:

    • function run()
    • which runs get_plugin_data()
    • which runs _get_plugin_data_markup_translate()
    • which runs wptexturize()

    wptexturize() has static variables and since they set up by first function run I cannot change them later in my functions.php.

    Can you fix this problem? Why your plugin uses ‘setup_theme‘ hook? Is it so necessary? As I said among 50 plugins on my site your the only one with this behavior. Even caching plugins doesn’t do that. Can you this functions later after WordPress reads code in functions.php file?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter JayFry

    (@jayfry)

    Any news on this topic?

    Plugin Support Tanjir Al Mamun

    (@tanjiralmamun)

    Hello @jayfry,

    I checked the issue locally but didn’t find any issue. The disable filter is working properly even the Product Feed Pro plugin is activated. Please refer to the screenshots:

    It seems the issue lies somewhere else. Please let me know if you are on the latest version of the Product Feed Pro (v13.3.7) plugin.

    If you’re on the latest version but still having the issue, then I would suggest you perform a conflict test to identify the root cause of the issue.

    Please follow the steps below to conduct a conflict test:

    1. Deactivate all plugins except for Product Feed Proand WooCommerce.
    2. If the problem persists, proceed to the next step.
    3. Switch to a default theme such as Twenty Twenty or Storefront and activate it.
    4. Additionally, make sure to clear both your site’s cache and your browser’s cache.
    5. Finally, check your texts to see whether the issue still exists.

    Let us know the update.

    Cheers!

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