Sorry for the delay. And thanks! So what is the input type that you get for that field?

Sorry, I can't reproduce this problem. By the way, that form definition is strange - because there is no input type defined, "values from namespace" will not have any effect - it's just a text input. Or do you something other than a text input there?

Okay, thanks. Is there a corresponding "Test" template, which contains a "test" field?

What does the full form definition look like?

I'm closing this as "invalid", because I'm pretty sure this has been fixed in the latest version of Page Forms. That said, if you upgrade Page Forms and still get this bug, feel free to re-open it.

@Krabina - is the issue that invalid approvals can't be removed? Because there's a relatively new script in AR, removeInvalidApprovals.php, that is meant to take care of this problem.

I added an en.json file here, with all the text messages I could find in App.vue and ArticleModal.vue:

Well, the first step is to add the right structure to the code, ideally by having an i18n/ directory containing at least two files, en.json and qqq.json. After that, it's certainly possible that the translatewiki.net people could be convinced to add this project in to their system.

Great to hear!

Great!

Closing this, because I think it's fixed.

@Christian.aus.Berlin - sorry about the problem. That's a pretty big bug! I think it's fixed now.

@Elisapoly - thanks for the bug report, and the fix!

Great!

@Renegade04 - sorry about that problem; I think it's fixed now.

Great!

Thanks!

What version of Page Forms are you running?

@Pushpaktiwari, @AndrewESayers - thanks to both of you for your intrepid work on this!

Good to hear!

Oh, sorry I didn't respond here. I believe this was fixed in 6ec2940a4f31, which means that "blank if unapproved" now works correctly again in version 2.4.1.

Okay, I get it - somehow I didn't realize that text input was a text input, maybe because it has no label.

Why is there no actual text input in the screenshot? Am I missing something?

Ah, yes - I had thought that was already covered on that page, but it wasn't really; I just added a note about that. Sorry about that problem.

I think this problem has already been fixed, so if you get the latest version of Page Forms, 6.0.8, it should work fine. In general, you should avoid using the "REL_" branches for Page Forms and just use master.

What's the actual input type, as specified in the form definition? Better yet, could you put the entire form definition here, if possible?

That screenshot looks strange - what is the input type you're using there? And how does NSFileRepo relate to this, if at all?

Oh yeah... sorry about that.

@Andmcadams - thanks for the patch! I just checked it in at https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Cargo/+/1298854

Thank you!

I'm glad it worked, though with some difficulty! Can this be closed?

@Disgustedorite - do you know about the regexp input type?

Thank you, @Osnard, for the fix!

This very long-running request has finally been fulfilled! Thank you, @Dumbledore .

Fixed, I think! Thank you, @Dumbledore .

Sorry, I let this slip. I did add in validation for that 2nd date issue, so that should no longer be a security leak either. If you know of other specific security issues with Special:Drilldown, please let me know. It would be great to change the code to use the SelectQueryBuilder, but I haven't done it yet. I'd be happy to accept a patch from anyone else that does this changeover, by the way.

Okay, that's good to know, thanks.

Oh! I didn't know that. How did they choose which two to reject?

Great to hear!

@asd - thanks for that bug report. This may be fixed now; if you try the latest code, please let me know!

I believe this is fixed now! Feel free to re-open if there are any problems with tabindex.

I believe this is fixed now! Though feel free to re-open if there are still any problem with tokens mapping.

Hi @th33k - unfortunately, this entire project was rejected; Google only gave the Wikimedia Foundation 8 slots this summer, and there were 10 potential WMF GSoC projects, so this was one of the two projects that the WMF admins decided to not submit. Your application was good, from what I remember, as were your microtasks.

I believe this was implemented in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Wanda/+/1270498 !

@SomeRandomDeveloper - thank you for finding this issue, as well as the fix for it. I have added some subscribers to this task.

Thank you also!

Done! Thank you, @TechieNK!

@Raymond - sorry for the delay. Yes, it works great; thank you!

The three extensions are connected: WandaScore and WandaScribe both require Wanda. I suppose that means they should be grouped together, though it probably doesn't matter that much in practice.

The actual application, on the GSoC website, was submitted before the deadline, for what it's worth.

Ah, yes, I missed that character. Well, switching to SelectQueryBuilder makes sense, though I think the validation is useful regardless, so that the malicious text is not displayed on the page.

@GICodeWarrior - thanks for pointing this out. I couldn't replicate that specific problem, and your two mock URLs look identical, but I assume both of those are just due to transcription errors. I just checked in this fix:

Fixed! Thank you, @Lakshya_Saxena, for the fix.

Adding another parameter to PFFormPrinter::formHTML() makes sense. I think modifying those other methods is fine also - as far as I know, there's currently only one other extension that defines a Page Forms form input, MintyDocs, and it can easily be modified to switch to the new header style.

Fixed! Thank you, @TechieNK .

Three years later, I think this is finally fully done! Thank you to @TK-999 and @Alex44019 for your help!

Done by @Lakshya_Saxena!

Oh! Yes it is, wow.

Fixed! Thank you, @TechieNK .

Actually, it looks like this was already reported in a different bug...

Oh, I see - renaming this bug now.

I believe this is now fixed! Thank you @Lakshya_Saxena for the fix.

That sounds right.

@Tan25489 - that's great! Let me know if you run into any problems.

Thank you, @cicalese, for the fix!

Thank you, @th33k, for the fix!

Done! Thank you, @th33k, for the fix. (And thank you also to @ChefYeshpal for your involvement.)

Done! Thank you, @ChefYeshpal.

Thank you! It works with "--use-latest-versions".