[Risolto] Errore critico con campi personalizzati Pods
Questo è il forum di assistenza tecnica di WPML, il plug-in multilingue di WordPress.
La sua lettura è permessa a tutti, ma la pubblicazione è riservata esclusivamente ai clienti di WPML. Il team di WPML risponde sul forum 6 giorni su 7, 22 ore su 24.
Salve, su questo sito abbiamo dei Custom Post Type "Prodotti", creati con Pods, con all'interno dei campi personalizzati, sempre creati con Pods. Usiamo Elementor Pro per impaginare il sito.
Prima di creare i campi personalizzati, i template Elementor con i CPT Prodotti si traducevano senza problemi con WPML
Quando abbiamo aggiunto i campi personalizzati e li abbiamo tradotti, le pagine dei Prodotti rispondevano con un errore critico, aggiungo qui sotto le informazioni di debug dell'errore.
Questo il link originale: link nascosto
Questa la traduzione con errore: link nascosto
Avete qualche consiglio da darci per risolvere il problema?
Grazie in anticipo.
Deprecated: Creation of dynamic property Yoast\WP\SEO\Premium\Generated\Cached_Container::$normalizedIds is deprecated in /www/deltan_444/public/wp-content/plugins/wordpress-seo-premium/src/generated/container.php on line 27
Warning: Undefined array key "reazione_al_fuoco" in /www/deltan_444/public/wp-content/plugins/elementor-pro/modules/dynamic-tags/pods/tags/pods-base.php on line 35
I speak only English if you prefer to continue in Italian only please let me know I will ask my teammates who speaks Italian.
I can see that the error is not coming directly from the WPML plugin itself, but it happens only when viewing the translation. Because of this, we will need to investigate it more closely.
It looks like some fields are either not translated correctly, not copied to the translation, or the data is getting lost during the translation process.
To check this properly, I need to request temporary access (wp-admin and FTP) to your website, preferably to a staging or test site where the issue can be reproduced. You will find the required fields below the comment area when you log in to leave your next reply. The information you provide is private and only visible to you and me.
Thanks for the details, and I can clearly understand your language!
I checked the site and found the problem is coming from the Pods fields. Especially this template link nascosto
Some of the Pods fields are causing issues with the translated template, not sure why. But I can confirm the template is translated correctly.
This is the field causing the issue
[title] => Aggiungi qui il testo del titolo
[header_size] => span
[__dynamic__] => stdClass Object
(
[title] => [elementor-tag id="39752d6" name="pods-text"
.....
...
It is a complicated setup I need to make changes on the site
- Disable plugins
- Use Xdebug
- Log data flow.
To investigate this issue properly, I will need to create a copy of your site and test it in a local environment.
For this, I will temporarily install the Duplicator plugin to generate a full package of your site (files and database). This will allow me to debug the issue safely without affecting your site.
Hello, thank you for your support.
You can create a copy of the site without any problems, as long as it remains private for this purpose.
If I can help you in any way, please let me know.
I look forward to hearing from you, thank you.
I found that Pods data is not available in the English language. The reason is that the post types _pods_pod and _pods_group are set as translatable, while they should be set to Do not translate. Because of this, the data is missing in the translation and Elementor is throwing the error.
To fix this, please follow these steps carefully:
- Create a database backup (always a good practice).
- Go to WPML > Settings and set the following post types to Not Translatable:
_pods_pod
_pods_group
_pods_field
- Save the settings.
- Run the following MySQL query to remove the records created due to the incorrect settings:
DELETE FROM wp_icl_translations WHERE element_type IN ('post__pods_group', 'post__pods_pod');
- Edit this product: /prodotti-delta2000/camera-bianca-pannello-laminato-hpl-deltawall/
and update it without making any changes. Then edit the English translation and update it as well, again without any changes.
This should fix the issue.
I can confirm that the error is resolved on my local copy. Please let me know if this also works for you.
You can translate the field labels in Pods by enabling the language here your-site/wp-admin/admin.php?page=pods-component-translate-pods-admin
And then you will see an option to add translation when you edit the fields.
Hi Sumit,
first of all, thank you so much for your support and patience.
I followed all your instructions faithfully, I believe correctly.
The SQL query responded that it deleted 9 rows.
I saved without modifying the product you indicated and its translation, including all Elementor templates involved in the product, but when I try to open the product in English, I always get a critical error. I am copying the debug information below.
Your access to the site should still be valid if you want to check.
Thank you again for all the time you devote to us. Please feel free to ask me for anything you need or any information you require.
==========
Deprecated: Creation of dynamic property Yoast\WP\SEO\Premium\Generated\Cached_Container::$normalizedIds is deprecated in /www/deltan_444/public/wp-content/plugins/wordpress-seo-premium/src/generated/container.php on line 27
Warning: Undefined array key "reazione_al_fuoco" in /www/deltan_444/public/wp-content/plugins/elementor-pro/modules/dynamic-tags/pods/tags/pods-base.php on line 35
Thanks again for all your support. I saw your latest notes and noticed that the English pods are now working.
I'll translate a few more pods just to be on the safe side, and I hope I won't have this problem again.
I'll update you as soon as possible. Thanks, and if everything goes well, I'll close the ticket.
Thanks again.
I'm Prosenjit from the WPML Dev Team – I'm stepping in to cover for Sumit today while he's away.
I'm really glad to hear that everything's working well for you now! Take all the time you need to test things out, and if anything comes up or if you have any questions along the way, just reach out. I'm right here and more than happy to help with whatever you need.
We ran some tests and added new translations, and everything seems to be working. I'm happy about that.
I wanted to ask: is it possible to get a summary of the causes and the steps taken to resolve the issue, to better understand the problem and avoid it in the future?
Let me explain: we have another site, also using Pods, Elementor, and WPML, which has a the same problem (I think). Custom Pods fields causing errors on the translation pages.
Perhaps with the summary of causes/solutions we can solve the problem ourselves, which would also be useful for the future.
If this is not possible, can I continue to report the problem in this ticket, since the problem is similar, or do I need to open another ticket?
Thank you for your help and patience.
Of course! Although this response should clarify the problem and solution, but here is a full summary of the root cause and the steps taken to resolve it, so you can apply the same fix to your other site.
The problem was that Pods internal post types (`_pods_pod`, `_pods_group`, `_pods_field`) were incorrectly set as "translatable" in WPML. These are structural/configuration post types that define your custom fields, they should never be translated. Because WPML was treating them as translatable content, the Pods field data was not available on the translated (English) product pages. When Elementor Pro tried to render those dynamic Pods fields, it received an array instead of a string, causing the fatal `TypeError` in `str_contains()`.
Step-by-Step Fix:
1. Back up your database before making any changes.
2. Set Pods post types to "Not Translatable" in WPML:
- Go to "WPML → Settings → Custom Post Types Translation"
- Find `_pods_pod`, `_pods_group`, and `_pods_field`
- Set all three to "Do not translate"
- Save the settings
3. Run this MySQL query to remove the incorrect translation records that were already created:
DELETE FROM wp_icl_translations WHERE element_type IN ('post__pods_group', 'post__pods_pod');
4. Re-save the Pods configuration:
- Go to "wp-admin → Pods → Edit" (for each relevant Pod)
- Open the Pod and click "Save Pod" without making any changes
- This forces Pods to regenerate its field data correctly
5. Re-save the affected product and its translation:
- Open the original language product in the WordPress editor
- Click 'Update' without making any changes
- Do the same for the translated version
6. Clear all caches (server cache, Elementor CSS cache, and any hosting-level cache such as Kinsta's)
7. Verify by visiting the translated product page, it should now load correctly.
Whenever you use Pods to create Custom Post Types and custom fields alongside WPML, always check that Pods' internal post types (`_pods_pod`, `_pods_group`, `_pods_field`) are set to "Do not translate" in WPML before you start translating content. This is a one-time configuration step that prevents this entire class of errors.
Regarding your second site with the same stack, if you follow the steps above and still encounter issues, it would be best to "open a new ticket" so the problem can be investigated in its own context without confusion. However, this fix is very likely to resolve it, since the setup is identical.
Please don't hesitate to reach out if anything is unclear. Happy to help!
