Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Thomas Widmann

    (@complexli)

    Actually, I seem to have one issue with it: The recipes don’t turn up on the front page (like regular posts). I’m guessing that’s because they’re not posts, but something more similar to pages? Is there any easy way to make them appear everywhere a post would?

    Thread Starter Thomas Widmann

    (@complexli)

    Wow, that’s brilliant! Thanks a lot – it does exactly what I want. I think the only thing I’d like to add now is a +New->Recipe in the logged-in header (like +New->Post).

    This problem still exists, and jQuery Migrate Helper certainly shouldn’t be a permanent solution – so we really need a new version that works with the Classic Editor without requiring jQuery Migrate Helper. It might just be a case of getting rid of the call to jQuery.fn.live().

    For those of you having this problem, first, relax. You’re not really on a “development” version. The only difference here is the displayed version number. It just happened to have the wrong version number in the files. That’s it. The files themselves are not dangerous. Your site is not broken.

    I understand that the problem started with 3.9.1 GB identifying itself as ‘4.0-alpha’, and that this didn’t cause any problems per se.

    However, when my site got upgraded 4.0-alpha-20140508 five hours later, surely that was a real alpha version? Which means that once this error has happened once, you’re stuck with alpha versions until you fix the error, and that your site could in the worst case get broken until you fix the problem as described above.

    Just wanted to say that it happened to me too. A production site got upgraded to 3.9.1 GB 13 hours ago and then to 4.0-alpha-20140508 5 hours later.

    I’m now back on 3.9.1 GB after following the advice above — hopefully it won’t “upgrade” me to a development version again.

    I’m a bit worried for all the production sites whose admins don’t read this thread. How many people have now suddenly started using beta versions without realising and without knowing what to do about it? I think WordPress needs to roll out a new beta test version that asks admins whether they want to move back to the stable release.

Viewing 5 replies - 1 through 5 (of 5 total)