[solved] Site not working: resourceMap and aliasMap are empty in context.cache.php

I use to clone my production sites to have copies for development. I have it automated by a bash script to help myself and it used to go without any problems. The steps are the following: upgrade MODX core from GitHub for the clone site, sync [tt]core/components/[/tt], sync [tt]core/packages/[/tt], dump source site db and import it to clone db, perform upgrade from CLI.

Now, I've got a problem with recent clone. The cloning operation went as usual but the cloned site doesn't work: the resources can't be accessed except of home resource, which displays its content but no navigation (by Wayfinder).

The error log contained nothing until I set [tt]log_level[/tt] to [tt]3[/tt]. Then it filled with the following warnings with ids of resources to be listed by Wayfinder:


I cleared the cache manually but the [tt]context.cache.php[/tt] has [tt]resourceMap[/tt] and [tt]aliasMap[/tt] arrays empty! The source site works without problems. I've run [tt]$modx->reloadContext('web')[/tt] and rebuilt aliases using this script to no avail.

The source site is running MODX 2.3-dev from GitHub "develop" branch; the clone was switched to MODX 2.6-dev from GitHub "release-2.2" branch commit [tt]aad71df[/tt]. FURLs and alias_map are on.

The clone site is just that, a clone with exactly the same settings as source. Why it doesn't work? [ed. note: gadamiak last edited this post 13 years, 11 months ago.]

You cannot run the develop branch and then switch back to an older branch (release-2.2). Develop is work in progress and not necessarily (rarely, if ever) fully backwards compatible with current stable releases.

Switching the site back to "develop" branch fixed the problem and the site is working again. Thanks!

Quote from: opengeek at Nov 05, 2012, 06:42 AM

You cannot run the develop branch and then switch back to an older branch (release-2.2). Develop is work in progress and not necessarily (rarely, if ever) fully backwards compatible with current stable releases.

I stumbled upon this mistake as well, as I was accustomed to using the Nightly downloads, but was surprised to see 2.3.0-dev...

Is it safe to assume the Nightly builds will continue to be based on the "develop" branch, rather than the next minor release?

Quote from: pixelchutes at Nov 16, 2012, 05:12 PM

Quote from: opengeek at Nov 05, 2012, 06:42 AM

You cannot run the develop branch and then switch back to an older branch (release-2.2). Develop is work in progress and not necessarily (rarely, if ever) fully backwards compatible with current stable releases.

I stumbled upon this mistake as well, as I was accustomed to using the Nightly downloads, but was surprised to see 2.3.0-dev...

Is it safe to assume the Nightly builds will continue to be based on the "develop" branch, rather than the next minor release?

develop is always representative of the next minor release, i.e. 2.2.x, 2.3.x. Patch releases for current minor releases will always be built from a release branch (e.g. release-2.2) and we make pre-releases of these available for testing when significant updates are available, separate from the Nightly builds from develop.