Bug #5134
No static template found! message with multipage setups
| Status: | Resolved | Start date: | 2009-10-27 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Reinhard Führicht | % Done: | 100% |
|
| Category: | - | |||
| Target version: | Beta 4 (v0.9.7) | |||
| Votes: | 0 |
Description
On a multipage setup i get sometimes a
|No static template found! Make sure to include "Settings (formhandler)" in your TypoScript template!|
message in the body-tag of the root page where the template is not included, even if there is no formhandler-plugin on the page.
That forces me to include the ts-template on every page of the multipage installation.
That makes no sense to me.
History
Updated by Reinhard Führicht over 3 years ago
- Assignee set to Reinhard Führicht
The idea was that the static template is included on the root page. So it should work fine if you include it there, you won't have to include it anywhere else.
Updated by Joerg Winter over 3 years ago
The static template is included on the root page of one site but not on every root page of every site off the multisite install.
And i get this message sometimes (think it depends on caching) on the other root pages of the installation.
Updated by Reinhard Führicht over 3 years ago
Sorry, I misunderstood.
Yes, I know that this is not the best solution. I have another approach in mind that will not require the static template.
I will add this in the next weeks, but currently the way to go is to include the static template on every root page, sorry.
Updated by Joerg Winter over 3 years ago
OK after a look into ext_tables.php I understand the reason for the problem.
So I do the workaround and wait for a solution.
But I think it is not so usefull to have this message displayed on the frontpage.
Updated by Caspar Stuebs over 3 years ago
- File formhandler_addFields_predefinedJS.patch added
This issue is solved in trunk since revision 26628...
(svn log message: - No more static template needed)
But there is still an error message in the backend while installing a new plugin.
I attached a patch for deleting the error message.
Updated by Reinhard Führicht over 3 years ago
Static TypoScript is still needed when using the default form.
I have to find a suitable solution for this first before closing this issue.
Updated by Reinhard Führicht over 3 years ago
- Status changed from New to Resolved
- Target version set to Beta 4 (v0.9.7)
- % Done changed from 0 to 100
Committed your patch to trunk.
I guess, I can live with that solution. If somebody wants the default form, the static template has to be included.