vb.org Archive

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 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:
  1. Log into your AdminCP first, using the normal admincp path.
  2. Then enter the install URL in your address bar.
  3. 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:
  1. Log into your AdminCP first, using the normal admincp path.
  2. Then enter the install URL in your address bar.
  3. 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?

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. Updates: With VaultWiki, you only need to maintain vBulletin and VaultWiki. Otherwise, you have to maintain MediaWiki, vBulletin, and a bridge (if used).
  7. Performance: MediaWiki has historically been slow on the average user's server.
  8. 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 06:29 PM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01566 seconds
  • Memory Usage 1,753KB
  • 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
  • (6)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (2)pagenav_pagelinkrel
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)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