Extension talk:BizzWiki

From MediaWiki.org
Jump to navigation Jump to search

Support for version 1.13[edit]

So far, I have 4 people that have shown interest by starring [1].

Resolved Cases[edit]

Lessons Learned[edit]

  • Lessons learned can be found here.

Issues NOT resolved (yet)[edit]

Update from old BizzWiki Version[edit]

Hi, I realy like the userright-management with BizzWiki - so thanks for the extensions. What I want to ask: I have two web-projects, on one I work with the old BizzWiki-Version an on the other one with the new BizzWiki. Now I wanted to update the older project and I installed all the used extensions and changed the includes-Folder as I have it in the newer project. Finally I got the message that there is a database read-error. So do you have a manual for update the old Bizzwiki to the new one?

Thanks a lot! Filburt, 16.2.2008

Unfortunately I don't. My apologies.
To the best of my knowledge, there aren't any database level changes from one BizzWiki version to another. That's the sort of things I strive to stay clear of. Jean-Lou Dupont 14:07, 16 February 2008 (UTC)

How can I give Anonymous the right to read new sub-pages (RESOLVED)[edit]

Hi, I have the following problem: I have allowed Anonymous to read some pages on my Wiki. User can read these pages too and also create new sub-pages. How can it be solved, that these new sub-pages are automatically also readable for Anonymous? Do I need the DirectoryManager Extension or someone else for this problem or am I able to make the settings in the BizzWikiSettings.php?

At the moment I have defined:

$oeffentliche_seiten = array 	("Hauptseite",
				"Projektberichte", 
				"Leben_im_Ausland",
				"Infos_zur_Bewerbung",
				"Bewerbungsformulare");

$seitenzahl = count ($oeffentliche_seiten);

for ($i=0; $i<=$seitenzahl; $i++)
	{
	$wgGroupPermissions['*' ][hnpClass::buildPermissionKey(NS_MAIN,$oeffentliche_seiten[$i],"read")] = true;
	}

Now I want to allow Anonymous to read new created sup-pages of "Projektberichte". I've already tried different ways, but nothing worked yet...

THANKS FOR THE HELP!!! --Filburt 05:09, 27 September 2007 (UTC)

Use a wildcard. E.g.:
$wgGroupPermissions['*' ][hnpClass::buildPermissionKey(NS_MAIN,$oeffentliche_seiten[$i]."/~","read")] = true;
This effectively instructs the permission sub-system to allow all sub-pages of the base pages in $oeffentliche_seiten[$i] readable by '*' group.
Jean-Lou Dupont 10:31, 27 September 2007 (UTC)

Thanks a lot for the fast answer. Unfortunately it does not work yet :-( Do I have to make some other settings - for example to define pages as sub-pages? Thanks Filburt

Yes, the namespaces must be part of the array $wgNamespacesWithSubpages. Jean-Lou Dupont 14:07, 27 September 2007 (UTC)

Hey, the problem is solved - thank you for your advices! Filburt

Conflict with Semantic Mediawiki extension??[edit]

Hi, I installed a latest version of BizzWiki and found it seems conflict with the Semantic Mediawiki extension. When I click "special pages", a popup panel shows "Object error" and a message shows "hnpClass: action delete namespace dependant but called from NS_SPECIAL". Any idea? By the way, is there any manual document for BizzWiki? Thanks, -Guoqian

I do not know enough about 'Semantic MediaWiki' (I wish I did though) to be able to help out in the near term. The message you are getting from 'hnpClass' (Hierarchical Namespace Permissions) suggests to me that 'Semantic MediaWiki' adds some special pages where namespace level permission management is not performed. It could be just a matter of going through the said extension and apply the same sorts of modifications I have performed on the stock MediaWiki. Jean-Lou Dupont 15:34, 23 July 2007 (UTC)
Thanks for your quick reply. The problem is that each time I access the "special pages", I will get the error message. Is there any way to disable the error message and tolerate the error before we fix it? --Guoqian
Assuming you are referring to the 'debug' message generated by 'hnpClass', then yes you can disable it by locating the 'echo' statements in 'HierarchicalNamespacePermissions.php' file and commenting them out.
Note that I am not committing to adjusting SMW to work in the BizzWiki environment just yet. Jean-Lou Dupont 16:04, 23 July 2007 (UTC)
Thanks. We look forword to that SMW can be adjusted working in the BizzWiki. In other word, BizzWiki would be accepted more widely if the solution works well with most of major extensions. --Guoqian

Hi, I installed the BizzWiki Extensions (1.10.10) to my local mediawiki installation to test it before putting to my live site. Initially it seems to worked perfectly. But when I tried click 'edit' page tab (Admin Login ) I got the following error

  Database error
 A database query syntax error has occurred. This may indicate a bug in the software. The last attempted database query was:
   (SQL query hidden)
 from within function "fnSelectCategoryGetChildren". MySQL returned error "1064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's_Investment_Group' AND tmpSelectCatPage.page_namespace = 14' at line 4 (localhost)".


I want following settings in my mediawiki installation

1. ALL Special Pages should be restricted except for Admin and Sysops. 2. Editing can be done by anyone but with ReCaptcha enabled.

Help with above will be appreciated. Thanks - Gautam

With regards to the database error, have you installed any other extensions besides BizzWiki?
Regarding point #1, you can use the Hierarchical Namespace Permission system to limit access to ANY pages (special or otherwise). Please see BizzWikiSettings.php for some examples (this file is located in the BizzWiki directory.
Regarding point #2, please see Extension:ConfirmEdit for more details on how to set ReCaptcha parameters (ReCaptcha is built ontop of ConfirmEdit).

Jean-Lou Dupont 16:57, 11 August 2007 (UTC)

re Database error, I've installed following extensions: FCKeditor, RSSReader, SelectCategory, TagAsCategory, and SQL2Wiki
re point #1, I have removed 'NS_Special' (at line no. 248) from 'Namespace accessible by 'Anonymous' array and NS_TEMPLATE, NS_TEMPLATE_TALK, (at line 271) from Namespace accessible by 'User' array in BizzWikiSettings.php. I wanted to check if this is sufficient for my first objective or I need to do change anything else.
Yes you need to remove NS_SPECIAL from the list + add the page 'Special:Userlogin' to the '*' permission.
$wgGroupPermissions['*' ][hnpClass::buildPermissionKey(NS_SPECIAL,"Userlogin","read")] = true;

NS_TEMPLATE does not play a role here. Jean-Lou Dupont 23:55, 11 August 2007 (UTC)

re point #2, by default anonymous edit is disabled in BizzWiki extension. I was wondering if adding line '$wgGroupPermissions['*' ][hnpClass::buildPermissionKey($bwx,"~","edit")] = true;' for anonymous user (somewhere between line 256 and 260) in BizzWikiSettings.php would be sufficient.
Correct. Jean-Lou Dupont 21:44, 11 August 2007 (UTC)
I am asking these question because very little documentations is available for BizzWiki and I am hardly a programmer to understand these details. For lesser mortals like me hopefully in future you may add a nice interface in Admin Menu to do all these change. But Kudos to what you are doing. I am really interested in using it to my site. Any idea when we can expect a stable release.
I am focusing on finishing up a critical module in BizzWiki: Extension:rsync. After that, I'll be adding even more documentation. Jean-Lou Dupont 21:44, 11 August 2007 (UTC)

-Gautam

I guess it was conflicting with SelectCategory extension. I have disabled it and now edit fuction seems to be working fine.
It is also having some conflict with TagAsCategory extensions. When I try Special:Categories I get following error "Pager::getBody : no recognized namespace= hnpClass: action browse namespace dependant but called from NS_SPECIAL."
That`s because the extension isn`t ``namespace aware`` i.e. not integrated with BizzWiki. Jean-Lou Dupont 23:22, 11 August 2007 (UTC)
re point #1 if I perform changes as mentioned above than I login become completely disabled. If not all is it possible to remove access to Special:Export for all users except Admin and Sysops?
See answer above. If you ever wanted to just remove access to 'Special:Export' just use:
$wgGroupPermissions['*' ][hnpClass::buildPermissionKey(NS_SPECIAL,"Export","!read")] = true;

Jean-Lou Dupont 23:57, 11 August 2007 (UTC)

- Gautam


Does ist work together with the LDAP_Authentication Extension? Tim

I do not know enough about this LDAP extension to say something intelligent. Sorry. Jean-Lou Dupont 12:54, 11 November 2007 (UTC)

Error message when accessing Special:AWCforum Forum[edit]

Hello, I have the BizzWiki installed as well AWCforum Extension, which is a special page-based forum.

Am getting the error:

HNP: action awc_ForumAdmin not found in namespace dependant array.  HNP: action awc_ForumAdmin namespace dependent but called from NS_SPECIAL. 
 HNP: action awc_ForumMod not found in namespace dependant array.  HNP: action awc_ForumMod namespace dependent but called from NS_SPECIAL. 
 HNP: action awc_CanNotView not found in namespace dependant array.  HNP: action awc_CanNotView namespace dependent but called from NS_SPECIAL. 
 HNP: action awc_CanNotView not found in namespace dependant array.  HNP: action awc_CanNotView namespace dependent but called from NS_SPECIAL. 
 HNP: action awc_CanNotView not found in namespace dependant array.  HNP: action awc_CanNotView namespace dependent but called from NS_SPECIAL.

Not sure what to do... add namespace? add rights? Any assistance would be most welcome. --Jeffmcneill 02:27, 28 September 2008 (UTC)


Error when accessing Special:Random and Special:SpecialPages[edit]

Hi I'm trying install your extension, on MW 1.12, but after did all steps, when I click in Special:Random page navigator show me next message:

Fatal error: Call to undefined method RandomPage::getLocalName() in ...\wiki\includes\SpecialPage.php on line 442

Same when I trying with Special:SpecialPages, the navigator show me:

Fatal error: Call to undefined method RandomPage::isListed() in ...\www\wiki\includes\SpecialPage.php on line 357

I don't know what it's wrong and need help because I need set MD 1.12, to restrict some page by users.

Thank you.

I don't support 1.12 nor any other versions except the ones listed on the project page. Jean-Lou Dupont 16:47, 28 October 2008 (UTC)