September 16, 2019 at 4:43 pm #1138870
We’ve run into an issue when creating new ALB elements. We’ve created a new element with two content editors in
Notice how we’ve used
- “id” => “content_left”
- “id” => “content_right”
Can you please advice in what is going wrong?
YanSeptember 18, 2019 at 8:52 am #1139338September 18, 2019 at 10:09 am #1139365
We apologize for the delayed response since there are lots of queries lately.
Can you give us the code you used? so we can check on it further.
Just upload the code in https://pastebin.com/ and give us the link to it, you can post it in private content so it’s only visible to you and the moderators.
NikkoSeptember 18, 2019 at 11:02 am #1139401September 20, 2019 at 6:18 am #1140117
We apologize for the delay.
I have checked into your created element and it works properly.
There were no errors in web console as well.
I think the problem in the screenshot you gave might be the html code is pasted in Visual editor. Have you tried pasting the html code in Text editor then select the Visual editor after? this should convert it to h2 tag and anchor tag.
NikkoSeptember 20, 2019 at 9:59 am #1140158
Thanks for looking into this, however I think you’re missing the point here and please try too test it again :-)
Here’s a step-by-step
* Open the element
* Enter some content, also links, H-tags, etc. into the content editors using the Visual Editor
* Save the element
* Re-open the element
You’ll see that the Visual Editor now contains the HTML-version of the previously entered content.
This is the problem, when reopening the element the content is then displayed as HMTL and then switching to the Text/HTML mode then converts it to a html_encoded version of the content.
YanSeptember 23, 2019 at 4:06 pm #1141036September 24, 2019 at 8:46 am #1141264
We apologize for the delayed response.
I have tested it again and it’s fixed if you use content instead of content_left, however for the second wyswyg editor since you’ll have that custom name it will show the html content and it will take a lot of time to fix since it’s more complicated than how it looks, which is outside the scope of our support. We apologize for the inconvenience :(
NikkoSeptember 24, 2019 at 10:23 am #1141322
Thanks for the info. This was unfortunately also what we concluded, that it would require extensive modifications. But I hoped you guys might’ve had an “easier” solution to it.
Thank you for looking into it :-)
YanSeptember 24, 2019 at 11:07 am #1141337
You must be logged in to reply to this topic.