[Resolved] Split: Unexpected 404 error on page reload

Yes, the design is ok. I made a backup restore and follow some of your previous advices (memory limit and elementor content translation) and now seems the design is working well. Related to the 404 error is still there and it is difficult to understand because it works just in portuguese, so it seems the server shouldn't be the problem. I did what you recommend, erase all the duplicate pages not used and even change the slug to the original but continues to give the 404 error when it should goes to the checkout page. I don't know how to make a staging website. I will upload some prints to explain the 404 error in English for example.

I'm not an expert but I feel like is something related to cache or something related to Amelia and woo commerce communication by wpml translations of endpoints maybe?

Because if you try no go directly by url to the checkout page in any language Bokkusu.pt/checkout it opens the page correctly but when you finish the purchase it gives another error agains instead of come back to the finish page of Amelia like it does in the original language, Portuguese.

After contacting the server supplier he replied the problem was with bad configuration of wpml plugin because of the automatic rules written in htaccess file because de rules are changing with the language and it's not supposed. In this way, if we change again a language, because of the rules have changed with the previous language alteration, it will give the 404 error. The rules surfing the website are always over written so changing manually doesn't solve.

Here the answer in Portuguese:

Estimada Cliente,
O servidor apenas se limita a interpretar a regras de .htaccess que são colocadas no servidor sendo que este problema nos parece algum tipo de conflito ou má configuração do plugin WPML.
As regras de .htaccess colocadas no servidor de forma automatica pelo vosso site são as seguintes:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /en/
RewriteRule ^index.php$ - [L]
RewriteRule ^zh-hans/wp-login.php /en/wp-login.php [QSA,L]
RewriteRule ^en/wp-login.php /en/wp-login.php [QSA,L]
RewriteRule ^fr/wp-login.php /en/wp-login.php [QSA,L]
RewriteRule ^de/wp-login.php /en/wp-login.php [QSA,L]
RewriteRule ^pt-pt/wp-login.php /en/wp-login.php [QSA,L]
RewriteRule ^es/wp-login.php /en/wp-login.php [QSA,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /en/index.php [L]
</IfModule>

Verificamos que ao navegar as regras vão sendo alteradas consoante a lingua do site, o que não é suposto e estará a gerar essa situação.

Neste momento acedemos ao fr e a regra mudou para:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /fr/
RewriteRule ^index.php$ - [L]
RewriteRule ^zh-hans/wp-login.php /fr/wp-login.php [QSA,L]
RewriteRule ^en/wp-login.php /fr/wp-login.php [QSA,L]
RewriteRule ^fr/wp-login.php /fr/wp-login.php [QSA,L]
RewriteRule ^de/wp-login.php /fr/wp-login.php [QSA,L]
RewriteRule ^pt-pt/wp-login.php /fr/wp-login.php [QSA,L]
RewriteRule ^es/wp-login.php /fr/wp-login.php [QSA,L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /fr/index.php [L]
</IfModule>

Tal irá provocar que se alguem aceder ao /en ou outro agora terá o erro que reporta.

Estas regras não nos parecem honestamente correctas pelo que sugerimos que contactem o suporte do WPML a reportar esta situação e a pedir suporte. Tentamos modificar as regras eliminando a lingua em RewriteBase /fr/ e RewriteRule . /fr/index.php [L] porém as regras são sobrepostas ao navegar pelo site, o que não seria a partida suposto.

Sem outro assunto de momento,

Apresentamos os nossos cumprimentos.

Francisco Esteves
Coordenador Dep. Suporte On-line
(Support Team Administrator)
Sampling Line - Serviços e Internet, Lda.
PTServidor® - Hosting, Housing e Network
Av. Amália Rodrigues, Nº6 D - 2675-432 Odivelas
Linha Comercial e Administrativa: (+351) 21 409 98 02 (dias úteis das 9h00 às 13h00 e das 14h30 às 18h00, chamada para a rede fixa nacional)
hidden link | hidden link

----------------------------------------------
Ticket ID: #000049
Assunto: Erros 404 pagina não encontrada às vezes com mensagem do servidor
Estado: Fechado
Ticket URL: hidden link

Great. Hope this solve. And yes, I need your assistance to apply. Thank you

However the error persist. And there is one thing in the queue that don't dismiss in spite of saying it should take 1 min.

It didn't worked on the child theme which gave a critical error, but I tried the same code in the parent theme and now I don't get any 404 error in any page so thank you Andreas.

Now I just noticed that the plugin Amelia for reservations is not being translated but tomorrow I will try to check it out if there is some strings missing translations.

Finally, I want to check with you if the two warnings in the status (image above) of woo commerce multilingual are ok or is something missing because when I look at endpoints they seem all translated.