Hello,
1. I would like to translate, using WPML, the text from this section:
Dashboard >> Newspaper >> Theme panel >> Footer >> Footer info content >> Footer Text. In the td_footer_extra.php file I’ve found this code (on line 64):
$buffy .= stripcslashes($td_footer_text);
I think I could add a method like _e() to make it tranlatable but I’m not sure and I can’t afford to make any mistakes because it’s a very big website (more than a few thousands posts).
I’ve also tried this: https://wpml.org/forums/topic/how-to-translate-my-footer-content/, but the website main language isn’t english so I wasn’t able to translate it to english.
2. How can I use the same widget ( here is: [tagDiv] Block 7 ) with different text for different languages? In Appearance >> Widgets >> [tagDiv] Block 7 >> Display on language, but when I hit save, it automatically switch the option back to All languages so the result is the same as before
3. Is it possible to translate News Ticker and Big Grid Slide from VisualComposer?
On front page I have a News Ticker with a Big Grid Slide, but on the translated version of the page it doesn’t show anymore.
Thank you in advance for your time
PS. I’m using Newspaper v8.7
Hi,
1. For the footer text the steps are mentioned in this similar topic
– https://forum.tagdiv.com/topic/newsmag-widgets-not-working-with-translations-wpml/
2. There was a problem with selecting the language for specific widgets to appear, it was solved a few updates ago I believe. The problem was that when setting a language the option was resetting to all languages.
In the latest theme version however this works properly. Maybe you are using an older theme version.
3. You can create a different page for each language, each with the content you want
– https://www.screencast.com/t/tBjxdAK4yLx
For example I have this page in a language – https://www.screencast.com/t/wUVMxwx6qlV
Clicking on the translate option will open a new empty page which you can build with the composer
– https://www.screencast.com/t/yWKrq5fBxTI
Thanks
Hi,
Yes, I have an older theme version so that might be the problem (for 1 and 2).
I will redo the page (for no. 3).
Thank you for your time 🙂
