ThBunte

yes, tnx for your fast and helpfull support!

Bye Thomas

I found out that it was an incompatibility with Divi Theme Version 4.5.8. After a rollback to Version 4.5.6 it works again.
Because Divi Theme was often used, it could also make sense to search for the reason from our side too.

tnx for these Information, it works well.
But I think for not so experienced WordPress users placing a code snippet in functions.php is not the ideal way.
In this case it would make much more sense to integrate the offset function directly into the blocks for post grid and post masonry.

I posted these question also in the Elegantthemes Support. Maybe it make sense if other Bloom-Users also post these in Elegantthemes Support System to get more pressure for these problem!

Also the Jackmail Team too ??

Any info / news about these theme?

Maybe you can give us such information, so that we also inform the eleganttheme over it in Support Forums?
So we get a little bit more “pressure” ??

ok, good to know.
But that means that these text will also display in the detailview of Newsletter.
And if you place there some special CTA Text elements to increase the opening rate, these texts made no sense on the openend Newsletter. Therefore was the PreHeader element created.
Some other high-professional Newslettersolutions like selligent and also some WP Newsletter solutions (Mailster) works with that.

Maybe you think about an enhancement in that way – looks not so elaborate for me ??

Ok, but maybe these was a sensefull enhancement for the future ??

Maybe these was related to the updates to vers. 1.2.18 https://www.elegantthemes.com/api/changelog/bloom.txt

Any info about it? How should i get a EMail-Provider to have fields for Name and EMail and a list where the infos goto.
Because with empty Value for Custom HTML Form i get still no fields in Bloom Form. See screencast from Website:
https://www.screencast.com/t/Z3BOoACUOK

hi, that doesn’t work. I become then an empty window from bloom without any field for placing name a.s.o..
Where should the system also knows wich fields and wich list should be used?

Works perfect with version 1.0.38 ??
tnx for quick support!

That sounds great ??

Hi Chris,
found the source of the problem – not related to Bellows,
tnx
Thomas

I have a lot of WP Sites with Divi and MLP running.
You must only create in Mainlanguage the Page, copy it to next language and open it in the backend of nextlanguage.
While Copy will all shortcodes used from divi will go to second languages.
I use normally the Link to draft in MLP Secondlanguage to do the shift to other languageversion.
And here you can work normally with the Divi-Editor.