ciordia9

Thanks Milap, I had no idea that the country specification was considered security. That was it. I appreciate you!

You will still need a fix, unfortunately mine no longer can find a universal hook. When making this it was rather easy to pick up on the author block and the alt tag associated with it. Comparing a few current themes and this has gone wide open. There is no standard for just the authors gravatar so my fix now fixes any gravatar on the page to be the author which is not a good way to fix this.

I find it crazy some 3 years after I threw this together the alt tag of a gravatar does not reflect the owners information.

Yea that’s crazy. Before I went forum diving I had to remove the plugin, it was causing an error 500. Reinstalled it and the error is still prevalent. Client is running a campaign now so I can’t just take this down to the rails–I’ll have to circle back once we hit a lull and then remove the noise and see if there is a conflict. Currently grepping the system though and I can’t find mention of the Yoast_GA anywhere and line 73 of that file erroring out makes no sense, hell its a blank space. Color me curious.

Letting you know we have the same issue after upgrade:

[Mon Feb 20 16:46:14.247980 2017] [:error] [pid 30921] [client 108.162.237.207:29914] PHP Fatal error: Uncaught Error: Class ‘Yoast_GA_Admin’ not found in /srv/www/tamelarich.com/public_html/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php:73\nStack trace:\n#0 /srv/www/tamelarich.com/public_html/wp-admin/includes/plugin.php(1882): include()\n#1 /srv/www/tamelarich.com/public_html/wp-admin/plugins.php(164): plugin_sandbox_scrape(‘google-analytic…’)\n#2 {main}\n thrown in /srv/www/tamelarich.com/public_html/wp-content/plugins/google-analytics-for-wordpress/googleanalytics.php on line 73, referer: https://tamelarich.com/wp-admin/plugins.php?plugin=google-analytics-for-wordpress%2Fgoogleanalytics.php

We used to run ManageWP years ago but haven’t in quite some time and the plugin is not present on the system any longer.

• This reply was modified 7 years, 9 months ago by ciordia9.

edit: Reworking kinks, maybe on my end..

• This reply was modified 7 years, 11 months ago by ciordia9.

This has made me realize I’m running the legacy code from the prior iteration 3.3.6.1 — you know things run great until they don’t, then you figure out where you are.

Do you think I can run the Legacy Converter, delete the old DM, and install the new one, and be good-to-go? Based on iconography between the github transition it matches.

Mine was a plugin conflict and I just happened to be running the same plugin on both sites. I just hadn’t ever received a Err 500 from any plugin issues in the past so I didn’t weigh it like I would most troubleshooting.

Rule that issue out first. If not from the response above you can obviously reach out to them for greater resources. ??

After testing PageFrog and seeing it handles things at the end of the chain via RSS VC is not an issue.

I’m sorry David, I had too many browsers open. I am also testing out PageFrog where I asked how they process VC codes, then realized after working in it that they don’t need to bother as they take the RSS feed and modify it as needed. So I thought I was closing that ticket, when in fact I closed up my original ticket by mistake. I wouldn’t have caught it unless you wrote back.

I’ve reopened this ticket and apologize for misleading anyone thinking it was resolved.

Never mind. This is taking a modified RSS approach instead of an internal content usage. Everything is rendered therefore VC compatible.

Chiming in as I just hit this. No solution? The ‘Disable Featured Image’ button doesn’t seem to tether to this.

Thank you for having this as a solution. I had the same error, peeked into the wp_config site_url database entry and had garbage. Like an error message had lodged itself into the field. Replaced that with what should be there and the site came back up.

Saved me a lot of further headache.

The real question I have now is how it happened…

songdogtech: Thanks, I’ll do that straight away. A hidden plugin sounds lovely. ??

I’ll also queue up isolated user groups (/moan/) hehe. I know all of this will help. At the very least it’ll give me a great indicator of who is being a bad install.

songdogtech: I’m running off Linode and I’ve got a pretty hardened box. I was a systems engineer for about a decade and thought I had everything in good order. Hardened ssh, no open ports beyond those services (imap/mail/web/ssh) that are needed. Fail2ban and its kin, clamav and its kin, etc.

Having this happen twice has made my head spin around.

The only thing I haven’t done is start running each apache directory with its own user/group–it’s the only thing I feel left to really isolate everyone. I think each of my recent breaches were coming through some outdated plugin. However in my last life I didn’t need that much web isolation so I haven’t crossed the bridge and I thought doing a little fishing expedition here for some other thoughts might be beneficial before I commit to the path.

Just tried–checkboxes uncheck after saving. No multisite here.