Nicolas V.
Supporter
Languages:
English (English )
French (Français )
Timezone:
America/Lima (GMT-05:00)
|
Hi Niels,
A quick update: we deleted some headers but the issue persist. We also found some errors in Console and some issues is translator's pairing languages.
Our team will do test that theme on a new sandbox site to see if the issues are related to the theme itself (compatibility) or if it's something specific to your site. I'll get back to you when I have some feedback.
Thanks for your patience.
Nico
|
evaK-2
|
Hello,
Thanks for the update!
The only thing i can say is that the issues came out of nowhere, everything worked fine for a few months and then the problems came one by one.
I first contacted the support of the theme, but they could not help me.
Kind regards
Niels
|
Nicolas V.
Supporter
Languages:
English (English )
French (Français )
Timezone:
America/Lima (GMT-05:00)
|
Hello,
Just a quick message to let you know that we're still working on your ticket. It has been escalated to compatibility.
|
Nicolas V.
Supporter
Languages:
English (English )
French (Français )
Timezone:
America/Lima (GMT-05:00)
|
Hello,
I have a first feedback:
Their child theme has a complex structure of templates.
The whole search template is not being rendered from DB instead being rendered from theme files and theme files missing the template e.g.
{"slug":"header","theme":"luminate-child"}
but it is
<!-- wp:template-part {"slug":"header"} /-->
That's why it is giving the warning. I will look further into why it is like this and try to replicate it.
As a workaround you can rename the search.html to ___search.html this will bring back the header in all languages.
|
evaK-2
|
Hello,
Thanks for the first feedback!
So all these problems could be caused by the theme?
Kind regards
Niels
|
Nicolas V.
Supporter
Languages:
English (English )
French (Français )
Timezone:
America/Lima (GMT-05:00)
|
Hi Niels,
Yes, by the template structure used in the child theme. We're still investigating this.
|
Nicolas V.
Supporter
Languages:
English (English )
French (Français )
Timezone:
America/Lima (GMT-05:00)
|
Hello,
I think we find the culprit. Here is the answer from my colleague:
1. I set up the themes child and parent on a fresh copy but I can't replicate the issue. So it was confirmed the issue is from client's database.
2. I checked the WP query for the template and found the reason is wp_theme taxonomy was translated. I did not suspect this taxonomy earlier because it was locked. My assumption is:
- They changed the taxonomy setting, and terms are created.
- They reverted the taxonomy to Do Not Translate
- Later our remote config locked that taxonomy.
3. To fix the DB:
- Make a full backup of your database and run the following queries
- Delete the taxonomies records from WPML table for both taxonomies
DELETE FROM `wp_icl_translations` WHERE `element_type` = 'tax_wp_theme';
DELETE FROM `wp_icl_translations` WHERE `element_type` = 'tax_wp_template_part_area';
- Delete these terms from WP tables.
DELETE FROM `wp_terms` WHERE `term_id` IN ("3872","3873","3874","3875","3876","3877");
DELETE FROM wp_term_relationships WHERE term_taxonomy_id IN ("3872","3873","3874","3875","3876","3877");
DELETE FROM wp_term_taxonomy WHERE term_id IN ("3872","3873","3874","3875","3876","3877");
- Correct the slug of Header-w template
UPDATE `wp_posts` SET post_name = 'header' WHERE `ID` IN (7296,30865,30798,30873)
4. Disable WPML Media Translation if you're not using different images per language.
Please let me know if this solves your issue.
Nico
|
