vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 4.x Add-ons (https://vborg.vbsupport.ru/forumdisplay.php?f=245)
-   -   Add-On Releases - Important Links In Navbar v3.00 (https://vborg.vbsupport.ru/showthread.php?t=259636)

ozzy47 10-14-2013 12:36 AM

You are running vB v4.1.12 correct? Did you try to upgrade recently and then downgrade?

tbworld 10-14-2013 12:40 AM

His board says v4.2.2 in the header, but his Javascript says v4.1.12, so I was going to ask a similar question.

tbworld 10-14-2013 12:57 AM

If your plugins are disabled and you reverted the correct 'navbar' template then you should not be seeing your old navtabs. So one of the two items has not been completed correctly for your test. Thanks for posting your link it was a big help. :)

Arrogant-One 10-14-2013 01:20 AM

Quote:

Originally Posted by ozzy47 (Post 2453070)
You are running vB v4.1.12 correct? Did you try to upgrade recently and then downgrade?

Yes, that's exactly what I did.

Arrogant-One 10-14-2013 01:20 AM

Quote:

Originally Posted by tbworld (Post 2453073)
If your plugins are disabled and you reverted the correct 'navbar' template then you should not be seeing your old navtabs. So one of the two items has not been completed correctly for your test. Thanks for posting your link it was a big help. :)

Oh, you wanted me to disable the plugins and THEN revert. I will try that.

Arrogant-One 10-14-2013 01:24 AM

I disabled the plugin by adding the line to config.php

I then tried reverting but it won't let me. I get this message:

Quote:

This template has not been customized in this style or any of its parent styles.

Double-click the template name or click the 'Customize' button to add a customized version of this template to the current style and its child sets.

Last edited March 28 2012 at 17:12 by vBulletin Solutions

ozzy47 10-14-2013 01:29 AM

Quote:

Originally Posted by Arrogant-One (Post 2453077)
Yes, that's exactly what I did.

Ok here is what I would do.

1) Turn your site off.

2) Make a full backup, just incase something goes wrong.

3) Re-upload the files that came with your v4.2.2 zip.

4) Run the upgrade script.

5) Then get a copy of v4.2.1 Pl1 upload those files to your server.

6) Turn on debug mode by adding the following to your includes/config.php
Code:

$config['Misc']['debug'] = true;
7) Go to ACP --> Settings --> Options --> Version Info and Other Untouchables, and change ONLY the setting, vBulletin Version Number to 4.2.1

8) Turn off debug mode by removing the following to your includes/config.php
Code:

$config['Misc']['debug'] = true;
9) Remove the install directory.

10) Turn your site back on.

Now you will be upgraded to v4.2.1 and not have to worry about the 4.2.2 and PHP errors.

Arrogant-One 10-14-2013 01:46 AM

Quote:

Originally Posted by ozzy47 (Post 2453080)
Ok here is what I would do.

1) Turn your site off.

2) Make a full backup, just incase something goes wrong.

3) Re-upload the files that came with your v4.2.2 zip.

4) Run the upgrade script.

5) Then get a copy of v4.2.1 Pl1 upload those files to your server.

6) Turn on debug mode by adding the following to your includes/config.php
Code:

$config['Misc']['debug'] = true;
7) Go to ACP --> Settings --> Options --> Version Info and Other Untouchables, and change ONLY the setting, vBulletin Version Number to 4.2.1

8) Turn off debug mode by removing the following to your includes/config.php
Code:

$config['Misc']['debug'] = true;
9) Remove the install directory.

10) Turn your site back on.

Now you will be upgraded to v4.2.1 and not have to worry about the 4.2.2 and PHP errors.

Thank you my friend, but when I tried upgrading to 4.2.2 after the Syrian Army hacked my 4.1.12, it completely messed up my site. So bad, that I needed to call the host to get a back up (and they only had one from 2 months ago). Pretty much everything is working on my forum now, except for this navigation issue.

I suspect, but don't know for sure, that simply using a navbar template for 4.1.12 will solve the problem, and that's the preferred route to re-upgrading and messing with the ftp files again.

I will click the heart for you because you have been gracious towards me and I appreciate that. Thank you.

ozzy47 10-14-2013 03:05 AM

Hopefully that will work, but there may be issues that could pop up elsewhere.

tbworld 10-14-2013 03:33 AM

I tend to agree with @Ozzy47, you board might not be in a known state. Keep the backups for a while, just in case.


All times are GMT. The time now is 09:13 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01188 seconds
  • Memory Usage 1,742KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (4)bbcode_code_printable
  • (5)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete