All posts by Andrewds1021
You are blocked on that particular wiki.
{| class="fandom-table"
| style="background-image: linear-gradient(to right top, yellow 50%, blue 50%);" | one cell, two colors
|}Yes, Safari and Chrome are web browsers; not search engines. As for iOS, that is a unique situation and only applies to the native Safari browser. For iOS, the OS version and the browser version are linked. If you install a different browser on iOS, you will not have the same restriction. Similarly, most browsers on most other OSs do not have this restriction. Safari on MacOS, Edge on Windows, Chrome on Windows, Firefox on Windows, Edge on Android, Chrome on Android, etc. all do not have a fixed browser version associated with the OS. The only other example I can think of where the OS and browser versions are linked is Windows 10 and Legacy Edge.
I don't understand your question. Could you clarify? You posted two different images. On your device, they would be stored as two separate files; at least, they should be.
Unfortunately, it doesn't look like there is any such script for comments where you can provide a specific list. However, if you want to delete all comments by a particular user, then there is a script for that.
Darn. I keep getting those two things confused and I just did it again. However, I am pretty sure the "for kids" wikis have the autoconfirmed requirement by default. The part where I messed-up is that the at-will toggle admins on other wikis have is only for anonymous editing.
4093 Alt, if your wiki requires users to be autoconfirmed, it is either because you marked is as "for kids" or an admin (though I assume you are the only admin) requested it. It can be removed by asking Fandom to remove it. Is this restriction actually in place on your wiki though? As I said, the restriction is the exception, not the norm.
Interesting. I have yet to have this issue. It would not be issues with an OS itself but rather the web browser (not search engine) that is in use. Fandom/MediaWiki likes to use the "latest and greatest" features which means users need to keep their browsers updated in order to not have as many issue with the platform. Though it is true that if your OS is too old, it might not be supported by current browser versions.
Ah, interesting. Well, I guess Fandom has always been more protective of its "for kids" wikis.
Not sure what to say but glad you finally got them.
It sounds like someone just added a category to a template incorrectly. Could you give an example page that shouldn't be in the category but is?
By default, wikis should allow editing by user whom are not autoconfirmed. If a wiki does not allow it, then there are 2 likely causes. First, the wiki may have been flagged as "for kinds". In those cases, Fandom puts the editing restriction on the wiki when the wiki is creates. Second, the local admins have decided (for whatever reason) to disallow editing by new users. Local admins can enable/disable this at will via the admin dashboard.
Where on the wiki are you trying to post? Article comments, Discussions, or message walls?
How is it preventing you from posting? Are you not give the interface or does it give an error when you try to post?
Which wikis are not allowing you to post?
If you go to your own user page, does it say you are blocked in your user masthead? Even if your account isn't blocked, you could have gotten caught by an IP block.
Once you compile a list of all the pages that need to be deleted, you can use AjaxBatchDelete.
Both images seem fine size-wise. What type of image file do you have them as on your device? I see that one is a PNG and the other is a JPG. If you mislabeling the file type is another reason images get rejected.
That particular page name has been protected. You should be able to create other pages.
I see the image in your screenshot. So either you have found a solution or it just took some time for things to update.
Do you have any ad blockers or anti-virus software the might be blocking the content?
Yes, in contrast to the legacy platform, UCP tries to find a suitable image from the page itself before defaulting to the community site image (or Wiki.png prior to implementation of the community site image).
Yes, in English, "size" is used in both cases. That is why it is so confusing. I usually make sure to always use two words just to be clear. "image size" or "image dimensions" for pixels and "file size" for bytes. Another confusion over terminology is "resolution"; which has 3 potential meanings depending on context.
I am not getting any error when I just type. Does the error occur when you try to save or literally exactly when you try to type something?
Yes, Muchos. That is the correct extension. I will take a look at the issue in a bit but here is a bit of background first.
Way back, like around 10 years ago, Fandom was a lot more generous about enabling random extensions at wikis' requests. One such extension was SemanticMediaWiki (SMW) which serves the role of a database. Gamepedia chose to use an alternative called Cargo. There were tons of additional extensions which built off of SMW and one of them was SemanticForms. However, these extensions were relatively computationally expensive to run. As such, Fandom never added them to the standard list of extensions nor officially supported them.
Since Fandom didn't update its platform until 2020, they just sort of left the extensions around for the few wikis that already had them and it worked fine. However, the rest of the MediaWiki community continued to develop the software and ended up retiring SMW and related extensions in favor of extensions which served similar purposes but were more computationally efficient.
The proposed replacements were DynamicPageList (DPL) and PageForms. When Fandom updated its platform, it had to switch (as much as possible) to these replacements. DPL is significantly different from SMW so Fandom had a fun time migrating SMW for the wikis that use it. In the case of PageForms, it was designed to function either on its own or with the retired SemanticMediaWiki extension. As such, Fandom changed from SemanticForms to PageForms. Despite the attention to backwards compatibility, there are some notable differences. The biggest is that the property "has default form" is not supported. Instead, one needs to use the #default_form parser function.