• Resolved Summer

    (@fpmsummer)


    Hello!

    I do not have Extension Manager installed, since I don’t see any of the extensions as items I need. But now I’m noticing an error msg popping up now and then:

    opendir(/wp-content/plugins/the-seo-framework-extension-manager): failed to open dir: No such file or directory

    Is there a new requirement that I must have Extension Manager installed in order to keep using SEO Framework? Couldn’t I just choose to disable any checks for Extension Manager if I don’t have any extensions installed?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi @fpmsummer! TSFEM is not required to run TSF. Can I ask, where the error message pops up for you? I have couple of sites that have only TSF installed, and I never saw the error message in frontend/backend.

    Thread Starter Summer

    (@fpmsummer)

    I’m seeing it in reports generated by Query Monitor (I’m currently troubleshooting one site for a different problem).

    Over the past week, I’ve seen it pop up in there under “PHP Errors” now and again, so it’s not a fluke activation related thing.

    I don’t see it in every back end admin action, but it is a repeating event.

    Plugin Author Sybre Waaijer

    (@cybr)

    Hi there ??

    Do you get this error on the plugins overview page in your admin dashboard?
    And, is the server you’re getting these errors on Windows-based?

    The only call TSF makes is silenced by WordPress– which means it should never output an error. So, I’m a bit confused about this behavior.

    TSF only looks for the plugin’s existence to remove the (easily missed) link to the plugin’s page (because you’d already have it installed), it’s completely independent of it otherwise.

    • This reply was modified 6 years, 5 months ago by Sybre Waaijer. Reason: explaining what it does
    Thread Starter Summer

    (@fpmsummer)

    I poked around a little bit more, and it happens whenever I activate or deactivate a plugin, any plugin.

    It displays as a PHP Error in the reports produced by the Query Monitor plugin.

    Plugin Author Sybre Waaijer

    (@cybr)

    Thanks for all the info!

    I have poked around in this issue, and I did find a way to prevent this from happening:
    https://github.com/sybrew/the-seo-framework/issues/374

    This enhancement will be shipped in a future version.

    For now, you can safely ignore this error.

    Showing this error is not intended or even expected behavior in PHP. The PHP configuration might be a little too sensitive on this. There’s probably a feature enabled which helps developers find issues:
    https://php.net/manual/en/errorfunc.configuration.php#ini.track-errors

    When such issues occur, we can choose to silence them. This is exactly what WordPress does, and it’s what I chose to utilized as a feature in the code.

    For more in-depth dev information, see:
    https://php.net/manual/en/language.operators.errorcontrol.php

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘PHP Error re: Extension Manager’ is closed to new replies.