-
When I tried saving a post it gave me this error message:
Fatal error: Out of memory (allocated 58195968) (tried to allocate 4507927 bytes) in /home/…/public_html/wp-content/plugins/fv-wordpress-flowplayer/controller/backend.php on line 1020
-
-
Hello Tao,
please let us know about the following:
1. are you using the latest version of plugin (2.1.35)?
2. is there any [fvplayer] shortcode inserted in the post you were saving?
3. is the video in the shortcode hosted on Amazon S3 and is it located inside one of the buckets configured in Settings -> FV WordPress Flowplayer -> Amazon S3 Protected Content?
4. the post should still be saved properly. Please check if the video checker works on the video when you view the post. There should be a “Checking video” message in the top left corner of the video and it should change to “Video OK” or “Video Issues” after few seconds.
If you buy our FV Flowplayer plugin license, we will be happy to fix this issue for you right away.
Thanks,
Martin
Hi Martin,
Please see the answers to the questions:
1. are you using the latest version of plugin (2.1.35)? Yes.2. is there any [fvplayer] shortcode inserted in the post you were saving? Yes:
[fvplayer src='my video url' width=640 height=480 autoplay=false embed=false]
3. is the video in the shortcode hosted on Amazon S3 and is it located inside one of the buckets configured in Settings -> FV WordPress Flowplayer -> Amazon S3 Protected Content?
We upload our videos to Rackspace cloud and use their CDN to serve the content. It’s worked up until the latest upgrade of FV player.
4. the post should still be saved properly. Please check if the video checker works on the video when you view the post. There should be a “Checking video” message in the top left corner of the video and it should change to “Video OK” or “Video Issues” after few seconds.
Looking at our existing posts with FV player the video checker is green/OK – we just can’t seem to post any new posts with FV player.
Hi tao83,
Thanks for the detailed report. We will get the out of memory issue sorted Monday or Tuesday at worst. In the meantime, please use 2.1.34.
Thanks for being part of Foliovision!
Hello Tao,
sorry about the delay, I forgot to subscribe on the thread.
I found a bug in how we check if the video is from one of the protected buckets. That could trigger too many video length checks and cause you issue. This was fixed and new version released – 2.1.37.
Could you please give it a try?
Thanks,
Martin
Hi Guys, Thanks for the quick response. I contacted my web host as well in the meantime to help make some adjustments to the Apache settings so it stopped that error for the time being.
I have also upgraded to 2.1.37 now and don’t seem to have any issues currently.
