Services Plugins FAQs

Issue with Rich Text Editor

Hello :wave:

Hey Zeroqode :wave:

We are having an issue with this plugin: Advanced Rich Text Editor Plugin | Bubble

It is not creating the correct HTML for us to use with regards the bullet point numbering.

You guys just pushed an update to fix the bullet points that really helped :+1: but it looks like you guys havenā€™t fixed the numbering bullet points yet. As you can see below, there is no difference between the two types of bullet points so I canā€™t do any find and replace to fix it.

This is how I am currently fixing the issue with a find and replace:

<li class="ql-indent-1ā€> **replace with** <li style="margin-left:30pxā€>

<li class="ql-indent-2ā€> **replace with** <li style="margin-left:60pxā€>

Etcā€¦

I canā€™t do that with the other parts since it doesnā€™t seem to work correctly. Any way to fix this? Any ideas?

This is what it is coming back when we send it to Docmosis to create the PDF Document:

Here is the code that it gives us from the RTE:

<html>

<head></head>

<body>

[

<div class="ql-snow">

<div class="ql-editor" style="height: auto; font-family: arial; font-size: 13px;">

<p><span class="ql-font-arial" style="font-size: 13px;">Testing</span></p>

<p><br /></p>

<ul>

<li>Field 1</li>

<li class="ql-indent-1">Field 2</li>

<li class="ql-indent-2">Field 3</li>

<li class="ql-indent-3">Field 4 </li>

<li class="ql-indent-4">Field 5</li>

<li class="ql-indent-5">Field 6</li>

<li class="ql-indent-6">Field 7</li>

<li class="ql-indent-7">Field 8</li>

<li class="ql-indent-8">Field 9 </li>

</ul>

<p><br /></p>

<ol>

<li>Field A</li>

<li class="ql-indent-1">Field B</li>

<li class="ql-indent-2">Field C</li>

<li class="ql-indent-3">Field D</li>

<li class="ql-indent-4">Field E</li>

<li class="ql-indent-4">Field F</li>

<li class="ql-indent-4">Field G</li>

</ol>

</div>

</div>]

</body>

</html>

Here is what Docmosis said that seems like would fix the issue, it seems like they arenā€™t adding the CSS to manipulate it but just adding the <ol> whenever there is a subitems next :

It would be possible to replace each of the different class attributes with inline styles as previously demonstrated. However in this case, CSS is being used to manipulate the list levels.

This example would need to be manipulated before sending to Docmosis. A nested list would be best represented with nested HTML lists, such as:

<ol>
 <li>List item one</li>
 <li>List item two with subitems:<ol>
     <li>Subitem 1</li>
     <li>Subitem 2</li>
   </ol>
 </li>
 <li>Final list item</li>
</ol>

Hi @jay,

Sorry for the late reply due to the weekend. :pray:

Could you kindly confirm if youā€™re using the most recent plugin version? Weā€™ve conducted tests on our end, and the RTEā€™s HTML appears to be working correctly from our perspective.

For example:


            <div class="ql-snow">
                <div class="ql-editor" style="font-family: Arial; font-size: 13px;"><p>Testing</p><ul><li>Field</li><li class="ql-indent-1">Field2</li><li class="ql-indent-2">Field3</li></ul><p><br></p><ol><li>Field A</li></ol><p>   </p><ol><li class="ql-indent-8 ql-align-right ql-direction-rtl">Field5</li><li class="ql-align-right ql-direction-rtl ql-indent-8">Field6</li><li class="ql-align-right ql-direction-rtl ql-indent-7">test</li><li class="ql-align-right ql-direction-rtl ql-indent-7">test</li></ol></div>
            <style>
                @import url("https://5eb2ccebcd71a733e0988f5de214c8ea.cdn.bubble.io/f1655375976130x567190025804119800/quill-emoji.css");
                @import url("//5eb2ccebcd71a733e0988f5de214c8ea.cdn.bubble.io/f1701783297531x876782772703974600/quillZeroqode.css");
            </style>
            </div>

Please inform us if thereā€™s any detail we might be overlooking in this matter. Your feedback would be greatly appreciated.

Best regards,
Gulce

Yes, we are updated to the newest version.

I believe the issue is that the code isnā€™t creating and closing the ā€˜olā€™ parts correctly. Itā€™s just using CSS to indent instead, which doesnā€™t allow us to send the HTML properly to Docmosis for it to read it.

Does that make sense?

Please see notes in first post for all the details.

Hi @jay,

Please allow us to investigate the issue youā€™re facing. Iā€™ll provide you with an update as soon as possible. Thank you for your patience. :pray:

Best regards,
Gulce

1 Like

Ok. Thanks. I appreciate it.

1 Like

Any update on this yet? Please keep me posted. :blush:

Hi @jay,

There havenā€™t been any updates as of now, unfortunately. Our developers are actively investigating the possibility of changing the format. Iā€™ll promptly inform you as soon as thereā€™s any news or progress on this matter. Hope for your understanding. :blush:

Best regards,
Gulce

1 Like

Ok, thank you. We appreciate it.

1 Like

Any updates? :blush: We really need this working since it is already in Live and it doesnā€™t work properly when we send the HTML over.

Hi @jay,
Thank you for your message, I hope youā€™ve had a great weekend, and Happy New Year. :partying_face:

Iā€™ve verified with the dev team and they are still working on your request, trying different methods and choosing the most feasible way.

I will keep you updated while @Gulce is OOO.

Thank you for your cooperation and patience.
Have a great week ahead.
Regards, :pray:

Ok, thank you @Igor. :blush: Please keep us posted since we are waiting to push an update for our clients since they canā€™t do what they need to do.

Is there any way we can speed up this process somehow? Do you guys have priority support or anything?

@Gulce @Igor

Any updates? We really need this working. :blush:

@Gulce @Igor

Iā€™m also experiencing this problem as well ^^

We need this as well. We are getting tickets saying that indenting is not working with things that are not bullet points when exported to HTML. A fix is much appreciated. @Gulce @Igor

We are also experiencing this issue, and clients have submitted ticket asking about a potential fix. @Gulce @Igor

Same thing here. Need a fix asap

Would love an update on this. :blush: Itā€™s been over 2 weeks now.

Hello all,

Thanks to everyone for your responses and for including us in the conversation. Apologies for the delayed response over the weekend.

Weā€™re currently in the last stage of testing new functionalities.

Iā€™m confident that weā€™ll complete our plugin testing today and plan to roll out an updated version shortly. We appreciate your patience during this process.

Stay tuned for further updates. :pray:
Best regards,

2 Likes

Thatā€™s great to hear. :blush:Looking forward to it.

Great news! Thank you so much!

1 Like