-
I’m unable to create any new FV Player records in WordPress. It keeps saying, “Error saving changes.”
-
-
Hello Francis,
We’re sorry to hear you’re experiencing these issues.
Please, try installing this plugin: https://wordpress.org/plugins/error-log-monitor/ Then try to save a player again and see, if any error appears in it.
You can also check PHP error logs directly on the server. If you are not sure about it, the server technical support should be able to give you a hand.
Thanks,
MariaHello Francis,
please also send over content of wp-admin -> FV Player -> Settings -> Tools -> System Info. That will tell us if there is any issue with the database tables.
Next thing is to look at wp-admin -> FV Player screen to see if your player was actually added. It’s possible that it saves properly but then it runs into a conflict with other plugin and reports the error.
Thanks,
MartinLooks like it maybe triggering these errors:
499 POST /wp-admin/admin-ajax.php?action=as_async_request_queue_runner&nonce=d6a605015a HTTP/2.0
403 GET /wp-json/jetpack/v4/jitm?message_path=wp%3Atoplevel_page_fv_player%3Aadmin_notices&query=page%253Dfv_player&full_jp_logo_exists=false&_wpnonce=86f1fb26c0 HTTP/1.0
====
Its not creating any player records from what I can see.Here is the system info: https://www.dropbox.com/t/s1osSdM99B1zt6j9
Hello Francis,
unfortunately these errors are not related. The first one is some WP Ajax call made by other plugin and the second one is JetPack.
It seems you found this in the web server access logs, but to diagnose the issue in detail you have to check the PHP error logs. The plugin which Maria mentioned can be useful if you want to see the log entries in your wp-admin, otherwise you can still check it in the logs.
Thank you for the System Info – it appears you have many instances of FV Player saved in the database. Did this issue only start occurring recently?
Thanks,
Martinyes it was working fine then just stopped…
Don’t really want to install the app if I can help it here is the error log:
Hello Francis,
I see there is a “Illegal string offset ‘percentage'” warning in your BuddyBoss theme in themes/buddyboss-theme-child/learndash/ld30/template-single-course-sidebar.php.
But that should not affect anything unless your website is set to show PHP errors in HTML. Please ensure that the PHP errors are not shown in HTML, your web host support should be able to help.
You can also try to switch to some other theme temporarily, it might help.
Then there are also some requests blocked by ModSecurity. Please try to disable that or ask your web host support to disable that to see if it helps with the issue of FV Player Editor not saving.
Thanks,
MartinThe mod firewall is only on detect only, so shouldn’t block traffic but switched it off anyway. The child theme error I know about, and this error doesn’t occur in wp-admin when I’m trying to add a video in fv player admin page so I think we can discount those. But the error is still occurring. Cloudflare is in front of the site but tried disabling that temporarily just in case as well and doesn’t seem to affect it.
Hello Francis,
it’s too bad that the error logs show nothing that could explain why the FV Player save operation fails.
Could you please check the following in the browser?
-
First go to wp-admin -> FV Player
-
Do a right click on the page and pick the “Inspect” option. A new panel on the side of the browser or at the bottom of it will appear.
-
In this panel switch to “Network” and clear the log if there are any items – see the attached fv-player-editor-save-troubleshooting-1.png.
-
Then click “Add new” to start adding a new FV Player and put in some video URL. The Network tab will show an
admin-ajax.php?fv_player....request, as seen on fv-player-editor-save-troubleshooting-2.png. Make sure it does not appear in red and the Status is “200”. -
When you click into that request in the Network panel it should show a nice looking response in the “Response” tab – see fv-player-editor-save-troubleshooting-3.png.
-
Clicking “Preview” tab should show the output properly formatted, see fv-player-editor-save-troubleshooting-4.png.
If the output shows empty and the code is not 200, but for example 500, then there has to be some fatal PHP error which the logs are not catching.
In that case please try to switch to some other PHP version for a minute, in different version the logs may work better.
We are also happy to fix this issue with priority right on your website if you order our Pro support: https://foliovision.com/pro-support
The next troubleshooting step would be to try disabling individual plugins, I can do that very effectively using some PHP code and WordPress filters (
option_active_plugins).Thanks,
MartinThanks found the issue. Seems like Cloudflare Superbot checking is blocking the request. But even if I switch everything off it seems to be still blocking it?! I’ve raised a case with cloudflare, fingers crossed they can figure it out.
Ok figured it out. It wasn’t the superbot but the cloudflare managed WAF rules were tripping it up. Added an exception and now it’s working!
Thanks so much for the help!
Hello Francis,
if you have a moment could you please let us know what managed WAF rules you have used? Was it some default or are there any presets?
Also, what exclusion rule you had to put in? I don’t think we do anything special with FV Player, but if the video saving request was detected as suspicious, I would like to know why.
Thanks,
MartinIt’s just the out of the box managed WAF rules from cloudflare so nothing I’ve added in the rule sets are:
Cloudflare Managed Ruleset
Cloudflare OWASP Core Ruleset
Cloudflare Leaked Credentials CheckLooks like it was the Core ruleset that it was being caught on:
Here is the rule I added. Posting it in a message rather than in the forum so I can expire the dropbox:
Hello Francis,
thank you for the follow up.
I think these OWASP rules might simply not like the way we use
?fv_player_db_savein that Ajax URL. It serves no purpose and was only there for some debugging in the early stages.So I tried removing that. If you could reinstall FV Player from this link https://foliovision.com/downloads/fv-wordpress-flowplayer.zip and see if you still run into issue with it, that would be great.
If that won’t work, I’ll have to put
?fv_player_db_saveback in place for youOtherwise it seems the OWASP rules do not even like that we send the JSON data. Perhaps we will have to find a different way of encoding it.
Thanks,
MartinI’ve found it’s failing on other calls that you are making to it without the ?fv_player_db_save. TBH, if you had fv_player_db_save on all the calls or something so I could determine that the call has come from fv_player then that is easier. I can add a URL exception that includes the ?fv_player. But without it, there is no way of telling if the call is coming from fv_player or something else. Ideally, I would only want to white-list the fv_player calls until you have a fix for the OWASP triggering issue rather than whitelisting everything and other apps making calls to it.
Hello Francis,
I see, so we are keeping
?fv_player_db_savefor now.I will concentrate on improving the way we handle the JSON data.
Please let us know what other calls are failing. It might be the player cloning or export, but I can’t think of anything else using JSON data.
Thanks,
MartinYup will keep an eye on it.
Hello Francis,
with the next major release of FV Player the editor data will use a proper JSON format for saving. That should avoid breaking these OWASP rules.
It will also no longer use URL ending with
admin-ajax.php?fv_player_db_savebutadmin-ajax.php?action=fv_player_db_save.Thanks,
MartinFab thanks! I’ll let you know when I upgrade or post a message to remind me when its released :)
-
