vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   Modification Graveyard (https://vborg.vbsupport.ru/forumdisplay.php?f=224)
-   -   Administrative and Maintenance Tools - vB Database Backup Pro (Lite) for vb 3.6 (https://vborg.vbsupport.ru/showthread.php?t=126925)

BadgerDog 08-10-2007 12:15 PM

Hi Paul.... :)

I assume since my Client API version says it's 5.0.24a, I should change this option below to "0"?

// Backup Optimizations
$backup['MYSQL4'] = 1; // Set to 1 if you are using MySQL4

Thanks

Regards,
Badger

kenfuzed 08-10-2007 02:16 PM

I posted this question a couple days ago but now I have the actual error to go with it.
PHP Code:

Warningpreg_replace() [function.preg-replace]: Compilation failedregular expression too large at offset 65539 in /includes/functions.php on line 555 

This error line repeats itself 50+ times down each forum page before the actual content is shown. This only occurs right after running the backup job, but not every time which is making it difficult to track down. It is cleared by toggling the forum off/on.

Here is my original question:
Quote:

Originally Posted by kenfuzed (Post 1312921)
This may be unrelated to the backup itself, but right after this runs each morning my db/site seems to be having trouble restarting correctly. This doesn't happen every time but lately has occurred several times per week. Only the forumhome page starts correctly but all other pages have errors and won't display their content (just lines of errors). When I go in and turn vB off then back on, all pages display correctly. The errors occur right after the backup completes. Is there a command I could add to the end of the backup config file that would perform this restart procedure after the backup is completed?


Paul M 08-10-2007 07:38 PM

I would guess there is some problem with the vboptions not being saved properly when the board is turned off/on by the mod.

I would just turn that option off in the config file (I don't use it).

(set $backup['SHUTDOWN'] = 0)

BadgerDog 08-10-2007 11:42 PM

Quote:

Originally Posted by Paul M (Post 1314690)
I would guess there is some problem with the vboptions not being saved properly when the board is turned off/on by the mod.

I would just turn that option off in the config file (I don't use it).


(set $backup['SHUTDOWN'] = 0)

Hi Paul.... :)

Question on a different option setting ...

I assume since my Client API version says it's 5.0.24a, I should change this option below to "0"?

// Backup Optimizations
$backup['MYSQL4'] = 1; // Set to 1 if you are using MySQL4

Thanks

Regards,
Badger

Paul M 08-10-2007 11:58 PM

It's actually an option for mysql4 or above, so you can leave it set to 1.

raiderlax 08-11-2007 05:21 AM

I really don't recommend people to install this, I know it royally screwed my site up, thank goodness for backups!

Deimos 08-11-2007 05:29 AM

Quote:

Originally Posted by raiderlax (Post 1315017)
I really don't recommend people to install this, I know it royally screwed my site up, thank goodness for backups!

How so? Works fine for me.

Paul M 08-11-2007 04:17 PM

Quote:

Originally Posted by raiderlax (Post 1315017)
I really don't recommend people to install this, I know it royally screwed my site up, thank goodness for backups!

I suggest you provide some solid proof to backup this claim.

raiderlax 08-11-2007 07:00 PM

Quote:

Originally Posted by Paul M (Post 1315262)
I suggest you provide some solid proof to backup this claim.

You are right, I should provide solid proof of this, but I have already re-stored my site and am not going to re-install this mod to prove this, in fact I didn't really have to re-store the site, I could have just uninstalled the mod and things would have been fine, I just didn't know at first it was this mod that caused the problems on the site.

Some problems were header links missing and a lot of functionality missing on the site.

So now I will spend some time fixing up the site only because I had previous mods installed that have got messed up from re-storing the site, but if you do have problems like ones I have mention uninstall this mod to see if it is it(in my case it was) and do not go ahead and restore all your forum files like I had done :(

Other than that I like the idea of the mod and the way it was working until these problems arose.

da420 08-11-2007 07:13 PM

I've had this installed since back in October when it was first released without any problems whatsoever.


All times are GMT. The time now is 01:38 AM.

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.01899 seconds
  • Memory Usage 1,752KB
  • 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
  • (1)bbcode_php_printable
  • (5)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (2)pagenav_pagelinkrel
  • (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