MODX Staff
Well, it’s a bit more complex than that, and at the moment there is not an API function for this, but you can look it up within a specific context by using something like this, assuming friendly URLs are being used:
is there a Modx API function call that returns a resource id, if you pass it a URL to a resource?
I’m sure Modx must do this internally, in order to display resources.
<?php
$uri = 'path/to/resource/';
$resourceId = 0;
if (array_key_exists($uri, $modx->aliasMap)) {
$resourceId = $modx->aliasMap[$uri];
}
// etc., etc.
?>
MODX Staff
That is correct.
This is perfect. Thanks, Jason!
I guess that the array that you’re referencing is read from context.cache.php, right?
☆ A M B ☆
MODX Staff
Hi,Any site with a large number of Resources will be affected by the aliasMap footprint. The amount of memory required of every request to load the map becomes too much, and the benefit of quickly looking up the URIs from this map is negated. This is why I introduced the cache_alias_map Setting in 2.2.7, which includes two new API methods for abstracting how you look up Resources by uri or id...
I just used this way and it worked well.
But I just wondered something.
While some of the packages start to use resources to hold their custom contents, let's say some e-commerce packages, will this aliasMap generation slow down the whole site?
$resourceId = $modx->findResource($uri, $contextKey);
$uri = $modx->context->getResourceURI($resourceId);
☆ A M B ☆