Page MenuHomePhabricator

itwiki: MediaWiki\Storage\NameTableAccessException: No insert possible but primary DB didn't give us a record for 'vue' in 'content_models'
Closed, DuplicatePublicPRODUCTION ERROR

Description

Steps to replicate the issue (include links if applicable):

  • On itwiki, try to create a page in the MediaWiki namespace with a .vue extension, for example MediaWiki:Test.vue.
  • Alternatively, try to change the content model of an existing page to vue.
  • Save the page or confirm the content model change.

What happens?:

The operation fails with a fatal error:

[f0f371b6-15a9-4ae0-9e73-fc61d81f757a] 2026-05-11 15:47:16: Fatal error of type "MediaWiki\Storage\NameTableAccessException"

As a result, it is not possible to create MediaWiki:*.vue pages or set the vue content model.

What should have happened instead?:

The page should either be created/edited successfully with the vue content model, or, if the vue content model is not supported/configured on itwiki, MediaWiki should show a handled, user-facing error message instead of throwing a fatal error.

Software version (on Special:Version page; skip for WMF-hosted wikis like Wikipedia):

Skipped: issue observed on WMF-hosted Italian Wikipedia.

Other information (browser name/version, screenshots, etc.):

Observed on Italian Wikipedia. Error ID:

[f0f371b6-15a9-4ae0-9e73-fc61d81f757a] 2026-05-11 15:47:16

Event Timeline

valcio renamed this task from Cannot create MediaWiki:*.vue pages or change a page’s content model to Vue on itwiki to itwiki: MediaWiki\Storage\NameTableAccessException: No insert possible but primary DB didn't give us a record for 'vue' in 'content_models'.May 11 2026, 3:53 PM
Restricted Application changed the subtype of this task from "Bug Report" to "Production Error". · View Herald TranscriptMay 11 2026, 3:54 PM

@Novem_Linguae It's moot now (given T410483#11910828), but just fwiw -- this was closed as a duplicate of the parent task, but from looking at that task's children, it seems like this might be something that's previously been solved (I guess maybe as an interim measure) on a wiki-by-wiki basis (in which case having a separate task to fix itwiki seems like it might've make sense). Just my thoughts, ymmv :)