4.2 rc2
I'm having no luck with modules and SSI. The blog I am working on has PHP SSI set up and I've tried alternating between using module cache and not, but the modules don't republish unless I publish the templates they are included in. I've checked the files via FTP and they are not updating when I save them but the main templates do have the php include code.
I understand that there is a difference between saving and publishing, but with no way of publishing the updated modules alone then the whole use of SSI seems completely pointless.
One example of how I am using it:
I have a global header module that has navigation in it. If I decide to add a new link then I would like to update one template, rebuild that and not have to rebuild every single page/entry/archive/index.
Am I missing something or misunderstanding the concept?
This is exactly correct. I know it sounds weird, but because modules, regardless of whether they are server side includes or not, may potentially produce different HTML depending upon the context they are used, modules won't "rebuild" upon save.
So yes, in order for a module to be refreshed, you have to republish a page that includes it. Then it will be refreshed across your site.
Whether it is worthless - well, this is definitely something we can improve upon no doubt, but I have found SSI to increase performance a great deal. I too find the extra step a little annoying at times, truth be told, but I wouldn't personally go so far as to say that the extra step makes the entire feature worthless to me.
As a workaround, you can always publish an index template and include it via a PHP include. That will rebuild automatically whenever you save it.
Does that help?
Thanks for replying. I ended up going with index template PHP includes, using PHP to pass some variables to it (for things like page titles).
Your post made me understand the performance benefit though, so I can see when it would be useful. Thanks again!