Hello Digitalpoint, congratulations for this great tutorial. I am very interesting at the part "CMS Article Caching", I use vB 4.0.2 but in the file article.php I find a similar code: if (!$view->pagetext = vB_Cache::instance()->read($md5_key)) { $view->pagetext = fetch_censored_text($bbcode_parser->do_parse( $this->content->getPageText(), vBCMS_Permissions::canUseHtml($this->getNodeId(), $this->content->getContentTypeId(), $this->content->getUserId()), $this->content->getHtmlState() )); I tried to change it with your code but than my CMS give error and doesn't works well. Have you suggest for this problem please? Thank you
yui 2.8.1 was released www. yuiblog.com/blog/2010/05/05/3-1-1-and-2-8-1-released/ (had to write it so, because i'm not allowed to use links^^ ) Maybe you should change 2.8.0 to 2.8.1
Hello, I resolved last my request, sorry I am seeing with "Page Speed", addon Firefox, than the vB CMS of default has a value more low of Forum, have you other interesting advice to improve it? Thank you
When I replaced the YUI from 2.7.0 to 2.8.1 the facebook login thing disappeared and the sidebar control stopped working
Not sure why that would be the case since 2.8.1 should be backwardly compatible with 2.7.0. But if it's causing issues for you, just go back to 2.7.0.
Shawn, at the Drop FULLTEXT Indexes, do we need to change anything? Or just a copy/paste at phpMyAdmin will do? Actually, I am concerned about ALTER TABLE thread ADD INDEX [COLOR=Red][B]forumid2_dp[/B][/COLOR] (forumid, visible, sticky, dateline); Code (markup): Does that need to be changed? I mean, I can't find any forumid2_dp at thread table.
You can name the index anything you want... I just named mine that so I remember I added it. The index name itself doesn't matter.
Nice, Bookmarked, I'm still stuck with the vb 3.8.5, I think I should consider the big move. Thank you !
These article shows a lot information about vB. I really should say that this is really nice. Thank you for this, it might help me so much. - Fusie
I have joined this site primarily to give a big thanks for this article. However having looked around fantastic site too
http://www.vbulletin.com/forum/entr...grow-performance-data-model-changes-in-vB-4.0 http://www.vbulletin.com/forum/entr...Optimization-Basic-Guide-to-InnoDB-Conversion Its all about InnoDB, and your saying NOT to convert to that?
Correct. It's better to solve the problem with WHY queries are causing table locks. The solution isn't to make table locks tolerable. We converted all the vBulletin InnoDB tables to MyISAM here and use 100% MyISAM tables at this forum (except for the MEMORY ones of course). InnoDB tables actually make things slower if you don't have problems with table locking (we don't).