This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing issues with Astra Pro Custom Layouts not showing on translated pages, it might be due to the fact that a Hook template in Astra can only be active in one specific location at a time. This means that when you translate a Hook template, it will not function in both languages simultaneously.
Solution: To resolve this, you can either create a new hook template in the translated language with the correct content and display conditions, or disconnect the translated hook from the default one and reconfigure its display conditions. Here are the steps to disconnect and reconfigure the translated hook: 1. Open the Translated Hook in the Editor. 2. Disconnect the translated Hook from the default one by following this guide: https://wpml.org/faq/how-to-disconnect-translations-from-the-default-language-page-or-post/ 3. Once the Translated Hook is disconnected, reconfigure the display condition for it, and then update the changes.
It's important to note that this issue is specific to Hooks. For other elements like Headers/Footers or custom layouts, the translated layout should display correctly without the need for separate templates. If this solution doesn't seem relevant or if you need further assistance, please open a new support ticket with us.
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.
I understand the issue you're having and will try my best to assist you in this matter.
The customized layouts won't be visible on the translated page until they are correctly translated. Please follow the steps outlined in the guide below to complete the translation of the layout, and then verify if this resolves the issue.
- hidden link
Let me know how it goes. I will be happy to help if you need further assistance in this matter.
tank you for your reply!
I cannot find 'Custom Layouts (astra advanced-hooks) in my 'Post Types Translation' section.
I don't have 'WPML Media Translation' installed. Could that be the reason?
The issue doesn't seem to stem from the Media translation plugin. It appears that WPML is unable to detect this post type for some reason. Could you please try these steps and see if the Post type then shows up in the settings?
- First, fully clear all caches from both your site and your browser.
- Next, head over to the "Avada > Custom layouts" section and create a new layout.
- After that, go to WPML > Support > Troubleshooting and click on the "Fix post type assignment for translations" button.
After these steps, please go back to WPML > Setting and check if you can see the post type in the list.
Let me know the update. I will be happy to help if you need further assistance in this matter.
thank you for the reply. I followed these steps but there is no change.
- After that, go to WPML > Support > Troubleshooting and click on the "Fix post type assignment for translations" button.
Here, I got this message : No errors were found in the assignment of post types.
Hello Klaus,
Thank you for trying out the suggestions.
Since the issue persists, a closer inspection will be required to understand the root cause of the issue.
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to have a testing site where the issue is replicated.
You will find the needed fields below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Maybe I'll need to replicate your site locally. For this, I’ll need to temporarily install a plugin called “Duplicator” or "All in One WP Migration" on your site. This will allow me to create a copy of your site and your content. Once the problem is resolved I will delete the local site. Let me know if this is ok with you.
IMPORTANT
-Please backup site files and database before providing us access.
-If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Hi Klaus,
Thank you for sharing the access information.
I've conducted a review and noticed that you've used the Astra Site Builder to create several hooks, which have also been translated. However, after a more detailed inspection, I identified the core issue. It appears that a Hook template in Astra can only be active in one specific location at a time. As a result, when you translate a Hook template into English, it only functions in German and not in English. Interestingly, if you eliminate the "Display and User Conditions" settings from the Hook in the German version, you will find that the contents of the Hook begin to display correctly in the English version.
When I created a new hook template in the English language, incorporated the content, and adjusted the "Display and User Conditions" settings, the Hook began to display correctly in the English version. For a clearer understanding of this process, I recommend checking out this video: hidden link
By taking this approach, you should be able to display the translated hooks in other languages.
If there is anything else if you need help with, feel free to let me know.
thank you for this reply.
I made a new English hook layout as you showed it. However, that is a very lengthy process and as far as see it creates doubles to the already existing English translations and these new customs layout will not be synched to the German ones?
And what are these instruction for then? hidden link
Can you tell me what you mean with:
'Interestingly, if you eliminate the "Display and User Conditions" settings from the Hook in the German version, you will find that the contents of the Hook begin to display correctly in the English version.'
Can this not be done to fix the problem for all in one go?
I understand that this might be a somewhat time-consuming process, but this is how the "Hooks" started to work correctly in Other languages. However, rather than creating an additional Hook template, you have the option to disconnect the translated hook from the default Hook, which is also an effective method. Here are the steps:
Astra's documentation outlines the procedure for translating Layout templates, but the underlying configuration for "Hooks" might be different than the templates like Header/Footer or any other custom templates.
To clarify my previous statement: if you translate a Hook and then remove the display conditions from the Hook in the default language, you'll notice that the content of the Hook displays correctly in the other language. However, by removing the condition from the default language, the Hook's content will no longer appear in that default language.
Furthermore, when Hooks are translated and linked, the Hook's content will be visible in only one language at a time. For instance, if you remove the display condition from the default language, the content will be visible in English. Conversely, if you remove the condition from the English version, then the Hook will appear in German, but not in both languages simultaneously.
This issue is specific to Hooks. When you create and translate other elements like a Header/Footer or any custom layout, you'll see that the translated layout displays correctly on the front end without the need to manually create a separate template for each one. Given this, it would be beneficial to contact Astra support and describe the situation to them. They should be able to offer a more detailed explanation regarding the behavior of Hooks.
I hope you can understand. Please feel free to let me know if you need further assistance in this matter. I will be happy to help.
