I think part of the issue is related to the syntax used in this template used for all funded grants in Project Grants, in addition to the individual templates for each button.

FormWizard is now operational in the Wikidata: namespace-- @Capt_Swing was able to solve the problem. See changes here to the javascript gadget file.

A little more detail:

Adding Trey (@TJones) to this task in case any related search work might be useful in ascertaining the cause of the problem or what approaches might help address it.

I've also tried reproducing this error, but I have not been successful with a few different browsers.

Filter was turned on today after updating the language on Wikipedia:User pages and developing an appropriate alert message when the filter is triggered.

The issue of unconfirmed editors not being able to edit their own user page has been resolved via use of a filter with the appropriate exceptions rather than using page protection as an implementation approach.

@Qgil I'm afraid I won't be able to attend the Summit, but I am interested in getting involved here, and am open to making changes to IdeaLab's structure to better accommodate technical proposals. I definitely encourage staff to use IdeaLab generally as a means to pitch ideas or draft proposals for the purpose of gathering community feedback. See this consultation where Community Resources pitched a new set of grant programs as an example, and followed-up with these outcomes based on the community feedback we received on the initial proposal.

The closing admin noted that this aspect was not supported by community consensus, so I think this request can't be fulfilled at this time.

@MusikAnimal Thanks for your work in writing up the filter and testing it out!

Thanks for all this work so far, @Halfak : )

@Halfak - Any idea on when this query might be able to be done? An RfC related to this data is being developed and the proposer is interested in getting this discussion started soon:

I've received a fatal error when attempting to use Notify Translators just now for this page:

Could we get an update on fixing this problem? Translation is a regular part of my work in terms of preparing consultations that extend to an international audience. After doing some testing myself, putting everything on one line doesn't appear to prevent the edit section links to stop working properly. They either produce errors in the form of "this section doesn't exist," or it attempts to edit another (usually subsequent) section altogether.

Co-op is inactive for the time being.

Co-op is inactive for the time being.

@Aklapper after bypassing my cache, meta.wikimedia.org is still gone.

Agreed, meta.wikimedia.org has been completely replaced with a broken-ish landing page for Wikimedia projects:

@cscott Oh neat! I didn't realize a script like this was hanging around. I'll see if I can wrangle up a few folks tomorrow and Friday to play around with this script.

A great use case for functionality like would be in edit-a-thons, especially ones that are conducted virtually. As an organizer, there are many many times I would like to be able to edit together with someone else, and there are sometimes editors working together. Some edit-a-thons are focused on building one or a small set of articles, in which collaborative editing in real time would be fantastic.

Finally! I've added a general banner to the top of the page pointing people to TWA and Teahouse, and why they may be better alternatives to the Co-op.

@Capt_Swing Yeah, I think a browser issue was the case. The two MediaWiki pages have been updated.

I've made the appropriate changes to the .js pages and the Gadgets-definition pages. I also had to restore the "Find a mentor" button to The Co-op front page, as it was commented out ebfore. The gadget is enabled in my preferences.

The specified pages were all moved over today to en.wiki.

OK. @Soni and I went back-and-forth how to organize learners and mentors. Personally, I am OK with either setup in terms of organizing learners and mentors in the space, and I think the category system works just fine. You make a good point about switching as being a matter of changing a few parameters. It would just need to be explained that this would need to be done manually rather than simply hitting the "become a mentor" button.

@Capt_Swing I think that would work very nicely, so let's go for it. Would the list be comprehensive or would it need to be updated in a report-like manner at the Teahouse?

I had said as much in this comment, and I agree that mentors can probably take care of tracking that one their own.

@Capt_Swing - Thanks for the update (and sorry I didn't get back to you yesterday). I think this will be an improvement, but @Soni and I were concerned that many editors who are recently autoconfirmed may have made a bunch of edits all at once and then dropped off. We're also a little concerned that 10 edits is quite small. Having done some evaluation of our mentorships so far, it appears that mentorship seems better suited for editors who are much more invested than this. Many new editors seem to be dropping off right away, even when a mentor contacts them.

@Fhocutt I think we can do without it then, given that it will happen infrequently-- and indeed, out of the 60 or so profiles in the space so far, this is the only case I've seen this double matching happen. I'll inform mentors that will happen rarely, but that whoever gets matched first is the *actual* mentor.

@Halfak Thanks for these more specific suggestions and providing that prior research as a basis for them. I support them. I also agree with @Soni that it would be helpful to know what criteria HostBot is currently using (which, as I recall, are the same as invitees for the Teahouse)

@Soni - Upon some examination, I believe the linking to an editor's userpage is embedded within the Module (https://en.wikipedia.org/wiki/Module:Co-op_profile), and I'm not sure how to implement this change. @Capt_Swing is better able to handle this, but this functionality is not critical for the space to work in that it saves a click to the editor's talk page.

I've updated the blocking tasks based on what is needed inre: performing deletions to allow Flow to be used on the Co-op.

Addressed with some helpful pointers from @Capt_Swing. : )

@Capt_Swing It might be best to just eliminate this circular frame and make it rectangular; I get the sense that it is causing more trouble than it is worth.

I've gone ahead and made this change. Thanks for the alternate option, Sohail.

@Mattflaschen If topics can actually be deleted individually, that's fine. I can direct admins who are mentors to use this method rather than attempt to delete the entire page, which addresses the issue with T90969.

A solid idea. I'll get to adding this in today. We of course want editors to use the Co-op, but I see no problem with adding in another box that provides some options for TWA and The Teahouse.