(WARN @ /index.php) `xxxx` was requested but no alias was located.

Thanks Bob, that def helped. The errors are gone, and now when I refresh my home page, I get these new errors. Any idea if these are related to the prior issue?

[2014-08-14 22:19:29] (ERROR @ /var/www/hampshireco.com/htdocs/core/model/modx/modx.class.php : 959) PHP warning: array_key_exists() expects parameter 2 to be array, null given
[2014-08-14 22:19:29] (ERROR @ /var/www/hampshireco.com/htdocs/core/model/modx/modx.class.php : 962) PHP warning: array_key_exists() expects parameter 2 to be array, null given
[2014-08-14 22:19:29] (ERROR @ /var/www/hampshireco.com/htdocs/core/model/modx/modx.class.php : 959) PHP warning: array_key_exists() expects parameter 2 to be array, null given
[2014-08-14 22:19:29] (ERROR @ /var/www/hampshireco.com/htdocs/core/model/modx/modx.class.php : 962) PHP warning: array_key_exists() expects parameter 2 to be array, null given
[2014-08-14 22:19:29] (ERROR @ /var/www/hampshireco.com/htdocs/core/model/modx/modx.class.php : 959) PHP warning: array_key_exists() expects parameter 2 to be array, null given
[2014-08-14 22:19:29] (ERROR @ /var/www/hampshireco.com/htdocs/core/model/modx/modx.class.php : 962) PHP warning: array_key_exists() expects parameter 2 to be array, null given

I think that's because the URIs are not in the current alias_map. I think if you log out, delete all files in the core/cache directory, and log back in, those error messages will stop.

Make sure those resources have an alias, though. An empty alias could also cause this.

Thanks Bob for the solution. But I think this should be automatically handled by MODX.

Quote from: BobRay at Aug 15, 2014, 12:05 AM

I think that's because the URIs are not in the current alias_map. I think if you log out, delete all files in the core/cache directory, and log back in, those error messages will stop.

Make sure those resources have an alias, though. An empty alias could also cause this.

Thanks Bob, I tried but no luck. I'll keep digging around, thank you for the help!
Anthony

@acaffiero: Check the uri field of those resources in the DB.

@gadgetto: MODX is supposed to do that during the upgrade, but it looks like for some combinations of versions, it doesn't happen.

Here's something you can add to SiteCheck: does the modx_site_content table have a cache_refresh_idx index?

Any somewhat recent version of MODX (starting with 2.2.5?) expects it to. Without it the caching system won't build resource and alias maps and things start breaking in strange ways. The view button opens a blank page, you get erroneous "`X` was requested but no alias was located." warnings (even when resource X has a proper alias and uri) and so on. Looking in core/cache/context_settings/web/context.cache.php reveals empty arrays for 'resourceMap' and 'aliasMap'.

In acaffiero's case this index wasn't present in 2.2.4 and didn't get added in the upgrade to 2.2.15.

It's simple to add. Another work around is to turn off cache_alias_map in System Settings then clear the site cache.

Good to know. That makes three (maybe four) things I know of that don't happen in some upgrades.

1. Creation of the cache_refresh_idx index in the modx_site_content table
2. Creation of the modx_extension_packages table
3. Creation of the 'name' field in the modx_context table
4.? Creation of the extension_packages System Setting

What concerns me most is that when you jump over versions in an upgrade, MODX is supposed to apply all the intermediate upgrades. If that's not happening (and it sure looks like it's not), were in for a whole lot more trouble. [ed. note: BobRay last edited this post 12 years, 1 month ago.]