4.5 crashed WPML site same as 4.4.1

Missed one essential info before hitting post…

Main language is English on a .COM ccTLD
local languages on .NL, .FI, .SE

After WP upgrade to 4.5 all ccTLD redirects to .COM instead to local homepage (aka .NL to acme.nl/index.php)

but if you add /contact to lets say acme.nl/contact then the correct page is presented. And as soon as it is just the startpage then it redirects to the .com startpage.

Since that is a commercial plugin, we ask that you please go to their official support channel, so you can get support from the people who know it best.

https://wpml.org/forums/forum/english-support/

Forum volunteers are also not given access to commercial products, so they would not know why it is not working properly. Other community members who may have faced your issue might be able to help you but your best bet is your product’s developer. Keep in mind we encourage you to use the official support venues, as it allows the developers to be aware of issues with their code and gives back to the community in a more robust way.

Dear Jan

That’s the exact same answer I received last time and I proved you wrong then so PLEASE understand that this is a WP CORE RELATED ISSUE and that wont be taken care of by ANY commercial plugins.

So once again please (!) make a 4.5.1 update that resolves the issue (exactly the same issue that was introduced in WP 4.4.1 core and that WP 4.4.2 resolved)

How do you know it is a WordPress core issue? Are you the developer of the WPML plugin?

Try reviewing this thread in WPML forum : https://wpml.org/forums/topic/bug-wpml-translation-management-when-i-updated-to-wordpress-4-5/#post-865098

@esmi
To be clear about your remark – no I’m NOT the developer of the WPML plugin/s neither am I in any way associated with them. I’m the webmaster of our companies web site and I thought (obviously my mistake) that this forum was about to solve WP Core problems and not blaming the customer or take the easy way of pointing to a plugin or theme developer to solve WP Core problems.

And for the record – How do you know that I’m wrong in blaming WP Core?
Do you know exactly all the tests we been carrying out before creating this thread?

We have had the exact same issue with the exact same behaviour with 4.4.1 and that was only resolved when the 4.4.2 update was installed. Had nothing to do with theme or any of our plugins – plain WP Core to blame for that.

So is it logical to assume that when the exact same issue and strange (to say the least) issue occurs again to assume it it is the same WP Core bug that is back again?

Ask James Huff – he will know the story back then and I’m sorry that I cant point you to that discussion in the forum since he deleted the whole thread when proven he was wrong blaming WPML and not trusting me that it was a WP core problem introduced with 4..4.1

So back to the problem – Are you capable of assisting in this problem? If so then your’e extreamly welcome to contribute to solving it.

BR /Nick

@tara
Thanks for the assistance in seeking a solution.
Unfortunately it seems that none of that is related to our problen nor did it solve the problem.

Side note:

We have had the exact same issue with the exact same behaviour with 4.4.1 and that was only resolved when the 4.4.2 update was installed. Had nothing to do with theme or any of our plugins – plain WP Core to blame for that.

Nope, that’s completely wrong. You’re making the case for developing WordPress to be compatible with plugins. Plugins need to be compatible with WordPress, not vice versa.

Here’s the thing: WordPress 4.5 was in development for months and it’s upon the plugin developers to test their plugins. Sometimes a .1 release does happen and 4.5.1 is being tested right now. But don’t expect that to solve your commercial plugin problem.

You’re asking for support of a plugin that we do not have access to the code. Nor do we want access. This isn’t necessarily a WordPress problem.

This is what I usually paste when someone has a commercial product problem.

For pro or commercial product support please contact the author directly on their site.

https://wpml.org/forums/forum/english-support/

As the author is aware, commercial products are not supported in these forums. As you are their customer I am sure they will have no problem supporting you there.

If you have information that you’d like to share to help others, then please do so. But just saying “WordPress 4.5 is broken. Fix it” will not solve anything for anyone.

@jandembowski

Magic! So you are 100% sure that I’m dead wrong and you’re correct when you say that this is not a WP Core bug?

Curious about what facts you base that on…
I base my oppinion on the fact that we have had the same exact issue before on 4.4.1 and it was solved by 4.4.2 and NO Other plugins or other updates where made prior to 4.4.2 update and after that the problem disappeared.

If – and I say IF – the commercial plugin had been updated during the time we run 4.4.1 and before 4.4.2 was released and installed, well then I would have considered the plugin to be the problem.

Since 4.4.2 was the only change made and immediately solved the problem, then you tell me what conclusion you you’re self would make….Of course its a plugin problem….

What you really are saying is that we are on our own and “As long as you add anything to Word Press then any errors are to be blamed to the add-on” – and blame me for “asking for support of a plugin that we do not have access to the code.”

I don’t! I asked for help with a WP problem – not the plugin. I’ve done all the tests you can imagine to rule out the possibility of being a plugin-problem, even with the plugin support. Everything and everyone is pointing to WP Core…except you of course.

But I do understand that you’re not interested of helping out and that I’m/we’re to solve this by our self and that is a great way to treat customers.

You’re misunderstanding the situation. WPML is a paid commercial plugin, it costs money to acquire.

WordPress is provided for free, and it’s developed and supported by volunteers.

As has always been the case, it’s up to the plugin and theme developers to ensure that their products work with the current version of WordPress, especially when they’re charging a fee for that product.

You can’t honestly expect all of the volunteers developing and supporting WordPress to purchase their own copy of WPML (and every single other commercial plugin/theme) just to make sure it still works. That’s simply unreasonable, which is why it has always been considered the responsibility of the plugin/theme developer to ensure compatibility.

This may very well be a WordPress Core bug, no one here has said otherwise. However, the correct path is to report the issue to the developers of WPML: https://wpml.org/forums/forum/english-support/

They have access to their own product, they know how it operates, and they can therefore determine if it’s a bug with their product or a bug with WordPress Core. If they determine that it’s a WordPress Core bug, they will certainly file a proper bug report with all of the information that our developers need to fix it.