Acorn issue on shared host

[cim]

@alwaysblank

In theory, sure. So far as I know, the docs don’t recommend using Acorn as a plugin, though. In fact doing so is explicitly not officially supported:

Thanks, yes I mainly read that as ’ it should probably work’ when I originally made the move to Sage 10 (from 8). But it is not as common a use case as it used to be in this community I feel.

@alwaysblank

just run it locally with --no-dev and then upload vendor. Acorn is, essentially, just a composer package. If you can install other composer packages and they work, Acorn should also work.

I tried that, see my answer to log1x which I’ll post in a minute

@alwaysblank

If the cache contents are incorrect, either the thing(s) that should be writing to them aren’t working, or they can’t write to the cache directory (i.e. permissions issues). Either of which are the problems you should be looking at.

That’s what I figured too. Acorn is able to write to cache though, so I don’t think it is a permissions problem

@alwaysblank

Yes, see above. Even if this “works” it’s not going to work.

I got the idea to sync the cache to the server from a post in this thread, so it seemed like a viable approach:

@QWp6t

It also just occurred to me that you could probably get around this issue all together if you precompile your views. Use wp acorn view:cache prior to deployment. You might consider checking out other commands that generate PHP cache files, such as for configs and providers. Acorn 2.x: WP-CLI | Roots Documentation