Re, Billyben Ring
Maybe I’ve done smthg wrong, but no idea…
Nah, sometimes the SVN gets weird.
The readme looks good. The fact that the download link points to version 1 (which isn’t a real version – 1.0 is, but not 1) is really odd! I mean http://downloads.wp.xz.cn/plugin/billyben-rings.1.zip doesn’t even exist!
I would drop an email to [email protected] and hopefully someone can kick it for you!
I’m having the a similar problem my Virtual Theme plugin is stuck two versions back.
Tried emailing [email protected] but haven’t heard a thing.
There’s one person who picks up those emails. Sometimes you have to wait a while and be patient. Sucks, but there it is.
After searching the forum I’ve found a lot of people randomly having this problem. Some of them have mismatched numbers or forgot to add a tag for the version but many seem to have everything set up correctly.
Maybe the svn/version/zip generating thing should be looked at if it is really this flaky and there is only one person that can fix plugins that get stuck. I’ve found reports going back a couple years, so it’s not a new problem.
Don’t mean to be critical, but I don’t see any reason why this couldn’t be a rock solid process instead of the flaky mess it is. Maybe I am missing something.
Nah, you’re not critical, the issue comes and goes. At it’s root, I THINK it’s a problem with the servers and how they’re caching data, but I’ve yet to be granted a peek behind the curtain 😉
I can tell you this: The WP engineers who built this site ARE aware of the problem.
Same thing here with FPW Category Thumnails plugin. Changed to new tag 1.2.3 and it is still showing 1.2.2 ( over 24 hrs now ).
Went back to normal 5 mins. ago.
Virtual Theme finally updated sometime last night.
Just so I am sure I understand. That “fix” was just some temporary thing and there is still an underlying problem that may result in future updates not showing up?
Pretty much. It’s a known issue that’s being worked on. It really shouldn’t ever lag more than an hour or so (I think the sync is hourly). When it gets THAT out of whack, though, an email to plugins@ is the best thing to do. Which is a really lousy answer, I know.
