issues after installed the ssl dv cert

Dear Sirs,
sorry to bother you but I must insist.
Polylang is a great plugin but I found this issue.

When changed from http to https the plugin started to create problems and the website became not stable: 404 not found, 500 and other errors.
Website and wp-admin does not work in that case.

Only deactivating all plugins via FTP I have access to wp-admin, and once entered I deactivate Polylang: all starts to work well again > if I go to Settings/Reading and re-confirm Homepage, Polylang restart to work.

BUT IT IS NOT STABLE!
If I clean the temporary files with CCleaner (f.e.) all the issue starts again.
I have the maintenance mode plugin: also in this case when activating or deactivating it Polylang needs to be “refreshed” (deactivate/reconfirm homepage in settings/ reactivate Polylang) …

Please!
Why nobody is replying to this topic?

• This reply was modified 5 years, 4 months ago by Mauro Vicariotto.

I couldn’t resolve the issue until I have deactivated the polylang plugin as ssl and other things was all working fine

and lack of documentation is missing on how to resolve this problem

Thank you for your reply @admyly.
You mean deactivated the ssl dv from whole site?
I will try with author, because obviously this plugin involves the WHOLE work of three months: they write “only paid version have support”, but in my opinion this is not totally correct.

People builds sites for business, and months of job wasted because only at the end you discover that the plugin has problems with ssl certificate … free or pay involves the time and money of users.

This is my opinion.
F.E. my company: needed a site since April: now it’s July and cannot publish???
While the author says “no support”?
The author MUST write of this issue before making people work for nothing!
Otherwise free or not it is unfair.

Or I will buy the pro version, but just to have the satisfaction to make them solve the issue and the problems.

First of all Polylang is a free plugin. The author has devleoped it and provides it free of charge to use. It is your responsibility if you use it.
It is your responsibility to use a staging site before publishing it to a live site. A good web devloper tries first a new plugin and settings before adding it to a live site.
So, don’t blame others for problems which are made by yourself.

Back to your “problem”: I use Polylang and Polylang Pro on 50+ websites, all with SSL, and not one page has any issue like you describe. So, in my opinion, the problem is especialy on your site, maybe in combination on toher plugins. I can only recommand to deactivate all plugins and switch to the twentyninteen theme and to check if you sill have an issue. If not, you have to activate theme and plugins one by one.

You are not right Coder, sorry.
It is normal to create an site offline: I made it with xampp.
But in any case you discover the problem at the end of the work, since the plugin involves all the net of permalinks inside, it is normal that you discover only after finished … and in my case after published, because the provider applied the ssl dv cert later.

Offline or online doesn’t change: it is in any case all build in months of work.
And since this problem is common,
not only “mine” (just check and see how many posts), the author should write an alert, so people are responsible of their choice, knowing the risk at the beginning.

Regarding Polylang I already found and solved some other conflict with other plugins (like f.e. wp-sweep) during the test offline: I had to add more than one mu-plugin to overcome … this is normal becaue multilanguage involves all the site.
This is not “blaming”.

The test you mention I have already done: but veeery long to understand now, because the issues come randomly and you can’t say when, could be a couple of days or more.
To check a list of plugins in this way you could take weeks.
Have you any idea?
I guess that could be maintenance mode in conflict with polylang … exlude google analytics and some other … is it possible?

• This reply was modified 5 years, 4 months ago by Mauro Vicariotto.
• This reply was modified 5 years, 4 months ago by Mauro Vicariotto.

Checking, and at this moment I guess it is WP Maintenance Mode in conflict with Polylang.
Rest are apparently irrelevant:

– Theme Twentyseventeen (do not change, because I have a Twentyseventeen Child Theme), and Classic Editor applied
– amr shortcode any widget (just for widgets), Easy Custom Sidebars and
Insert Headers and Footers
– Contact Form 7 (working well with Polylang)
– Disable Comments on Post Categories and Don’t Muck My Markup
– GDPR Cookie Consent, seems nonsense to be worried of that
– WP Cerber Security, Antispam & Malware Scan (as above)
– WP sweep, for which already added a mu-plugin vs Polylang

practically that’s all: so? I guess it is WP Maintenance Mode: when active deactivates the starting page and (might be) Polylang looses “the track”.
Might be?

any idea?
I already said that Polylang is a great plugin and normal that since it involves the whole site it is easy to find some conflict.
What I say is that:
1) Polylang was installed with http and started to create problems when added ssl: this could mean that some internal address could create problems, and Polylang is based on internal addresses between pages and scripts
2) WP_Maintenance Mode adds a page re-routing the main homepage address: of course WP Maintenance Mode is only in one language (EN): possible that this creates problems once activated?
3) I see that .htaccess seems wrong, even if created by WP itself: but once I add
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

These three are my questions.
If someone can give me his idea, thank you.

FYI:
the conflict was between WP Cerber Security and Polylang: 99.99% sure.
I will try to fix also this with a mu-plugin or change antispam.
The previous bug was between WP Sweep and Polylang, fixed with a mu-plugin “ad hoc”.

This is the second bug which I fix for Polylang:
it’d be prove of courtesy from Polylang Authors to write a short reply,
or people has the idea (me too) that authors consider users of free version like a sort of “testers”.

Regards.