Tim McGuinness

This appears to be a plugin incompatibility issue

The theme only displays what was registered for the post type, right?
The word “Project” is not controlled by the theme, but by your plugin? Why not add an option field in JetPack to allow it to be changed?

@beardedginger thank you

Yes Filter Non-English Characters (Security> Settings> System Tweaks) is a problem because it interferes with search strings and producing the 403 errors

However, we traced it back to BulletProof security that we use as well. We continue to use it, but we had to turn off its strongest feature because it was causing the 503 errors when incoming from external links.

The new troubleshooting plugin is great for helping to resolve complex plugin incompatibilities

We had to abandon this plugin due to the fact that it stopped working and was provided with very poor support. We installed a competing plugin and it worked fine.

Website is working just fine: https://romancescamsnow.com

We do block many countries, what country are you trying to access the website from?

Send an email with you IP address to [email protected] and we will white list you.

Which version are you using?

Facebook is reporting: Graph API v2.3 will be deprecated on July 10, 2017

That is when your plugin stopped displaying Facebook posts.

Thank you for the response by email!

• This reply was modified 7 years, 8 months ago by Tim McGuinness.

am using it on https://www.RomanceScamsNow.com

For any that find this error in Chrome, the solution took months to discover.

It turns out that Kasperski Password Manager it at fault.

When you install and activate the KPM in the browser, and then edit WordPress pages, it installs this string in your pages:

<div style=”width: 0; height: 0; visibility: hidden; opacity: 0; position: absolute;”><object id=”kpm_plugin” type=”application/x-KPMPlugin” width=”300″ height=”150″></object></div>

WTF! Why would Kasperski install what is in effect a viral string in your WP documents? No idea, but there it was.

To resolve this requires the following: 1) uninstall this crap password manager from your Windows computer – you can keep the anti-virus, but get rip of the password manager (use LastPass instead); 2) remove the KPM extension in all of your browsers; 3) make sure that your WP site has JetPack installed and Omnisearch enabled – use it to search fro “KPMPlugin” – then edit each page or post in TEXT mode and remove/delete the code string above for each page or post.

This solves the problem.

Except, if you edited the source of any theme or plugin, you need to check for this addition in those files too!

As a WordPress professional, you need to eradicate the Kasperski Password Manager from every computer you, your team, and your clients use.

This was a monster. Kasp[erski owes me a few years of their service to repay me for this screw up!

If this is Chrome disabling Java altogether, then the WP architecture may be the problem, there is Java throughout.

For now, it is only a one time message. And I tell my clients to refresh.

However, we are also going through every function of our sites looking for what was disabled. This is a horrific task. It could take more than a week per site just to review.

We need an immediate guidance from Automatic and the WP dev community now!!!!

However, new upgrade problem with JetPack. Updating to the latest version is producing these WP errors:

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method NY_OG_Main_Admin::wpog_add_pages() should not be called statically in /homepages/27/d535696580/htdocs/dronenoflyzones/wp-includes/plugin.php on line 496

Notice: Undefined variable: help in /homepages/27/d535696580/htdocs/dronenoflyzones/wp-content/plugins/filebrowser/app/functions.php on line 16

Notice: Undefined index: Submit-DBB-Reset in /homepages/27/d535696580/htdocs/dronenoflyzones/wp-content/plugins/bulletproof-security/admin/includes/admin.php on line 441

seems to have resolved itself. never like problems that solve themselves. which leads me back to, yes we saw a time out error in the logs, but it was a long time. so this looped back around to the repository itself, since it is the same browser and I did not clear the cache on this one for testing purposes – so same exact environment works today and did not earlier.

A mystery

Never had a problem before, so unlikely is server issue, and happening on different hosting companies (GoDaddy and 1and!). Also the timeout is immediate – for example when attempting to redownload WordPress, it doesn’t show even the first status of any successful operation. This is unique to 4.2.2 also, I have previous versions that updated fine.

A very significant mystery that needs to be understood.

I am thinking it is either a brand new hack – and I can find no mention of it, OR it is a problem with WordPress’s update repository not working properly.

That lack of response from WordPress leads me to believe it is the later. They must be heads down trying to fix it.

I am going to wait a week before I try to update anything.

If you try and it freezes, you will have to go into your housing account to delete the “.maintenance” file to return your site to normal.

Problem was solved by deleting the .htaccess file, and rebuilding it using your tool.

Nice try on the interface cleanup, but it is still terrible.

If the majority of your users are turning on everything, just make it one button. That’s what we do on our 1and1 host. We don’t need a million option, so keep them if someone really needs them, but take a lesson from ithemes’ security interface.