problem with multi quote
How to Backup before Upgrading to 4.0
Collapse
X
-
Easy, click the multi-quote symbol on each post you wish to quote then when done simply click reply to thread and it fills in all the posts, quoted in the editor below all the posts and you type your reply then hit post reply.
Glad this thread was useful
Former vBulletin Support Staff
Hacked recently? See my blog post "Recovering a Hacked vBulletin Site".
Thinking outside the box? Need modification support? Visit www.vBulletin.org and have at it!Comment
-
Just a quick note; I've released a Upgrade video for 4.0 and most of this is covered within however there is more valuable information within this thread for reference.
Former vBulletin Support Staff
Hacked recently? See my blog post "Recovering a Hacked vBulletin Site".
Thinking outside the box? Need modification support? Visit www.vBulletin.org and have at it!Comment
-
Thanks for the info..
On my test site I removed all mods and forgot some I guess and had to deal with them later on
My question now is it better to disable all hooks via config.php OR just simply remove all mods?
and when disabling the hooks and then reenabling them, should still remove the mods? If Yes, then why not remove them before the upgrade?
I am talking about upgrading from 3 to 4 by the way since most vB3 mods won't work in vB4
Thanks againTo be or not to be... Where the hell is the question????My psychiatrist told me I was crazy and I said I want a second opinion. He said okay, you're ugly too
Live vBulletin 4.2.0 Multilingual * Alpha/Beta vB 4 - vB 5 Tier 1A
CentOS 6.2 - Apache:2.2.15(Apache2Handler) - PHP:5.3.3 - MySQL:5.1.61
Xampp/Win-XP - Apache v2.2.21(Apache2Handler) - PHP:5.3.8 - MySQL:5.5.16
Comment
-
Wanted to raise this thread
Thanks for the info..
On my test site I removed all mods and forgot some I guess and had to deal with them later on
My question now is it better to disable all hooks via config.php OR just simply remove all mods?
and when disabling the hooks and then reenabling them, should still remove the mods? If Yes, then why not remove them before the upgrade?
I am talking about upgrading from 3 to 4 by the way since most vB3 mods won't work in vB4
Thanks again
Here's what I do:
- Check on the mods, see if they are updated for vB4 already or if the developer has posted soon etc.
- If there is no update and you don't plan on keeping the mod or having someone update it for you then uninstall it.
- If there is an upgrade then disable it in the product manager. If you plan on waiting for it to be upgraded leave it as most mods will use the old data in the new version
.
- Sometimes an old mod or plugin can cause an issue, I have ran into cases where an old vB3 style was the reason for error so if you don't need to reference any old styles then delete all your vB3 styles and use or make a default style before upgrading.
- I always disable mods in the system and then by adding in the line to the config file, once the upgrade is complete remove the disable hooks so the CMS and Blogs will work then upgrade any you have an update for and enable them and for the rest enable one by one to see if it's compatible if you could not confirm that beforehand.
Former vBulletin Support Staff
Hacked recently? See my blog post "Recovering a Hacked vBulletin Site".
Thinking outside the box? Need modification support? Visit www.vBulletin.org and have at it!Comment
-
-
Former vBulletin Support Staff
Hacked recently? See my blog post "Recovering a Hacked vBulletin Site".
Thinking outside the box? Need modification support? Visit www.vBulletin.org and have at it!Comment
-
Comment
widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Comment