Often the “flash of unstyled text” (FOUT), where you see one color, then the over-ride is due to a slight time delay between original style sheet loading, and then your over-ride being written in header (if using theme panel CSS over-rides, vs editing the actual theme stylesheet in core files).

Basically elements are loading in order by the browser for speed (‘enqueued’), but what happens is the
> base CSS loads
> theme files load
> theme panel over-rides in header for custom styles

if there is any latency in loading, you may see split second with stock CSS, before the custom over-rides happen.

Not sure that helps, just some info.

Google+ connectivity sometimes times out; sometimes does not show the preview but then shows it when posted. Nothing to do with the theme which simply “sends” the URL to Google+ to capture. FYI, you can always simply “paste in” the URL of the page you’re posting to G+ to post there.

There were some notable issues with G+ a week or so back, where every post I’d do from my website (not using Newspaper theme), would only show a single line break for preview (!), but then on submit it would do “confirmed posted” and show the image and snippet.

But this may not be related to your specific issue.

Be aware Yoast SEO had a big memory leak issue that raised our server processes by 30x on one of the 1.5x versions; and various other issues. We reverted to 1.4x due to that while they get their act together – might not be issue on your site, but see my other thread on that. Jetpack also had a recent update, and some folks had issues with that.

Might not be related — but this stuff is from the past 2 weeks, specifically.

TIP:
1) do updates via FTP if you can
2) we’ve had nothing but problems with the envato “theme updater” – I recommend avoiding it unless you are very savvy in doing full backups of your site via FTP prior to running the plugin (in which case you wouldn’t likely use it anyway)
3) FTP is always best because you can a) make full snapshot backup of your site files, including images, themes, core WP files, config, htaccess, etc. – and also do a dbase backup via WP Admin > tools > Export (all); b) upload files so you know they are properly uploaded

CAVEAT/CAUTION: if your site has ownership permissions where files/folders are “owned” by Apache/server and not the ftpuser, then you may NOT want to use the FTP method for updates. If you are unable to replace your theme folder due to being “owned” by Apache, you can rename the theme folder, then upload fresh copy by FTP which would be “owned” by the ftpuser and not server. You can view “ownership” permissions of your folders by going to your hosting > filemanager > public root > files … “who” owns the folders will be shown in that application.

And YES, you can upgrade from 3xx to 3xxxx without first installing 3xxx.

New to FTP? Good to learn. Filezilla is free and open source way to get started.

• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.

FYI:
it’s against Google policy to “reload” a banner on a page with resize, hence why you can’t do the “drag browser” in to see the ad change. You have to launch a new “visit” at the size you test with to launch a new session cookie and “ad serving” for that “instance.” This is particularly and specifically for image-based ads or fixed-layout text-ads.

The *NEW* text-ads being developed by Google with rolling-slide animations via CSS3/Ajax, etc. may be able to resize with the viewport, but the way Google provides the “responsive adsense code” is to serve different code block PER VIEWPORT or BREAKPOINT.

Anybody really curious about this topic should read Google’s complete AdSense webmaster guidelines/requirements (“LAWS”) since they are really specific about that stuff.

Upshot: things work correctly if you resize your screen from wide to narrow, and the ad stays wide — it’s still the same session/cookie/ad unit. You would have to refresh AFTER you resize to get a new session/cookies/ad unit at the NEW size.

Just my input on this since I had to suffer this last year when we built our own responsive wordpress theme and had to do custom javascript to swap out the 300×200 to 250×250 for vertical ipad so it wouldn’t break the page layout.

Google is working on this stuff … but it’s still a bit newish. They were a bit late to the party on “responsive” stuff.

@scrappy
Posting the same question 3 times doesn’t help anything, btw.

Also, this forum thread is for the “Newspaper” theme not the “Newses” theme.

You’ve posted your query there, you may wish to follow up with tagdiv support by email for that theme.

We had a lot of problems with Envato plugin due to localized file permissions. So, we don’t use it. FTP is still the best way to go.

and more …

1.5.2.5
◾Bugfixes ◾Fixed: Premium support link was being added to all plugins, not just ours 😉
◾Only show the breadcrumbs-blog-remove option if user uses page_for_posts as it’s not applicable otherwise and can cause confusion.
◾Clean up url query vars after use in our settings page to avoid actions being executed twice – props Jrf.

Yes, the version number can be found on the plugins panel (installed/active) in WP admin.

Changelog / March 20

1.5.2.4

◾Bugfixes
◾Changed ‘wpseo_frontend_head_init’ hook to ‘template_redirect’ to prevent incorrect canonical redirect.
◾Improved upgrade routine for breadcrumbs maintax/pt option as reported by benfreke in issue #849 – props Jrf.
◾Fixed a bug where the banners overlapped WordPress notices/errors.
◾Fixed: Slashes in Taxonomy text inputs as reported by chuckreynolds in issue #868 – props Jrf.
◾Increased priority (decreased priority int) on the template_redirect for the sitemap redirect hook.

◾Enhancement
◾Enhanced validation of webmaster verification keys to prevent invalidating incorrect input which does contain a key as reported by TheZoker in issue #864 – props Jrf.

Note –
one option may be to create a custom RSS feed, using a “page” and then publish custom RSS where you strip out any shortcodes for the post meta; then replace all pointers in the head for your custom RSS.

This is somewhat advanced, but if you google how to make a custom RSS feed it’s one way to work “around” any of these types of issues. Or, perhaps hack the RSS template in core WP code to strip shortcodes?

Not a perfect answer. Just a thought. We built a custom RSS feed for specific purpose to create a clean feed without auto-hyperlinks for a syndication thing. Works well. I don’t have the code handy, unfortunately — but upshot is you copy the RSS template to make new page template like ourrss.php and then create new page with that template to have rss be at /yoursite.xyz/ourrss

Might help. Might not. Was just checking in here today since I saw ping on new update 🙂

• This reply was modified 12 years by simchris.

There have been a LARGE number of bugs with the Yoast SEO plugin released last week (1.5), and about three or four patches so far. Still buggy as hell with 1.5.2.3 (including option for Google News keywords not saving to dbase or showing in the SEO post panel). I rolled back my sites to the prior version (stable), 1.4.25 due to a lot of issues including a major memory spike on our server post 1.5 update. If you look at the changelog for 1.5 it’s pretty awful, and doesn’t bode well for their new development team, frankly.

SERIOUSLY …. (!)

— YOAST SEO 1.5 BUG FIXES (SO FAR) —

1.5.2.3

** Note: if you already upgraded to v1.5+, you will need to retrieve your Facebook Apps again and please also check your Google+ URL. We had some bugs with both being escaped too aggressively. Sorry about that. **

◾Bugfixes
◾Added missing settings menu pages to wp admin bar.
◾Replaced old AdWords keyword tool link.
◾Fix wp admin bar keyword density check link
◾Taxonomy sitemap will now also show if empty.
◾Prevent infinite loop triggered by sitemap_close(), fixes #600 as reported and fixed by pbogdan.
◾Fixed a link count Page Analysis bug.
◾Fixed a keyword density problem in the Page Analysis
◾Fixed OpenGraph/GooglePlus/Twitter tags not showing in a select few themes, issue #750 as reported by Jovian and wwdboer – props Jrf.
◾Fixed Facebook Apps not being saved/ “Failed to retrieve your apps from Facebook” as reported by kevinlisota in issue #812 – props Jrf.
◾Fixed duplicate feedback messages on WPSEO -> Social pages as reported by steverep in issue #743 – props Jrf.
◾Flush our force title rewrite buffer earlier in wp_footer so it can be used by other plugins in wp_footer. Props Gabriel Pérez Salazar.
◾Start the force rewrite buffer late (at 999) in template_redirect instead of get_header because of several themes not using get_header, issue #817 as reported by Jrf.
◾Fixed ‘Page %d of %d’ / %%page%% variable not being replaced when on pages, as reported by SGr33n in issue #801 – props Jrf.
◾Restore robots meta box per post to its former glory, it now shows even when blog is not set to public.
◾Fixed individual page robots settings not being respected when using a page as blog as reported by wintersolutions in issue #813 – props Jrf.
◾Fixed: Too aggressive html escaping of the breadcrumbs.
◾Fixed: Last breadcrumb wasn’t always determined correctly resulting in crumbs not being linked when they should have been.
◾Fixed: Breadcrumbs were sometimes missing separators and default texts since v1.5.0.
◾Fixed: 404 date based breadcrumb and title creation could cause corruption of the $post object.
◾Fixed: Filtering posts based on SEO score via the dropdown at the top of a post/page overview page no longer worked. Fixed. As reported by gmuehl in issue #838 – props Jrf.

◾Enhancements
◾Added filters for the change frequencies of different URLs added to the sitemap. Props to haroldkyle for the idea.
◾Added filter wpseo_sitemap_exclude_empty_terms to allow including empty terms in the XML sitemap.
◾Private posts now default to noindex (even though they technically probably couldn’t be indexed anyway).
◾Show a warning message underneath a post’s robots meta settings when site is set to noindex sitewide in WP core.
◾Updated licensing class to show a notice when requests to yoast.com are blocked because of WP_HTTP_BLOCK_EXTERNALS.

◾Other
◾Refactored the breadcrumb class – props Jrf.

1.5.2.2

◾Bugfixes
◾Fix for issue with Soliloquy image slider was not applied to minified js file.
◾Fixed some PHP ‘undefined index’ notices.
◾Fix banner images overlapping text in help tabs.
◾Fixed meta description tag not showing for taxonomy (category/tag/etc) pages as reported in issue #737 and #780 – props Jrf.
◾Prevent a fatal error if wp_remote_get() fails while testing whether the title needs to be force rewritten as reported by homeispv – props Jrf.

◾Enhancements
◾Added composer support – props codekipple and Rarst.

1.5.2.1

◾Bugfixes
◾Fix white screen/blog down issues caused by some (bloody stupid) webhosts actively disabling the filter extension – props Jrf.
◾Fix for some PHP notices, issue #747 as reported by benfreke – props Jrf.
◾Fixed: GooglePlus vanity urls were saved without the + as reported by ronimarin in issue #730 – props Jrf.
◾Fix WP Admin menu items no longer clickable when on WPSEO pages as reported in issue #733 and #738 – props Jrf.
◾Fix strict warning for W3TC, issue 721.
◾Fix RSS text strings on options page being double escaped, issue #731 as reported by namaserajesh – props Jrf.
◾Avoid potential confusion over Facebook OpenGraph front page usage, issue #570 – props Jrf.
◾Potentially fix issue 565 bbpress warning message. Thanks inetbiz for reporting and tobylewis for finding the likely cause.
◾Filter ‘wpseo_pre_analysis_post_content’ output is now only loaded in DOM object if not empty. – props mgmartel.
◾$post_content is now unset after loading in DOM object. – props mgmartel.
◾Fix Alexa ID string validation, as reported by kyasajin and Bubichka in issue 736 – props Jrf.
◾Fix issue with Soliloquy image query, as reported by osalcedo and mattisherwood in issue #733 – props Jrf.

◾Enhancements
◾Twitter metatag key is now filterable by ‘wpseo_twitter_metatag_key’.
◾Added a filter called “wpseo_replacements” in wpseo_replace_vars to allow customization of the replacements before they are applied – props martinernst.
◾Added useful links for page analysis – props bhubbard.

◾i18n Updates
◾Updated nl_NL, id_ID, it_IT, fr_FR and de_DE
◾Added ko
◾Updated .pot file.

1.5.2
◾Bugfix: ◾If mbstring extension isn’t loaded, fatal error was thrown.

Share buttons at bottom of post seem to be working fine on this page
http://indietravel.net/patagonia-series-things-to-do-in-ushuaia-tierra-del-fuego/

+1

OH…did you increase the php memory limit on the site ?
128MB is a good place to start if your host allows that high a limit.

If you have a virtual server or dedicated server try even higher, like 256MB.

I will be retrying W3 cache soon. Not today 🙂

Let me know how it goes for you, and update here!

• This reply was modified 12 years by simchris.

LOL….
and I was hoping you’d be the guinea pig on this one!

Actually WP3Cache messed things up a bit on my v2 install and not using it. Leaning toward using WP Super Cache since it’s made by Automattic (who make WP). On the other hand the horror stories on that include garbage collection deleting entire website not just cache files, etc. Some of the stupid things about W3 include this issue:
http://wordpress.org/support/topic/empty-all-caches-should-delete-page-cache-folder

I’m doing tweaks to v3 now and will revisit cache plugin once there, but haven’t gotten to it yet. I keep wanting to have time to test Varnish on our server, but just no time to deal with another possibly server crippling adventure.

My actual problems with W3 only stemmed from fact that the install was “owned” by Apache and not the ftpuser, and hence it was impossible to delete stuff without using command line via shell. Ugh.

Anyway…. sorry. No help, right? I’ve not yet revisited caching with a plugin.
And so … I shall thus be quiet! 🙂

• This reply was modified 12 years by simchris.

Check to make sure you didn’t paste in a CSS or text element into a widget or elsewhere with garbage characters, or direct from MS Word, etc.

Ideally, open your page in text editor or find the line 233 noted in error and look at what is there which is not clean text (UTF-8).

The simpler way to check errors in your feed is here:
http://validator.w3.org/feed/

this can also SHOW you the error in your text that needs to be fixed 🙂
(it’s what I use when my feed gets borked…)

This seems to work
https://forum.tagdiv.com/w3-total-cache-configuration/

Hi,
you don’t need to duplicate the expires header section. I just changed the method I was using from days to seconds. Doesn’t matter either way. 🙂

Nothing you can do about elements loaded exetnally like add this .css

For the local .css files you need to optimize those by either minifying them manually, and make sure they are enqued properly with the speedbooster plugin.

Good luck! Hope all my ranting helped a bit.
Again, all of this was covered in the pagespeed topic.

There are some great ad management plugins for WP you might look into in the meantime.

I’m not part of the support team. Best bet is to post images online and then link to them in a post.

(oops… you may not NEED to do the addition to wp-config.php — we do it as matter of course as it helps with our system and mod_pagespeed; I may have mentally cross-linked that with hard-coding paths in the header file for the theme to explicitly put in the site URLs vs [theme path] dbase lookups…. upshot, always best to actually specify your URL to website in ALL code vs [get theme path] type stuff … your mileage may vary)

😉 Chris

(I NEED A VACATION!)

Um… what do you mean “what’s the point” — point of WHAT ?

The point of adding the URLs to the wp-config.php file is so that the system doesn’t have to do a dbase QUERY every time the theme tries to figure out what the URL is. That could be dozens of time per page, PER VIEW on your site. You were asking about page speed and optimization, RIGHT?

For the async method — why not try doing search in this forum ?
like, oh …. addthis async method

which would have led you here:
https://forum.tagdiv.com/topic/holiday-tip-making-fancy-social-media-buttons/

Usually it’s a permission problem in not being able to write to the media folder, if I’m reading that right?

I *have* had an issue twice now with the latest version of WP, where I go to upload a file and it tells me “sorry – can’t do that right now” … which never happened up until this latest version of WP. Wait 2 minutes and it works. Almost like WP is busy doing something like checking for an update or something.

If you’re saying you have uploaded photos via the media manager, and they are not “findable” when you go to create a post, that isn’t an issue with the theme – if you can find the images using the default theme. If you’re uploading images via FTP to a media folder – WP can’t find images that way as it’s not in the dbase; you’d have to add the files via URL to the media library.

Not sure if that helped – perhaps more info?

The “title” is pulled from the meta data in the head of your page/post, and not from the button itself. Check to make sure your OG tags are properly formatted. Twitter reads the title, description, section/category, etc. from the meta tags in head of each post.

However looking at one of your pages the meta data seems correct except I think the site should be your site URL and not @jetpack … ?

If it passes the Twitter API check for twitter cards, it should work unless Twitter having hiccups.

<!-- Jetpack Open Graph Tags -->
<meta property="og:type" content="article" />
<meta property="og:title" content="Podcast: The Real Housewives of New York: If You Can Make It Here" />
<meta property="og:url" content="http://tvfishbowl.com/podcast-the-real-housewives-of-new-york-if-you-can-make-it-here/" />
<meta property="og:description" content="Welcome to SHAGGIN' ON THE RED CARPET- TVFishbowl's behind the scenes show that brings you an earnest, sometimes brutal look at the reality shows you love and love to hate. Your hosts Ed B. and Car..." />
<meta property="article:published_time" content="2014-03-12T04:31:39+00:00" />
<meta property="article:modified_time" content="2014-03-12T05:20:45+00:00" />
<meta property="article:author" content="http://tvfishbowl.com/author/fishtales/" />
<meta property="og:site_name" content="TVFishbowl" />
<meta property="og:image" content="http://tvfishbowl.com/wp-content/uploads/2014/03/Sonya-Morgan-Kristen-Taekman.png" />
<meta name="twitter:site" content="@jetpack" />
<meta name="twitter:image:src" content="http://tvfishbowl.com/wp-content/uploads/2014/03/Sonya-Morgan-Kristen-Taekman.png?w=640" />
<meta name="twitter:card" content="summary_large_image" />
<style>body {visibility:hidden;}</style>

and am always first to admit I could be entirely wrong in perhaps not having the correct answer to your situation 😉