V4 auto updater error: Cannot get contents of path, the path is invalid
News and General
First time posting, I’ve got a site that’s been upgraded in the last year or so from V2… to V4.
The full error message:
Update Stopped Oops, looks like the updater couldn’t complete. We stopped on Preflight check. Cannot get contents of path, the path is invalid: /www/eh22851/public_html/themes/ee/
Well, eh22851 is two servers ago. Last time I tried to figure this out I downloaded most of my ee system folders (including index.php and config.php) and did a text search for that server name … nothing, of course. In the early days of V4 I saw a thread about this being a problem.
I’ve been able to do manual upgrades, but why should I? Any ideas where the updater would be grabbing this path so I can fix this? Thanks.
Still happening today trying to get to v5.2. Sigh.
Make sure your theme path is valid for each site in your install.
My main website paths are are legit at /cp/settings/urls.
I downloaded my ee and themes directories and text-searched for the old server reference with no luck. This site is 12 years old on EE, there is a bunch of old stuff lying around, and could be a rogue setting somewhere. Where else would the path be saved?
Do you have an override in your config.php? Try removing that and then see if all your paths look right in the control panel. The updater might be pulling from the database instead of the config for some reason.
It continues to be a mystery. I have a custom ‘system’ folder rename/override and renamed index.php. I looked thru the EE database, I don’t know where a themes-path reference would be stored.
The themes path would be stored in the site_system_preferences column in your sites table. It’s tricky to edit though, you need to base64-decode it and carefully edit the serialized array, which there are tools online to help you with, and then re-encode everything back.
That solved it, but not in the way I expected! I had multi-site set up in the past, the preferences for the old site were what was tripping these up, it has to be. When we upgraded from 2 to 3, we didn’t set up multi-site, so EE doesn’t even know it exists … except when running an upgrade, apparently it looks at exp_sites. I’ll wait for v5.2.2 to see if it works for sure. Thanks Kevin.
Ah that might be it! Yes the updater simply loops through sites in the sites table, but doesn’t account for if you have multiple sites but have MSM disabled, perhaps an improvement could be made there. Thanks!
So I deleted the extra db entry, and ran the updater for the newest release. It ran !!!, and stopped :(
No such property: ‘logger’ on EllisLab\ExpressionEngine\Legacy\Facade
Again, I feel like a special snowflake having issues with my old site. Nothing really online to give a hint about it.
Hrm- I’ve seen that with the old jquery plugin, which was removed. But I don’t think that’s it. What version are you getting to? If you look in the config.php, what’s the current version number you’re stopped on?
Make sure your admin.php and system/index.php are up-to-date, too.