Hello. Unfortunately I am still stuck on this extension, and haven't much progress on my website as I am still determined to prepare a functional JSON/JSON5 environment implementation. As of this time I have not been able to prepare any sufficient code that is actually of significance or value. I probably opened this ticket prematurely, and if necessary, you are welcome to close it if you would like.

https://phabricator.wikimedia.org/T307631 closed as a duplicate of this issue.

Thank you for assigning the task to me. I saw the task status change since May 12th, and since I initially considered working from scratch, at the time I did not have any code ready to publish that is functional, and I am still working on developing an initial code base to submit. I'm also tinkering with forking the JsonConfig extension as well. As I get a reasonable code base to push git commits to a public repo, I'll follow up with the progress here.

https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/JsonConfig/+/refs/heads/master/i18n/qqq.json#56

	"jsonconfig-optional-field": "A short suffix appended to one of these messages to indicate that the field is optional.\n* {{msg-mw|Jsonconfig-err-bool}}\n* {{msg-mw|Jsonconfig-err-string}}\n* {{msg-mw|Jsonconfig-err-integer}}\n* Or any other field error message provided by another extension\n{{Identical|Optional}}",

Also I am using this code snippet for Supporting Wikimedia templates https://mediawiki.org/wiki/Extension:JsonConfig#Supporting_Wikimedia_templates

Also note that this doesn't help to explain the Apache error log warning messages:

Where 'this' is defined as why does https://dev.moasspedia.org/w/index.php?title=Ape_data:Ape-made_artwork33&action=edit show permission denied, and https://dev.moasspedia.org/w/index.php?title=Ape_data:Ape-made_artwork33.json&action=edit is valid because it matches regex rule (and the expected behavior is for JsonConfig to entirely ignore anything that doesn't match, and to not interrupt with showing permission denied)

Repeating this bug mention https://phabricator.wikimedia.org/T307978#7916685 since it appears this task is closed, and the bug is perhaps still not yet resolved, and I believe that this is related to "something is wrong in the code base (a so-called "software bug")":

@Aklapper Also I am curious, how do I tag the JsonConfig project in the MediaWiki Support Desk so that relevant devs can easily identify the support question being tagged/affiliated with the project?

@Aklapper Aha! Thank you! I made this mistake this entire time. I intended this as a support request, but also slightly skeptical that it may be a bug, but that is not my intention/priority. I'll mention in the Mediawiki Support Desk also.

Several days back in the Libera.chat IRC channel I suggested:

Also, I think I better understand the case that using the 'json' (CONTENT_MODEL_JSON constant in MediaWiki) content model type, which I initially thought was preferable to use and build on top of, that this is not the case, and that I should instead utilize the content model types created by JsonConfig extension. In this case, however, I am curious about the slight differences in html rendering markup that exists between the two views. For example:

Yuri replied to my email also:

I stumbled upon this strange issue with LocalSettings.php commenting out all of my JsonConfig configurations, and using only:

Also per further comparison of the HTML output rendering from the native 'json' content model type to the one provided by JsonConfig, I see the native 'json' shows:

Also see

Is there a reason that JsonConfig is not able to allow pages to be created so that the MySQL database pages table page_content_model column is set with the value 'json' using MediaWiki's native model type for this? Is it necessary that JsonConfig ignore/neglect that existing model type to reproduce/replicate/duplicate it redundantly? And if so, it is there any way that JsonConfig can ensure that editing pages with either of the identical content types are not showing any errors preventing editing user interface expereince?

I stumbled upon this proposal and thought I would ask, has anyone here heard about Nuxt? Also Nuxt3 was announced/released recently too. https://v3.nuxtjs.org/

Also continuing from where I last left off in The W3C CSS Validation Service results:

Also noting from my mention of this yesterday on IRC in Libera.chat/Mediawiki,

I got a reply from IRC Libera.chat/MediaWiki:

Closing this since the latest version in git repo does not reproduce the error.

As a newbie, I am determined to figure out why and resolve issues with ExtensionDistributor releases not having the actual latest version releases. I just started learning about this extenison in the last 24 hours or so, but I also noticed https://phabricator.wikimedia.org/feed/7086462105921143751/ and of course the very first concern I saw at https://www.mediawiki.org/wiki/Extension:External_Data/Download_and_installation ("Not recommended" section) mentioned similarly, however, I asked about this on MediaWiki discord server, and response was:

So... all three of my inquiries regarding this ExternalData extension:

I see the git repository has a lot of code revisions changing the functions related to this post also. It seems this is already being worked on, and the tag appears to be customizable by site admins.

Also, I propose suggestion to change the code so that the tag created by this extension matches the name of the extension. e.g. <externaldata>...</externaldata> and <externaldata />

In T307136#7889737, @Aklapper wrote:

@Jasonkhanlar: Hi, do you plan to disable https://github.com/jasonkhanlar/mediawiki-extensions-PhotoSwipe/issues ?

"if you're willing to use Phabricator for bug tracking re extension PhotoSwipe."

Oops! I am sorry for removing @MarcoAurelio as assignee of this task! That was not intentional! I think it happened because I was editing at same time as assigned. My apologies!