You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the free version of Qubely 1.6.9 and unfortunately my Qubely Timeline block was not properly showing in the English translation of my German page. The styling was corrupt. The page was translated with WPML.
My workaround
I solved the problem by making a diff between the source code of the German and the English page. This has shown me that in the translated page the following two entries were missing:
After copying the content of the German block, tranlating the texts and entering these two elements in the beginning of the translation field for English (in Text mode) the page works nicely.
I just wanted to let you know, because maybe this helps in debugging or helps other users as a workaround. If I may improve the issue description please let me know.
The text was updated successfully, but these errors were encountered:
I am using the free version of Qubely 1.6.9 and unfortunately my Qubely Timeline block was not properly showing in the English translation of my German page. The styling was corrupt. The page was translated with WPML.
My workaround
I solved the problem by making a diff between the source code of the German and the English page. This has shown me that in the translated page the following two entries were missing:
<link rel='stylesheet' id='qubely-bundle-css' href='MY_URL/wp-content/plugins/qubely/assets/css/qubely.bundle.min.css?ver=1.6.9' media='all' />
<style type="text/css">:root {--qubely-color-1:#696CFF;--qubely-color-2:#04C3EC;--qubely-color-3:#363636;...VERY_LONG_STYLE_DEFINITION...</style>
After copying the content of the German block, tranlating the texts and entering these two elements in the beginning of the translation field for English (in Text mode) the page works nicely.
I just wanted to let you know, because maybe this helps in debugging or helps other users as a workaround. If I may improve the issue description please let me know.
The text was updated successfully, but these errors were encountered: