Closed GwendolenLynch closed 9 years ago
I was away on holiday until yesterday
Zero stress mate, we all have real lives and I just figured you were ultra busy.
Am I missing something?
Depends on the last time you did a git pull && composer update
. We have done a tonne of moves, as well as a bunch of changes with Composer installed vendor libraries.
Let me know if you're still stuck, happy to help :-)
I pulled in the latest master, ran a composer update
and cleared the cache, just double checked again and still no luck. No worries for the time being though, I'll try setting up a fresh bolt installation sometime this week.
If, in the meantime, you could try installing the latest menu editor on your end (tag 2.0.1) and verify that it's properly working and in line with the bolt extension requirements, that'd be great.
Yep, as soon as Ross' latest PR lands, he's broken stuff :-)
Great, thanks =)
Confirmed working, both install and accessing the admin menu!
There is another couple of PRs about to land too that fix a couple of other corner cases that may or may not affect you... Bob will declare beta-3 a green light at that stage.
Awesome. Okay, waiting for beta-3 and will try again with a fresh installation. Thanks!
On 03.11.2014, at 19:43, Gawain Lynch notifications@github.com wrote:
Confirmed working, both install and accessing the admin menu!
There is another couple of PRs about to land too that fix a couple of other corner cases that may or may not affect you... Bob will declare beta-3 a green light at that stage.
— Reply to this email directly or view it on GitHub https://github.com/bacbos/bolt-menu-editor/pull/2#issuecomment-61526231.
Turns out a space in the directory name of my virtual hosts caused all the trouble https://github.com/bolt/bolt/pull/2204
Hi Gawain
Thanks a lot for your PR and sorry for getting back to you so late - I was away on holiday until yesterday :)
I merged your patch along with a minor update so the menu editor now runs again smoothly with the latest bolt codebase. However, I'm unable to install the extension (or any other extension really) through the backend. The extension log keeps saying:
Am I missing something?