• Resolved declanmair

    (@declanmair)


    I have website which use MyThemeShops OnePage theme. updating to the new version of SG it breaks the site and the only way to fix is a server restore.

    This is the issue I get:

    Warning: require_once(): https:// wrapper is disabled in the server configuration by allow_url_include=0 in /XXX/wp-content/themes/mts_onepage/options/options.php on line 9

    Warning: require_once(https://brownshire.co.uk/wp-content/plugins/sg-cachepress/google-typography/google-typography.php): failed to open stream: no suitable wrapper could be found in /XXX/wp-content/themes/mts_onepage/options/options.php on line 9

    Fatal error: require_once(): Failed opening required ‘XXX/wp-content/plugins/sg-cachepress/google-typography/google-typography.php’ (include_path=’.:/usr/local/php70/pear’) in /XXX/wp-content/themes/mts_onepage/options/options.php on line 9

    I spoke to the theme developers who suspect it’s a SG issue. HAving said that all others themes I have on other sites work ok with the latest update.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Hristo Pandjarov

    (@hristo-sg)

    SiteGround Representative

    This is not a plugin problem but issue with the OnePage theme. In their option/options.php file they do:

    global $url;
    require_once($url.’google-typography/google-typography.php’);

    and $url; points to our plugin. When we disable it its var_dump is empty and the plugin is loading just fine. It seems like some sort of a leftover in their code because it doesn’t make any sense whatsoever.

    We use $url as a local variable which is not accessible outside the plugin.

    Please, contact the theme developers and provide them with this information. It is the only themes from MyThemeShop that have such issues!

    Plugin Author Stanimir Stoyanov

    (@sstoqnov)

    SiteGround Representative

    We’ve added a patch in 5.0.10 which fixed the problem, but the real issue is with their themes and the way how they are including some files.

    We still recommend you to contact them about the issue, because other plugins may face the same problem.

    If you already have 5.0.10, you should deactivate, delete and then install the plugin.

    Regards,
    Stanimir Stoyanov

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Broken websites after update!’ is closed to new replies.