Batch video and splash image url replacement

Hello Bruno,

do you use the [fvplayer src="..."] shortcodes most of the time, or do you post the videos with editor? In that case they are stored in database and you can see all of them in wp-admin -> FV Player.

In the first case you can run search and replace using a plugin like Search Regex on post content.

In case of database you can just run search and replace on the wp_fv_player_videos database table, on the src, src1, src2 and splash columns. When we designed the database structure we were trying to keep it simple to let experienced users manipulate data with ease – in contrary to the WordPress Custom Post Types where and non-standard fields are just postmeta.

Please let us know if this did help, or if you need any further help.

Thanks,
Martin

Hello Bruno,

wp-admin -> FV Player lists the players stored in database, but the actual database is the data storage which feeds all the information into your WordPress website.

Using a database tool like phpMyAdmin you can run relatively simple commands like this to replace all the source video paths in one easy step:

UPDATE wp_fv_player_videos SET src = REPLACE( src, 'https://bunnycdn-domain.com/', 'https://digitalocean-spaces-domain.com/bucket/' );

It’s easy to run, but it’s also easy to make a mistake, so I wonder if we could provide an easy to use function like this directly in FV Player together with some instructions to backup your website database before running such global search and replace.

Perhaps it could let you enter the source and target URL and show the preview of the changes by trying to load a single video from that new location to let you check if it plays. It would take a couple of days to get it done but it could be a nice tool for all the users.

Thanks,
Martin

Hello Bruno,

it seems to me we could build this using the wizard technology from FV Player Coconut. That way we could guide you through the process and avoid mistakes.

The first wizard step would only contain a description of what is going to happen. The seconds step would let you enter the URL part to replace – like https://bunnycdn-domain.com/bucket/

Then the third step would list the matching players making it easy for you to check what is going to change. There you could enter the new URL – to replace with: https://digitalocean-spaces-domain.com/bucket/

In fourth step you could check that same list of affected players in preview mode – already using that new URL and allowing you to test that it all appears properly.

Fifth step would only be a warning for you to backup the database or create site snapshot.

Sixth step would let you confirm the replacement.

Thanks,
Martin

Hello Bruno,

please reinstall FV Player from this ZIP file: https://github.com/foliovision/fv-wordpress-flowplayer/archive/3535016984-migration-wizard.zip

Then you will be able to click the button at wp-admin -> Settings -> FV Player Pro -> Tools -> Migration Wizard, at the top of the screen.

Once you run that you will be prompted for the part of URL to replace (https://bunnycdn-domain.com/bucket/) and the URL to replace with (https://digitalocean-spaces-domain.com/bucket/). It will provide a visual way of checking if the URLs are all right.

If this works fine for you we will make this tool part of the next release.

Thanks,
Martin

Hello Bruno,

that is the FV Player VAST plugin, which is different from FV Player. So the FV Player upgrade won’t cause any change there.

I see that the filter for the global configuration parameters of FV Player VAST could be useful, so I added a new “fv_vast_conf” filter for the upcomming release. You can get it right now if you reinstall the FV Player VAST plugin. Then you would only have to rename that fv_flowplayer_vast_args_pre filter hook name in your custom plugin.

Thanks,
Martin

Hello Bruno,

when reinstalling the plugin please first deactivate and delete the current FV Player plugin you are using. WordPress will warn you that you might loose settings and data, but it’s not the case with our plugin, no settings now videos will be lost. Or you can just replace the plugin files via FTP.

That will avoid the error.

Thanks,
Martin

Hello Bruno,

sorry about that, I see where I made a mistake. I’m working on a fix.

Thanks,
Martin