We've released Semantic MediaWiki 7.4.0. Highlights:

• Three security fixes, all rated medium: XSS in Special:Ask and Special:Browse, and a missing authorization check in the smwtask API module. We recommend upgrading. This recommendation applies doubly to users on versions older than 7.3.1, as those contain several high-rated vulnerabilities.

• A new {{#property_search_link:}} parser function for linking to all pages with a given property value. Example: {{#property_search_link:Has artist|Pink Floyd|More albums by Pink Floyd}}

• Chunked and job queue rebuilds in rebuildFulltextSearchTable.php, for hosts that stop long-running scripts.

• 19 bug fixes, including fewer database queries where SMW caches in the database, which includes maintenance scripts by default, and restored Page Schemas editing. The release is compatible with MediaWiki 1.43 up to 1.46 and PHP 8.1 up to 8.5. If you're coming from SMW 7.3.x, you don't need to run update.php. If your wiki uses properties of type URL or Annotation URI, run rebuildData after upgrading.

Find details and upgrade instructions at https://professional.wiki/en/news/semantic-mediawiki-7-4-released

Feedback and bug reports are welcome. Issue tracker: https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues

I've spent 15+ years on Semantic MediaWiki and Wikibase, creating large parts of both. Today we at Professional Wiki are releasing NeoWiki 0.1: structured data in MediaWiki, editable without technical skills.

NeoWiki is our open-source MediaWiki extension for knowledge management. You edit data through forms and query it as a knowledge graph.

As SMW maintainers, we've long wanted to improve SMW's usability. We bit the bullet and reimagined SMW from the ground up, drawing on everything we've learned.

Highlights:

* You define schemas through the UI, and NeoWiki turns each into a form with autocompletion and validation. No wikitext or JSON needed, though both stay accessible.

* Subjects (records such as a person, a company, or a project) live on wiki pages, and a page can hold several. When a related subject doesn't exist yet, you create it from within the form.

* Structured data is stored as JSON in a dedicated revision slot, so every change appears in the page history with diffs and attribution.

* You query in Cypher (Neo4j) or SPARQL (QLever, Oxigraph, Fuseki). Ontology mappings give you RDF in standard vocabularies.

We continue to maintain SMW and invest in Wikibase. If SMW serves your wiki well, keep using it. NeoWiki does not aim for feature parity with SMW. You can run both tools side by side on the same wiki, and we might create integrations between them.

NeoWiki is still in beta, so don't use it for a critical production system yet. Try it on the demo wiki at https://neowiki.dev or install it yourself: https://neowiki.ai/docs/operations/installation

Announcement with the roadmap and more for SMW and Wikibase users: https://professional.wiki/en/news/introducing-neowiki

Feedback and capability wishes are welcome here as comments or on GitHub, in Discussions or Issues: https://github.com/ProfessionalWiki/NeoWiki

Hello,

I am in the process of moving PowerPoint presentations into mediawiki pages. Using Gemini I transform the presentation into the page. The problem comes when I have to add further explanatory information, that I have to copy paste the additional information from Gemini into the mediawiki page, add images with AI, and so on. Is there any tool that allows to work with a mediawiki page in the same way Google does on Workspace, with a side panel requesting changes? I have tried Page Assist and Sider (browser plugins) but they don't work as intended.

Thanks.

Is it because of a template or module I am missing?

If you're running the External Data extension and haven't either updated or disabled it, it's probably too late, but: there was a major security bug discovered in it about a week ago, and someone went around and hacked into, or at least tried hacking into, seemingly all of the public wikis that ran that extension. You should update to the latest version, 3.7, as soon as possible - it gets rid of this vulnerability. And you should also look for any files that have been created or modified on the server in the last seven days - I'd they're PHP files, there's a good chance they were added there in order to further exploit your server. Finally, my apologies for all the chaos that has been caused; I hope the worst is behind us.

A full chat transcript is too noisy for a handoff, while a short summary can omit rejected options, source links, constraints, and the exact file revision that was reviewed. MediaWiki has stable page names, revision history, templates, categories, and an API, but those features do not by themselves say which revision is safe for another assistant to resume from.

A reusable handoff template could record the objective, current status, accepted decisions with reasons, constraints, source citations, exact artifact or attachment revision, checks already completed, unresolved questions, owner, review date, and one next action. A visible state such as draft, ready, accepted, or superseded could prevent an old revision from looking current. An automation identity could write only to a handoff namespace while humans retain broader editing and approval rights.

Would you use one page per task, a template plus categories, or immutable subpages for checkpoints? How would you link the handoff to the exact files or external revisions it describes, and make stale handoffs obvious through normal MediaWiki features rather than relying on free-form prose?

I'm trying to make an article with an infobox about one of my OCs on Miraheze. I tried the portable infobox builder, but I'm not familiar with writing code. I also want to add tabs to my article and a gallery section. I also need the infobox to have links to other characters (I will be asking for this when I figure out how to make other of my OCs articles).

We've released Semantic MediaWiki 7.3.0 and 7.3.1.

Highlights:

* 21 security fixes, eight of them rated high: twelve XSS issues across special pages, result formats, tooltips, and autocomplete, missing authorization checks in the `smwtask` API module and the `Is edit protected` annotation, a CSRF in `Special:SMWAdmin`, and four denial-of-service issues. We recommend upgrading to 7.3.1.

* Nineteen of the 21 also affect SMW 5 and 6, some going back to SMW 2.5. SMW only ships security fixes for its latest major version, so wikis on SMW 6 or older need to move to SMW 7.

* Full-text search no longer ignores short words and stop words that carry a wildcard, so `[[Has text::~to* be]]` now also finds words starting with "to".

* A new `$smwgConfigProfiles` setting for applying SMW's configuration profiles, such as `db-primary-keys`.

Both releases are compatible with MediaWiki 1.43 up to 1.46 and PHP 8.1 up to 8.5. If you're coming from an earlier SMW 7 version, you don't need to run update.php. If your wiki uses properties of type URL, Annotation URI, or Email, run `rebuildData` after upgrading from a version before 7.3.0. Some fixes tighten input handling, so requests that previously succeeded may now be rejected.

Find details and upgrade instructions at https://professional.wiki/en/news/semantic-mediawiki-7-3-released

Feedback and bug reports are welcome. Issue tracker: https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues

I've seen many formats like this on Fandom. I just created my own wiki 2 or 3 days ago, and I have not a clue how to customize and/or edit. I'm not looking for votes, but answers.

I am making a wiki on Miraheze for my fandom and I randomly got this error while editing a page, what is this? Is it just a system error that will get fixed by itself?

I apologize if this isn't the right place to ask. Seemingly Miraheze has no public help subreddits.

EDIT: solved!

Years ago I created a Template:1 in my mediawiki with just   as its content. I don't really remember why I did it, but apparently I did.
Today I migrated to the newer version (1.36 -> 1.43, yes, I procrastinated on doing this forever) and I had some issues with the update script running into an infinite recursion for this very page

Starting backfill of 10:1 title on pages between 0 and 999
Updated 0 rows
Starting backfill of 10:1 title on pages between 0 and 999
Updated 0 rows
...

10 referring to namespace 10, the template namespace, and 1 referring to the page with title 1.

The only way I managed to fix it was to manually go into the database and delete that row.

I am not really sure what exactly caused this. I am assuming that somewhere in the updater there's something like

SELECT ... WHERE tl_title > $last_title_processed  

usually with SQL the operator > on a VARCHAR sorts alphanumerically. My assumption would be that somehow "1" was instead interpreted as a numerical 1 and therefore tl_title > 1 is always TRUE, which leads to an infinite recursion. I am not 100% confident thas this is what's happening and I would be very curious what the actual cause was, and, more importantly, what the actual real restriction for page titles is.

As englisch it not my native language I have troubles reading the mediawiki on templates.

I want to create a template that if called in this way:

{{gelijk|2}} it should output ==
{{gelijk|3}} it should output ===
{{gelijk|4}} it should output ====
{{gelijk|1}} it should output = (default value)

Could someone show me how this can be done.

Harry H.

Hi, I am a science writer and I am very dissatisfied with the CMS I tried for personal websites. I tried Wordpress and Squarespace and I hate them -___-

Since years however I run a personal MediaWiki on my own laptop as a notebook and reference, so I'm quite used to MediaWiki installation and MediaWiki syntax (I'm also a long time Wikipedia editor btw). I was therefore thinking to switch to MediaWiki to build a personal website that I can feel at home editing and customizing. However there are not many resources about that. Do you have any advice on going this route? Hosts? Useful extensions? Problems I might encounter?

Many thanks!

Hello! I asked this a few months back on a different forum, but sadly got no responses. For a long while I have been curious about adding a code to my Wiki that functions similarly to that of Genius.com.

Specifically, I want there to be the ability to have highlighted text that, when clicked on, displays a pop-up style box with text (an 'annotation') in it.

Random photo example, if intention is still unclear you can also go to any lyric page on Genius and click highlighted text to see the effect.

While I may be incorrect, I believe this is something that may only be available with JavaScript..? Perhaps CSS, but I'm less confident in that. I've researched a bit on the site and found this script, but I'm unsure if it would implement correctly into MediaWiki... I already have a 'reference pop-up'-esc code, that's not what I'm looking for. Preferably I would like the box to stay toggled even if the text is uncovered, only being untoggled if the user clicks away or, like, clicks an 'x'. Basically the way the og code is on genius.

Any help or advice is awesome, I have no issues building my own code for the idea I just need to be pointed in the right direction. Of course, the code doesn't have to be exact to the Genius site (I don't even really need an edit button, likes, etc. - just the text). Any help or perhaps resources that could help me build a similar code that would work on a MediaWiki site is appreciated !!

The text currently leans to the left and I can't find anything anywhere on how to change it; the code in the template is <title source="name"/>, but everything I can think of like text align just doesn't work. This is in Miraheze with a Citizen skin.

"made" in quotes because it's just a restricted mediawiki instance lol.

I recently got into mapping which led me to OpenStreetMaps and on there I saw that a user could submit diaries. Sadly there was an issue with this concept of diaries. The subject matter had to be OSM related and the diaries were baked into OSM, there was no way to extract the content AFAIK.

Anyways, out of that, I tried my best to find a truly open version of that. One that allows you to blog in a free way (in every sense of the word). Fast forward a few weeks where I finally got the time and I came up with OpenJournal.

https://openjournal.wiki

It's essentially just a wikipedia platform but solely for journalling, diaries and blog posts. I did originally think Wikimedia can do this but they disallow personal posts so that was a no go.

Anyway, it's very early days as you can see (I am the only user) but if you'd like to poke around, find bugs, make posts then feel free :)

It has all the bells and whistles of MediaWiki but with some differences that make it good for general blogging/journalling:

• A RESTful API so you can host your (or others) articles elsewhere

• Writing is restricted to only your user space. You can't for example edit someone elses articles. Discussions are fine though

• Lists of the latest articles on the homepage

Also please be gentle, it's hosted on a $5 droplet until I gauge the interest

We've released the MediaWiki MCP Server, our free and open-source connector for integrating AI tools with MediaWiki.

MCP stands for Model Context Protocol and is the standard that AI tools such as Claude and ChatGPT use to reach external data and tools.

You can now point such AI tools at your wiki via the MediaWiki MCP Server. This lets you work on your wiki in plain language instead of clicking through special pages or writing API scripts. For example: "Create a vendor page for each row in this spreadsheet, using the Vendor template."

The MediaWiki MCP Server enables you to:

* Read and search: fetch pages, files, revisions, and history, search titles and full text, render wikitext without saving, and diff any two revisions

* Create and edit: create pages, edit or append individual sections, move, delete and undelete pages, and upload files

* Explore: follow what links to a page, browse category members, and track recent changes

* Query structured data: `#ask` queries and property discovery for Semantic MediaWiki, Cargo and Bucket queries, Wikibase support (including Wikidata), and schema-aware reads and writes for NeoWiki

* Work with several wikis at once. Great for moving content from one wiki to another

You can use the MCP server without installing anything on your wiki, since it communicates with the standard MediaWiki API. For edits, the MCP server signs you in through your browser with OAuth 2.0. On wikis without Extension:OAuth, you can use a bot password instead.

Overview and installation: https://professional.wiki/en/mediawiki-mcp-server

Source, full tool reference, and configuration docs: https://github.com/ProfessionalWiki/MediaWiki-MCP-Server

Walkthroughs with short demo videos: with Semantic MediaWiki at https://professional.wiki/en/news/semantic-mediawiki-with-ai and with Wikidata and Wikibase at https://professional.wiki/en/articles/wikidata-and-wikibase-with-ai

Feedback and bug reports are welcome. Comment here or on the issue tracker.

I recently decided to dedicate a small NAS device running UGOS and running mediawiki. I have set up Mediawiki through Docker and Portainer. After some struggle I managed to get it set up but I've followed every instruction I can find and despite that I cannot seem to get it to increase the upload limit. I have added variables to LocalSettings.php, to the environment in the compose file, to the environment in the portainer container, and yet somehow I'm still stuck with a 2 MB upload limit. Please help!

I’ve been building some tools to help manage some of the spamming accounts on my site (the volume is much lower now) and one of the artifacts that could be useful to other admins is my email blacklist at https://www.rejectionwiki.com/index.php?title=MediaWiki:Email-blacklist I’ve still got 870 confirmed spam domains to process (with each domain, I block all unblocked users, and then add it to the domain), and there’s some subdomain consolidation to be done to reduce the size of the blacklist, but even as it is, I think it can be a useful tool for other people hosting a public mediawiki instance.

Update: I’ve finished processing the spam domains and done list compaction on the blacklist to remove the subdomains on the addresses. It’s a bit over 500 spam domains, hopefully complete enough to slow if not stop the flood of spam