Bug #18049
closed
Submodules of Web module can't work with mod.php and the _DISPATCH system
0%
Description
When using the new mod.php system for backend modules, problems arise when module is a submodule of Web module.
Error is like:
Value "web_utestmodM1&id=123" for "M" was not found as a module.
Create extension with kickstarter, add a module as submodule of Web module.
Change conf.php, ext_emconf.php, index.php as described by docs.
Select module from the list works ok.
As soon as you select a page in the page tree you get something like:
Value "web_utestmodM1&id=123" for "M" was not found as a module.
(issue imported from #M7265)
Files
Updated by Andrea Boselli about 16 years ago
Whops, made error in writing down report.
The error I get is:
Value "web_utestmodM1?id=123" for "M" was not found as a module
(Notice the ? instead of & I wrote earlier... btw, THIS is the problem)
Updated by Christian Kuhn over 15 years ago
I remember a similar issue that lead to this error message and it had been solved.
However I just created a tiny test extension (just a submodule of web) and can not confirm the mentioned error in current trunk (rev 4024) now.
I think we can close this one.
Updated by Dmitry Dulepov over 15 years ago
Nope, we do not close. I confirm the bug. The problem is related to page tree.
Updated by Steffen Kamper over 15 years ago
the bug isn't complicate. The only error page-tree does is adding
?id =xyz
So the Url looks like
mod.php?M=web_txtemplavoilaM1?id=1
correct would be
mod.php?M=web_txtemplavoilaM1&id=1
I will dig into and make a patch
Updated by Steffen Kamper over 15 years ago
committed to trunk and 4_2, rev 4570 / 4571