Please put a pause in your save flow or split it like I did in the demo where export happens on button click, name popup comes up, and export results are saved after name.
Basically it’s not being given enough time to export.
I’ll be updating the plug-in this week with a new “export complete” event & a few other useful features.
@chris.williamson1996 Thank you so much.
Hey @chris.williamson1996
I hope you’re doing well. I wanted to touch base regarding the plugin update.
Are you planning to launch this update anytime soon?
The export event would help us a lot since we are facing issues in saving the data even after adding a pause in our workflow.
I did Misspeak, they actually don’t have an export event. I tried adding when I pushed my large update.
There’s multiple ways about this:
extend pause action and add UI loader
UX flow where you export when they click save, show a naming popup, once named then you save. This adds a natural UX flow pause that has beyond enough time to export.
set a “saving” state that sets to yes once save is clicked and use a “do only when” workflow that states do only when builder HTML is not empty and saving = yes. initiate save to db. Set saving back to no.
This allows for the saving to only start once it’s good to go.
I very rarely ever see saving take more than 0-3 seconds. We use this to do contact builds as well that are VERY long and have no issues saving. So all options work you just need to workout what the best option for your app is.
Hi guys, was hoping to test run before I purchased today but after I initialise the builder nothing seems to be happening in the demo. Could someone let me know what I’m doing wrong please?
Thanks in advance
Is this app still current / supported? I see @LA81638 's comment above hasn’t received any replies.
I’m considering installing/configuring this plugin. Are there current active users in 2023 who are happy with it?
I bit the bullet and signed up for a month at first and so glad I did, it’s amazing. Also @chris.williamson1996 messaged me separately so can confirm that it’s still supported 
Still very active and used. If you need help feel free to reach out directly.
Thanks Lisa, glad it’s working so well for you 
This Plugin is showing as Depreciated!
Hey Shaun, it will be updated by end of next week. If I’m not mistaken all features should still be working. Let me know directly if you’re having issues with it.
Can I create my own ui with this plugin?
Only to an extent, we have a few versions of it for client apps we’ve overhauled with JS/CSS
You’ll need to use the custom initialization action to inject it in and follow the documentation
Not experienced any problems - I’m about to purchase another license for another app I love the plugin that much! Then saw the tag as Depreciated and thought damn - what a shame, I better find a new solution fast.
Cheers Chris for the response!
I’ve received multiple emails regarding the recent depreciation alerts within apps connected to my plugin. To shed light on this matter, please refer to the Bubble team’s announcement here for comprehensive information on the required upgrade to Plugin API V4 node 18 by Jan 4th 2024.
To clarify, the depreciation notices currently serve as warnings and should not have any immediate impact on your apps. I want to assure you that the Node 18 update has been successfully completed and submitted to Bubble for review to remove all depreciation warnings.
The most common question I received via email since these depreciation warnings started is: “Will this be updated? My app relies on your plugin.”
I want to address this question publicly as the fear of having to find ways to pivot quickly with software can be very unsettling. This plugin holds immense importance for many of my own projects, client apps, and over 240+ Bubble users. I have no intentions of discontinuing support and updates. My goal is to continue making it the go to Bubble emailing plugin.
Should there come a time when I can no longer provide support, updates, or address customer feature requests, I will either pass the reins to a fellow plugin developer in the Bubble community and/or release an unmanaged legacy version publicly.
Regarding the Node 18 update, I want to give a public thank you to @nocodeventure - Mido and his team. This quarter has been exceptionally busy for me with clients as well as a personal out of state move. Recognizing the time constraints, I reached out to Mido at @nocodeventure who handled the update to node 18 for me.
For those seeking plugin upgrades or fully custom-built plugins, I recommend checking out their recent thread here.
Once the update is accepted by Bubble, I will provide another update in this thread. As always, feel free to reach out to me directly for support, feature requests, or general questions.
Currently it doesn’t allow on behalf of or WL sending it all goes through your keys, however I do have that on the to do list
@chris.williamson1996 Hey, I recently came across this amazing plugin! I have a question concerning smart text. I would like to use my own openai’s API key to generate text. could you please assist with how that would work?
@anubhavprabakar
It does not require your own key to use the native text generator and currently does not support using your own key.
Can you point out where you create dynamic tags? I am only seeing first name and last name as options. Thanks!
Hey! @calicass83 You will put them in the initialization action under merge tags when starting the editor, add any values you’d want in that list. Formatted just like those default tags are.
Make sure when you actually run the action to save the HTML, send email, or display the HTML you :findandreplace the values with the real info.
Make sure the JSON save doesn’t replace the tags (that’s how you can reload that content into the editor for future editing) only :findandreplace the HTML content.
If you have further issues just let me know and we can setup a call.
Hey @chris.williamson1996 - great work on this plugin!
Any chance of exposing a ‘This editor’s HTML/JSON exported’ event?
That way we don’t have to fiddle around with conditions to check when the code is exported.
Thanks!
