Page MenuHomeMiraheze

Validator-fatal-error with Maps on Famepedia
Open, NormalPublic

Description

For the entire Miraheze wikis

Please install this Validator Extension as it tends to be the solution to the

Validator-fatal-error

error message that shows on famepedia coordinates instead of maps. This would be needed for wikis that'd be using maps and anything coordinates.

Thanks very much. More information can actually be found at The Extension Page

Event Timeline

Universal_Omega claimed this task.
Universal_Omega edited projects, added Extensions; removed MediaWiki.
Universal_Omega moved this task from Backlog to Short Term on the MediaWiki (SRE) board.

Validator is an automatically installed composer extension, that is installed with Maps. The only issue with it is i18n does not currently work. Although I have seen this specific issue before, but it was resolved somehow. Can't remember how.

So how do I resolve this one please?

Can you please link the page this happens on?

Okay doing that now, so many pages though.

You could find such an error a the bottom of this article in particular, more can be found in this category

Please try disabling GeoData and try again.

Disabled but it changed nothing though

Interesting... I just traced everything on your wiki and it seems Maps itself is at fault. Just to see if it will work, do you mind trying to disable Maps entirely? As the issue seems to be it and it's validator interfering with https://en.famepedia.org/wiki/Module:Coordinates.

Ahhh, Let's see that
Maps itself is at fault on famepedia? Wow.
Let me disable maps and see

I'm unsure that'll work, because the Maps extension comes with a #coordinate parser function that is required by module Coordinate
It's no longer Validator-fata-error it now Lua error: callParserFunction: function "#coordinates" was not found.

I'm unsure that'll work, because the Maps extension comes with a #coordinate parser function that is required by module Coordinate
It's no longer Validator-fata-error it now Lua error: callParserFunction: function "#coordinates" was not found.

Ah, I see. I am not sure how we would resolve this then, but cords seem to show, just with error under it, you can probably use just CSS to hide the errors, and it should still work.

I'm unsure that'll work, because the Maps extension comes with a #coordinate parser function that is required by module Coordinate
It's no longer Validator-fata-error it now Lua error: callParserFunction: function "#coordinates" was not found.

Ah, I see. I am not sure how we would resolve this then, but cords seem to show, just with error under it, you can probably use just CSS to hide the errors, and it should still work.

Nope, it doesn't work at all, maybe you should purge, because I know very well that the module calls a parser function #coordinates and that parser function is only available when Maps is turned on.

What if we install the dependencies i18n wouldn't that help use without any stress? :((

I'm unsure that'll work, because the Maps extension comes with a #coordinate parser function that is required by module Coordinate
It's no longer Validator-fata-error it now Lua error: callParserFunction: function "#coordinates" was not found.

Ah, I see. I am not sure how we would resolve this then, but cords seem to show, just with error under it, you can probably use just CSS to hide the errors, and it should still work.

Nope, it doesn't work at all, maybe you should purge, because I know very well that the module calls a parser function #coordinates and that parser function is only available when Maps is turned on.

What if we install the dependencies i18n wouldn't that help use without any stress? :((

I am aware it won't work without maps I mean enable maps, then hide the errors with css.

I'm unsure that'll work, because the Maps extension comes with a #coordinate parser function that is required by module Coordinate
It's no longer Validator-fata-error it now Lua error: callParserFunction: function "#coordinates" was not found.

Ah, I see. I am not sure how we would resolve this then, but cords seem to show, just with error under it, you can probably use just CSS to hide the errors, and it should still work.

Nope, it doesn't work at all, maybe you should purge, because I know very well that the module calls a parser function #coordinates and that parser function is only available when Maps is turned on.

What if we install the dependencies i18n wouldn't that help use without any stress? :((

I am aware it won't work without maps I mean enable maps, then hide the errors with css.

Actually, as that template coord is placed at that bottom, it's not supposed to appear at the top left hand corner of th article page.
So... Hiding the error is not just the thing, it also needs to appear the top left hand corner not at the bottom.

Please are all the dependencies of the Validator extension installed? Don't you think that's why we have such errors?

Why does the i18n does not currently work?
Because I got help from someone and they said "that looks like a missing translation" that "Looking at https://codesearch.wmcloud.org/search/?q=validator-fatal-error&i=nope&files=&excludeFiles=&repos= it appears that it is used by JeroenDeDauw / Maps but defined in JeroenDeDauw / Validator (on GitHub they're now ProfessionalWiki/...)."
"If you did intend to install JeroenDeDauw / Maps it seems that you also need JeroenDeDauw / Validator"

And I think this whole comment makes sense
Here is a link to the JeroenDeDauw's Maps and Validator on Github

Please are all the dependencies of the Validator extension installed? Don't you think that's why we have such errors?

Why does the i18n does not currently work?
Because I got help from someone and they said "that looks like a missing translation" that "Looking at https://codesearch.wmcloud.org/search/?q=validator-fatal-error&i=nope&files=&excludeFiles=&repos= it appears that it is used by JeroenDeDauw / Maps but defined in JeroenDeDauw / Validator (on GitHub they're now ProfessionalWiki/...)."
"If you did intend to install JeroenDeDauw / Maps it seems that you also need JeroenDeDauw / Validator"

And I think this whole comment makes sense
Here is a link to the JeroenDeDauw's Maps and Validator on Github

I18n should be fixed with https://github.com/miraheze/mw-config/commit/9915567, it just needs rebuilt, and I'm currently not available to do that. Also their validator repository is apparently deprecated as obsolete since Validator is a composer dependency we don't need to install the actual extension. We actually removed it previously for that exact reason.

Please are all the dependencies of the Validator extension installed? Don't you think that's why we have such errors?

Why does the i18n does not currently work?
Because I got help from someone and they said "that looks like a missing translation" that "Looking at https://codesearch.wmcloud.org/search/?q=validator-fatal-error&i=nope&files=&excludeFiles=&repos= it appears that it is used by JeroenDeDauw / Maps but defined in JeroenDeDauw / Validator (on GitHub they're now ProfessionalWiki/...)."
"If you did intend to install JeroenDeDauw / Maps it seems that you also need JeroenDeDauw / Validator"

And I think this whole comment makes sense
Here is a link to the JeroenDeDauw's Maps and Validator on Github

I18n should be fixed with https://github.com/miraheze/mw-config/commit/9915567, it just needs rebuilt, and I'm currently not available to do that. Also their validator repository is apparently deprecated as obsolete since Validator is a composer dependency we don't need to install the actual extension. We actually removed it previously for that exact reason.

Okay, I just hope that the commit solves the problem after the rebuilt
But who can now help us do the rebuilt since you're not on ground for that? :((
@RhinosF1 can you help do the rebuilt? Or maybe @Voidwalker

@Universal_Omega Any luck on this?
You have time for this now> :((

Okay, I found out that map.wikimedia.org is not available for third-party wikis. Please check the $wgKartographerMapServer on FAMEPedia and check if it's on https://maps.wikimedia.org if yes, then we might start making progress when you change it https://maps.google.com or https://bing.com/maps.
The also the $wgKartographerStyles needs to change, I really don't know what it is current but maybe it could change to ["google-maps", "gp"]
I really don't know for that styles.

And If possible these options could be added to ManageWiki, I don't know if I should file a new task for these.

@Reception123 Please can anyone get to this? :((
The above?

@Reception123 I have been able to get maps working through...... As in this page

What remains is the validator-fatal-error we get on coordinates.
Which can probably be solved per the above comment. (I'd quote it below now).

Please are all the dependencies of the Validator extension installed? Don't you think that's why we have such errors?

Why does the i18n does not currently work?
Because I got help from someone and they said "that looks like a missing translation" that "Looking at https://codesearch.wmcloud.org/search/?q=validator-fatal-error&i=nope&files=&excludeFiles=&repos= it appears that it is used by JeroenDeDauw / Maps but defined in JeroenDeDauw / Validator (on GitHub they're now ProfessionalWiki/...)."
"If you did intend to install JeroenDeDauw / Maps it seems that you also need JeroenDeDauw / Validator"

And I think this whole comment makes sense
Here is a link to the JeroenDeDauw's Maps and Validator on Github

I18n should be fixed with https://github.com/miraheze/mw-config/commit/9915567, it just needs rebuilt, and I'm currently not available to do that. Also their validator repository is apparently deprecated as obsolete since Validator is a composer dependency we don't need to install the actual extension. We actually removed it previously for that exact reason.

The above thread. ^^^^

Could you please just make a new task instead of commenting on this closed task with unrelated discussion? You will have a better chance there, in my honest opinion.

What I'm requesting is still on-topic, will you now tell me that opening a new task talking about this same validator stuff isn't redundancy?

Void renamed this task from Install Validator Extension to Validator-fatal-error with Maps on Famepedia.Fri, Aug 27, 17:28
Void reopened this task as Open.
Void added subscribers: Universal_Omega, Void.

I18n should very likely have been rebuilt already. If the issue is still present it may be unrelated to other steps taken so far. It may be worth posting the stack trace to the error on this task (and preferably updating the description with more accurate details to the problem), so that it can be investigated more easily by others, and potentially be referred to upstream for assistance.

Actually at first I thought it was Maps, the coordinate template can not work without the Maps extension enabled.
I eventually got maps working, like Wikimedia maps now show up well on pages (you might want to check the pages with Maps category.

But yet the error still persists. I mean, I noticed something, that, the coordinate template when inserted in a page, is supposed to make the inputed coordinate appear at the top right hand corner of the page, as it is in Wikipedia. But the case here is that instead of going to the top right hand corner, it returns a {validator-fatal-error} message. You could check the coordinates on FAMEData category for pages with coordinates.

Right now, it's the coordinate. I don't know what Kartographer actually does since we have Maps, but I for sure know that the GeoData extension works along with the coord template too.

With my i18n fix, the error is now properly displayed:

Fatal error: The format of the coordinate could not be determined. Parsing failed.

The module seems to conflict with maps extension.

If disabling Maps from Special:ManageWiki/Extensions doesn't work, setting $egMapsDisableExtension = true; might work.

Okay, I'll disable the extension now and check.

It didn't work.
On preview mode, it doesn't show that error but yet it still doesn't work as expected.
But it doesn't work. So maybe the latter might work.

OK I will do some testing using test3 with the module and maps extension at some point in the next couple weeks to hopefully resolve this.