To better understand the problem youâre experiencing, could you please provide more details? Specifically, we would appreciate screenshots or a screencast showing how you have set up the plugin element, the associated workflow, and the repeating group (RG) where the element is located. Please make the video in step-by-step mode, and check with inspect how the values are changing in the element from the beginning.
Additionally, does the element display a different value between what you have initially set versus what is shown, or does this discrepancy occur after a specific change or action?
If you are making changes in the database and wish to reflect these in the RTE element, you can use the âSet Text/HTMLâ action and input the same value you have set as the initial content.
Thank you once again, and we look forward to your response.
I have a new question about running actions on the ZQ input inside of a repeating group. Seems that if I have a workflow run on an element outside of the repeating group where the ZQ input is, then I canât do any actions on the ZQ input? Itâs not available to select in the action.
However, if the element that triggers the workflow is inside the same repeating group, only then I am able to select the ZQ input.
Based on your description, it seems youâve attempted to trigger an action for the RTE element inside a repeating group (RG) from outside of it. Have we understood your situation correctly?
Unfortunately, Bubble does not natively support triggering actions for elements inside a repeating group from the outside. This limitation applies to all elements, including Bubbleâs native ones like the âInputâ element.
We appreciate your understanding. If you have any more questions or need further assistance, please donât hesitate to contact us.
Yes, I assumed it was the limitation of Bubble, not the plugin.
This makes this plugin a bad fit for me as the Autobinding does not work as with native bubble inputs⌠since a workflow action is needed in order to change the value of the input instead of that automatically happening as youâd expect when Autobinding is selected.
The limitation occurs only when you attempt to trigger a plugin element action from outside a repeating group (RG) while the element itself is inside the RG. This applies to all elements, including native Bubble input.
Regarding the use of Autobinding with the RTE, it appears to function correctly and updates the database as expected. To illustrate this, weâve set up a test page for you to review: zeroqode-demo-06 | Bubble Editor
Could you please check it out and let us know if it meets your needs? If you have any further questions, feel free to ask.
The updating the database does work, but updating the inputâs initial content value only happens on page load or by using a workflow action⌠whereas the native bubble inputs all will automatically change their initial content value in the UI without a workflow action.
So in my scenario using Custom States that change the data source ZQ RTE will not update the value in the source and input. The action âupdate ZQ htmlâ has to run in a workflow. Also I canât run that outside of a repeating group (where my ZQ RTE element is) so Iâm stuck not being able to update the value when using states.
Could you please provide more details, such as screenshots or screencasts, to clarify exactly what youâre trying to achieve? You mentioned previously wanting to use auto-binding with the RTEâhave you had a chance to visit the test page we provided to see how the initial content is updating accordingly as you make changes in the element.
If you prefer not to use auto-binding, you might consider using the pluginâs âStop typingâ event to update the database value [image]. Could you please try this approach and let us know if it addresses your needs?
Thanks again, and we look forward to your response.
When I am setting the max image size to for example 500 x 500, that works in the editor. But when I load the HTML in my app, there is no limit in size.
This does happen when I resize the image inside the editor when I upload an image as a user, but as this will not always happen, this is not enough.
You would expect something like style=ââcursor: nesw-resize;ââ width="â500"â> in the HTML right?
Based on your message, we understand youâre encountering an issue where the output HTML lacks height and width specifications when you first upload an image. After conducting some tests, I confirmed that images uploaded without manual resizing in the element initially do not include the "style=âcursor: nesw-resize;â width=â500"â attributes, these only appear after manually resizing within the RTE editor. We have already reported this concerns to our development team for further investigation and resolution.
Could you please confirm if this describes the problem you mentioned in your previous message? If thereâs anything else weâve overlooked, do let us know. Additional details such as screenshots or screencasts showing how you set up the element and the issueâs occurrence would be very helpful.
Thank you once again and we look forward to your reply.
The demo page of the plugin doesnât work, could you help me with my question ?
In the plugin page, it says that you can make checklist/add checkboxes, but on the promotional clips I donât see any button or options to add them within the editor. So can we add checkboxes in the editor ?
It seems youâve encountered the missing element issue, which occasionally appears on the Demo Pages of the plugins. We are aware of this and are currently awaiting a resolution from Bubble. Currently the live demo is working fine for you to explore.
Regarding your request, unfortunately, the Quill JS library currently used in our plugin does not support checkboxes or checklists. However, if you are interested, we can explore the possibility of integrating 3party tools that would allow these features. If you would like to proceed with requesting new features or improvements, we invite you to sponsor the development. Please complete the Sponsoring Plugin Features Form to initiate this process: Interface Form - Airtable
Additionally, you might consider exploring another RTE plugin, the Notion-like Rich Text Editor, which supports checkboxes and checklists.
We look forward to the opportunity to collaborate and better serve your needs.
Thank you for your message and for sharing your feedback.
Absolutely, please feel free to explore the plugin further. And if you will have any questions or encounter any difficulties, donât hesitate to contact us at any time. Weâre always here to assist you.
Thank you once again, and we hope you have a wonderful day ahead!
Looking to use this RTE in a chat application, but cannot figure out a way to allow for âEnterâ to submit a message (i.e. - trigger a workflow event) and âShift+Enterâ to create a new line. Has anyone successfully managed something like this with this plugin?
Thanks for reaching out to us and the bubble users here
The plugin library currently accepts the enter key as a new line in the Rich Text Editor element. As you know from our email conversation, weâve discussed the possibility of improving this feature, but that would require a Paid Plugin Development as simply modifying the key could cause multiple strange behaviors with the plugin.
If some users are aware of how to achieve this feature without modifying the plugin, you could try it out and see if it works as you expect!
Hi @ZeroqodeSupport
I have a performance question.
At the moment, I have dozens of RTE light elements on a page, in a RG.
Iâm displaying the content in an HTML element and when the user clicks on it (and if they have the editing rights), I switch between the HTML container and the RTE.
And I reverse back when the RTE is blurred.
I would prefer for the RTE to be displayed as static âread-only modeâ for users who donât have the rights and editable when a user has the rights. Would it be bad in terms of performance to display lots and lots of RTEs rather than HTML blocks ?
Thank you
Thank you for reaching out with your performance question.
Regarding your concern:
Hereâs some insight that might help you decide:
Performance and Simplicity:
Using Only Rich Text Elements: Transitioning to solely using Rich Text Elements (RTEs) can simplify your application. This means you wonât need to manage both HTML and RTE elements, reducing complexity. Bubbleâs RTEs come with built-in functionalities that are easy to control with conditions, which can make your app more maintainable in the long run.
Performance Impact: Displaying multiple RTEs, especially in read-only mode for users without editing rights, typically doesnât have a significant negative impact on performance. The overhead is generally minimal compared to managing separate HTML elements.
Flexibility and Control:
Rich Text Limitations: While RTEs offer convenient features, they might be limited compared to custom HTML in terms of advanced styling or scripting.
Custom HTML Advantages: If you require advanced customizationâlike intricate CSS styles or JavaScriptâyou might prefer sticking with HTML elements. However, this can increase the complexity of your codebase.
Maintenance:
Simplifying with RTEs: Using only RTEs reduces the number of elements and custom code you need to maintain. This can make debugging and future updates more straightforward.
Long-Term Considerations: If your application is intended for long-term use and maintenance, minimizing custom code can save time and reduce potential errors down the line.
Recommendation:
If the Rich Text Editor meets all your needs in both read-only and editable modes, it would be beneficial to switch entirely to RTEs. This approach simplifies your app and should not cause significant performance issues, even with numerous RTEs on a page.
If you find that you need more advanced customization that only HTML can provide, it might be worth retaining the HTML elements, despite the added complexity.
In Summary:
Switching to RTEs can simplify your application and make it easier to maintain without adversely affecting performance. Evaluate whether the functionalities of Bubbleâs RTE suffice for your use case. If they do, transitioning away from HTML elements could be advantageous.
Hope this information will prove helpful to you, please let us know if everything is clear or if you have more questions or need further assistance!
Would I be able to use this plugin to edit a contract template and add dynamic fields which can be replaced with data from the database?
Here is an example: Dynamic fields.mov - Google Drive
