Thanks @vini_brito
In the meantime I think I’ll go with the find and replace expression.
Thanks a lot man 
Looked into it, while there are no bugs per se, since that field expects HTML and line breaks and styles are expected to be in HTML, I feel your pain.
Try looking for a rich text editor that outputs both HTML and BBCode, that way you show the BBCode in Bubble and uses the HTML in the email.
If you don’t find any, free or paid, tell me, I do have a private rich text editor that outputs BBCode, HTML and plain text, so I can enable it in your app. While a lot of work went into polishing it, it still may have some rough edges and I won’t be able to fix or polish them in a timely manner, that’s why I keep it private. I’m saying this just so you don’t get stuck and have an alternative.
P.S: It works fine for my use cases. It’s just that a lot of unknown unknowns appeared over time and were fixed, so I know that unforeseeable stuff may show up. But generally it’s pretty stable now.
1 Like
Can I use this postman plugin with a free Bubble plan?
I think so.
2 Likes
Yep you can
Hey @vini_brito just checking if this postmark change will effect the plugin?
Hey there @equibodyapp,
I believe @vini_brito addressed it an another thread, but it will not.
1 Like
Thanks @johnny 
No problem 
Hello @ryanck
Did you find a way to solve this? I have the same problem (RTE >postmark)
@vini_brito maybe you fixed this ?
Thank you
Hello,
My workaround has been using the find and replace operator and it’s working fine at the moment.
Hope it helps.
Thank you @ryanck
How do you do for color / urls / email /size ?
I can’t get this with find&replace
Try seeing if there is a rich text editor plugin that outputs BBCode and HTML, so you have both from the start (:
Running into an issue here where Bubble gives me the “we ran into a temporary bug yada yada” when trying to send batch emails.
At first it only affected one workflow sending 501-1000, before and after that particular one it worked fine. Today none of them works and gives the same error. It’s near impossible to find what’s causing it, and I don’t dare sending a Bubble bug report if they for some reason end up sending out newsletters to thousands of users. And I’m pretty sure they’ll just give me the “you’re using a plug in, good luck” answer anyway.
For obvious reasons I can’t reproduce it in the dev. environment. So this is more of a hope that someone has had the same issue and found the cause? I’m thinking of splitting up the batch in smaller chunks. But it’s a risky business trying to solve this in the live app.
Hello @vini_brito I had this error message :
do you know what conditionnal to put for not having this popup ? thanks
You might want to use Postmark’s API to check if the recipient is unsubscribed or has previously bounced
2 Likes
okay got it thanks @johnny !! always there to help !
2 Likes
Still facing issues with not being able to send the second batch of 500 emails. It always sends the first 500, fails to send the second 500, and is fine after that. I’ve tried spacing it out with 30min between calls, running it in the browser vs running it on the server. Nothing works.
Has anyone been able to send +500 emails by using Postmark and bubble, plug in or no plug in?
Postmark’s limit is 500
It’s 500 per API call. That’s the reason I’m splitting it up in multiple calls, each sending 500 or less.
The problem I’m facing is that the second call doesn’t work, ever. But subsequent calls works fine.