WebsiteBaker Support (2.13.x) > General Help & Support

Lets dump .php pages files

<< < (2/2)

sternchen8875:
tip: search in your archive for modules with a file "WBReorg.php". Every module with this file has the possibility, to work with subpages and this file rebuilds the access-files, if you send the request for this in the wb-info-window.

i use it also in some private modules in different list's to build subpages for detailed information about a item, but i use a switch in the module settings (for every section), with or without subpages. "without" means, i display only a overview, item by item. "With subpages" means, every item has a "Read more"-Link
Works like OFA

CodeALot:
I think it's a good idea, it will make a cleaner file- and database structure overall.

crnogorac081:
What would be challenging is that we will need to deal with show_menu2  then too, because some time ago I was helping forum member here to make another sm2 function, because he has big site with like 3-4000 pages and it was challenging to me because I have similar project, and you can see how slow loading is here and this is all because it takes time to load menu.

I analyzed show_menu2 function and it checks menu item one by one: if page is visible, then if page is for registered viewers etc, and this is all few DB calls per menu item, so it would be much faster if menu function would work like this:

1. check if there is any page set for viewing groups and users (you can do this with 1 DB query and if these fields are empty for all pages dont check this anymore, or if there are fields populated for some pages put them in array for further check)

2. a new procedure where _pages table would have like column "active" with true/false - so when page is added (first section) make it false, and then when you finish go to Sections and Activate page (check if section is active and date is between publish start / end).  This would be much easier and faster for menu loading.

Navigation

[0] Message Index

[*] Previous page