The {exp:pages:load_site_pages} tag is not very well documented in how you use it. Gleaning from system/expressionengine/modules/pages/mod.pages.php, what it does is merges the specified site's pages URIs with the current site's. It does this in runtime - not saving to config in the DB.

The fact that it is a template tag makes it less useful because the first segment of the URL has to be specified, directing EE to the template with this tag and then possibly the second segment could be used in conjunction with Pages URIs. (Haven't quite figured that out).

The problem I'm facing is our landing pages use the first segment for Pages URIs. So for example we have /about-us that hits a page with the designated template. I tried putting this tag on our site/index and on our designated 404 to no avail. How can you alter Pages URI functionality with a template tag when Pages URI functionality is triggered pre-template?

My question is, how in the world can I make Pages URI's from one site available on another site?

1 Answer 1


The only way I could find to do this was creating an extension which functions very similarly to this tag. Basically the extension I wrote will merge Pages URIs for the current site in with other sites you designate when you save an entry in EE Admin.

Its quite simple and makes Pages URIs available across sites in MSM.

This saved us having to copy channels, entries, categories etc to other sites when all we wanted was a few landing pages. We still needed MSM however to support the alternate template and some alternate variables/snippets.

I've shared my extension on GitHub and have also updloaded to Devotee as a free addon.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.