jpinches

I rebuilt my website to straight HTML so I can no longer try the fix.

Yes the code will not place in the footer. Only in the header. After I closed this thread, the plugin stopped working on my subdomain where I have your plugin also installed. It was working for awhile and then only was logging, now doesn’t log or track any events per Analytics Real Time / Events.

I went back and checked all the settings, reset the plugin and verified the code placement is after the analytics code. I even have tried disabling Google Analytics by Monster Insights and changed the code to .js and still nothing.

At this point, the plugin is working on the primary domain just fine and I’m thinking that Google Analytics shut it off for the subdomain, but that is just a guess. Stumped.

https://photostream.meinmypantyhose.com/ (adult / pg13)

Okay I was able to cut and paste the analytics code above the plugin and all is good. Closing topic.

My apologies, the error was not being caused by the plug-in I found All fixed and working as exected.

Allow me to reiterate what I previously wrote;

“Now on to doing a larger batch for 2nd test. Deleted a bunch of portfolio posts and ran the index(ing) again. This time it didn’t find any orphaned images even though I just deleted and emptied the trash for 70 or so posts that had featured images attached to them.”

That was my experience. Since then I have deleted the plugin and used the native orphaned image search which found the featured images referenced above.

As I previously wrote;

“4-Appended “/photos” to the end of the blog page address at which point the RSS feed was present but with no posts or photos. It was just a blank RSS feed.”

Any other ideas?

One of my 3 sites was having the same error before updating to new version. Webmaster Tools reported error. Update didn’t fix. Tried the following fixes suggested elsewhere by adding to root level htaccess;

AddType application/xml xml

AddType text/xsl xsl

As well as added;

</Files>
<Files “xml-sitemap-xsl.php”>
Allow from all
</Files>

Went back to Webmaster Tools and submitted sitemap for test and now Google reports no errors. Why this had to be added to htaccess all the sudden indicates this was due to changes server side. FYI I use shared hosting with GoDaddy.

If anyone else is having trouble with the pop-up reappearing when returning to the home static page, the only plugin I have found that still works after upgrading to WP 3.6 is Age Verify. However, it uses the text formats that are set for via my theme; so it is not as customizable as CW3. Additionally, it appears to not be SEO friendly as the warning text appears to be appearing now in Google SERP snippets. But at least I have something that works for my configuration.

Hmmm. Wasn’t coming up for me either with all 3 top settings disabled since there is a static page set. I enabled the site-wide option to get the warning to come up and now have the warning reappearing when navigating back to the home page either by menu or browser back button. Sorry for any confusion.

Hi Jerry,

Sorry for the delay in getting back to you. I see that you have updated the plugin to 3.47; so I tried that on my test site and still have the issue of the pop-up appearing when returning to the home page. Although it no longer appears when navigating to another page; as in my case the blog page.

The issue still is after entering the static front page, navigating away and then returning to home page, the Warning reappears. You can see this at;

https://phgtestserver.com/

This is password protected so use the password: content3

The settings I have are;

Sitewide – Disabled

Home Page – Disabled

Misc. Pages – Disabled

Cookie – 1 Day

Enter URL – Blank (removed the default # and still have issue)

Hope this helps you

Emailed on August 5th

Conclusion for anyone else who runs into this problem. The simple fix to stop the errors was to create an absolute URL redirect to the plus.png file.

I used the Redirection Plugin to change the requested path from;

/wp-content/plugins/follow-button-for-jetpack/plus.png

to

https://mydomainname.com/wp-content/plugins/follow-button-for-jetpack/plus.png

Yes the png file does exist. I verified it and no the domain name is not xxxx.xxx. Every visitor with Mozilla generates this 404 on two different sites with the same configuration and different content. When someone hotlinks, they get the nohotlinking.png graphic. I see that happen in Analytics real-time, so I know they are getting that file which is located at the root directory. I think the hint for the problem is the Permalink Finder error reporting that it is a non-Wordpress file. Other than that, there seems to be no explanation for it and I wish I knew what the graphic is even for. I can’t ask the Follow Me Button plugin author because he is long gone and there is no other source or solution for getting this follow me button on my sites that I know of or capable of doing myself!

Well I tried disabling PermalinkFinder and then entered the path to the plus.png in my browser and it finds an orange burst tiny graphic which is never displayed on the Follow Me floating button. I don’t recall ever seeing this graphic before and don’t know what the orange burst graphic is meant for.

The path in the Follow Me plugin php file matches where the png file is installed and accessible which is;

background-image: url(<?php bloginfo(‘url’ ); ?>/wp-content/plugins/follow-button-for-jetpack/plus.png);

I also examined the htaccess file and the only code I see that could possibly be causing this is the rewrite rule to prevent hot linking;

RewriteCond %{REQUEST_URI} !hotlink\.(gif|png) [NC]
RewriteRule .*\.(gif|jpg|png)$ https://xxxxx.xxx/nohotlinking.png [NC]

Still befuddled!

Yes I did read those posts and was able to get the plugin to go green. But the issues persisted as I described.