vb.org Archive - Major Additions - VaultWiki: A Wiki for your forum

Page 4 of 13

« First

Last »

Show 40 post(s) from this thread on one page

vb.org Archive (https://vborg.vbsupport.ru/index.php)

- Modification Graveyard (https://vborg.vbsupport.ru/forumdisplay.php?f=224)

- - Major Additions - VaultWiki: A Wiki for your forum (https://vborg.vbsupport.ru/showthread.php?t=239377)

thincom2000

08-19-2010 06:36 AM

There is no separate demo for the Lite version. I use a wiki on my site for company info, and would rather not open that up to allow everyone to edit. I don't have enough vBulletin licenses to create a dedicated demo site for free mods.

This is why I've linked to the commercial version site, because they have a demo there. The link contains a feature comparison so you know what features you see in the demo that you will be getting with the Lite version. On the feature compare page, click the "screenshots" link to see some screens.

morrow

08-28-2010 03:38 PM

I have a question... Is there an option in the pro version to add google maps along with a map marker or something like that? I'm seriously considering this product.

Thanks!

thincom2000

08-28-2010 11:24 PM

This is not a built-in option. The wiki by default is not a map add-on, but it should be relatively simple to use a Google-Map custom BB-Code from vbulletin.org (if one exists), and place that in your articles.

DAMINK

08-29-2010 06:12 AM

http://www.ftw.net.au/fileuploads2/1...33_Capture.gif

I am getting this error. Even after rebuilding namespaces. Effectively cutting me off from my forum under the admin account.
Anyone know how to get around this?

*fixed it. I had not created a forum and thus the namespaces could not be rebuilt correctly.
Now when i post an article they come up with Default: followed by the thread title. How can i fix that?

thincom2000

08-29-2010 03:42 PM

In AdminCP > VaultWiki > Wiki Namespace Manager, edit Default and set "Prefix Namespace Title?" to "No".

betts02

09-10-2010 10:13 AM

Has anyone got some instructions on how to use this with the lite version ?

Just want some help in actually getting it set up and used to it

Cheers in advance

thincom2000

09-11-2010 11:39 PM

Sorry, but what exactly are you trying to use with VaultWiki Lite? You didn't post the link.

Merjawy

09-12-2010 10:05 AM

Quote:

Warning: Invalid argument supplied for foreach() in [path]/vault/special_plugins_newpost.php on line 352

This is what I get when I click on any article on my CMS page even when I disabled the mod from vBulletin Options

I get that error at top of article page and but I can read the page fine

I have the mod disabled now and still see the error message

thincom2000

09-12-2010 04:29 PM

In vault/special_plugins_newpost.php, find:

Code:

foreach ($vbulletin->bbcodecache AS $removekey => $bbcode)

Add before:

Code:

    if (

        $allow_custom_bbcode AND

        (

            strpos($toolbar_template, 'quickreply') === false OR

            $GLOBALS['show']['phpkd_vbaqr_active']

        ) AND

        $toolbar_template != 'editor_toolbar_off'

    )

Merjawy

09-12-2010 04:56 PM

Quote:

Warning: Invalid argument supplied for foreach() in [path]/vault/special_plugins_newpost.php on line 359

Now another error

and the comment box layout is messed up both times

thincom2000

09-13-2010 05:09 AM

Do you have any custom BB-Codes appearing in the editor when you try to post a new thread?

If you only see the default BB-Codes, your BB-Code cache might be corrupt. In this case, go to AdminCP > Custom BB Codes > BB Code Manager, and click Edit for any BB-Code. Then click Save.

If you have no BB-Codes because you deleted them all, then this is the problem. In this case, you should not have deleted the ones that were installed by VaultWiki.

Stefanus

09-19-2010 08:46 PM

Quote:

Originally Posted by Stefanus (Post 2028615)

Thanks.

https://vborg.vbsupport.ru/attachmen...1&d=1272473655

The "Rate This Page" alignment is off:

The problem arise when "Store CSS Stylesheets as Files" is set to "Yes"

Quote:

Originally Posted by thincom2000 (Post 2029774)

It wouldn't make a difference what the setting is, it would pull from the same CSS templates.

Nope, there is a definite difference in the way it renders the page.

thincom2000, can you look into this issue again?

Quote:

css linked saves bandwidth, download time for your users, and will remain chached for every page. having it inline will effectively slow your site down to your users by 25% or more.

1. Store CSS StyleSheets as Files
By default, vBulletin will store the CSS of your pages as HTML within the head of the document. This, when taken over thousands of pages, can be quite a heavy burden.
Storing CSS Stylesheets as files will allow users/spiders to cache the CSS as a file, and make each page smaller, HTML wise, giving your server a bit of a breather.
To begin, ensure your forums/clientscript/vbulletin_css directory is chmod 777 so the stylesheet files can be created.
Next, in the AdminCP, select the vBulletin Options menu then vBulletin Options.
Select Style and Language Options.
Set "Store CSS Stylesheets as Files?" to Yes.
Click Submit.

thincom2000

09-20-2010 05:32 AM

Have you upgraded VaultWiki or vBulletin at all since this started happening? If you were using CSS files during the upgrade, it should have rebuilt them. The only way this would happen for CSS files, and not for inline CSS too, is if your CSS file cache is not up-to-date.

Try visiting vault/install/finalupgrade.php while CSS is enabled, and run through the process. You may have to clear your browser cache as well.

I am still not experiencing any issue on my test site and I'm storing CSS as files...

Stefanus

09-20-2010 08:20 PM

Quote:

Originally Posted by thincom2000 (Post 2100817)

Started with:
VaultWiki v3.0.0 Lite - vBulletin? Version 4.0.2
At the moment on:
VaultWiki v3.0.6 Lite - vBulletin? Version 4.0.6
Would say had quite a lot of version "upgrades" during this time!

Cleared all "browser cache" run vault/install/finalupgrade.php while CSS is enabled, no difference at all, problem still there.

When "IE8 Compatibility View" is on, the page renders correctly with storing CSS as files to Yess, otherwise not.

thincom2000

09-20-2010 09:34 PM

This occurs only in Internet Explorer 9 beta when using a Document mode that doesn't match your Browser mode. This causes problems parsing the Internet-Explorer conditional tags because the browser now has 2 conflicting version numbers.

Make sure the Developer Tools menu is open when you are changing versions and you'll see that the option "Force IEx Document mode" doesn't change the version numbers correctly. You want to change both versions from this toolbox together.

I think the Document mode affects DOM parsing, and the Browser mode affects CSS/JS parsing. If these two numbers are out of sync, then yes, you will have problems.

If the Document number is too high, conditionals for style (CSS) tags that only affect IE7 won't parse.
If the Browser number is still IE7, then it will follow IE7 CSS rules, but doesn't have them because the style tag wasn't parsed.

If the Document number is too low, conditionals for style (CSS) tags that only affect IE7 will parse.
If the Browser number is still IE9, then it will follow IE9 CSS rules, but the IE7 rules were loaded above, and IE7 CSS is "broken" in non-IE7 Browsers.

This isn't something VaultWiki has control over, it's just something you have to keep an eye on when you're messing with your Debug menu.

Stefanus

09-21-2010 05:30 PM

Quote:

Originally Posted by thincom2000 (Post 2101172)

This isn't something VaultWiki has control over, it's just something you have to keep an eye on when you're messing with your Debug menu.

Yip, but it does not account for FF or any of the other browers doing the same with the css.

A quick fix for this problem would be to copy vw-tabbed.css into the additional.css, (this rectifies the problem, and shows that there is a problem with "/vault/special_plugins_css.php") but how do you disable vw-tabbed.css in this case?

Hope this leads you to the root of this problem, and a stable fix!

donjuevas

09-21-2010 07:04 PM

I have been using the commercial version for a few months, and while there is a bit of a learning curve with the product, it runs well, integrates flawlessly, and support has always been johnny on te spot with an answer.

thincom2000

09-22-2010 11:42 PM

Just released 3.0.7, which fixes the following issues:

- infinite redirect for URL with space after colon
- Title with entities always counts as changed
- article missing after AJAX title edit
- flood check breaks inline moderation
- CSS order when stored as files
- TABLE BB-Code creates broken HTML

mitch84

09-23-2010 05:32 AM

thank you for update

Stefanus

09-23-2010 04:35 PM

Thanks! :)

Crimm

09-29-2010 05:25 PM

Freaking awesome mod. *tagged*

bposner

10-01-2010 08:52 PM

I don't see the paging options or any way to make chapters? or article display options.
How do I make a lead in page like a regular wiki? I see it on your site demo. No history tab? what am I missing?? :)

Thanks

thincom2000

10-02-2010 06:23 AM

I don't think the Lite version has any Paging Options or Article Display Options.

As for making a lead-in page, one is not included in Lite, but you might be able to set it to one of your articles by editing the forum and putting the URL as the "Forum Link" setting.

You should have a history tab on your articles. Check your Usergroup Permissions to make sure you are allowed to view it.

Crimm

10-14-2010 01:49 PM

Bought the Pro version. This is a great mod!

thincom2000

11-23-2010 02:14 AM

Thanks to the recent release of vBulletin 4.0.8 Patch Levels 1 and 2, we were able to identify and address 2 security vulnerabilities in VaultWiki Lite. VaultWiki 3.0.8 Lite addresses both of these issues.

Even though these vulnerabilities only affect users with Internet Explorer 6, we still highly recommend that customers upgrade as soon as they are able. Keep in mind that these issues affect customers on all versions of vBulletin, not just those with vBulletin 4.

SwollenCranium

11-23-2010 01:44 PM

Lite Vs Pro Q:

I'll install the lite and give it a try for awhile, if it serves my needs I'll buy the Premium set, BUT how is upgrade handled?

Are all created WIKI and permission settings carried over to Premium seamlessly and with no loss?

thincom2000

11-23-2010 02:42 PM

Yes, there is no loss if you follow the normal upgrade path.

On the other hand, if you uninstall Lite first, you WILL lose data.

linuxwhy

11-28-2010 10:11 AM

I just purchased, but I don`t know (or can`t) download the script, can you check, thanks
Date Type Status Details Amount
2010-Nov-28 Payment To Theodore **** Completed ... -$69.98 USD

linuxwhy

11-28-2010 10:57 AM

oho, I saw it , it`s solved.

thincom2000

12-02-2010 02:50 AM

Just updated 3.0.8 Lite to fix some compatibility issues with vBulletin 4.1.0 Beta 1.

If you are already running 3.0.8 Lite, you don't need to update unless you also want to upgrade to vBulletin 4.1.0 Beta 1. For this particular release, you don't need to run the VaultWiki upgrade script, just copy and replace the files from the ZIP.

thincom2000

12-03-2010 02:49 AM

Note that after the confusion over 4.1.0 only having 1 Beta, and the stable version going missing for a while, we can confirm that the current 3.0.8 Lite should still work correctly on 4.1.0.

Vikingant

12-05-2010 11:56 PM

Whenever I hit the History tab I get the following error.

Quote:

Database error in vBulletin 4.0.7:

Invalid SQL:

SELECT revision.*, user.username, user.usergroupid, user.membergroupids,
MAX(previous.revisionid) AS prev_revisionid, MIN(next_rev.revisionid) AS next_revisionid,
roll_rev.ipaddress AS targetipaddress, rolluser.username AS targetusername,
previous.userid AS rolluserid, prev_user.username AS rollusername,
previous.ipaddress AS rollipaddress, previous.unzip AS prev_unzip

FROM vb_vault_revision AS revision
LEFT JOIN vb_vault_revision AS next_rev ON (next_rev.lastrevisionid = revision.revisionid AND next_rev.pending = 0)
LEFT JOIN vb_vault_revision AS previous ON (revision.lastrevisionid = previous.revisionid)
LEFT JOIN vb_user AS user ON (user.userid = revision.userid)
LEFT JOIN vb_vault_revision AS roll_rev ON (roll_rev.revisionid = revision.rollback)
LEFT JOIN vb_user AS rolluser ON (rolluser.userid = roll_rev.userid)
LEFT JOIN vb_user AS prev_user ON (prev_user.userid = previous.userid)

WHERE revision.threadid = 1405
GROUP BY revision.revisionid
ORDER BY dateline DESC
LIMIT 0,1;

MySQL Error : Unknown column 'next_rev.pending' in 'on clause'
Error Number : 1054
Request Date : Monday, December 6th 2010 @ 01:11:54 AM
Error Date : Monday, December 6th 2010 @ 01:11:54 AM
Script : http://mysite.com/showwiki.php?title...***&do=history
Referrer : http://mysite.com/showwiki.php?title...******&p=26213
IP Address : ***********
Username : *******
Classname : vB_Database
MySQL Version : 4.1.22-standard

thincom2000

12-06-2010 06:35 AM

Thanks, logged this error, so the fix should be included in the next update. You won't get the error if you have permission to undo edits.

oddball118

12-06-2010 09:35 AM

Any reason why when I try to run the install script i'm prompted for my admincp username and password over and over? Tried it on different browsers with the same results.

Vikingant

12-06-2010 10:27 AM

Thanks for the tip thincom.
I created a wiki author group giving them permission to edit, and added admins to that group but didnt allow admin to edit but have now and its all working fine.

Shouldnt it allow for secondary group permissions?

Ant

thincom2000

12-06-2010 03:18 PM

Quote:

Originally Posted by oddball118 (Post 2129966)

Any reason why when I try to run the install script i'm prompted for my admincp username and password over and over? Tried it on different browsers with the same results.

This is a known compatibility issue with vBulletin 4.1.0. In order to get around it:

Log into your AdminCP first, using the normal admincp path.
Then enter the install URL in your address bar.
The installer won't ask for your password now, because you are already logged in.

Quote:

Originally Posted by Vikingant (Post 2129977)

I created a wiki author group giving them permission to edit, and added admins to that group but didnt allow admin to edit but have now and its all working fine.

Shouldnt it allow for secondary group permissions?

Yes, it should allow for secondary permissions. Even though it's passed through a separate function, the permissions are returned exactly as vBulletin constructs them. Make sure the wiki author group you created has the following permission "Allow Users to have Member Groups". If this is No, only permissions from the primary usergroup would be used.

Vikingant

12-06-2010 08:30 PM

Quote:

Originally Posted by thincom2000 (Post 2130065)

Make sure the wiki author group you created has the following permission "Allow Users to have Member Groups". If this is No, only permissions from the primary usergroup would be used.

Already there. Im note sure if it is wiki or VB (4.0.8) that is doing this. I will try and look deeper into it.

Ta

RichieBoy67

12-09-2010 02:41 PM

Hey folks,

#1 - What is the difference, pros' cons from using this instead of media wiki?

#2 - Does anyone have a working version I could check out? please feel free to pm me if you do not wish to post the link.

Thanks,
Rich

RustedBucket

12-09-2010 11:23 PM

Quote:

Originally Posted by thincom2000 (Post 2130065)

This is a known compatibility issue with vBulletin 4.1.0. In order to get around it:

Log into your AdminCP first, using the normal admincp path.
Then enter the install URL in your address bar.
The installer won't ask for your password now, because you are already logged in.

That doesn't work either with the latest 4.1 build. Can't run the install at all. Tried multiple browsers.

thincom2000

12-10-2010 03:15 PM

Quote:

Originally Posted by RichieBoy67 (Post 2131359)

#1 - What is the difference, pros' cons from using this instead of media wiki?

Syntax: If you use MediaWiki, your users will have to learn a whole new syntax to create articles. In VaultWiki, they can continue using BB-Codes.
User Base: VaultWiki is a vBulletin addon so your users don't need to register separately for your wiki, and you don't need to install a separate user bridge. Permissions are handled by vBulletin's usergroups, so you don't need to learn how to set up any new rights systems.
Comments System: VaultWiki allows users to comment on your articles. In MediaWiki, there is only one comment post for each article -- multiple users contribute to it.
Integrated Search: VaultWiki's search is handled by vBulletin's search engine. In MediaWiki, this is only possible with a separate bridge; otherwise, searches are handled by a different script.
Style Integration: VaultWiki's pages are displayed in your forum style and layout. MediaWiki might only do this if you installed a separate bridge. VaultWiki's style and layout can be modified using the familiar vBulletin admin interfaces.
Updates: With VaultWiki, you only need to maintain vBulletin and VaultWiki. Otherwise, you have to maintain MediaWiki, vBulletin, and a bridge (if used).
Performance: MediaWiki has historically been slow on the average user's server.
More: There are a lot more differences, especially in the paid version, but I'm not allowed to post them in this forum.

All times are GMT. The time now is 02:25 AM.

Page 4 of 13

« First

Last »

Show 40 post(s) from this thread on one page

X vBulletin 3.8.12 by vBS Debug Information
Page Generation 0.01598 seconds Memory Usage 1,850KB Queries Executed 10 (?)
More Information
Template Usage: (1)ad_footer_end (1)ad_footer_start (1)ad_header_end (1)ad_header_logo (1)ad_navbar_below (2)bbcode_code_printable (13)bbcode_quote_printable (1)footer (1)gobutton (1)header (1)headinclude (6)option (1)pagenav (1)pagenav_curpage (4)pagenav_pagelink (1)post_thanks_navbar_search (1)printthread (40)printthreadbit (1)spacer_close (1)spacer_open Phrase Groups Available: global postbit showthread	Included Files: ./printthread.php ./global.php ./includes/init.php ./includes/class_core.php ./includes/config.php ./includes/functions.php ./includes/class_hook.php ./includes/modsystem_functions.php ./includes/class_bbcode_alt.php ./includes/class_bbcode.php ./includes/functions_bigthree.php Hooks Called: init_startup init_startup_session_setup_start init_startup_session_setup_complete cache_permissions fetch_threadinfo_query fetch_threadinfo fetch_foruminfo style_fetch cache_templates global_start parse_templates global_setup_complete printthread_start pagenav_page pagenav_complete bbcode_fetch_tags bbcode_create bbcode_parse_start bbcode_parse_complete_precache bbcode_parse_complete printthread_post printthread_complete
Messages: