..You’ve never the Recent Entries or any other object dynamically shown unless you do Rebuild of the system, of the entries, or of the pages in which you want the new result.
Is it true? Only when you rebuild the blog you see updates.
If it’s true, the new templates schema is completely useless for a weblog, sadly.
Reported on Movable Type 4.2
Questo non E' vero. Ho tentato spiegarsi che come sta utilisando <mt:Include> non E' come era intendito utilisare in questo situazione. Quello comando solamente E utilisando includere un Template Module in un Index Template. Dimentichi la documentazione ed acceti che lo sta importando piu o meno essatamente lo che vedi nel Module al Index Template.
Le nostre lingue sono una problema qui. Non parlo molto Italiano, e non posso avere una gran conversazione in Italiano, ma non posso spiegarlo in Inglesse e questo E' la mia ultim'opzione per spiegarla prima finisco da mancanza di optzioni.
Grazie Mike per il tuo tentativo di scrivere in italiano - thanks. :-)
Anyway, if I'm not wrong, I should have found a way to obtain the Recent Entries updated on each entry/comment submission!
That's the old method I used, in confidence, nothing new (to include a dynamically generated file among all website pages-that makes not needed to rebuild all to see changes)
Forget the documentation on this for now. The Include tag does a raw text dump of the contents of the SHTML file into your other templates. All of the code inside the SHTML is simply copied into those templates. That is what this tag is for. Obviously the SSI attribute isn't working for you, so use a work around here of setting it up yourself. It is either that or your templates will continue to get the SHTML contents merged into them, which is the last thing you want.
If you seriously believe you have a bug, then write it up and submit it here. Make sure that you give them a detailed description of how your templates are built, how they output, etc.
If you don't just accept the work around and move on, you will just keep beating your head against a wall.
One last point, as this is the last thing I can say that may make it clear:
If you have an index template that generates the SHTML file, and other files that read in the SHTML file, you have a cross dependency in your situation. This makes no difference when you are using your own PHP or SHTML import commands, but when you use <mt:Include> you are including the contents of the SHTML file into almost all of your templates as a raw text dump before MT has a chance to update it.
This might not ALWAYS be true, but it is certainly good enough for government work, and good enough for most everyone else, as a reason why you need to write your own import statements that will do the real SHTML or PHP include/import operation.
This is true what you write. In effect I've reached my target, because the SHTML content now is included in every page and entry, and since the SHTML content is changed each time, I've the recent entries updates reflected on all website.
But there's a theorical problem that you say about. It's not really a dependancy, but a small delay. When I save a new entry or a comment, the MT engine writes down the SHTML with the new data.
In that moment, the user won't see the changes, but in a while the SHTML will be updated - in that moment it's the SSI inclusion that works: all pages include the SHTML and in real time show the updated entries.