Some NuWiki import questions

In preparation of NuWiki > Vaultwiki import, I have the following questions:

A forum needs to be created for templates ( because I did not use this in NuWiki, but will need templates for Vaultwiki) and for categories. But where? Instructions state:

Quote:

Except for NuWiki islands and the forums mentioned above, move your other NuWiki forums such that they are children of the Default namespace.

So does this mean the template forum, forum_headers forum, books and the category forum will be subforums of the default namespace?
Or should no namespace be a subforum of the default namespace?

I have a forum for redirects. What to do with these?

I do not allow lower usergroups to edit wiki articles, but I do allow them to discuss wikis and to suggest content. For this I have a Wiki Discussion forum. This was a subforum of my main wiki section, but it seems it should be outside of the default namespace. Thoughts?

Whenever editing a forum in the forum manager, I get this message:

Quote:

The forum could not be added to the namespace. Create the forum with the Wiki mode disabled, and configure the namespace in the Namespace Manager to include this forum. You can then activate the forum's Wiki mode.

Changing the display order in forum manager doesnt work.

The image namespace is already included, but should it be? We currently use vb album attachments.

No namespace should be a forum of the default namespace. You can have your default namespace, template forum, forum headers forum, books, and categories forums all in the same parent category, but do not nest them within each other.

The instructions suggest to nest all NuWiki forums because in NuWiki you could only have 1 namespace.

You can move the redirect forum to inside the default namespace (as a sub-forum).

You can continue to use your Wiki Discussion forum if you want. You can use VaultWiki's permissions to achieve the same higher-usergroup-only editing. If you don't want discussions on articles themselves, this can be disabled on a per-namespace basis.

If you are trying to change a forum in the Forum Manager to Wiki mode, you must be making it into a child forum of an existing namespace first via the Namespace Manager. This ensures that all the wiki metadata is compiled correctly.

In the case where the forum is already defined as a namespace, you may need to "Rebuild" the namespace first to reconstitute the cache. Check that the Namespace Functions in the bottom of the Namespace Manager are assigned correctly. Otherwise it depends on the specific forums you are modifying.

As for the Image namespace, if you don't plan on using it for now, then you can go ahead and delete it.

Im afraid I made

I cant move forums associated with a namespace. I Have created a new Wiki parent forum, to place all namespaces in. But asides the wiki discussion forum, I am not able to move any of them.
My Template forum is associated with the template namespace. No templates have been added to it. Its not a child of another namespace. But won't move.
My default namespace will not move.

When trying to edit namespaces, I encounter this error:

Code:

Database error in vBulletin 3.8.5: Invalid SQL: INSERT INTO vb_postlog (postid, useragent, ip, dateline) VALUES (864055, 'Mozilla/5.0 (Windows; U; Windows NT 6.1; nl; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6'); MySQL Error : Duplicate entry '864055' for key 1 Error Number : 1062 Request Date : Wednesday, July 14th 2010 @ 10:56:10 PM Error Date : Wednesday, July 14th 2010 @ 10:56:14 PM Script : /forum/admincp/vaultwiki_namespace.php?do=rebuild&namespaceid=9&meta=398,177&types[0]=0&types[1]=1&parents[0]=398&parents[1]=177&postcache=,9 Referrer : /forum/admincp/vaultwiki_namespace.php?do=save Username : Alfa1 Classname : vB_Database MySQL Version : 5.0.90-log

Im confused. How do I fix this? Do I need to start over?

Try this. In vault/plugins/data/forum.php, find:

Code:

if (!$okay)

Add before:

Code:

if (!$okay AND $data->existing['forumid']) { $vault->unserialize('vault_namespaces'); foreach ($vbulletin->options['vault_namespaces'] AS $space) { if ($space['forumid'] != $data->existing['forumid']) { continue; } $okay = true; } }

That works.

Deleting a forum within the default namespace lead to this error:

Code:

Database error in vBulletin 3.8.5: Invalid SQL: DELETE FROM vb_vault_forummap WHERE FIND_IN_SET(397, parentlist); MySQL Error : Unknown column 'parentlist' in 'where clause' Error Number : 1054 Request Date : Thursday, July 15th 2010 @ 12:25:19 AM Error Date : Thursday, July 15th 2010 @ 12:25:20 AM Script : /forum/admincp/forum.php?do=kill Referrer : /forum/admincp/forum.php?do=remove&f=397&s= IP Address : Username : Alfa1 Classname : vB_Database MySQL Version : 5.0.90-log

It seems to be gone now though.

To get past the post-log errors, you will want to make the following change. Not sure why this is needed in vB 3. IMO, the postlog should use INSERT IGNORE or REPLACE.

In vault/dm/revision.php, find:

Code:

$threadman->set_info('skip_first_post_update', true);

Add after:

Code:

$threadman->set_info('skip_moderator_log', true);

Sorry, for the separate posts. Will be moving these to separate bug reports. To prevent future forummap errors, you will want to make the following change. In vault/plugins/data/forum.php, find:

Code:

$dataman->db_delete(TABLE_PREFIX, 'vault_forummap', $dataman->condition);

Replace with:

Code:

$dataman->db_delete(TABLE_PREFIX, 'vault_forummap', "forumid IN ($forums)");

I have 3 main NuWiki sections. 1 for each language. My English section is a normal Wiki namespace, while my Dutch and German wiki forums are Wiki Islands.
Each NuWiki section is currently in the forum category that relates to the language. i.e. English wiki in the English forum category, Dutch wiki in the Dutch forum category and German wiki in the German forum category.

Should I move these to become a child of the main namespace? I do not want them to interlink to each other, but I do want the Dutch and German wiki to be imported.

Also: Does it matter if the wiki forums: books, category, templates, forum headers have the 'Forum is Active' setting set to 'no'?

If "Forum is Active" is set to "No", I believe you wouldn't be able to create any new pages in those forums. If you don't want them to receive comments, you should be able to set this at the namespace level.

If the Dutch and German wikis are NuWiki islands, they should be automatically imported as VaultWiki islands without any extra configuration on your part, so they would still be unlinkable.

After importing, if you wish, you will be able to associate them with their English/Dutch/German translations so users can easily switch between them. This feature was overlooked in the last Manual update, but it is an option on each page's Apply tab.

Optimally, I would like to have each language version create autolinks in the related forum category. Is this possible and how do I accomplish that?

It is not possible to create autolinks like this in VaultWiki 3, since those wiki areas are not linkable and you can only autolink from one namespace in VaultWiki 3.

In VaultWiki 4, you might consider making Dutch and German wikis into their own namespaces. If this were true, it would be an interesting feature request for VaultWiki 4: to have a forum setting for choosing what namespace autolinks are taken from, rather than always using the default/current namespace.

Yes, that would be an optimal solution.

Quote:

Originally Posted by pegasus

It is not possible to create autolinks like this in VaultWiki 3, since those wiki areas are not linkable and you can only autolink from one namespace in VaultWiki 3.

In VaultWiki 4, you might consider making Dutch and German wikis into their own namespaces. If this were true, it would be an interesting feature request for VaultWiki 4: to have a forum setting for choosing what namespace autolinks are taken from, rather than always using the default/current namespace.

Is this feature request in the tracker already or do I need to add it?

I don't think it's in there. Wouldn't hurt to add it; if it's a duplicate, I'll mark it when we get around to working on it.

Added