I want to get an overview, how a page that is requested from a user, is generated in XOOPS. I look up the most things in the wikidoc and tuts around, resp. in the forum… regarding the last point, the forum, I have to thank everybody who takes some time and answer questions to new (and old) users (that, sometimes, were often asked before)... Perhaps there’s a lack of documentation in XOOPS but the community and support, so far, is really great...


So far what I think about the generation of pages… (nothing cached in template_c)

- User site request… index.php (or other)
- PHPParser go trough index.php and included classes (nearly the whole system except not needed modules and blocks, I guess) with authentications and functions…
- PHPInterpreter starts with index.php over mainfile.php, common.php… we get to xoopsblock.php that sum up the blocks that have to be displayed and includes smarty
- Smarty generates the HTML for each block and caches them in the template_c
- Smarty fetches the single theme_block.htmls, the compiled blocks and put the blocks into the theme_block.htmls. Again smarty compile them as html and put them in the template_c
- Now Smarty fetches the compiled block-html-files and the theme.html, put the blockfiles into the theme.html compile it and put the compiled theme.html back in the template_c
- Now common.php includes header.php and footer.php, which also includes the xoopsblock class and again smarty…
- Anywhere here the php-interpreter gets the theme.html go through the php code generated by smarty with references to the other needed html-files and fill in the needed contend and functionality with data from the database and server (e.g. images, interpreted php-module-classes)
- server sends requested file with needed blocks, modules… back to the user…