Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • wierdthingsayer

    (@wierdthingsayer)

    Hello, Jeffrey,

    I, too, encountered the same warning (Warning: unserialize() expects parameter 1 to be string, array given in /home/content/p3pnexwpnas12_data03/05/3640305/html/wp-content/plugins/widget-options/core/functions.option.tabs.php on line 30) after installing Widget Options on a site running WP 4.6.1, theme GeneratePress, with an assortment of other plugins (list on request). The warning did NOT appear while I was configuring and testing the site while logged in (in Firefox) as an administrator, but DID appear when I viewed the site without logging in, using Safari and Chrome. Logging out of Firefox caused the warning to appear there, too.

    I’ve replaced the functions.widget.display.php file on the site with the development version in your reply, and the error no longer displays on the home page, however unfortunately show/hide doesn’t appear to work (all three widgets in the right sidebar on the home page appear although the Search and Archive widgets are supposed to be hidden), and the warning for unserialized() appears on the Blog page.

    I’m not seeing the same issues on a test site which also uses WP 4.6.1 and GeneratePress, and the same set of plug-ins but a lot less content.

    Thread Starter wierdthingsayer

    (@wierdthingsayer)

    Similarly, I see the default sans-serif font for the site, not the chosen Typekit font, for the text on the WordPress pages that match the selector(s) I entered for the Typekit font.

    Thread Starter wierdthingsayer

    (@wierdthingsayer)

    On the Fonts page of FM control panel, when one adds a font from the lists of available fonts, a preview sample of the selected font appears in the top box, with the font name, against a gray gradient background. The word “PREVIEW” to appears to the right of the samples of all chosen fonts. For Font Squirrel and Google fonts, I see the pangram sample text in the selected font. For Typekit fonts, I see a default sans-serif font, not the sample selected font.

    Thread Starter wierdthingsayer

    (@wierdthingsayer)

    What I have done to resolve my problem at this point is to edit the various “feed-xxx.php” files in /wp-includes/ to remove the call to wp_title_rss() in the “<title>” tag of the feed description. I had thought that didn’t work but had only removed it from the atom, ref, and rss template files; I had overlooked feed-rss2.php. Once I removed wp_title_rss() from the title tag, the doubled feed name disappeared from my reader.

    So my problem is for the time being solved, but what remains unanswered is why the feed templates call both bloginfo_rss(‘name’) and wp_title_rss(). Best answer I’ve been able to find is that wp_title_rss() is supposed to insert the title of the blog post, but that isn’t what it’s doing. Instead it’s inserting the blog name.

    If anyone who understands what was intended in the basic feed template files happens along to read this thread and can explain I’d be grateful. I hate using a hack when I don’t understand why it’s necessary.

    Thread Starter wierdthingsayer

    (@wierdthingsayer)

    Thanks for sharing what you found, I had received no other replies to my original post back in January. What’s odd is that on my site I have no plugins except the default Akismet and Hello Dolly, and both are disabled. I am, however, using the Weaver II theme with a lot of visual customizations.

    I’ll keep looking for my version of the problem.

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