-
Hi,
as I wrote here: https://foliovision.com/support/fv-wordpress-flowplayer/how-to/upgrading after updating the plugin to version 8 all FV Player instances in the block editor are damaged.
Is it save to rollback to version 7 and which steps should I follow?
-
-
Hello Gerald,
Thank you for letting us know about the issue.
We did run into the same issue, which is why we added code to deal with this situation and make sure the blocks keep working.
It should be a problem with the post editing only and we can fix it.
Please check if the videos do appear in front-end as they really should.
Then we can plan the next steps.
Thanks,
Martin
Hi Martin,
thank you for the quick response.
Yes the videos work in the frontend. Just so you know, we use a custom post type called “video” where almost all the videos are placed.
What are the next steps?
Hello Gerald,
Please go to wp-admin to edit one of your video custom posts. It will show that the block is damaged like you said.
Then click the three dots on the top right (next to the Save button) and pick “Code editor”.
You should see HTML code similar to this:
<!-- wp:fv-player-gutenberg/basic {"src":"https://vimeo.com/492296565","splash":"https://i.vimeocdn.com/video/770835449-32a65f81ae90ee8bfa2be615e25b6337637a6c4144881aa347fcff5745ea0829-d_960?region=us","timeline_previews":"http://example.com/test","title":"An airplane approaching in super slow motion against a blue sky","player_id":"312","forceUpdate":"0.5495063177936184"} --> [fvplayer id="312"] <!-- /wp:fv-player-gutenberg/basic --> <!-- wp:paragraph --> <p></p> <!-- /wp:paragraph -->Please send it over as a screenshot. That should allow me to fix the bug.
In the meantime I’ll get a block posted with FV Player 7 and then switch again to FV Player 8 on a test site to double-check it works as intended.
Thanks,
Martin
This is a screenshot from the latest video.
Just to make sure, do you need the whole block code of the page? Because the screenshot above just shows the part with the player.
Hello Gerald,
Thank you, I found that we run the conversion on init hook with priority 10. So if your custom post type is created later, it would not be converted.
Could you please reinstall FV Player from this link? https://foliovision.com/downloads/fv-player-8.zip
Then you should be able to edit these posts again and there should be no warning about broken blocks.
Thanks,
Martin
Hi Martin,
okay, I just uploaded the version from the provided link via the plugin file upload and overwrote the existing one.
Now when I open a video post I see the video and no broken block. I will do a view more checks but it seems to work.
Our custom post type runs on init as well but with no specific priority.
There are some scheduled video posts where an empty FV player block was inserted but no video set yet. For these blocks I still see the broken block info like:
“Block validation: Block validation failed forfv-player-gutenberg/basic` (Object).Content generated by
savefunction:Content retrieved from post body:
<div class=”wp-block-fv-player-gutenberg-basic”></div>“`
I guess I have to change them manually, right? But this is something I think I can explain to the editors.
Hello Gerald,
Keeping the workflow simple for editorial staff is important.
Could you please reinstall FV Player from this link? https://foliovision.com/downloads/fv-player-8.zip
Then the empty FV Player 7 blocks with no selected video will convert properly and your editor will know what to do.
Thanks,
Martin
Hi Martin,
Great, this also changed the empty blocks.
Thank you so much for your help.
I think everything works now as expected.
