[Resolved] Popup Maker: popup does not open on translated page
This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing issues where a popup created with Popup Maker does not open on a translated page, even though both the page and the popup have been translated, this might be similar to the issue we addressed. In this case, the popup worked on the original language page but not on the translated version. Solution: First, ensure that the popup ID is correctly set for the translated versions. You might need to manually adjust the popup settings in the WPML translation management dashboard. If changing the popup ID does not resolve the issue, it could be related to a theme error. We recommend checking the debug log for errors and consulting with the theme author if necessary. For instance, a PHP error related to a 'call to a member function get_type() on null' in the theme's files was identified as the cause in a similar situation.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I am trying to translate a page that contains a button to open a popup using Popup Maker. The page and the popup have both been translated. However, on the translated page, the popup does not open. Link to a page where the issue can be seen: hidden link
Symptoms:
On the translated page, the popup does not open. The CSS class "pum-trigger" is missing for the button link.
Questions:
Why does the popup not open on the translated page?
Is the missing CSS class 'pum-trigger' causing the issue?
I will need to closely examine your website. Therefore, I will require temporary access (WP-Admin and FTP) to a test site where the problem has been replicated, if possible. This will enable me to provide better assistance and determine if any configurations need to be modified.
Please note that it is important to have a backup for security purposes and to prevent any potential data loss. You can use the UpdraftPlus plugin (https://wordpress.org/plugins/updraftplus/) to fulfill your backup requirements.
Your upcoming reply will be treated with confidentiality and will only be visible to you and me.
✙ To resolve the issue, I may need your consent to deactivate and reactivate plugins and the theme, as well as make configuration changes on the site if necessary. This emphasizes the significance of having a backup.
I tried to change the popmaker ID here hidden link for English, but it broke the page hidden link . Also, I deleted the English language contents and duplicated it from DE language for a test.
I tried accessing your FTP access to check the debug log, but it's empty and could you please check? Also, it says my FTP access doesn't have the permission to edit the files.
Thank you Kor. With this hoster only files in wp-content may be edited.
WPDebug has to be switched on from the admin panel. I just did that.
I noticed this behaviour before: when you try to save the English (translated) version of the page directly it breaks. This can only be reversed when you completely delete the translated page and create it again ...
The debug.log works now. You can also see the server error log at 246851_test/logs/ via FTP.
Based on the debug log below, it looks like the issue is related to the theme.
[11-Feb-2025 18:16:35 UTC] PHP Fatal error: Uncaught Error: Call to a member function get_type() on null in /data/sites/web/b1400m8myrdbxio/www/wp-content/themes/uncode/woocommerce/single-product/rating.php:30
Could you maybe check the rating section of the translated product to see if anything is causing the breakdown? or check with the theme author.
