Moderator’s note: Split from this thread.
Not to hijack an older thread, but I believe I’ve run into a similar issue.
I’m working on a site with the MSM to manage sites for different divisions. The various divisions’ sites are identical in terms of structure, but may have different content. For example, each division will have a “People” page that lists all of the staff members for that division. The template is the same, but the content will, of course, be different.
At some point, our I.T. staff moved the site—which is still under development (so sorry, I can’t divulge the URLs)—to a different server, and so I’ve been trying to deal with various issues related to that. I’ve fixed most of the issues, but this one has me baffled.
I’ve created a template called “people” that will contain the aforementioned “People” page. It is located inside a template group called “about-us”. In that template, I’m calling embedded templates from a “master” site, such as header and footer info, using this method:
{embed="site_short_name:template_group/template"}
(Since the sites are identical in design, this made the most sense to me.)
However, when I go to the “people” template in a browser, it’s broken. The embedded templates don’t render, or they render incorrectly.
On a whim, I created a brand new template called “personnel” in the same template group. I copied the code from the “people” template and pasted it into the “personnel” template, without changing a thing. When I pull up the “personnel” template in a browser, it renders just fine.
At first, I thought there might be a caching issue, but I’ve emptied the cache on both this site and the “master” site several times, to no avail. And I can’t think of any settings that might be causing this.
Of course, I could simply use the “personnel” template instead of the “people” template, but that doesn’t really fix the issue. I’d like to know what might cause this, in case I run into it again.
Don’t hesitate to post a new thread if necessary.
