fraughtithrouble

JS, I tried what you said, and the error message does not reoccur. So I presume it works. A BIG THANKS! Now if only the support at wordpress.com reads this thread!

I understand that the issue about not being able to modify it is a wordpress.com issue, but my topic is about the theme lacking the SEO compliant header tag. And that is a www.remarpro.com forum topic for the theme.

Wordpress.com I meant to say…typo….

Excuse me for saying “Loginizer” in my previous post, I meant to say “IP Geo block”…that is the plugin I believe is conflicting with WP Globus.

OK, here is the installation info, given by your plugin…

– PHP 5.6.27
– BC Math yes
– mb_strcut yes
– WordPress 4.7
– Multisite no
– Experon Pro 1.6.7
– Akismet 3.2
– Anti-Malware Security and Brute-Force Firewall 4.16.39
– Black Studio TinyMCE Widget 2.3.1
– Block Bad Queries (BBQ) 20161114
– Contact Form 7 4.6
– Contact Form 7 – PayPal Add-on 1.3.4
– Copyrighted Post 1.2.18
– Easy Digital Downloads 2.6.14
– Easy Updates Manager 6.2.9
– Email Address Encoder 1.0.5
– Fast Secure Contact Form 4.0.44
– Gauntlet Security 1.4.1
– IP Geo Block 3.0.1
– Loginizer 1.3.2
– Page Builder by SiteOrigin (ThinkUpThemes compatible) 2.4.8
– PayPal Donation 1.2.2
– Remove Footer Credit 1.0
– Send Email From Admin 1.0
– Subscribe Button by AddToAny .9.10.0
– Theme Check 20160523.1
– Theme Preview 1.4
– Tweet Wheel 1.0.8
– WaspThemes – Yellow Pencil Pro 5.5.0
– Wordfence Security 6.2.8
– WordPress Social Sharing Optimization (WPSSO) 3.37.8-1
– WP Author, Date and Meta Remover 1.0.4
– WP Edit 4.0
– WPGlobus 1.7.1
– WP Spell Check 5.3
– WP Statistics 11.0.2
– WP Subscribe 1.1.3
– 2016-12-14 13:58:42 wp-zep POST:/wp-admin/admin-ajax.php
– 2016-12-13 22:31:18 wp-zep POST:/wp-admin/admin-ajax.php
– 2016-12-14 13:58:42 wp-zep GET:/wp-admin/admin.php?page=WordfenceActivity&ip-geo-block-auth-nonce=…
– 2016-12-13 15:20:06 wp-zep POST:/wp-admin/admin-ajax.php
– 2016-12-13 17:18:14 wp-zep POST:/wp-admin/admin-ajax.php
– 2016-12-13 21:16:56 wp-zep POST:/wp-admin/admin-ajax.php
– 2016-12-14 13:58:42 wp-zep POST:/wp-admin/admin-ajax.php

Thanks, Tokkonopapa, for replying, I really appreciate the attention from the author of the plugin for this issue.

As far as I understand it, since WPGlobus, when you select via the flag on the menu the alternate language, calls a url which does not exist in the format

domainname/2letterlanguagecode/pagename

whereas the real page is at

domainname/pagename

Loginizer reacts to such a url call as if that page did not exist and responds as if it were a 404 call…

So somehow, if Loginizer is to work with WPGlobus it must allow the exception for that plugin calling a virtual but not actual url. Perhaps Loginizer could whitelist the plugins which are installed and active when they do things like this?

The tech finally solved it during the night, by creating an entirely new wp installation and database and re-importing everything a new.

What caused it? Do not know. But it began to happen after the SSL cert was installed on the site, since the wp installation and plugin installation was done before that, which is probably a no no.

You can consider this resolved, then.

I forgot to mention that there are buttons for text and visual but they do not work, and they are buttons and not tabs….its totally bizzare..