- 1 Extension:Simple_namespaces
- 2 ERROR: The namespaces table is empty, or something else went wrong.
- 3 Not a restricted page
- 4 Default vs. Canonical
- 5 Default link prefix
- 6 Moving pages to a new namespace?
- 7 Unable to resolve namespace name for anonymous requests
- 8 Default Namespace
- 9 Revision, removals and improvements
For mw version 1.11.0 I ran into trouble that this version checks the return value of hooks and function wfNamespaces didn't return true. changed that locally and would put it into the source as well.
added: return true; (line 276)
- Yes. It's languages/Language.php --188.8.131.52 17:48, 13 January 2007 (UTC)
Hrm. I'm running 1.7.1, and in my languages/Language.php, I can't find anything remotely similar to that code block. The only two instances of "load" are two comments:
" * overload this." and "// Preload base classes to work around APC/PHP5 bug"
Did something change? I was able to add the table successfully, however.
I'm trying to change all my "Talk:" pages to "Comments:" and "User_talk:" to "Wall:". I'm assuming this is how I should go about it? --184.108.40.206 17:07, 19 January 2007 (UTC)
- At the current time, no. The built-in namespaces are named in the *.php files under /languages/ and can be renamed there, but trying to do so through this extension no longer works. It *used* to be possible pre-MW1.18 to get away with this but that is now breaking namespaces. --Carlb (talk) 23:23, 3 March 2012 (UTC)
ERROR: The namespaces table is empty, or something else went wrong.
When I use the Special:Namespaces, it answers: "The namespaces table is empty, or something else went wrong." That's right, the namespace_names table is entry, but why? Shall I fill it using the mysql console (Sorry about my english)? PiPi
- PS:It is not a trouble, it is the first open screen when you created the namespace_names table (if wasn't it) and you are not a superuser. PiPi 22. April 2007.
OK, I inserted a test record in namespace_names. I open Special:Namespaces, and the test record is there. But I can't manipulate it, and I can't creating new namespace. What's the matter? PiPi 21. April 2007.
- Wow, I was a simple user, and not superuser! PiPi 21. April 2007.
Ok, this is my last check-in :) I do'nt know why (I'm not a software developer), but the function call "discard();" in 128. and 181. lines of code was given an error (call to undefined function). I changed this two lines to "$this->discard();" and it works! Did somebody try this extension ever? PiPi 21. April 2007.
- The two should be interchangeable... and yes, this extension is in use on Unciklopédia and others. --220.127.116.11 00:27, 30 April 2007 (UTC)
So, after installation and running the update.php, it's normal to get "The namespaces table is empty"? (I have a couple custom namespaces defined in LocalSettings.php). Johnywhy (talk) 21:51, 20 June 2018 (UTC)
Not a restricted page
Is there any way to make this page a restricted page that can only be utilized by sysops or above? Right now, it's a special page that anyone can see? Thanks. - Marc 05:25PM EST 10/01/07
- Anyone can see it, but only sysops can change anything on it. --18.104.22.168 22:18, 15 December 2007 (UTC)
Default vs. Canonical
I can not find any more info on what default and canonical do. I read that default should be checked, but what does that mean? Also how should this work with creating the paired equivalent namespace talk portion? Just create a namespace and its talk portion and away you go, or is there more to it? Any help?
- Each namespace should have one default name and one canonical name. The canonical name (at least for built-in namespaces) is the English-language name ("image:", "category:" and the like). The default name is the name in the local language of your wiki (so "bild:" in a Swiss-language wiki or "imagem:" in a Brazilian-language project). The two are the same only if the language of the wiki is "en". All other names are merely aliases for the same namespaces.
(Note: The 'canonical' bit is now basically meaningless within this extension as we no longer have an easy means to rename the built-in namespaces from the namespace editor. Carlb (talk) 23:27, 3 March 2012 (UTC))
Hello, does this extension provide the same functionality as the Namespace manages? I am mostly interested in the default link prefix as it is described here. Thanks a lot. --Jamlc 10:42, 6 October 2008 (UTC)
- As far as I know, there is no way to provide the arbitrary default link prefix without changing core MediaWiki code in some way. It's not something that could be done using this extension. The information on the Extension:Namespace_manager page is not about an extension, but about the Wikidata version (branched from MediaWiki 1.6, a predecessor of omegawiki.org but seemingly not otherwise maintained). Most of what's there dates from two years ago and no effort has been made to update the information, sadly. I have no idea why that page is in the Extension: namespace. --Carlb 18:21, 12 November 2008 (UTC)
Moving pages to a new namespace?
It doesn't look like it, but will this extension allow me to move all pages from one original namespace to a new one? Or is there an easier way to do that besides clicking through each page manually? Thanks -- firstname.lastname@example.org
- The extension doesn't provide this, but there is a maintenance script maintenance/NamespaceDupes.php included with MediaWiki. Manual:Namespace and Manual:Using custom namespaces have more information on using namespaces in MediaWiki installations. --Carlb 10:06, 6 September 2009 (UTC)
Unable to resolve namespace name for anonymous requests
I'd like to thank you for this extension, first.
Then, I'd like to report an issue. I used this extension to create 6 more namespaces (3 ns + 3 talk ns). They are all working fine when I (ou any other user) am logged in.
However, when I connect to the wiki as an anonymous user, I cannot access the pages within these namespaces, whereas I can access all the pages belonging to standard namespaces (like "template"). Links to the pages of custom namespaces are red, as if the page they link to did not exist. If I follow the link, the wiki will show me the edit form. This is a normal behaviour of a wiki which does not have SpecialNamespaces extension installed.
I thought it was a problem with rights. But it seems read rights are granted to anybody (and they are indeed, since anonymous users can access all the other pages of the wiki).
Then I thought of a conflict with another extension. I disabled one or two useless extensions, and nothing changed.
Did I forget to define some specific rights for my newly-created namespaces? Where am I to define them, and how?
Any help is welcome. Thanks!
Alvinos 21:26, 19 January 2010 (UTC)
- The only permissions required are to edit the table; the code to take the `namespace_names` list and stuff it into $wgExtraNamespaces and $wgNamespaceAliases on startup runs for *any* user, including IPv4 and IPv6 anonymous users. One thing to check would be whether caching (such as memcached) is set up correctly on your server - the namespaces are (like other info such as user logins and the mediawiki sidebar) stored there to keep execution time reasonable. I haven't seen this fail in such a way as to redlink namespaces (it should just go back to the database if the cached copy is missing for any reason).
- Are you using the current version for everything? (There was an old version of this extension, intended for MW1.15 and earlier, which required patches to core code - but their absence would affect everyone, logged in or not.) There are no rights to define for the individual namespaces (at least not in this extension) so normally the only difference is that pages are cached more aggressively for anon-IP's. --Carlb (talk) 18:39, 1 March 2012 (UTC)
I would like to know if there is a chance to setup a default namespace in wiki. I mean, every page user create is by default in the main namespace, if the user needs to create a page in a custom namespace he must search it as CustomNamespace:MyNewPage. I would like to setup wiki so all new pages are created automatically in the CustomNameSpace without specify it. Is it possible ?
Thanks a lot.
- It is not possible for an extension to do this; it would require major changes to core MediaWiki code. If users create pages by typing the proposed name into an inputbox or createbox those extensions can start the new page with a predefined namespace or pre-fill part of the body content, but even then there is no means to rename main space itself. Carlb (talk) 14:32, 3 May 2012 (UTC)
Revision, removals and improvements
Cheers to everybody.
I needed an extension capable to manage several new namespaces. I tried this one, and it partially suited my needs. But it wasn't enough because i needed a tool to change some of the new NS features (default search and permissions). I worked on this and ended up with a brand new thing that I would like to submit for approval. Changes:
- removed support for memcache since it's deprecated.
- plan to reinsert a cache system via "eval"
- removed support for core NS changes, including rename the project ns
- plan to reinsert a partial edit table for core NS, eliminating the name change field. Need hints on how to integrate this with existing core features.
- removed ns number edit field. Namespaces are numbered on their ID basis, starting with 3000, because this is the lowest MWcore-safe and extensions-safe namespace ID.
- default and simplified NS code creation
- filter for NS duplicated names (not working on aliases) in order to avoid duplicate prefixes.
- support for alias creation/change on the fly: every time an NS is added/edited, a new Alias field is added to the edit form. Aliases can be added, edited, removed and the default name/alias can be changed simply clicking on a radio button. In case of change, the NS old name is added to the aliases in order not to break existing links.
- if needed, an "add more alias fields" could be made working via JS.
- support for "content namespaces", "default search", "subpages" added with simple checkboxes. Common settings pre-checked by default.
- namespace edit protection: 2 levels (move/editprotected) to tell user and admins apart. In case of protection only, another checkbox allows to create a custom protection level to be added to user groups (in the form of "ns-#index-edit" string).
- automated creation for talk namespaces, without adding entries to the db. Talk namespaces are in the form of "Discussione _name_", with all the aliases of the subject ns, no "content", no "default search", supported "subpages", no "protection".
- EDIT: Talk namespaces settings now globally editable through $wgTalkNamespaceSettings variable in LocalSettings.
- completed internationalisation for English and Italian (my mother language).