Error when i edit a topic

[Keldaria]

Ok so I recently upgraded to VB 4.03 and then I purchased and installed Vaultwiki yesturday. I believe I followed the install setup documentation to the letter. It allows me to create new articles and transfers me to the edit page just fine but when I attempt to save the changes I get an error as follows

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /var/www/vhosts/hosted.3rdfleet.com/httpdocs/forums/vb/cache/observer/db.php on line 85

Honestly I'm somewhat confused about where to even begin looking for a solution

[pegasus]

That's a good question. The error suggests that it's a vB bug, but since you have a limit, try disabling Link Caching under Settings > Options > VaultWiki: Server Settings. Then try posting the same article as a regular post, then editing it. If you encounter the same issue, it's very likely a vBulletin issue.

[Keldaria]

no effect. Also noticed a neat little side effect that while it gives me that error it also duplicates the article, but even in the duplicated article the content isn't saved.. just the title

[Keldaria]

Also I don't really think its a vb error since the rest of the site functions fine and its only the wiki area's that seem bugged like this. If anything I'd say its an incompatibility error of some sort, is there anyway to allocate more memory? Is that a Server function or a VB thing?

[Keldaria]

Ok i've fixed it.

It was a server issue, I needed to allocate more memory to my php by modifying my php.ini file. It was set for 32mb and I upped it to 128mb

So far so good it seems,

[pegasus]

It's a server function, and can be changed in php.ini if you have access:

memory_limit = 32M

or in PHP using:

@ini_set('memory_limit', '32M'); 

If you have permission from the server owner to do so. '32M' is what I think your current memory limit is. DigitalPoint (a notable big-board owner who makes a lot of performance suggestions to vBulletin staff) suggests using at least '64M' if you're allowed to change the value.

The reason I think it's a vBulletin issue is that the function it failed on was a vB function, not a VaultWiki function, and USUALLY the function that finally throws a memory limit error is one that's involved in an inefficient loop. Except during the install process, VaultWiki doesn't directly access or modify vBulletin's cache object.

[Keldaria]

lol I seem to have beat you to the punch. but while I have you hear allow me to pick your brain on another issue that I've just now run into. My attachment system works fine for the rest of the forums but the attachment button doesn't function at all on the wiki... any ideas?

[pegasus]

That just means that somewhere on the page the Javascript is broken. This could be due to VaultWiki or a conflict with another script. Check the Javascript Error Console in Mozilla Firefox to see what's broken.

[Keldaria]

hmm not getting any errors off the console for the edit pages

[pegasus]

What about after you try to click the button for "Manage Attachments"...

[Jella]

I ran into this also and it was another plugin unfortunately so I had to decide what was more important... the wiki was

[pegasus]

What plugin was it? Perhaps there's a way to get both to play nicely.

[Keldaria]

What about after you try to click the button for "Manage Attachments"...

nothing.

Oh and Thats what I thought aswell Jella, but after disabling all mods it still has this issue. I think i'm going to try setting up a test board with a fresh VB install and Vaultwiki install with no other mods to see if my test board has the same issue, atleast then we'll be able to rule out another server issue.

for some reason I think that due to my previous bug with the memory, that something didn't install fully or correctly with VaultWiki since i'm also apparently getting an error message when I save changes to my namespaces, but unfortunately my webpage refreshes to fast for me to be able to catch exactly what the error message is

[pegasus]

Turn off Javascript in your browser before saving. Then the page won't refresh automatically and you'll have time to read the error.

In clientscript/special_assetmanage.js, find:

		VaultImageButton.selection = vB_Editor[VaultImageButton.essoc[e.target.id]].get_selection();

Replace with:

		var button = YAHOO.util.Event.getTarget(e);
			VaultImageButton.selection = vB_Editor[VaultImageButton.essoc[button.id]].get_selection();

Does this help at all?

[Keldaria]

Nope didn't do a thing,

oh and the error message I get when saving the namespaces is

Warning: Invalid argument supplied for foreach() in [path]/admincp/vaultwiki_namespace.php on line 1144