-
Posts
-
Hi folks!
I was looking for a way to define a “reusable element” in Enfold, so that after adding it to several pages, if I decide to change any of its features (e.g. text, colour or size), the change is automatically propagated to all the other “reusable elements” I have added to the pages.I thought the “Custom Element” would achieve this, so I read the Custom Elements documentation.
However, I discovered that if you change anything in a Custom Element that has already been used, the change is not propagated to the pages where the element has been used.So, what is the difference between a “Custom element” and a “Template”? Any component that I have just configured can be saved as a template very quickly. Why should I use a custom element instead? Just because I could lock some attributes?
(last question: any way to achieve my original goal, e.g. create a “reusable component” that is automatically updated in all pages when I change its features in a second time, without using CSS tricks? I don’t think so, but you never know :-)
THX in advance.
Bye!
A.-Hey Angelo,
Thank you for the inquiry.
However, I discovered that if you change anything in a Custom Element that has already been used, the change is not propagated to the pages where the element has been used.
On the Custom Element Templates, you have the option to lock certain element options. When an option is locked, you won’t be able to adjust it on the instance, and when this locked option is updated in the original source, it will be propagated to every instance. However, unlocked options can be changed on every instance of the CET and are unique to each instance, so when this particular option is updated in the original source, every instance will retain its own value. In that case, if you need a global element that can be updated from a single source and doesn’t need to look different or contain different content on certain pages, make sure to lock all the options.
On the other hand, if you need to create a global layout that can be updated from a single source and contains multiple elements, including Custom Element Templates, use the Custom Layout feature.
Let us know if you need more info.
Best regards,
IsmaelThat is FANTASTIC. Thanks Ismael, it works as expected. I misunderstood the “Lock/unlock” feature.
Thanks again!Unfortunately, it is not 100% compatible with WPML.
I created a CET component of type TEXT, with a simple word: CASA in Italian.
I translate it with WPML, HOUSE.
I add this CET to several pages: in all of them, you see CASA in the Italian version and HOUSE in the English version.If I now change the word to ‘LIBRO’ in the CET, the pages are showing LIBRO in the italian version, but HOUSE in the English version.
I have to open EVERY single page where that CET was used, do a blank ‘UPDATE’ (as it seems like WP is not detecting the change) and then update the English translation in WPML. For every single page.Too bad.
Hi,
Thank you for the update.
You may need to update the EN version of the CET as well. If you can provide the login details in the private field, we’ll take a closer look.
Best regards,
IsmaelSure thing.
I’ve prepared a “test case” for you.
1) take the the first 2 “portoflio items” (see screenshot 1).
2) In the 1st portfolio, I’ve created a “Text block test 1” item, with a simple word, “CASA”, locked. I’ve added it to the same portfolio, and I’ve translated it to EN (HOUSE) and FR (MAISON). See screenshot 2).
3) I’ve added the “Text block test 1” also to the 2nd portfolio. Now the 2 pages are shown correctly, in IT, EN and FR.Now please try to change the “CASA” italian word another word (e.g. LIBRO) in the portfolio #1 (in the CET area, of course, opening the CET for editing), and translate it in WPML while being in Portoflio #1.
See screenshot 3.At this point, If you open the portfolio #2 page, you will correctly see “LIBRO” in the italian version of the page, but the EN and FR pages will still show the old translation (HOUSE, MAISON).
To update the EN and FR pages, you need to open portfolio #2 in edit, then “UPDATE IT” so that WPML notices that there is a change, and only at that moment you can open WPML translation editor and “validate” the translation.Thanks for you help, Ismael!
Hi A,
Thanks for the information!
I tried reproducing the issue, but I’m not sure if I’m following the final step correctly. Could you please send us a screen recording so we can make sure we follow the steps correctly?
Best regards,
YigitHi Ygit, thanks for your help.
Here is the video.
Let me describe what you will see.
I added a CET to the first two PORTFOLIO pages. The CET is a “text component” that displays the word “CASA” (HOUSE in English).
I’ll show you the two pages, which display correctly in both languages.Then I edit the CET on the first page, change “CASA” to “LIBRO!”, and translate (with WPML) “LIBRO!” to “BOOK!”. As you can see, the first portfolio displays correctly in both languages (“LIBRO!” and “BOOK!”).
When I open the second portfolio, however, the Italian version displays “LIBRO!” correctly, while the English version still displays “HOUSE.”
From here, I make several attempts to translate “LIBRO!” in WPML.
In a previous attempt, I simply did an UPDATE on the page, and then WPML updated and showed me “LIBRO!” so that I could translate it. This time, however, nothing works. As you can see, it continues to show me “CASA” + “HOUSE”…Does it make more sense now?
Hi A,
Yes, it does. Thank you.
We contacted the WPML Support team as well. We’ll investigate this further and give you an update.
Best regards,
YigitHey A,
Upon further investigation, I found that you forgot to enable the Additional Translate Icon option in Enfold theme options > Custom Elements > WPML Specific Options ( see https://imgur.com/a/U7MYDJ0 ). I also missed checking this option at first.
I enabled this option and tried translating the Custom Element, and it worked as expected. I shared a screen recording in the private content field.
Please let us know if you have any other questions.
Regards,
YigitThank you so much, @Yigit. It works like a charm! Unfortunately, I was not aware of that option. Thanks again!
- The topic ‘Difference between a Template and a Custom Element’ is closed to new replies.