Goose

Have not updated to 4.0 either and have had the same exact issues so I do not think it is 4.0 – I think it is an error at LinkedIn somehow. Have had issues over the past week with this.

Thank you John – it was indeed a DNS propagation issue which is now resolved. Thank you for your responses and for your hard work on a great plug-in.

Thank you John, for the prompt reply. I am using another plug-in (WP RSS Aggregator) and it is creating cron jobs. These are some of the jobs that are just listed as “now” and in their documentation they also suggest the alternate cron method by adding:

define( ‘ALTERNATE_WP_CRON’, true );
define( ‘WP_CRON_LOCK_TIMEOUT’, 1 );

To wp-config. I went head and did this and going back to Crontrol, the DNS alert has gone away. However, all of the jobs are still listed as “Now” and the WP RSS Aggregator plug-in is still not working (I assume this is because the jobs it is spawning are not running). Sorry for my technical ignorance here, but with the changes above employed and the DNS error now absent, would I be going back to my host or to the other plug-in author for follow-up on why things are not working? Again, appreciate your response.

You are welcome and keep up the good work! I’m not sure if Blogroll is history but I did just use a text widget and everything is OK. I think the Blogroll functionality may have migrated to “Links” of which there was a type “Blogroll” maybe leftover from prior versions. So, I’m all set here. Have a great weekend.

Hi Brandon – thanks for the response. I just tried the support link again and I think I goofed on the earlier report. I thought the dialog box was a search for the knowledge base and didn’t see that it also popped up the contact form below – so chalk that up to user (me!) error. Sorry!

On the feature request part, I think the new icons are really cool and will increase sharing. We use a few of the sharing sub-modules (Twitter, LI and Facebook). I see now that the numbers of shares are showing up. I was just wondering if there was a way that that data could be viewed site-wide (e.g., what are the most popular posts/pages in order by way of total shares through any of these sub-modules, separately by sub-module, trends overall by date range, etc.). I guess in a way this data can show you what content is the most viral or popular, trends in sharing figures, etc. This are just ideas but I think a lot of users would find value in knowing more about their social stats.

Thank you again for your response and for your plug-in!

I saw some of this behavior on first install (but not on all pages). I use a caching plug-in – I deleted the cache and then rebuilt it and it seems like the problem was resolved.

Ok I gave it a shot – the first addition (adding ‘wordpress-seo-premium/wp-seo-main.php’,) did not seem to work but the next one did work:

‘wordpress-seo-premium/wp-seo-premium.php’,

So, for the premium plug-in I think that one addition by itself does the trick.

Hope that helps!

Rich – one more thing – the links I provided above are for the premium version – I’m not sure if the file names have changed in the non-premium version – perhaps the OP can provide this information.

Hi Rich – TGIF and for your response. I’m not a techie but think I have an answer:

This is the directory of the plug-in I see when I access via FTP:

/wp-content/plugins/wordpress-seo-premium/

There are folders within that folder, but directly inside I see two PHP files that may be relevant:

/wp-content/plugins/wordpress-seo-premium/wp-seo-main.php
/wp-content/plugins/wordpress-seo-premium/wp-seo-premium.php

I thought I’d give you both as I’m not sure which is the important one (or whether both are!)

Jetpack was generating additional OG tags on my site as of today which was using WP SEO Premium (the premium version of the WP SEO plug-in). I could see both sets of OG tags when viewing source. I installed the following plug-in and it seemed to fix the issue:

https://github.com/sgthemes/Remove-Jetpack-Open-Graph-Tags/blob/master/RemoveOGT/index.php

Hope that helps.

Richard: Thanks. I did go through the trial and error and found the issue. For some reason it was WP-Super Cache. I deactivated all plug-ins and turned them all on one by one. WP Super Cache was the last and when turned on, everything went haywire as described in my original posts. Odd since I do use WP Super Cache on other sites with Jetpack without any issue at all. I’m a little time-pressed right now but when I have time I may try to turn on WP Super-Cache with debug on and see what it generates – maybe there is something in the debug file that would shed some light (although it probably be well over my head). Thanks, Geoff

@akis @wpyogi Thanks. I did delete the plug-in altogether via FTP. I have no problem with Jetpack’s latest version on another blog on WP 3.6. It’s just an issue on a much smaller blog with far fewer plug-ins. Can’t figure out if it is the Genesis/Frederik theme part that is doing this.

Woops, I meant WP 3.6, the latest version. TGIF.

Yes that lead to a live site folder – I did a search on Google for a zip file with that name and found a hit but did not download it yet – when I get to my computer I will try to find the link – it was on some random download site so who knows.

I do not get that error but I do see sitemap.xml coming up as a 404 in my Redirection plug-in log. This is after installing the new version, clearing cache, etc. Clicking the link leads to the correct sitemap.xml page and I do not get any errors. So maybe it is something with WP SuperCache or some other plug-in that is interfering.