Please Log in to join the conversation.
krileon wrote: The WYSIWYG editor is usually adding the <p element back in on every save. Within Extensions > Plugin Manager editor your WYSIWYG editor plugin and change it so it doesn't use paragraph elements for linebreaks, but instead br elements. That should stop it from doing it ...
krileon wrote: ... remove the <p elements, remove any extra whitespace, then save and its language string should work fine.
krileon wrote: ... If the string was changed from its default then copy the string and add a translation for it as follows ...
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
Nope, that's to escape the single quote so it won't be invalid PHP. That language string should be as follows.Maybe the \ causes the problem ?
'YOUR_REGISTRATION_DATA_HAS_NOW_BEEN_SAVED_BUT_YOUR_a8bdff' => 'Your registration data has now been saved, but your subscription isn\'t active yet. You need now to pay the subscription:',
Looks like there's 2 language strings for sales that that would need to be translated. They're in language.php as follows.The text "Sales Tax" is not translated
'SALES_TAX_542702' => 'Sales Tax',
'SALES_TAX_36e536' => 'Sales tax',
The "Text -duration- FOR -price-" isn't the string you're using. I believe you're seeing the below usage.The "for" between duration and username is not translated, but as I modified the value in the setting to "pour" I thought that I do not need to insert some translation string somewhere !?
'ITEMSALIASES_FOR_USERNAME_4643af' => '[ITEMS_ALIASES] for [USERNAME]',
'PREFIXTEXT_ITEMNAME_FOR_USERNAME_ab86cf' => '[PREFIX_TEXT] [ITEM_NAME] for [USERNAME]',
Please Log in to join the conversation.
Please Log in to join the conversation.