Errors after installation (NuWiki import)

[Alfa1]

I'm installing Vaultwiki on a testing installation, which has a copy of my big board, including NuWiki. Installation itself was a breeze. Except that an error/warning was on the screen shortly. Im preparing for the importation of NuWiki > Vaultwiki. I must say that the instructions here should be expanded with the exact settings for each namespace and should define whether or not Vaultwiki should be enabled for the forum that needs to be created for books or templates.

Now when adding a new forum (for books), I get this error:

Warning: Cannot use a scalar value as an array in [path]/admincp/vaultwiki_namespace.php  on line 479

Warning: array_keys() [function.array-keys]: The first argument should be an array in [path]/includes/adminfunctions_options.php on line 422

Warning: Invalid argument supplied for foreach() in [path]/includes/adminfunctions_options.php on line 422

This is likely the same error as I saw before.

Every wiki shows about a hundred lines repeating this error:

Warning: Missing argument 3 for nuwiki_handle_bbcode_wiki(), called in [path]/vault/class/bbcode/autolink.php on line 350 and defined in [path]/nuwiki/nuwiki_plugins.php  on line 731

What do I do now?

[pegasus]

As long as it continued past it, you should be able to ignore the error when adding the new forum. It occurs when VaultWiki tries to update the cache too many times on the same page load. You can click the "Rebuild" link for the Book namespace to make sure everything was cached correctly.

As for the BB-Code error, ideally NuWiki should be disabled at this point. Right now there is a conflict because there are two definitions for the BB-Code "wiki".

[Alfa1]

Rebuilding any namespace gives the same error.

I have disabled NuWiki.

[pegasus]

Okay, after looking again I see that the line in question should not affect the namespace cache. It's trying to turn the wiki back on if it was disabled in vBulletin Options > VaultWiki: Server Settings > Turn on the wiki.

Not sure why that's happening because basically the error is saying that $vbulletin->options is not an array, but a string. This is possibly due to a conflict with another mod, but I'd like to do a few tests of my own. What version of vBulletin are you currently on?

You should be able to ignore the error if you manually make sure that setting is turned on.

[Alfa1]

The setting is turned on. I am on vb3.8.5

[Alfa1]

Just want to add that I have applied the fixes in the other thread, but the error above persists.

[pegasus]

Can you please list/link to any modifications that use admin_ hooks?

[Alfa1]

none of the plugins use the hook location admin_ hooks

[pegasus]

Can you clarify EXACTLY the process that results in the "cannot use scalar value as array" error? For this is occur, $settings has to actually be set to a non-zero numerical/boolean value somewhere and I'm not finding it.

[Alfa1]

Rebuilding any namespace will do it, but just now I rebuilt the default namespace and got the exact same error

[pegasus]

I trust this is still on the test-board. If you disable all other products, and attempt to rebuild the namespace, does this still occur? If not, re-enable them one-by-one and let me know on which product the conflict occurs.

[Alfa1]

I found it. The errors are a conflict with: Product : AWCoding- Back-End
This is the back end of the AWCoding Donation System. Version 3.0.8

AWCoding adds values to the object, but in no shape or form does it change it to a string.

The plugin in that affects Vaulwiki is the init_startup:

include(DIR.'/awcoding/plugins/awc.php');

How can this affect Vaultwiki? Its the standard add to object array.

[Alfa1]

Bug report was moved here:
http://www.vaultwiki.org/issues/1814/

Next build will have a fix.

Any idea when the next build will be out or if I can apply the fix?
Would be nice to advance on the conversion test. Looking good so far.