No point having 3 $templatesused - combine them into 1 line.

Any template being eval() that's not in $templateused will be 1 query. No question about it.

To see exactly what queries are being run, add this line to your config.php file in your admin directory:

debug=1

Then run any php file with ?explain=1 at the end of the file, and you will see the list of queries being run.

Remember to remove that line from config.php - it's a security risk.

N9ne: that post was directed at hellsatan, not erwin ;)


to see the querys on any page add:

to the config.php file then put &explain=1 at the end of any url on your vbulletin you wish to see the query's for, remember to trun off debug mode when your done as it poses a risk.

Erwin you just beat me to it ;)

Isn't it done that way to kinda group them together for different circumstances? Ex - All templates that are used when a user is logged in are in one set, all templates for a guest are in the next set, and all templates used by both are in another (or something to that effect). I could be wrong about that, but I thought it was done like that for a reason.

its also just to make it easier to read, its not going to execute any extra queries or anything.

You can end up doing more table scans than needed if you combine all 3 queries as Anime-Loo said.

Forumhome page was : 38 Queries
Forumhome page is now : 32 Queries

Yey!:)

Satan

PPN - How would you do that?

Satan

I found something out guys...

If I were you, I would go through all your files, and add :

to the end of templatesused...

There are no end of files without it;)

Satan

In most cases that will actually slow things down (just a bit, but still). Think about how often that page is displayed, as opposed to how often it won't be. It's better to not have the template pulled from the database every time a page is loaded when it is only used maybe 2% of the time.

Have you looked at the vB files, recently if ever?

Have you seen how many times:

occurs?

Satan