Issues with 0.5.1

julian

@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 install after switching to the v0.5.x branch?

Scuzz

Im having mega issues on this "Stable" branch.
Had to reset to a previous git version to get anything stable.

Shard

@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.

psychobunny

If you have a custom theme, just remove the admin folder and config.json to 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

psychobunny

forking this thread over to 0.5.1 (since the original topic is about 0.5.0)

Shard

@psychobunny I only blew away the admin folder. Didn't touch the config.json. Is that necesssary?

julian

If you didn't change it, you can delete it, it'll just read the one from vanilla.

psychobunny

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

? Offline

This seems to be in the Blog section?

julian

@Ted does it?