The 1.4.1 update seems to have fixed the issue for me. More testing this evening. Thanks.
Issues with 0.5.1
mootzville last edited by
@julian Am seeing this today in my ACP...?
Shard last edited by Shard
After seeing this I pulled off of the old 0.5.1 checkout I had and switched to the v.0.5.x and did the update procedure as documented.
I suspect either that was not the right way to go about this or something is amiss at the Circle K.
None of the admin routes except the general config and the plugins individual panels seem to exist.
Since I'm not anywhere near production this is mostly an inconvenience - but if I was "doing it right" I'd hate for someone else to be broken...
Any ideas what happened?
@Shard We'll probably re-release 0.5.1 with some updated changes tonight, but in the meantime, it sounds like your themes might be out of date?
Did you run
npm installafter switching to the
Im having mega issues on this "Stable" branch.
Had to reset to a previous git version to get anything stable.
Shard last edited by
@julian I did not, as that wasn't on the procedure - but there was the update which behaved similarly.
I fond the issue. I'm building up my own theme - which you might have noticed with all my other stupid questions - and I had fully copied over the vanilla theme and was hacking away at that... Including the admin. Nuked my themes copy and there you go.
So the old theme does not line up with the new build.
If you have a custom theme, just remove the
config.jsonto make it compatible with 0.5.1
I think that's it, let me know if that works for you
EDIT: Unless you customized the
templates/config.json, if so, there's a new hook from 0.4x that you need to use to modify that, let me know
forking this thread over to 0.5.1 (since the original topic is about 0.5.0)
Shard last edited by
@psychobunny I only blew away the admin folder. Didn't touch the config.json. Is that necesssary?
If you didn't change it, you can delete it, it'll just read the one from vanilla.
Yeah that file is being tracked in core now, so your theme's config.json will overwrite the core's version. Which is fine if you're doing it on purpose
it'll just read the one from vanilla
from core , it is no longer tracked in the vanilla theme
This seems to be in the Blog section?
@Ted does it?