Please open your browser console (press F12 to open it), There more information about the error in the "Network" and "Console" tabs.

Also, make sure you can view https://www.wikidata.org/ and is logged in there.

@Bugreporter I tried as you said but I couldn't do it. I think this is a software wiki error, Please try checking the wiki software for errors, thanks .

I tested this and when I click on add interlanguage links I get redirected to the corresponding Wikidata item. (I tested it on https://en.wiktionary.org/wiki/Template:uk-1928_superseded_spelling_of ) and both logged in and not logged in. So doesn't sounds like a software issue.

@Mbch331 Try connecting these two Template:fr-preposition and ထာမ်ပလိက်:fr-preposition, I myself don't understand how this needs to be fixed. anyway, I need your help. Please try again, thanks .

On https://mnw.wiktionary.org/wiki/%E1%80%91%E1%80%AC%E1%80%99%E1%80%BA%E1%80%95%E1%80%9C%E1%80%AD%E1%80%80%E1%80%BA:fr-preposition I do get an error.
Error: Dependency jquery.wikibase.linkitem failed to load

enqueue https://mnw.wiktionary.org/w/load.php?lang=nl&modules=startup&only=scripts&raw=1&skin=vector-2022:10
jQuery 6
    using
    initLinkItem
    js
    dispatch
    handle
    addInterwikiLinkToMainMenu

load.php:644:56

jQuery 4
    initLinkItem
    fire
    fireWith
    tuple[0]
enqueue https://mnw.wiktionary.org/w/load.php?lang=nl&modules=startup&only=scripts&raw=1&skin=vector-2022:10
jQuery 6
    using
    initLinkItem
    js
    dispatch
    handle
    addInterwikiLinkToMainMenu

In T390949#10707543, @Mbch331 wrote:

I tested this and when I click on add interlanguage links I get redirected to the corresponding Wikidata item. (I tested it on https://en.wiktionary.org/wiki/Template:uk-1928_superseded_spelling_of ) and both logged in and not logged in. So doesn't sounds like a software issue.

The same issue is being reported on itwiki. It happens with unconnected items, when clicking on "Add interlanguage links" in the sidebar.

Thanks for the report - I'll take a look. It does seem like it is probably related to the recent changes, and I am able to reproduce the issue between my local development wikis.

Change #1134174 had a related patch set uploaded (by Arthur taylor; author: Arthur taylor):

[mediawiki/extensions/Wikibase@master] Add Item and CustomItem classes as properties to `$.ui.ooMenu`

https://gerrit.wikimedia.org/r/1134174

Change #1134190 had a related patch set uploaded (by Lucas Werkmeister (WMDE); author: Arthur taylor):

[mediawiki/extensions/Wikibase@wmf/1.44.0-wmf.23] Add Item and CustomItem classes as properties to `$.ui.ooMenu`

https://gerrit.wikimedia.org/r/1134190

Change #1134174 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@master] Add Item and CustomItem classes as properties to `$.ui.ooMenu`

https://gerrit.wikimedia.org/r/1134174

Change #1134190 merged by jenkins-bot:

[mediawiki/extensions/Wikibase@wmf/1.44.0-wmf.23] Add Item and CustomItem classes as properties to `$.ui.ooMenu`

https://gerrit.wikimedia.org/r/1134190

Mentioned in SAL (#wikimedia-operations) [2025-04-04T10:46:25Z] <lucaswerkmeister-wmde@deploy1003> Started scap sync-world: Backport for [[gerrit:1134190|Add Item and CustomItem classes as properties to $.ui.ooMenu (T390949)]]

Mentioned in SAL (#wikimedia-operations) [2025-04-04T10:54:03Z] <lucaswerkmeister-wmde@deploy1003> lucaswerkmeister-wmde: Backport for [[gerrit:1134190|Add Item and CustomItem classes as properties to $.ui.ooMenu (T390949)]] synced to the testservers (https://wikitech.wikimedia.org/wiki/Mwdebug)

Mentioned in SAL (#wikimedia-operations) [2025-04-04T11:01:29Z] <lucaswerkmeister-wmde@deploy1003> Finished scap sync-world: Backport for [[gerrit:1134190|Add Item and CustomItem classes as properties to $.ui.ooMenu (T390949)]] (duration: 15m 04s)

The fix for this has been rolled out to production - please retest and let us know if the issue is resolved for you. We have filed a follow-up ticket T391089 to add automated tests of the functionality to avoid similar regressions in the future.

In T390949#10712341, @ArthurTaylor wrote:

The fix for this has been rolled out to production - please retest and let us know if the issue is resolved for you. We have filed a follow-up ticket T391089 to add automated tests of the functionality to avoid similar regressions in the future.

Tested with a newly created article and I cannot reproduce it anymore, thank you.