Hi TheSickle and Matt,
we are getting the same issue. We reported it to ww.wp.xz.cn already and we are waiting for their reply.
Seems like a problem with their caching. I’m able to only download the plugin ZIP file on its latest version if I log in into ww.wp.xz.cn and download it in the same browser.
Perhaps we can tag the new version and then set the stable tag to it to speed up the fix?
Me too. I’ve tried 3 times now, deleting the old version and loading the new one via FTP. WP4.7.3 The WP dasahboard reports that Flowplayer is still using the previous version.
Hello all,
ww.wp.xz.cn staff is looking into the issue.
Thank you for your patience!
Hi,
Yes I think indeed its something general on ww.wp.xz.cn site, as I noticed few other plugins are having the same problem when updating.
Suggest to close topic as it is not related directly to your plugin in the end and ww.wp.xz.cn staff is already addressing the problem.
Thank you for the prompt reaction.
My site is NOT hosted on ww.wp.xz.cn but is hosted at 1and1. I have reverted to the true previous version 6.5.21 as it appeared I was also having some slow access issues in the main site but this may not be related. Currently working well with this version apart from the update flag. This is the only plugin that I have this issue with.
Guys, sorry for the hassle.
This is a ww.wp.xz.cn issue. They struggle to manage any transition of their production systems very smoothly.
If you are having issues with the version you have installed, please install an older version from the developer tab but in the new plugin directory there is no developer tab and the tools which are there are complex direct SVN browsers. The new plugin directory sucks and developers have been saying so for six months but our complaints fell on deaf ears of the Apollo team (set up to push through unpopular changes to ww.wp.xz.cn which Automattic and Matt Mullenweg want.
So basically until ww.wp.xz.cn works again you are a bit stuck. Ignore the update tag.
Thanks!
Alec
Just thought I’d post the fact that this issue seems to be solved now………..
Yes indeed it is fixed, I was able to update as well.
