Quick patch: FluentCRM 3.0.6 is out

Screenplay Unlimited as I stated previously, Gutenberg is complicated in terms of v2 and v3, so only option is, try to recover the blocks. That’s the Gutenberg way.

So I would recommend you to preview the campaign, copy as text and paste in the new editor.

Shahjahan Jewel You haven't read what I just wrote (sorry I must have posted it by mistake in another 3.x thread, I can't find where). If you create a brand new campaign in 3.0.6, you can't duplicate it without corrupting half the blocks. It's not the Gutenberg way, it's the FluentCRM 3.x way. FluentCRM 2.x has zero issues with Gutenberg blocks, especially those as simple as the one we're using (H1, H2, text). 2.x can both create and duplicate campaigns that use Gutenberg blocks without causing any issue. Please read my second message, basically FluentCRM 3.x duplicate campaign feature is broken. And again, once broken by 3.x, most of these blocks are non-recoverable. So basically "duplicate" campaign in 3.x is "destroy" campaign.

To reproduce: create a new campaign in FCRM 3.0.6, using the default / recommended setting (Gutenberg editor). Add H1, H2, text and "Latest Posts" blocks. Save. Duplicate the campaign. It should be full of broken blocks, most of them non-recoverable. Can anyone reproduce this?

Actually, it's even worse than that. Even on the original campaign, created by FluentCRM 3.0.6, the blocks are destroyed as soon as you save the campaign as a draft. So duplicate isn't necessarily a factor, the blocks can be corrupted when you save the campaign with 3.0.6. You are recommending Gutenberg editor by default, surely that's not the intended behaviour to have half the blocks corrupted when you save the campaign as a draft?

Screenplay Unlimited works on my end. created a new Campaign inserted Heading, text and Latest post block. Duplicated it -> works. Duplicated the duplicate -> works

Manuel Müller Thanks for trying to reproduce, I appreciate it. And if you go back to the original campaign saved as a draft, no corrupted / unrecoverable blocks? What's your environment? I don't see any of these issues with 2.x, so it's definitely a 3.x issue, but if all users don't experience it, then it might be specific to some setups. I tried to disable Redis Cache Pro, it makes no difference. I'm on a staging site (hosted by Rocket.net) with all non-Fluent plugins disabled.

Shahjahan Jewel I recreated our newsletter block by block in 3.0.6, and it looks like the very last paragraph contains some unknown formatting that trips 3.x (yet it was created with 2.x).

The block looks greyed out when selected, and there is an option that appears, asking to "clear unknown formatting". If I clear it, I can save and duplicate the newsletter. But if I copy this single text block with formatting created by 2.x but not recognised by 3.x, it corrupts the entire campaign.

You can find that block of text and look at it in the .json export of the campaign in ticket #154432. It's the block that reads: "Any questions or any feedback -- or if you'd like to discuss how we might work together in the year ahead -- simply reply to this email.".

If you import the .json in 2.x and simply copy that paragraph and paste it into a 3.x campaign, you should see the "clear unknown formatting" message in 3.x. If you don't clear it and save, the newsletter should be corrupted.

If you clear it, you should be able to save without corrupting. Please let me know if you can reproduce this. I'll post this in ticket #154432 as well.

Of course this can't be done when duplicating an existing campaign in 3.x, but hopefully if you identify the unknown formatting created by 2.x that trips 3.x, you can fix this bug.

Screenplay Unlimited replied in the ticket.

Masiur Rahman Siddiki Thanks will reply there too.

For those experiencing the same issue, the current workaround is, instead of clicking on the "Recover" button when a block is corrupted after import/duplication -- which will most of the time delete the content -- to click on the three dots and select "Resolve", which actually recovers the content of the block.

Hopefully, this issue will be fixed at some point, but in the meantime that removes the main dealbreaker for us to move to 3.x. There are a few cosmetic issues to solve in the campaign emails, but apart from that it looks like we should be able to upgrade soon.

Thanks a lot to Masiur Rahman Siddiki for looking into this and suggesting this workaround :)

Nikki Stokes Any specific issue you are afraid of?

Shahjahan Jewel Just don't want my already-created broadcast emails or my many and complicated automation emails + logic to break, and to have spend hours going through everything with a fine tooth comb to make sure they all still work correctly. With such a big overhaul of the architecture, it's hard to make sure everything's properly backwards compatible, esp the email builder experience. I like the idea of it being faster, don't care about AI or SMS, but just nervous to spend time I don't have testing and (potentially) fixing.

As an example, I discovered a bug just the other day from a previous upgrade that had switched my automation to send my internal notification emails to the contact instead of to my custom internal email address! I hadn't touched that automation for months and it took me months to notice! It's having to check that every single detail is still working correctly after such a big upgrade that makes me nervous.

As I feared, such a major update was not without issues. Updating to 3.0 broke ALL of my email layouts, so I had to go through and individually update 90+ automation emails so everything was properly aligned. 😭