thebigboss, and why didn't you say that you are part of the vBPortal team (scotsmist)
If you look at the hundreds of fixes that are currently posted in the vBP support forum, and since these fixes are not yet integrated in the currently downloadable Beta 1, I must say that it is anything BUT NOT STABLE.
Btw, even wajones agrees with me that vBP 3 Beta 1 is not stable enough for a live system.
I thought it was common knowledge (it is know, )
it doesn't actually say it isn't stable enough. On the contrary, the Credits say the opposite.
the issue around installing on a live site is a simple one, its to seperate vbportal issues from vbulletin issues and not spend time looking for needles in haystacks.
Quote:
vbportal is fully capable of 100 + queries..
, but we are talking about vbportal 3.0 and its well capable of 15 querys. 100+ applys to phpnuke modules such as web_links, downloads, encyclopedia (150+), classifieds in their 'unconverted' state. Every module for vbportal 3.0 uses 6 querys for a no-permission page and 1-3 querys per modules content, again depending on where your viewing, then whatever blocks. The blocks can be cached, so its down to the individual laying out each module and what blocks they want, displayed where, remembering that every module can have its own blocks in the left right and center columns, in their own weight and its own templates if you want.
Quote:
Quote:
Originally Posted by thebigboss
If your just 'dropping' unconverted nuke modules in place, they would be using whatever number of querys the module is coded with and some of them go into the hundreds on a single page. How do you propose to keep the query count down then, if your not changing the phpnuke core code ?
I've given this a great deal of thought too. I'm considering releasing the PHPNuke 7.1 based version as the beta and using CPG-Nuke as the basis for the final release.
So VB3Nuke Final Version 1 would also encompass all of the CPG-Nuke improvements:
CPG Nuke Core Features
CGP-Nuke C...
I meant how are you going to keep down the number of querys the phpnuke modules and blocks use, if its using phpnuke modules in a drop in form ? the downloads, with 10 categories and 10 subcategories in each will produle 100 querys just to open the downloads index page on any system, unless you redo the code. it loops inside loops querying the db.
What do you propose to reduce the downloads module producing 100+ querys when viewing the index page or the encyclopedia module producing 150+ querys ?