Integration with vBulletin - CES Wiki Conditionals

CES WIKI CONDITIONALS
Version: 1.1.0
Requires vbWiki Pro v1.3 RC3 or later (also unsupported).

*** NEWS ***
5/30/2007 - linked first post to a bug fix for vbWiki Pro that prevents this mod from working
5/20/2007 - v1.1.0 released
5/14/2007 - v1.0.3 released on vb.org

Products to Install: 1
Plugins Included: 2
Files to Upload: 1
Template Edits: 0
Files to Edit: 0

What It Does:
Allows you to use vBulletin template conditionals in MediaWiki articles.

<if condition="code"> ... <else /> ... </if>

Known Issues:
- Because of some bugs in the MediaWiki parser, nesting <if> tags inside each other will result in unexpected behavior.
- Some public versions of vbWiki Pro have a bug where the hooks don't work properly. Until a new build corrects this, use the fix here: https://vborg.vbsupport.ru/showthread.php?p=1257327
- You should NOT be using this mod to hide or show dynamic content based on Usergroup Permissions, since there are holes in the implementation.
- We have abandoned most of our other-party-wiki addons since we started our own wiki project for vBulletin called VaultWiki.

*** Changelog ***
As of Version 1.1.0:
- rewrote the parser function to use vBulletin's code
- fixed bug where the page would cache

As of Version 1.0.3:
- finally compatible with public versions of vbWiki Pro

As of Version 1.0.2:
- uses vBulletin's hook system
- else parameter changed to vBulletin's <else /> tag

As of Version 1.0.1:
- added else parameter

[thincom2000]

Okay that's a step in the right direction...

[RedGTiVR6]

btw - I do really appreciate your assistance on this. It is greatly appreciated.

If I used PayPal (I refuse) I would donate.

Any other way you suggest?

[thincom2000]

I registered and made an edit to the page. It's working. The problem was that the old version of the page was cached, so it wasn't trying to reparse anything after the hook issue was fixed.

Since I made an edit you should probably re-edit to remove the extra text "Only showing to admins..." (don't revert to the last revision).

P.S. If you are using the conditions to hide text by Usergroup, I would not recommend letting anyone lower than that edit the page. With the hook vbw_map_permissions, you should be able to lock down certain pages if this isn't already a feature of vbWiki Pro.

[RedGTiVR6]

Thanks.

I noticed this change, but I also noticed the <else /> as being still visible when I check the page, but the first part of the code isn't.

Also, if I logged in as a non-admin and looked at the page, it showed as desired, but if I went in to edit it, I could see it all.

So by your last post...

If I have an article that the members of the company are working on but we don't want to be visible by the public yet...we shoud only allow that user group to edit the article. Do I understand that correctly?

[thincom2000]

That understanding is correct.

EDIT: I noticed what you said about using <else />. I will fix that for the next build, thanks.

[RedGTiVR6]

Thanks for the support! It's greatly appreciated.

I'm off to send an email to the company to let them know about the new ability.

[RedGTiVR6]

I'm back...

Perhaps this isn't possible, but I cannot figure out how to allow only certain user groups to edit an article.

I can see where we can protect it, but there's only the Sysops group that I can choose or the unregistered group.

Am I missing something?

[majorxp]

Originally Posted by Wayne Luke

Then don't use it. Quite simply, I see a Wiki as simply another form of content management. I may not want the general public to change my content and integrations like this allow me to lock things down without worrying about protecting every page.

I'm incredibly confused by this message.

integrations like this allow me to lock things down
I was pretty clear that you do not want to use this plugin to lock down content. Simply adding your wiki to an rss feed will show any 'protected' content you may have (as well as showing the code you place on the page). You could also show the full content of the page by adding the "raw" option.

without worrying about protecting every page.
This plugin requires page by page protection since it only works on a per page basis.

[thincom2000]

Working on this... How do you view the RSS output of the page? Is this a new feature in MW 1.10?

[majorxp]

You can get the rss feed of the recent changes which would include any code you add to a page.


RSS Feed:
http://www.crackedeggstudios.net/wik...anges&feed=rss
(you have disabled the feed presumably to not show the code)

Furthermore, you can see the diff history of any page and see the code. This is just too easy to see the 'hidden code' that it is (unfortunately) ineffective at best.

For example, see this page:
http://www.crackedeggstudios.net/wik...anges&days=100

From there, you can look at this page:
http://www.crackedeggstudios.net/wik...293&oldid=2292

This page clearly shows the 'protected content' and the CODE.

To make matters worse, you could view the raw page and see the full current page with all of your code and the hidden content:
http://www.crackedeggstudios.net/wik...ent&action=raw


EDIT: If anyone is going to say something like, "well...this is just to hack or someone who tries to see hidden code" you are fooling yourself.

A simple search also shows hidden content. Someone could search for something as simple as the word "links" and show 'hidden content' (since the search engine has no idea it is supposed to be hidden from that user).
http://www.crackedeggstudios.net/wik...searchx=Search



Again, this mod should NOT be used to hide or protect content under any circumstance. It just doesn't work. If you want to protect or hide content, I would wait until there is an extension that will tie categories or pages to user groups and then use the vbwiki tool to match wiki user groups and vb groups.

Seriously, a wiki is not designed or intended to protect or show content. It is a tool to openly share information where everyone can edit it. If you need to hide or protect information, mediawiki is not the tool you are looking for.