VaultWiki has been the only commercial solution explicitly vBulletin forum owners to launch a wiki since its launch in 2008. Since that time, free lite alternatives have emerged, and have circulated some bad reviews about the product - specifically in relation to ease of configuration issues.
Today, the eggs cracked Studies launched a new series in the VaultWiki family VaultWiki 2.5.x. Despite having developed almost in secret, 2.5.X is probably one of the largest and expected changes in the product so far.
Many of the changes we see in VaultWiki 2.5.X were, until recently, 3.x, scheduled for later this year. However, it would only be compatible with 4 vBulletin 3.x, which seems to have been delayed for at least another 2 months. And rather than force their customers to update and wait for a new product vBulletin, cracked eggs along 2.5.x. Studies
The level of difficulty for customers new to wikis in general has been historically high. In his own fault, cracked eggs Studies waited almost a year before compiling all the official documentation for VaultWiki. However, even with documentation, VaultWiki remains a complicated product to set up, to the frustration of many users - is "Namespacing" to be particularly difficult.
Previously, users create the wiki wiki forum categories and forums, edit each name names Manager, find that their forums were not valid, they have to use different settings, and then move to another area of the AdminCP VaultWiki names that say it is.
In 2.5.X, VaultWiki the installation process has been simplified names. Restrictions on the wiki forums have been removed, so most of the new forums will be available in the Name Manager. If an administrator wants to use a new forum, rather than jumping to the Forum Manager, the administrator can choose a "Create a New Forum" option. To configure the namespaces as "default", "Category", "image" or, instead of jumping to the Options page in vBulletin, the file appears in the form of building names, and may be changed later by the Website Manager names.
Another source of confusion has been the use of books. In the past, an editor would have to visit another name and create a gap in the books before they try to add any chapters. However, if there is a book, an editor, you can select "Add a new book's chapter-being.
VaultWiki has always boasted about its search engine optimized URL structure. Unlike most default vBulletin URL VaultWiki uses the page title on the road. In the past, the URL of the wiki page using a URL coded in PHP function, thereby changing the spaces and special characters + sign in a string of numbers% and forgettable.
2.5.X now VaultWiki eliminate the use of special characters in place of the rules, configurable via the new URL Manager Wiki. Administrators can now choose to replace the blanks with the characters -, _, or + characters. The new URL is compatible with the old URL, which means that any bookmarks "permanently redirect to the new location.
However, the new coding processes give rise to new constraints. Since many characters are stripped or converted to other, it is possible to have multiple titles at the same URL. For this reason, we now control the names of the existing articles on the basis of the encrypted channel and not the original title.
In the past, many editors of the articles created with similar titles to be redirected to one of the main articles. While this practice is still supported, some of the current automatically redirected to the main section to be resolved under the new URL of the application. Help managers to address this issue, the new administrator of the Wiki list of URLs of pages that must be solved at the same URL, and provides the tools to update or remove those pages.
VaultWiki 2.5.X attempts to reduce memory consumption and improve processing speed in a number of areas. The list of items in the cache as needed now, new fields of the database have been added to help the questions previously expensive, and many loops have been simplified or eliminated completely.
To save disk space and improve response times of the consultation, the revised text of former article is compressed in the database. In some tests, this resulted in a 80% to save disk space.
Users can now report offensive or SPAM wiki articles to moderators vBulletin using built-in reporting system. This link has been added to the dropdown menu next to each item in the title.
VaultWiki now follows suit with other vBulletin addons and added a copyright notice in the footer of every page that initializes the wiki. An additional fee must be paid to remove this notice.
Cracked egg Studios offers improvements on many fronts VaultWiki 2.5.x. Some of the code changes should increase the performance of the site, and the new Wiki URL encoding should result in better SERPS in the old URL. Although the name changed to the configuration and management of the books seem to simplify things, it remains to be seen how they react to new users.
Read more >>
Today, the eggs cracked Studies launched a new series in the VaultWiki family VaultWiki 2.5.x. Despite having developed almost in secret, 2.5.X is probably one of the largest and expected changes in the product so far.
Many of the changes we see in VaultWiki 2.5.X were, until recently, 3.x, scheduled for later this year. However, it would only be compatible with 4 vBulletin 3.x, which seems to have been delayed for at least another 2 months. And rather than force their customers to update and wait for a new product vBulletin, cracked eggs along 2.5.x. Studies
The level of difficulty for customers new to wikis in general has been historically high. In his own fault, cracked eggs Studies waited almost a year before compiling all the official documentation for VaultWiki. However, even with documentation, VaultWiki remains a complicated product to set up, to the frustration of many users - is "Namespacing" to be particularly difficult.
Previously, users create the wiki wiki forum categories and forums, edit each name names Manager, find that their forums were not valid, they have to use different settings, and then move to another area of the AdminCP VaultWiki names that say it is.
In 2.5.X, VaultWiki the installation process has been simplified names. Restrictions on the wiki forums have been removed, so most of the new forums will be available in the Name Manager. If an administrator wants to use a new forum, rather than jumping to the Forum Manager, the administrator can choose a "Create a New Forum" option. To configure the namespaces as "default", "Category", "image" or, instead of jumping to the Options page in vBulletin, the file appears in the form of building names, and may be changed later by the Website Manager names.
Another source of confusion has been the use of books. In the past, an editor would have to visit another name and create a gap in the books before they try to add any chapters. However, if there is a book, an editor, you can select "Add a new book's chapter-being.
VaultWiki has always boasted about its search engine optimized URL structure. Unlike most default vBulletin URL VaultWiki uses the page title on the road. In the past, the URL of the wiki page using a URL coded in PHP function, thereby changing the spaces and special characters + sign in a string of numbers% and forgettable.
2.5.X now VaultWiki eliminate the use of special characters in place of the rules, configurable via the new URL Manager Wiki. Administrators can now choose to replace the blanks with the characters -, _, or + characters. The new URL is compatible with the old URL, which means that any bookmarks "permanently redirect to the new location.
However, the new coding processes give rise to new constraints. Since many characters are stripped or converted to other, it is possible to have multiple titles at the same URL. For this reason, we now control the names of the existing articles on the basis of the encrypted channel and not the original title.
In the past, many editors of the articles created with similar titles to be redirected to one of the main articles. While this practice is still supported, some of the current automatically redirected to the main section to be resolved under the new URL of the application. Help managers to address this issue, the new administrator of the Wiki list of URLs of pages that must be solved at the same URL, and provides the tools to update or remove those pages.
VaultWiki 2.5.X attempts to reduce memory consumption and improve processing speed in a number of areas. The list of items in the cache as needed now, new fields of the database have been added to help the questions previously expensive, and many loops have been simplified or eliminated completely.
To save disk space and improve response times of the consultation, the revised text of former article is compressed in the database. In some tests, this resulted in a 80% to save disk space.
Users can now report offensive or SPAM wiki articles to moderators vBulletin using built-in reporting system. This link has been added to the dropdown menu next to each item in the title.
VaultWiki now follows suit with other vBulletin addons and added a copyright notice in the footer of every page that initializes the wiki. An additional fee must be paid to remove this notice.
Cracked egg Studios offers improvements on many fronts VaultWiki 2.5.x. Some of the code changes should increase the performance of the site, and the new Wiki URL encoding should result in better SERPS in the old URL. Although the name changed to the configuration and management of the books seem to simplify things, it remains to be seen how they react to new users.
