ah its been so long since I`ve been up here. anyhow I had a question and figured it was best to ask one of the staff here since this is my first time doing so how do you send in a wiki adoption request? I would like to try and adopt the SaGa wiki since well..its sorta dead there not much activity at all and I have not seen an admin or anything around there since I first began editing up there so I want to try and breath a bit of life into it I`ve already began editing there alot.
Hi, I'm just curious about something. Basically, I made a wiki a few months ago, but I want a chatroom (like a Wiki Chat, not IRC). Do you know how to put that on a wiki?
Hi, I am one of the admins of the Just Cause Wiki, the one of us who comes up with most template ideas and add-ons. I am currently testing an more advanched automatic categorisation code on one of our infoboxes using the #switch feature. The categories links are surrounded by 'includeonly" tag, so the template itself not will be included in the category. The problem is that we have examples of this template on the same page, and these will make the template added to the categories EVEN if we used 'includeonly'. We don't neccessary want to remove these examples, as they can be helpful. Are there any code tags you can use so you can save the examples even if using automatic categorisation, to prevent the templates from being added into the categories?
It would help if I was able to see the template(s) in question... What I've did on Aion is set it to NOT categorize unless the template was included onto a page in the main space. (So if it's an example on a template page, it isn't categorized) You can see that effect here. Basically, you want to wrap all your categorization code inside a mainspace clause like so:
{{#ifeq: {{{categorize|{{#if: {{NAMESPACE}}|n|y}} }}} |n| |
category switches here
}}
Basically, this code does nothing if {{NAMESPACE}} is not NULL (if it exists - it sends a 'n') or if {{{categorize}}} = 'n'.
Also, my latest version of the username tags can be found here.
Rappy 4187 wrote: It would help if I was able to see the template(s) in question... What I've did on Aion is set it to NOT categorize unless the template was included onto a page in the main space. (So if it's an example on a template page, it isn't categorized) You can see that effect here. Basically, you want to wrap all your categorization code inside a mainspace clause like so:
{{#ifeq: {{{categorize|{{#if: {{NAMESPACE}}|n|y}} }}} |n| |
category switches here
}}
Basically, this code does nothing if {{NAMESPACE}} is not NULL (if it exists - it sends a 'n') or if {{{categorize}}} = 'n'.
Also, my latest version of the username tags can be found here.
So you can insert this code anywhere in the code section where it is clear and not in the middle of a tag? Also, you mean this will add a new section in the visual adding window where default is "Null"?
There we go! Then this type of code will apply to most of our infoboxes. :)
I am still confused about how the username tags function. If you want to add a "Bureacrat" tag or a "Patroller" tag which will be added on the right side of your username on your user page if you gets these certain rights, what exact code do you insert? Because the one with your username in made me confused. :/
Norrlanning96 wrote: There we go! Then this type of code will apply to most of our infoboxes. :)
Yep.
Norrlanning96 wrote: I am still confused about how the username tags function. If you want to add a "Bureacrat" tag or a "Patroller" tag which will be added on the right side of your username on your user page if you gets these certain rights, what exact code do you insert? Because the one with your username in made me confused. :/
If you want your name to show both Bureaucrat and Patroller, you'd make your line look like:
I don't think the username tag idea will be in action immediately. It may be put on ice. I just wanted to know how to do. I need to concern the three others in the active Admin council firstly; I am probably like second-in-command on our wiki now, I am not bureacrat though. But even if I was Main I can't really do such big tasks without telling the others first.
Do you by any chance know whats up with the tag flash?
The username tags (i.e admin, blocked) have been buggy lately. They flash when you go to the users page. Should I send this to the Special:Contact/bug?
Actually no, it works perfectly fine on that page. And yes, the wikis I am experiencing this on have the custom usertags loaded. Maybe theres an issue going on with it or something
No, that's the way UserTags work. The original images appear for a second before the script overwrites them—you might want to inquire at w:c:dev:UserTags if this can be fixed, but I doubt it.
Hello, it is nice and all the change to the File pages to make them more about the pages an file is used on, but first, the new lay-out doesn't even work.
The collapsed link to show more info is unable to actually show more info, it only shows more info for a split second after attempting to hide more info again.
Secondly, the pages it is used on section is way too prominent. It makes it very hard and tedious to maintenace images and such. The old versions of images etc shouldn't be hidden under a collapsed menu. It should be visible immedeately and shouldn't be dominated by the pages it is used on. It doesn't even have a use to show a file and some text about the page it used on as the name of a page always is more than descriptive enough, often an image is used on a great amount of pages and that will make a file page very very large, and slow to load. Another problem is we may need to go through a load of tabs of pages a file is used on to find what we're looking for.
Please fix your mistakes. And revert to the previous lay-out.
The 'show more' issue you described above appears to be a conflict with Runescape's local JS. I have not seen this issue on any other wiki.
Per the rest of your feedback, I have forwarded it to the team working on this project. Please direct feedback like this to us via Special:Contact/general rather than a staff members' wall. This ensures that it doesn't get lost along the way.
I'm someone who frequently posts on the blazblue fanon wiki, and I wanna tell you that this rule had also been broken on the fan wikia with the chatango code. As I never used the contact thing before I'm relaying my emssage through here. Since I feel inexperienced with the tool.
That's all I wanted to say. I'm just surprised how they put chatango codes in wikia rails :P
I have a problem and can't see an ideal place to report it. One user account on the Disney Wiki has been indiscriminately copying content from the Tron Wiki. This isn't just a bit of text, but also some of the templates, and template styling, to the point that a number of TRON-related articles have practically been cloned on the Disney Wiki. eg. TRON: Uprising (Tron Wiki) --> Tron: Uprising (Disney Wiki).
One of the Disney Wiki admins deleted one page that I used as an example of what was happening, but the account holder who is copying has not made any move to make any further corrections and continues to copy. I followed up the matter after a few days and got the following comment on my Tron Wiki talk page:
"Tron is Disney everything here belongs to Disney so how are you any different."
If the position of one editor is just to claim content, then the only road out is through administrator intervention. My position is that editors on the Tron Wiki have put a lot of effort into trying to create an authoritative information source, formatted to offer a particular visual style, and I don't believe that should be copied to the degree that it has. I also feel that the editor in question should have reverted those additions when asked to, and cited some community guidelines when presenting my request, but I've hit resistance on the issue.
