wiredpinecone

Actually I was able to fix it by editing php.ini

allow_url_fopen = On

Somehow it had been set it to off at some earlier point, which caused the error.

We’d recently changed webhosts – this error occurred on Bluehost.

• This reply was modified 7 years, 5 months ago by wiredpinecone.

Via debugging using Query Monitor, I found that the webhost had blocked a call, generating the following error:

simplexml_load_file(): https:// wrapper is disabled in the server configuration by allow_url_fopen=0

which then generated this one:
simplexml_load_file(https://(myurlhere)/stats.rss): failed to open stream: no suitable wrapper could be found

This is while the php widget is nested the pagebuilder plugin by siteorigin.
So far I’ve seen recommendations to use CURL instead if the webhost won’t unblock.

• This reply was modified 7 years, 5 months ago by wiredpinecone.

This patch worked well for me as well. Thank you!

Thank you for the info!

Hi Jeremy, I recently changed the setting on Akismet to save spam in the spam folder rather than silently discard, so perhaps that will allow other attempts to at least show up somewhere. This only happens occasionally and we have good communication with users, so we’ll keep an eye on it and come back if we get additional reports. Thank you!

Now I’m seeing a 405:
405 https://ourdomainame.com/subdomainfolder/xmlrpc.php

Hi Scott, thanks, will look out for that – additional info is that other sites on the same multisite do archive correctly, but the site I’m working on now is REALLY big.

Aha: I just figured out that the number of feed items showing up seems to take its settings from the WP Dashboard General Settings > Reading settings about how many items to display on a blog page at once. When I increased the number from 3 to 4, I got 4 instead.

Is there a way to determine this number independently of the number of items allowed on a blog page?

Hi, I have the same issue – more than 100 feed items, yet the feed URL shows only 3 – despite using dashboard settings which allow for many more.

Thank you!

Hi Shea,

Thanks for your reply – in the meantime, I figured it out: the feature I was trying to disable (site icon) has now become a part of WordPress core and is no longer in Jetpack.

However, the code which should be working to accomplish that is still not working – any ideas would be helpful:

add_action( “customize_register”, “l_c_theme_customize_register” );
function l_c_theme_customize_register( $wp_customize ) {

//=============================================================
// Remove site icon and even title/tagline – which is also configured in Settings – in the “Site Identity” area from theme customizer
//=============================================================
$wp_customize->remove_setting(“site_icon”);
$wp_customize->remove_control(“WP_Customize_Site_Icon_Control”);
$wp_customize->add_section(“title_tagline”)->theme_supports=false;
$wp_customize->remove_control(“title_tagline”);
$wp_customize->add_control(‘WP_Customize_Site_Icon_Control’)->theme_supports=false;
}

Wonderful, it’s good to know that all of these modes can be run simultaneously without any problems!

Hi, a followup question to this one – just to be clear, if it’s network activated on a multisite for code we want applied network-wide, it’s still then possible for the individual sites to ALSO have different snippets unique to those sites in force at the same time? Thank you!

Hi Scott,

Terrific, we’ll look forward to hearing your assessment. (email is js at wiredpinecone.com)

best,
Jenny.

Hi Scott,

I’m jumping in here on this issue; I’ve been doing development work on the same site Jim mentions and investigating this issue. Unfortunately it is not possible to disable SSL on the site and any changes to our .htaccess are pretty quickly overwritten by regex rules. Unfortunately our host is unable to disable https on a site-by-site basis on the multisite.

What would it take to get Simply Static to work around the SSL redirect?
We may be able to support some custom development here.

best,
Jenny