Import Troubles

[Kaelon]

This requires a plugin edit. In the VaultWiki plugin at hook search_complete, find:

special_search_complete(); 

Add before:

require_once( DIR . '/vault/special_plugins_search.php'); 

Great, thanks, that did it.

Still seeing that "Header for Header" appearing on some of my forum threads. For example:

http://www.playbypost.com/forums/com...ki-search.html

[Kaelon]

Thanks, those two moves fixed it.

[Kaelon]

Another bug/failure:

When trying to run the "Convert Articles" tool to update my old NuWiki syntax to the new supported CES Syntax, the server stalls out (even though I am only processing 50 posts per cycle). Help?

[Kaelon]

Another bug/failure:

When trying to run the "Convert Articles" tool to update my old NuWiki syntax to the new supported CES Syntax, the server stalls out (even though I am only processing 50 posts per cycle). Help?

When running this, my twin-dedicated server configuration saw its load averages jump to 1.99 and 1.76, respectively, with MySQL taking the principal brunt of the performance hit. Is this intentional? The process is still stalling on my end.

[Kaelon]

When running this, my twin-dedicated server configuration saw its load averages jump to 1.99 and 1.76, respectively, with MySQL taking the principal brunt of the performance hit. Is this intentional? The process is still stalling on my end.

Loads are still climbing: 2.19 and 2.17, respectively. Not a single update yet from the Admin CP > CES VaultWiki > Convert Legacy Code to BBCode function. It's basically been running for the past few minutes without a single update (even though I set it at 50 posts to process per cycle), so I have no idea where it is in the process or what it's even doing, but my site is essentially inaccessible in the interim.

[pegasus]

Did you uninstall NuWiki yet, or at least disable it? If you haven't that could be where it's coming from. You don't need NuWiki enabled to convert the syntax.

[Kaelon]

NuWiki has been disabled the entire time. The only script eating up this memory is vaultwiki.php, with no end in sight.

[Kaelon]

The Servers were brought down to a halt with a 22.39 load average each, and TOP assigned the blame to vaultwiki.php.

I'm uninstalling this and reverting to a backup.

[pegasus]

Well, I would stop it for now. This one is a bit puzzling, though. I don't see why your MySQL should take such a heavy hit, since it's going to run about 51 queries altogether on each pass (you have it set to 50). The only other thing it could be is that it's stuck in a legacy parser loop which also doesn't make any sense. We tested this on our own 1000 article database before this last build with no issues like this. I'll have to get back to you on this one.

I guess in the mean time you can enable the VaultWiki option to Support Legacy Code. It's not the ideal solution, but it'll have to do for now.

See this bug: http://www.vaultwiki.org/issues/283/