Viewing 3 replies - 1 through 3 (of 3 total)
  • I get these errors too (on activation and every pageview thereafter).

    I think it’s the same problem described in [resolved] HTTPS update broke my site (not actually “resolved” yet)

    I don’t believe this issue is related to the bug report listed above by Sam_a. I think this is an issue of the plugin being a bit too greedy when it scans the plugins directory for plugins. For example we use subversion to manage our install, and when I tried to activate the plugin I got the following error:

    =====
    /var/www/mysite.com/www/wp-content/plugins/wordpress-https/lib/WordPressHTTPS/Module/Admin/.svn.php): failed to open stream: No such file or directory in /var/www/staging.creativecommons.org/www/wp-content/plugins/wordpress-https/lib/Mvied/Plugin.php on line 372
    =====

    This patch fixed the issue for me, but something else will be required for jabetong. Perhaps the code shouldn’t try to load any plugin whose directory doesn’t begin with /[a-zA-Z0-9]/, to avoid trying to load version control directories or other control dirs:

    https://pastebin.com/ajarUNTX

    Nathan

    Thanks, Nathan.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Plugin: WordPress HTTPS (SSL)] problem loading plugins’ is closed to new replies.