All posts by Andrewds1021
I don't see anything in the wiki's logs so the 2 most-likely explanations are:
You have mis-remembered
Fandom staff suppressed the revisions for some reason
It is often difficult to troubleshoot an issue based just on a description. It i best if you save the content in the broken state so that we can examine what is happening rather than just taking guesses. In the event that the error is preventing you from saving, it is helpful to describe when/where you get the error. For example, is it a pop-up message after you click the save button or is a message on the side of the editor?
Regardless, it sounds like you get the error when you try to use the template markup you posted here instead of what is currently on the page, correct? If so, there are a few things about your TemplateData JSON that are not correct. Let's start with the one that is likely generating the error. When specifying paramOrder, the last item in the array has a comma between it and the closing square bracket. This is a violation of the JSON syntax and the extra comma should be removed. The second issue probably isn't producing the error message but will cause unexpected behavior. When specifying the params, you have closed the object before specifying the items in the object. As such, the items meant to be in the params object are now siblings of the params object instead. You need to move the closing curly brace and comma to after the definition of the last parameter. And similar to the paramOrder issue, you will need to remove the errand comma between the closing curly brace of the last parameter and the closing curly brace of the params object.
The editor is outdated but technically :is() is a de facto standard since the official documentation is still in the working draft phase. As is usually the case these days, early adoption is driven by the 3 largest desktop web browsers: Chromium (>70% market share), Safari (~18.2% market share), Firefox (~2.7% market share).
Yes, polls intentionally cannot be edited after they have been published.
You are missing the closing parenthesis after the URL. Also, the intent is that you replace "__FONT NAME__" with the actual name you want to use.
My advice, don't do it unless it is really critical to understanding the topic of the wiki. There is neither a built-in nor extension feature available for creating family trees. Some wikis use elaborate templates to make a table look like a family tree but they are very hard to maintain. Any slight change to the appearance of the wiki (whether by local admins or from changes in Fandom's global styling) can easily throw off the appearance of the tree.
If the issue is with the mobile page but the desktop page is fine, then you probably just need to purge the mobile page.
It might be because you attempted to use a navigation magic word as a root menu item. Per the help page, navigation magic words must be used as 2nd level items.
The way you have said things, there are a few unclear details. First, are you saying the . references are on the archetype page pointing to all the characters or that each character page has a reference/link to the archetype page? Second, are you just looking for a way to get the count of an individual archetype like in your example or are you looking to create a table that lists the counts for all archetypes? Assuming the latter for my first question, the simplest solution would be if each page in the archetype was also a category member. For each category, a list of members is automatically aggregated on The corresponding category page. If you need the get the member count for use on a different page, you can just use the pagesincategory magic word. If you do not want to use categories for some odd reason, you only solution would be to use DPL which may need to be enabled on the wiki. DPL is much more complicated to use so I would recommend using categories if at all possible.
I wonder if the html and body tag selectors are actually parsed or just that TemplateStyles inserts the article selector between them and the rest of the selector. For example, if the body had a data attribute, I wonder if we could use the attribute selector or if that would be stripped out?
In case it isn't clear, 2.6 MB is the same as 2660 KB. In other words, the issue is that your file is 5 times too large.
What do you mean by it didn't work when you tried to re-upload them? As far as I am aware, uploading duplicate files might produce a warning but you can just click right through the warning. If by "wrong name" you mean that you uploaded imageA as ImageB, then it is even easier. You can just go to the imageB page and upload the correct file as a new version; no need to delete first.
In theory, yes. However, I am not sure of any pre-made mobile bot platform. Also, it would probably not be the best idea.
To understand why a mobile bot would probably not be the best idea, let's first clarify what is meant by the term "bot". The type of "bot" and Fandom users can use is not some script you upload to the wiki and leave running while you log out and do something else. It simply refers to a script or alternate method of making changes to the wiki that require you to remain logged in on the device running the external script or program.
As for why it probably isn't a good idea to do this on mobile, it is simply a matter of the how much/long the script will be running. While the script continues to run, it will be using your device's resources just like any other application. While mobile devices have come a long way in recent decades, they are still usually more limited than desktops (or even laptops). So if you have a truly large list of changes to make (which is where bots reap the most benefits), it would probably be best to use a desktop/laptop instead.
There are 2 main alternatives to Fandom. The first is Miraheze as SnowedLightning pointed out. The second is ShoutWiki. Both allow private wikis and are free but they also have differences.
Miraheze is a community-supported project. That means it is managed by a non-profit comprised of volunteers. There are no official staff or "professional" support. The project is funded by donations though I am not sure if they have a fundraising season like Wikipedia does.
ShoutWiki is a company with staff and professional support. They are funded primarily through ads since the wikis are free. That said, there are some paid features; primarily ad-free wikis.
Yes, the account must be at least 96 hours old in order to post a comment. Furthermore, you must be using desktop mode. Even once you are allowed to comment, doing so cannot be done in mobile mode.
If you re-download the original file and compare it to your local copy, are they different? What is the file size of your local copy of the MP4?
Is this happening with other GIFs too? If so, all GIFs or just GIFs that have been uploaded by certain users? I am looking at the following 2 GIFs which were recently uploaded to Fandom and not seeing any issues.
Image - Kafka.gif | Community Central | Fandom
Image - Emu dancing to ego rock.gif | Community Central | Fandom
Oh, I just assumed that was part of the animation. Seems to be a result of the resizing since viewing the original size doesn't have the same issue. Has this been reported to Fandom yet?
What is wrong with that GIF?
Since you already went through the effort of importing the module, I would just keep it. Using the module is slightly better for performance. The performance benefit increases the more complex you get with your string manipulations.