## Misc

• Set a small-text notice or a tooltip on skill pages (both medical and not) that says "click on timestamps to navigate through the video" --Emilio (talk) 22:17, 9 December 2020 (UTC)
• Adding license and keywords parameters to Template:Video.
• Increase margin-right of the image of Template:Mbox
• Add link to the GSTC Toolbox from GSTC
• Create GSTC banners reminiscent of https://www.nremt.org with the ability to set the color, logo, and text separately
• Add image to NREMT Skillset
• Perfect video display on all screen sizes
• Fix error with video at CPAP (Continuous Positive Airway Pressure) Administration
• Timestamp links don't work on mobile (Android)
• Make links to timestamps work
• Make Template:Banner cover full width and maximum height of 275-300px perhaps
• Fix VisualEditor error on subpages
• Whitelist self.gutenberg.org
• Verify that GSTC medical skills look fine on mobile
• Add feedback button
• Investigate if SMW can detect linked files and show in the infobox
• Video annotations form isn't showing
• Fix bug when linking to the English Wikipedia
• Show history button by default in the Poncho skin
• In GSTC, change the selected skill section for the toolbox page
• In GSTC, set NREMT Skillset as the default example course
• Create Template:Banner
• Some GSTC medical skills do not show the parent skills, despite being children
• Add assessment box to Template:Infobox GSTC medical skill
• Our platforms are MediaWiki and to a lesser extent WordPress, both of which are coded in PHP. We are working on getting a number of extensions working (see the Tech workstream). This means researching, choosing possible solutions, installing them on the dev site and troubleshooting, as well as related server work.
• We do some work with Pywikipediabot, which uses Python scripts. See Appropedia:Bot tasks. There are sometimes some modifications we would like to make to the scripts.
• Smart phone apps for iPhone (Objective C and/or C++?) and Android (Java and/or C++?). We hope to have a mobile skin active soon, but an app for people to get in the Android Market or iPhone app store would be a big plus.
• Skin - we are working on a mobile skin and probably a new regular skin (or more precisely, User:Tahnok is working on them, mid-2011).
• An anti-vandal bot - adapt from from one of the ones used on Wikipedia. (This looks like a difficult job, though, and isn't one of our top priorities, so only if this is the only task that grabs your interest.)
• Navigation banner for visitors from partner sites (work in progress, mid-2011)

## Install mw:Extension:GoogleAnalyticsMetrics

Sophivorus (talk) 22:20, 10 December 2020 (UTC)

@Emilio Hi! Check out this ugly link and the pages that make it possible: Appropedia:Analytics, Form:Analytics and Template:Analytics. Soon I'll add links in the infoboxes. Feedback welcome! Sophivorus (talk) 22:07, 16 December 2020 (UTC)
Oh my!!!! @J.M.Pearce, you have to see this! Emilio (talk) 22:11, 16 December 2020 (UTC)
I would recommend adding below a title as "Pageview report for {{PAGENAME}}". Emilio (talk) 22:26, 16 December 2020 (UTC)
Done! Sophivorus (talk) 12:17, 17 December 2020 (UTC)

## Install mw:Extension:DiscussionTools

Much more likely to receive future support than mw:Extension:Flow. Sophivorus (talk) 22:20, 10 December 2020 (UTC)

I tried installing this extension on a wiki of mine and although the installation went smoothly and there were no errors, it just doesn't seem to work! I reported the issue at https://www.mediawiki.org/wiki/Topic:Vzeokjjlr5czh9v0, lets hope for an answer soon. In any case, however, the extension is still rather immature and some key functionalities (like a friendlier way to start a new talk page) are still upcoming, so I think we should be patient and it'll eventually work. Sophivorus (talk) 14:44, 11 December 2020 (UTC)
I want to propose testing this extension in a section other than the talk pages, perhaps a place like Appropedia:Village Pump and a lounge-type space for the GSTC. This will allow us to see how users interact with it and to debug it more smoothly. What do you think of this idea? --Emilio (talk) 22:32, 11 December 2020 (UTC)
Hi! I just finished installing DiscussionTools. I also styled the comments on the talk namespace and on the Appropedia namespace, check it out! Finally, notice that some of your comments on the Village Pump don't have the [reply] button. That's because you probably signed with three ~~~ and the software detects signatures based on the timestamp added by four ~~~~ That being said, from now on, when replying using the new tool, signatures are added automatically. Cheers! Sophivorus (talk) 20:34, 14 December 2020 (UTC)

## Create support page for the GSTC

Perhaps make something similar to the Village Pump. --Emilio (talk) 21:11, 1 January 2021 (UTC)

Done! Emilio (talk) 14:36, 2 January 2021 (UTC)

## Skill page video error

Check this. The video input isn't a text box. --Emilio (talk) 04:55, 2 January 2021 (UTC)

Fixed? The "simple upload" feature of the PageForms extension can only be enabled at the site level, which means that every uploadable field got simplified. Sophivorus (talk) 12:21, 2 January 2021 (UTC)

## Skill pages (both regular and medical) do not navigate back to 0

@Emilio Fixed! Sophivorus (talk) 12:42, 30 December 2020 (UTC)

## Hide YouTube ads from embeded videos

Sophivorus (talk) 18:01, 24 December 2020 (UTC)

YouTube no longer allows this, but I limited the related videos to videos from the same channel. Sophivorus (talk) 12:32, 30 December 2020 (UTC)

## GSTC course form prompts wrong form

When editing a GSTC course (see for example this) and add a non-existent skill, it opens with Form:Skill instead of Medical_skill.

@Emilio Fixed! Sophivorus (talk) 12:13, 24 December 2020 (UTC)
@Sophivorus ¡Gracias! No estaba seguro si solo eso había que editarse, por eso preferí esperar. :) —Emilio (talk) 12:52, 24 December 2020 (UTC)

## Hotjar feedback form covers overlay photo navigation

link=https://www.appropedia.org/File:Hotjar feedback nav issue.jpg

A user pointed out a problem navigating (the Hotjar button hovers over the next button) when viewing the clicking on images on mobile to view as a slideshow: How to: Reciprocal Roof.

Fixed! Sophivorus (talk) 15:35, 14 December 2020 (UTC)

## Install mw:Extension:Popups

Sophivorus (talk) 22:20, 10 December 2020 (UTC)

Done! Sophivorus (talk) 13:43, 11 December 2020 (UTC)

## Unify templates that should be using Template:Fix as a meta-template

Sophivorus (talk) 22:20, 10 December 2020 (UTC)

Done! Sophivorus (talk) 15:02, 15 December 2020 (UTC)

## Infobox device bug

I noticed that the infobox currently requests contributor usernames in the form User:USERNAME, but the asynchronous search function only displays USERNAME, which had me confused for a bit. It took me about five minutes to find out what was the right way to do it. —16:09, 15 December 2020 (UTC)

@Emilio Unfortunately the search function of the PageForms extension doesn't show the namespace and doesn't have an option to show it. I disabled the search function from the "authors" field to avoid confusion. Ok? Sophivorus (talk) 13:45, 4 January 2021 (UTC)
No worries, thanks. Emilio (talk) 15:37, 4 January 2021 (UTC)

## Improve Template:Banner

Make it hide the page title and actions and incorporate the actions to the banner to give it more prominence. Sophivorus (talk) 16:06, 17 December 2020 (UTC)

@Emilio Hi! I copied the banner to Template:Header (since it's becoming more of a header than a banner) and made several improvements. Now whenever a page uses this template, the title of the page gets hidden, see for example GSTC. I also did several CSS improvements. Next I'll focus on getting it to display right on mobile devices and adding the possibility to add other links to the header, so as to turn it into a sort of menu. I also did some changes to the Poncho skin to better accommodate hidden titles and other issues. I'm still working on it so please use Vector in the meantime. Cheers! Sophivorus (talk) 15:26, 18 December 2020 (UTC)
@Emilio Hi again! I just finished improving the Template:Header. It now displays much better on mobile devices (though there's still room for improvement) and more importantly, it now includes a bunch of parameters for creating a menu within the header. See GSTC for an example and the template documentation for more. This also deprecates Template:Banner, which is now a redirect to Template:Header. Cheers! Sophivorus (talk) 16:34, 24 December 2020 (UTC)
Simplified the menu parameters and did some tweaks to optimize mobile display. Sophivorus (talk) 14:48, 3 January 2021 (UTC)

## Create template for file pages

The template should get automatically inserted when uploading a new file. See File:Stick figure.svg Sophivorus (talk) 18:28, 24 December 2020 (UTC)

I renamed Template:Information to Template:File info, improved it and made it the default template when uploading via Special:Upload. However it seems like it isn't possible to do the same when uploading via the forms (due to limitations on the PageForms extension) nor the visual editor (probably). I'll try to figure out the best way to provide a simple, easy and consistent file-upload flow within the software limitations. Kind regards, Sophivorus (talk) 16:43, 30 December 2020 (UTC)
@Emilio Today I found about \$wgUploadDialog and I was able to configure the file upload mechanism of the visual editor so that it also uses the Template:File info, yay! Check out File:Vegetable garden in Junín.jpg for an example of an uploaded file, and please try it out yourself when you find the time. There're still many things to improve but I think we're getting there. Next step would be trying out what the Extension:UploadWizard can do to see if we can provide an even simpler and more consistent file upload experience, as well as creating a Form:File for editing the entire File namespace. Cheers! Sophivorus (talk) 14:00, 31 December 2020 (UTC)
I'm testing it! Can you please allow the mp4 format for the UploadWizard? Emilio (talk) 04:08, 3 January 2021 (UTC)
@Emilio Done! Sophivorus (talk) 11:58, 3 January 2021 (UTC)

## Tooltips do not seem to work on Poncho

See for example, How to use Appropedia and the ones on the form at Airway Management. --Emilio (talk)

@Emilio Fixed! I also did several other fixes and improvements to Poncho, see https://gerrit.wikimedia.org/r/q/project:mediawiki%252Fskins%252FPoncho Sophivorus (talk) 13:41, 14 January 2021 (UTC)

## Jan 2021 GSTC checklist

• Add free-form text field to video annotations - DONE
• Clicking on a timestamp should scroll to the video - DONE
• Reorder elements on the mobile version of GSTC pages, banner on top - DONE
• Enhance the GSTC knowledge page infobox to set subskills and to show the parents in the infobox - DONE
• Hide the hashtag # when linking to a section in the GSTC infobox - DONE
• Clicking on a timestamp should play the video - DONE
I wonder. It does work for me when I enter a page and click on the timestamp. I believe that it doesn't work after editing a page. —Emilio (talk) 16:30, 11 January 2021 (UTC)
@Sophivorus, GSTC Here is an explanation. We just noticed that it is in Chrome that it doesn't work (videos play for me as I use Firefox). —Emilio (talk) 16:39, 11 January 2021 (UTC)
Ah, I see. Nothing we can do about that then, I'm afraid. I've marked the task as DONE. Sophivorus (talk) 16:42, 11 January 2021 (UTC)

## Wikipedia section excerpts

Following Appropedia:Village pump#Wikipedia excerpt templates?, make {{Wikipedia excerpt|Article#Section}} work, maybe by combining Module:Excerpt with Template:Wikipedia excerpt. Sophivorus (talk) 14:27, 12 January 2021 (UTC)

Done! Sophivorus (talk) 12:42, 18 January 2021 (UTC)

## Update Template:How to

@Emilio Ongoing work is at Template:Steps. See the template documentation and the following cases where I just replaced the old template for the new one, without modifying anything else (check them out on mobile too!):

Unfortunately, hacky cases like Design of a low-cost household water treatment system#Assembly will inevitably need manual intervention. Let me know of any feedback! Sophivorus (talk) 13:45, 13 January 2021 (UTC)

This is one of the best improvements on Appropedia ever! Emilio (talk) 16:30, 13 January 2021 (UTC)
@Emilio Hi! Today I finished the new template and made the old one a redirect to the new, so that it's now officially gone. I was also able to find and fix all "hacky" cases. Cheers! Sophivorus (talk) 15:03, 14 January 2021 (UTC)
I tweaked the stylesheet a bit to have some padding and added a left border with a gradient just to test visual cues. It's just a test, for now, so let me know what you think. We can also consider using box-shadow or something along those lines to showcase each step. Emilio (talk) 19:40, 14 January 2021 (UTC)
I am loving these developments! Hopefully all the old weird ways we used the template make it through...and I will make sure future students fit this much cleaner style. --Lonny (talk) 00:01, 15 January 2021 (UTC)

## Broken Search

The SDG input at Search doesn't work for me.

Fixed! Sophivorus (talk) 12:35, 22 January 2021 (UTC)

## Add bold tags to timestamps on skills infobox

The objective is to make obvious that the timestamps and the links are two different ones. --Emilio (talk) 19:23, 25 January 2021 (UTC)

@Emilio Done! Sophivorus (talk) 13:59, 27 January 2021 (UTC)

## Change order of video on mobile version of skill pages

The requested order is: banner-video-infobox. --Emilio (talk) 19:24, 25 January 2021 (UTC)

@Emilio Done! Sophivorus (talk) 14:06, 27 January 2021 (UTC)
@Sophivorus it appears not to work well. Emilio (talk) 18:46, 1 February 2021 (UTC)
@Emilio Now yes, thanks for verifying. Sophivorus (talk) 20:34, 1 February 2021 (UTC)

## Confirm whether CleanTalk is correctly installed

See this link. Thanks! —Emilio (talk) 01:14, 2 February 2021 (UTC)

Fixed! Sophivorus (talk) 20:50, 2 February 2021 (UTC)

## Show video on Form:GSTC medical skill

This would make it much easier to add video annotations. It isn't pretty but it does seem to be useful. --Emilio (talk)

@Emilio I'm not even sure this is possible. Did you find a way? Sophivorus (talk) 13:21, 11 December 2020 (UTC)
@Emilio @GSTC Hi, great news! I found a way to embed the videos, check it out! Sophivorus (talk) 12:44, 3 February 2021 (UTC)
Are you talking about embedding the video in the form? Yes, that would be very useful when writing your annotations! GSTC (talk) 03:05, 10 February 2021 (UTC)

## Template for inline attention messages

@User:GSTC and User:Emilio: Today I created Template:Attention. Is this the kind of template you were thinking of? Are the colors ok? Cheers! Sophivorus (talk) 15:32, 22 January 2021 (UTC)

This hadn't been on my list, but it looks useful. The colors are quite visible. Will they change as skins are created, or are the colors hard coded in? GSTC (talk) 03:11, 10 February 2021 (UTC)
@GSTC The color was hard-coded, but I just made it configurable. Check out the template documentation again for an example, cheersǃ Sophivorus (talk) 13:23, 11 February 2021 (UTC)

## Add list of "what links here" pages to GSTC knowledge pages infobox

Something along the line of: "Pages that link here" (within the GSTC category). Is there a way to do that? The original request was to help people go back to the previous page where they came from. --Emilio (talk) 19:30, 25 January 2021 (UTC)

@Emilio There's no way to do that with current tools. I could develop a small custom extension. However, if the request is really to give people a way to go back, that's what the Back button is for (one of the most basic features of every browser in existence). Sophivorus (talk) 13:30, 27 January 2021 (UTC)
@Emilio @GSTC Hi! I developed a small custom extension for the job, and added a "What links here" section to the infobox of knowledge pages, check it out! Is this what you were thinking of? Let me know if you'd like to change the title of the new infobox section, or if you'd like to tweak the functionality in some other way! Sophivorus (talk) 21:24, 2 February 2021 (UTC)
This looks great! This is exactly what I wanted. GSTC (talk) 03:12, 10 February 2021 (UTC)

## Fix dead links

@Emilio, Kathy Nativi As Kathy pointed out, dead links affect SEO and UX negatively, it would be great to fix them. I checked Wikipedia:User:InternetArchiveBot and https://github.com/Internetarchive/internetarchivebot, but they seem overly complicated and Wikipedia-specific. On the other hand, the Internet Archive's Wayback Machine API seems amazingly simple to use, and given that we already have a CSV with all or most the dead links and the pages where they're found (see https://docs.google.com/spreadsheets/d/1lK8Vx9mrCziXscae9GQCGvl2nf_v1XKS_3oMav_kYmU) it should be quite easy to write a script to replace the dead links for archived ones. Sounds good? Sophivorus (talk) 13:21, 27 January 2021 (UTC)

@Emilio, Sophivorus Yay! That sounds great! Just one more thing and I don't know if this is gonna make a difference, but the last time Ahrefs crawled http://web.archive.org/web/20210310224331/https://permies.com/forums/, it responded with a 404 HTTP status, so they reported it as broken. I reached out to someone from tech support and was told that the next time they crawl that page, and if it's live and responds with a 200 OK HTTP status, it will be reported as a live link again. Let me know if there's anything I can help you with! :)
@Kathy Nativi I'll make an exception for permies.com, cheers! Sophivorus (talk) 14:12, 27 January 2021 (UTC)
Yes to all! We had actually been looking at Wikipedia:User:InternetArchiveBot and wondering if we could implement something like this. I think we must be careful to maintain many old links since they're references to projects and other content that doesn't exist anymore. So this is perfect! Emilio (talk) 16:04, 27 January 2021 (UTC)
@Emilio @Kathy Nativi Good news! Today I wrote the script. Tomorrow I'll do further testing and debugging, but it already works quite well, as can be seen from here. Cheers! Sophivorus (talk) 15:08, 28 January 2021 (UTC)
Woo-hoo! Excited to see we have no broken links in the next Ahrefs report! Kathy Nativi (talk) 15:30, 28 January 2021 (UTC)
@Emilio @Kathy Nativi Script is running! In order to not abuse the Archive.org API, I set it to run once every few seconds, so it may take a few days to complete. Check out the progress from Special:Contributions/Dead links script ;-) Sophivorus (talk) 21:14, 30 January 2021 (UTC)
@Emilio @Kathy Nativi Hi again, I got great news! I was able to improve the script so that now it doesn't rely on Ahref reports, but instead goes systematically through every external link on the wiki and replaces them for archived links if it gets a 404 response. This new script has fixed thousands of broken links already and is still going! Sophivorus (talk) 15:11, 1 February 2021 (UTC)
This is brilliant! Thank you. --Lonny (talk) 18:34, 1 February 2021 (UTC)
@Sophivorus, Kathy Nativi, Lonny After implementing a solution to keep track as it advanced through the database, it appears the script is done! 135331 records. There are a few things to solve (Google Drive and Dropbox links, links with no Internet Archive mirror, etc.), but the script has done its nice share of work. :) —Emilio (talk) 22:20, 29 March 2021 (UTC)

## Hotjar feedback button still generating bad feedback

Here is an example feedback. —Emilio (talk) 21:37, 27 January 2021 (UTC)

@Emilio Hi! After about 30 mins of trying, I wasn't able to move the feedback button behind images, or the images on top of the feedback button. For some reason, z-index is not working. The CSS of both Hotjar and the Minerva skin is complicated, obscure and bizarre. I was able at least to move the feedback button a bit more out of the way. I don't think it's worth spending more time on this. Sophivorus (talk) 20:40, 2 February 2021 (UTC)
@Lonny, Sophivorus Perfect. Thanks a lot. Emilio (talk) 21:24, 2 February 2021 (UTC)
Thank you! --Lonny (talk) 00:15, 9 February 2021 (UTC)

## New security question

@Lonny, Sophivorus, Kathy Hi, I believe that the security question has been too difficult for many people. Could we change it please? I'm considering something like "write down the result of 2+3 in letters" or "What is the sum of 2 and 3 (in letters)? Is it easy to understand, or do we need another question? --Emilio (talk) 21:34, 2 February 2021 (UTC)

Done! Sophivorus (talk) 15:37, 3 February 2021 (UTC)

## Video error

There seems to be a youtube error at User:Lonny#Video. Thanks, --Lonny (talk) 05:10, 13 February 2021 (UTC)

Fixed. You can see the reference for the implemented video template (with metadata) at Template:Video. I hope this helps! Emilio (talk) 07:42, 13 February 2021 (UTC)
Thanks! --Lonny (talk) 08:32, 13 February 2021 (UTC)

## Fix bug when converting pages to PDF

The bug seems to be Firefox-specific. Sophivorus (talk) 22:20, 10 December 2020 (UTC)

@Emilio After some investigation, it looks like this issue is related to the Vector skin, rather than Firefox. If you load the Poncho skin, it doesn't happen. Can you confirm? Sophivorus (talk) 13:10, 16 February 2021 (UTC)

## Add timestamp or date (yyyymmdd) to filename when uploading to avoid duplicate names

mw:Extension:PageForms promises various options to control the name of the uploaded files but nothing seems to work! The only thing I could get to work is setting today's date and time as default filename. However prefixing the date doesn't seem possible, except perhaps with some custom JavaScript. However, before doing that, please comment on the current situation (see Special:FormEdit/Project/Foobar) and let me know where should the JavaScript run (if when creating pages with forms, in the visual editor, etc).

I think the visual editor is where it's most likely to be useful. I'm looking at the current idea and it works well. Better if there're no colons in the filename, because that may bring trouble down the road. I'd use UNIX time or random characters. It'd also be good to add the file format, though that may be difficult. I uploaded an image through the form the organization form and threw an error due to the colons in the filename. My recommendation after using it would be to simply use the yyyy-mm-dd format. --Emilio (talk)
@Emilio I changed the default filename to the yyyy-mm-dd format. Sophivorus (talk) 12:29, 30 December 2020 (UTC)

## Error related to https, images and Firefox

See for example CCAT solar bug out box. --Lonny (talk)

@Lonny, Sophivorus We found that it only seems to occur on Firefox (not on Chrome). Might be a browser thing, or a server thing.
@Emilio, Lonny After some investigation, I think the issue is actually related to the Vector skin. The skin seems to be loading the little PDF icons via http, which triggers a Firefox non-encrypted resource warning. If you load the Poncho skin (from Preferences > Appearance), the issue disappears. Can you confirm? Sophivorus (talk) 13:03, 16 February 2021 (UTC)
@Sophivorus Confirmed: Firefox with Vector = the non-encrypted warning. Firefox with Poncho = no warning. Not logged in to Appropedia on Firefox = the non-encrypted warning (and it seems that vector must be the not-logged-in skin. --Lonny (talk) 20:33, 16 February 2021 (UTC)

## Look into privacy-control extensions

This may not be necessary if we decide to implement a private wiki at https://private.appropedia.org Sophivorus (talk) 13:21, 11 December 2020 (UTC)

@Emilio Is this still a request? Sophivorus (talk) 12:52, 18 January 2021 (UTC)
I can ask User:GSTC about this but I think it will still be relevant. — Emilio (talk) 16:02, 18 January 2021 (UTC)
The key thing is that the participants in the GSTC can spend time developing their content and sharing it internally with their team without it being published to the wider world. We will then want to "turn on" visibility for everyone to see the content, but up until then, it should be protected from view. GSTC (talk) 03:07, 10 February 2021 (UTC)
@GSTC @Emilio Hi! After evaluating the available extensions to restrict viewing, I settled for the Extension:Lockdown. I installed the extension, created a new namespace called GSTC, a new user group also called GSTC, and configured it all so that pages in the GSTC namespace can only be created and viewed by users in the GSTC user group (and admins). So for example, I created the page GSTC:Test, which should only be viewable by users in the GSTC user group. Catherine, I've added your user to the group, so you should be able to view the page (please confirm) but if you visit the page while logged out, you won't. Furthermore, I've given your user a special right so that you can add other users to the GSTC group. To do so, just visit Special:UserRights. When you want to publish a page, simply move the page out of the GSTC namespace (by clicking the Move button next to Edit). Hope this helps, let me know of any questions or issuesǃ Sophivorus (talk) 13:08, 11 February 2021 (UTC)

## Image upload form is broken

Tried uploading an image at [1] and gave an error: [X@grks5HnOUAcSXF7EftfwAAAAc] 2020-12-27 06:37:06: Fatal exception of type "Error"

@Sophivorus I am testing this again. Uploading from forms such as the organization form is throwing errors despite eliminating colons in the filename. --Emilio (talk) 22:55, 29 December 2020 (UTC)
@Emilio I was unable to reproduce the error you encountered. I uploaded all sorts of files without any trouble, from the organization form, from the skill form and from the regular upload form. Anything weird about the specific file you tried to upload? Are you able to reproduce the issue at will? Sophivorus (talk) 12:26, 30 December 2020 (UTC)
@Sophivorus Here it is (video plays in Chrome only due to it being mkv):
EmbedVideo received the bad id "2020-12-30_09-48-03.mkv" for the service "youtube".
Emilio (talk) 15:51, 30 December 2020 (UTC)
I was now able to reproduce it, enabled debug mode and captured these details:
I'll try to figure it out tomorrow! Sophivorus (talk) 16:39, 30 December 2020 (UTC)
@Emilio Hi! I just enabled the "simple upload" feature of Extension:PageForms, which basically simplifies the upload mechanism enormously (test it out!) and apparently also fixes this bug. However, it has some downsides. First, it doesn't allow the user to select a new file name. The file is uploaded with the name it already has. Furthermore, if there's another file with that name, it will replace it with no warning. :-( To mitigate all this, I wrote a fairly clear warning next to the upload button (check it out). Given that the previous upload form we had was complicated, not-configurable and buggy, this may be a reasonable solution. I can also code a way to add a timestamp to file names, so we don't have overwrite issues, though that would imply modifying the PageForms source code. Coding a patch that can be merged upstream would be trickier and demand more time, but also doable. What do you think? Sophivorus (talk) 12:40, 31 December 2020 (UTC)
Hm. Tricky. I am curious as to whether this file renaming problem is consistent across all of MediaWiki and how other people sort it out. But definitely, the best option is to code a patch and hope for the best. Could we share with the community and see what do they think? Emilio (talk) 13:36, 31 December 2020 (UTC)
@Emilio Hi! Today I installed mw:Extension:UploadWizard and configured it so that it creates similar file pages to the visual editor. Check it out! The upload wizard has a friendlier user interface and allows to upload several files at once, among other features. This brings us another step closer to a simple and coherent file uploading experience. Next step would be to create file form to edit all pages in the file namespace. Tomorrow I'll also rise the min file size to 100 MB. Cheers! Sophivorus (talk) 15:56, 2 January 2021 (UTC)
Beautiful!! Emilio (talk) 16:20, 2 January 2021 (UTC)
@Emilio I'm glad you're liking it! Today, rather than creating the file form, I was able to greatly simplify and improve the UploadWizard flow, please test it out! We may still simplify it further by removing some licencing options that we don't really want to support (let me know). But other than that, I think it's ready!
See File:Time-lapse of tomato seedlings.mp4 for an example of a file page created using the UploadWizard. By commenting out two lines of JavaScript code from the UploadWizard source code, we can get rid of those abominable =={{Int:filedesc}}== and =={{Int:license-header}}== headers and make the file pages consist of a simple {{Information}} template followed by a simple license template like {{Cc-by-sa-4.0}}. If we do comment out those lines, we should inaugurate some page like Appropedia:Source code changes to document these and any other source code changes. Modifying the source code is generally undesirable, but it may actually become necessary at some point. For example we already have another case where modifying the source code a little would be handy, namely to add a timestamp to the files uploaded via the PageForms "simple upload" to prevent undesirable file overwrites. I think that if you, me, Lonny and every other user with access to the server are made aware of the documented source code changes, and we keep them to a minimum, we could benefit a lot more than the minor inconvenience of having to re-do them every so many years after updating a modified extension. Also, if we do forget to re-do the changes, it wouldn't actually matter much, at least not for the two source code changes I'm suggesting. What do you think?
I also just increased the max upload size to 100 MB, though I didn't test it out. Cheers! Sophivorus (talk) 14:02, 3 January 2021 (UTC)
Sorry for not noticing earlier, but I'm curious about whether we can leave only CC-BY-SA 4.0 and CC-BY 4.0 as options. I see that 3.0 versions are available. Emilio (talk) 03:33, 14 January 2021 (UTC)
@Emilio Hi! I just limited the licencing options when uploading a file as your own work to CC-BY-SA-4.0 or CC-BY-4.0, cheers! Sophivorus (talk) 15:35, 3 February 2021 (UTC)
@Sophivorus, J.M.Pearce One comment from User:J.M.Pearce was the possibility to also add the GNU FDL option. Here is his comment: I really like the new file uploader -- only thing is we lost the GNU FDL -although not the functionality. Could we have that one too? — Emilio (talk) 17:17, 3 February 2021 (UTC)
@Sophivorus, J.M.Pearce I would add CC0 to this list. So it would be:
What do you think? Emilio (talk) 18:18, 9 February 2021 (UTC)
I just added CC0 and GFDL, so the current list is:
• CC-BY-SA-4.0
• CC BY 4.0
• CC0
• GFDL
Should I remove CC BY 4.0? Sophivorus (talk) 11:32, 10 February 2021 (UTC)
Hmm...yeah, maybe it's a good idea. I wonder what the rest of the community think, but we can see that as more organizations start generating content with us and adapt to their needs. Emilio (talk) 20:08, 1 March 2021 (UTC)
Did you decide to do any source code changes? I agree that keeping track of them will be super useful. Emilio (talk) 19:35, 3 March 2021 (UTC)

## Exemplary articles

@Emilio Build a list of exemplary articles of each category and link them from the most relevant places in the help documentation. Sophivorus (talk) 15:31, 12 January 2021 (UTC)

Started at Appropedia:Toolbox#Exemplary pages. Sophivorus (talk) 13:24, 16 February 2021 (UTC)

## Twitter Cards

Hi @Sophivorus! Can you help me implement Twitter Cards to the website? It'd be nice to look good in the Twitter feed as those tags instruct Twitter what information (title, description, image, etc.) to display whenever a URL to a page is shared. I think you'll need my help to access the Twitter developer platform.

@Kathy Nativi, Emilio Done! I installed the Extension:TwitterCards which is designed to add precisely that functionality. I tested the cards at the Twitter Card Validator and they seem to be working fine except that the robots.txt file was blocking access to images. So I added another exception to the rules, but it looks like our cache (either Varnish or CloudFlare, not sure) is still serving the old version, so it may take a few hours to catch up. Cheers! Sophivorus (talk) 12:14, 16 February 2021 (UTC)
@Sophivorus Hi! Apparently there are some pages with one or more of the basic Twitter card tags missing. Basic Twitter cards include twitter:card, twitter:site, twitter:title, twitter:description, and twitter:image. Can you take a look at it? Thanks! Kathy Nativi (talk) 15:32, 17 February 2021 (UTC)
@Kathy Nativi Hi! As far as I can tell, the reason why many pages don't have their basic Twitter card tags, is because many pages don't have an intro or main image. So for example, if you go to the Twitter Card Validator, you'll notice that How to build a bamboo shade structure generates a decent card, while How to start a solar company does not. But that's because the first page has an intro and a main image, while the second doesn't. This cannot be fixed on the software side. The solution is to normalize and improve pages so that they all have an intro and a main image. Other reasons for wanting to do this are to have the "popups" display correctly (hover over the links above to see what I mean) and to help Google and other search engines display a good snippet on their search results. Kind regards, Sophivorus (talk) 14:55, 18 February 2021 (UTC)

## Facebook pixel

@Sophivorus @Emilio Hello again! I just sent you an email with a pixel base code from FB to install it on the website :) Kathy Nativi (talk) 18:57, 16 February 2021 (UTC)

@Kathy Nativi we are thinking that it might be best not to include Facebook code on our code. I know it can help us get better-driven traffic, but we want to maintain a clean experience as much as possible for our users. So far we have Google Analytics and Hotjar, but we'll make sure to be careful in how we gather usage data. Do you think we can find any alternatives to this problem? Emilio (talk) 20:35, 18 February 2021 (UTC)
@Emilio Got it! I'll just set goals and funnels in Google Analytics to measure conversions :). Just be aware that if installed, the FB pixel information will not match the GA data because Facebook is a people-based tracking and GA is cookie-based tracking. Kathy Nativi (talk) 21:12, 18 February 2021 (UTC)

## Add semantic capabilities to an Mbox

For the text, we can take a course page such as 3D-printed chemical etching handle. The relevant information is the following: organization (link to organization page), course (link to course page), year, open edit (yes/no).

@Emilio Hi! I just did a first implementation of this request, check it out at the wikitext of the Template:L3999 Fall2017 template and the resulting properties of 3D-printed chemical etching handle and let me know your thoughts! I haven't implemented the open edit yes/no property yet, but before I do so I'd like to share a thought about semantic properties. In order to maximize the chances of them getting used and reused, I think we should carefully balance precision vs practicality. For example, we currently have Property:Date of publication and if we followed the infobox properties verbatim, we should have Property:Date of update and Property:Date of creation. But isn't so much precision an obstacle both for querying projects and for adoption by new users and use cases? Wouldn't it be better to have just Property:Date? Sophivorus (talk) 13:51, 5 February 2021 (UTC)
Hi! I was looking at Understanding solar concentrators as a great example of ported content that does not describe a specific project or device. I will remove the notice template and use an MBox to try and describe what is on this page.
A thought: date of publication exists because there could be old projects that are recently ported or published by someone. I think we can start thinking about these issues, for example, in terms of when a project/device was created and when it was documented. Open Know-How standard considered the creation of the manifest file, which seemed to me a bit unpractical (and this is one of the cases). But the documentation being made at a later date in time is definitely important.
Some property ideas I'm thinking of:
• Document type (topic page/lit review/technical brief/research note)
• Source--when a verbatim copy (URL/citation of PDF file/etc)
• Derivative of (citation, other document, or article on Appropedia)
• Translation of
• Language
Check this example of derivative works: Aerial Ropeways in Nepal (original) and Aerial Ropeways in Nepal. -- Emilio (talk) 20:43, 18 February 2021 (UTC)
@Emilio Hi!
1. I think maybe Understanding solar concentrators could maybe be a use case for the new generic Template:Infobox page, though admittedly, the infobox would need several new parameters to capture the meta data in the intro of the page.
2. Regarding the Property:Date of publication, ok then, lets keep it.
3. I do agree that having meta data about the manifest itself is impractical. It adds complexity to the infoboxes and forms while yielding negligible benefits. If you agree then, I'd like to remove them.
4. Regarding your property ideas:
• Document type: already implemented, see Property:Type. You can see all currently existing types from the dropdown at Search. I just created Template:Literature review and modified Template:MOST lit so that they use this property. As to "topic page", "technical brief" and "research note", it'd be a matter of creating an mbox/infobox for each and add them to the relevant pages.
• Source: do you have an example of a page in need of this?
• Derivative of: already implemented, see the Property:Variant of and the "instance-of" parameter in Template:Infobox device and Template:Infobox medical device. Should I rename it?
• Translation of: already implemented, see the Property:Translation of and the "derivative-of" parameter in many infoboxes.
• Language: already implemented, see Property:Language code, the "language" parameter in many infoboxes and the corresponding field in many forms. Using language codes rather than language names is important because it allows the software to understand it.
5. As to Aerial Ropeways in Nepal, check out this strategy which allows us to get rid of static pages like Aerial Ropeways in Nepal (original), like I just did here.
Maybe we should do a call to talk about some of these points? Kind regards, Sophivorus (talk) 14:16, 3 March 2021 (UTC)
I agree. Can we make a working page for these properties? I'm writing a full description with some examples to get the discussion going since I'd love to hear your thoughts on them. Emilio (talk) 21:11, 3 March 2021 (UTC)
I've been playing with Template:Literature review and copied the format from Template:Page to make one of my own. Emilio (talk) 06:23, 20 March 2021 (UTC)

## Convert image error

Hi @Sophivorus! A couple of weeks ago, Emilio and I noticed that the images inside the infoboxes are causing the following error:

"Error creating thumbnail: / bin / bash: warning: setlocale: LC_ALL: cannot change locale (C.UTF-8) convert: cannot extend cache / home / appropedia / public_html / w / images /a/aa/IMG_1096.JPG ': File too large @ error / cache.c / OpenPixelCache / 4091. convert: no images defined /home/appropedia/public_html/w/tmp/transform_93c40989d5e1.jpg' @ error / convert .c / ConvertImageCommand / 3235. Error code: 1"


We've been editing the photos to avoid formatting problems, but I'm afraid there are a couple more that need to be taken care of.

@Kathy Nativi Thanks for the report. The error report says "File too large", but the relevant file, namely File:IMG 1096.JPG, is a regular size file, and the only page using it, namely Zane Middle School sundial, doesn't currently have any errors. So I'm not sure what the issue could have been, or if it's still occurring. Unless I'm able to reproduce the error, I won't be able to fix it. If you notice a pattern that may enable me to reproduce it, please let me know. Kind regards, Sophivorus (talk) 22:21, 9 March 2021 (UTC)
@Sophivorus Yes! It was an example; that one doesn't have any errors right now because I uploaded the edited photo. Maybe if you take a look at the history of the URL that contains that file, you'll be able to see what I'm talking about. And I'll let you know if I notice the "File too large" error on another page. Thanks! Kathy Nativi (talk) 23:08, 9 March 2021 (UTC)
@Sophivorus Just found another one! Athena Engraver mod Kathy Nativi (talk) 23:11, 9 March 2021 (UTC)
@Kathy Nativi Good catch! I think I fixed it, but let me know if you encounter it again. Cheers! Sophivorus (talk) 23:30, 9 March 2021 (UTC)
I've been solving this by downloading the image, transcoding it (saving it with minor changes) and reuploading it as a new version. I'm curious about whether something on the file header is creating these problems. Emilio (talk) 03:29, 10 March 2021 (UTC)
@Emilio I'm not sure what was the cause, but some weeks ago I did a change to the infoboxes so that they output the main image in full-size, and then the image was shrinked via CSS. I did this to fix an issue with certain aspect ratios. However, it looks like my fix triggered this new bug, and also come to think about it, it increased the page sizes considerably, so I reverted my change. Sophivorus (talk) 11:11, 10 March 2021 (UTC)
Hm. Just a thought: perhaps CSS object-fit could help sort these display problems? Emilio (talk) 18:37, 10 March 2021 (UTC)

## Quizzes

@Emilio Hi! I installed mw:Extension:Quiz and created a simple demo at Appropedia:Quiz. There're many more options to quizzes, you can read all about them at Wikiversity:Help:Quiz. Sophivorus (talk) 11:42, 10 March 2021 (UTC)

Wow! So cool! Emilio (talk) 18:34, 10 March 2021 (UTC)

## PdfHandler

This extension might be useful, especially to display many PDF files such as documents and presentations. PDF might also serve in the future as the second type of media available at skill pages.

@Emilio This extension requires some command line tools (pdfinfo, pdftotext and maybe others) that are not currently available on our server and don't seem trivial to install via WHM. Sophivorus (talk) 14:24, 3 January 2021 (UTC)
Issue solved by Wikiteq. Emilio (talk) 05:22, 9 May 2021 (UTC)

## Create template for Bill of Materials

Sophivorus (talk) 19:36, 18 January 2021 (UTC)

Can we call it Template:BOM please? Some Bill of Materials might not contain costs. -- Emilio (talk) 18:04, 19 January 2021 (UTC)
@Emilio Sure! Today I started Template:Bill of materials (I made Template:BOM a redirect, as I think abbreviations should be allowed but not encouraged), check it out! It still has a long way to go, but I think it had a good start. To design it, I searched for "bill of materials" and opened several pages to see what elements were most common. In the next iteration I want to make the "buy" link more flexible, since it looks like users sometimes write plain text, other times link to Appropedia pages, and other times to external sites, see for example Open-source metal 3-D printer#Bill of Materials (one of our top pages). Feedback welcome! Sophivorus (talk) 14:59, 22 January 2021 (UTC)
As I'm using this template, I think that there is one improvement to be done to the buy field by renaming it as source, to accept either a URL or text such as "donation", "previously owned" or "repurposed" (perhaps as recommended fields in the documentation). An optional image field would also be useful. What do you think? Emilio (talk) 03:34, 10 March 2021 (UTC)
@Emilio Hi! I just extended the template to support images, check out the documentation for the syntax. As to the buy/source/whatever field, I renamed it to just "text" so that the user may enter any kind of extra information they wish. I think that until we have a real use case in sight for this extra information that will justify specific fields, having a generic text field is the simplest, sanest and most flexible solution. Sophivorus (talk) 12:37, 10 March 2021 (UTC)
@Emilio Hi! I just improved the Template:Bill of Materials so that it doesn't throw errors when no costs or amounts are given. Check out for example your simple tool list example. You'll notice that it also makes some assumptions, namely that if the amount is not specified, it assumes 1, and if the cost is not specified, it assumes 0. I think these are reasonable assumptions, but maybe you'll think it'd be better to hide all unused columns. However, this leads to quite complicated, ugly and unmaintainable wikitext, and more importantly, it defeats the purpose of it being a table. If all that needs to be shown is a list of items, then surely a table is not the proper HTML structure. Another template that outputs an unordered list (maybe similar to Template:Steps) would probably be more adequate. What do you think? Kind regards, Sophivorus (talk) 15:57, 11 March 2021 (UTC)
@Cassandreces, Sophivorus I agree with you. I'll add Juli to the conversation, but I think that one way to do this is to have a tool with similar syntax that can turn from one to the other. One example is a person who starts with a list and then changes the name of the template to include costs once the documentation is finished?) Emilio (talk) 16:27, 11 March 2021 (UTC)
@Emilio Today I created Template:Tools. I'm a bit short on time so I only did the structure. Next I'll focus on styling. Unless you say otherwise, I think I'll mostly copy the style at Template:Steps. Cheers! Sophivorus (talk) 13:03, 12 March 2021 (UTC)
Seems like a great idea, I agree that a similar stylesheet will work. Emilio (talk) 16:23, 12 March 2021 (UTC)
@Sophivorus I just found out that you cannot do both text and image in this template. Is this a desired behavior? See Preload:ESEN Innovación Proyecto 2021#Presupuesto for an example. Emilio (talk) 02:37, 20 March 2021 (UTC)
@Emilio Hi! You were missing a "3", see here. XD Sophivorus (talk) 13:11, 27 March 2021 (UTC)
Whoops! Thanks a lot!— Emilio (talk) 20:20, 28 March 2021 (UTC)
@Emilio While creating the stylesheet for Template:Tool, I realized the entire template was an exact copy of Template:Step, only with another name. So instead of duplicating templates, I made Template:Tool a redirect to Template:Step. I also generalized Template:Step so that now it doesn't require a number. If no number is provided, no number is displayed. This effectively makes Template:Step a generic template for creating list items of any type (steps, tools, ingredients, whatever). So I'd like to rename Template:Step as simply Template:Item, but it seems like you already created Template:Item in connection with Module:Item. They don't seem to be used much though. Do you have any plans for them? PS: I also created Template:Ingredient as a redirect to Template:Step, see Preload:Recipe, cheers! Sophivorus (talk) 13:32, 27 March 2021 (UTC)
@Sophivorus I think I created this from Wikipedia:Template:Item but I don't think I ever used it. So yeah, feel free to change it to anything you need, and yes, great idea to have a generic template! Maybe we could create some style elements for it in the future so it holds an icon or some sort of identifier, as well as a custom template for specific pages? —Emilio (talk) 20:17, 28 March 2021 (UTC)
@Emilio Done! Not sure I understand your idea. Do you mean some kind of visual identifier to distinguish steps from tools from ingredients? Sophivorus (talk) 13:08, 29 March 2021 (UTC)
@Sophivorus Yes, something like that. We had a talk in person regarding using specific CSS classes for Fashion Revolution infocards. Maybe this is not a good idea (we'll have to discuss it) but it might work to have a specific set of classes for organizations that could apply to the toolbox in general: color, borders, etc. Perhaps that'll be something to talk about once we have a somewhat finished version of the toolbox for us to play with. Emilio (talk) 16:58, 29 March 2021 (UTC)

## Private namespaces per GSTC team

@Emilio, GSTC To prevent each team from seeing the work of others, we'll create 12 private namespaces, named GSTC1, GSTC2, etc. and 12 user groups, also named GSTC1, GSTC2, etc. Each group will only have access to their own namespace, so all that you need to do (Catherine) is add each user to their user group. Makes sense? Sophivorus (talk) 20:13, 16 March 2021 (UTC)

@GSTC We are choosing something like this (and less verbose) because namespaces are usually short and made up of one word. Given that these will be temporary work spaces, this might be a decent solution for now. What do you think? Emilio (talk) 20:16, 16 March 2021 (UTC)

## Create template with target for user pages

I was curious about how to use Template:Create to help users load a specific user page template. Perhaps a button that directs users to Special:MyPage with the preload? Is that possible? Also, I'm thinking that the ability to direct to subpages would be super useful as well. I wonder if that one is possible too! Emilio (talk) 20:46, 19 March 2021 (UTC)

@Emilio Hi! I just added a "prefix" parameter to Template:Create, so now you can define input boxes that create subpages. See the template documentation for an example. As to your other request, I just modified MediaWiki:Noarticletext which defines the text to be shown whenever a page doesn't exist. If the page is a user page, it'll now show a nice blue button to create it and it'll preload the text at Preload:User. See for example a non-existent user page (like https://www.appropedia.org/User:Danlevi) and compare with a non-existent page in the mainspace (like https://www.appropedia.org/Some_page) and a non-existent page in some other namespace (like https://www.appropedia.org/Template:Foo). Notice however that Form:User is still set as default when following red links to user pages (like User:Danlevi). Once we have a decent preload for user pages, I can disable the form as default. However, there's also the issue that red links in general (see Some page) will jump straight to the edit box. I'm still thinking on how to best solve this, so any feedback would be welcome. Also, if you simply want a template that may be inserted anywhere and that serves to create a user page, you can use the following:
{{Button|url={{fullurl:Special:MyPage|veaction=edit&preload=Preload:User}}|text=Create your user page}}
which will output:
Kind regards, Sophivorus (talk) 15:11, 21 March 2021 (UTC)
@Sophivorus Hi! I noticed that this template is active by default on all user pages, but I noticed that it also appears on subpages (for example at User:Emilio/non user page which may confuse users. Is there a way to deactivate this for subpages? Emilio (talk) 22:01, 26 March 2021 (UTC)
Fixed! Sophivorus (talk) 13:37, 27 March 2021 (UTC)

## GSTC Preloads

@Cassandreces, Sophivorus I created Preload:GSTC medical skill. I am thinking of a few technical items that we should look into: (1) the timestamp anchor in the description doesn't work for me at all times (on Firefox). (2) The equipment and materials template needs a bit more love. I also created Preload:Quiz with not much content for now, but it's a good start. Let me know your thoughts! —Emilio (talk) 06:33, 23 March 2021 (UTC)

@Emilio Hi! (1) I'm not 100% sure but I think I just fixed what was causing your issue. Let me know if it happens again! (2) Do you mean Template:Tool? Done, see my other message! Sophivorus (talk) 14:28, 27 March 2021 (UTC)

## Preloads don't seem to work on all mobiles

See a reproduction using Firefox at File:Video 2021-03-25 15-30-53.mp4. Compare with the form on a laptop at Vigyan Ashram. —Emilio (talk) 21:32, 25 March 2021 (UTC)

@Emilio This is so unfortunate :-( It seems like the issue was reported and fixed years ago. However it wasn't fully fixed and we're just now finding out. I reopened the issue with a clear way to reproduce it, so maybe we'll get a fix soon. Lets wait a few days to see if there's any activity. Sophivorus (talk) 14:04, 27 March 2021 (UTC)
Someone commented that if you click on the X on the mobile editor, you go back to another editor that does include the preload. It's definitely not cool but at least worth knowing. Sophivorus (talk) 13:12, 29 March 2021 (UTC)

## Infobox project errors

@Sophivorus No rush on this, I imagine it is being debugged but just in case, I found two of them: (1) items on the 'keywords' and 'authors' mix together into authors. For example, I ended up with this after editing with the form: |authors=playground, Fabio López, Rafael Machado. (2) the 'ported from' field doesn't form external links correctly.—Emilio (talk) 23:42, 30 March 2021 (UTC)

Fixed! Sophivorus (talk) 19:13, 19 April 2021 (UTC)

## "Back to course home" link or button on Template:Infobox medical skill

@Sophivorus, Mhanifw One of the feedback from the NREMT course was that students find it hard to go back to where they started when reviewing the course content. One way to solve this is to have a "go back home" link, perhaps after "About this medical skill". —Emilio (talk) 18:59, 19 April 2021 (UTC)

@Emilio @Mhanifw Done! I called the field "part-of" to try to keep it generic, but if a more specific name be required or desired, just let me know. See Cardiopulmonary Resuscitation (CPR) and Patient Handoff as an example of a skill page and a knowledge page that are part of the NREMT Skillset course and link to it. Also see the "Edit with form" button for the editable interface. Cheers! Sophivorus (talk) 19:43, 19 April 2021 (UTC)
@Sophivorus Thanks a lot! @GSTC, Mhanifw Hi, please let us know your thoughts! —Emilio (talk) 23:16, 20 April 2021 (UTC)
@Emilio @Sophivorus Despite it might be a little redundant with the banner, I think this direction is helpful since infobox is more intuitive than looking at the banner. I wonder if it could be even more helpful if we link it to the relevant syllabus instead? e.g. for Cardiopulmonary Resuscitation (CPR), instead "Part of NREMT Skillset", we put "Part of NREMT Skillset - Fundamentals" Mhanifw (talk) 14:54, 22 April 2021 (UTC)

## Multiple video annotations

Please see FiltAirs DIY air filter#Assembly and FiltAirs DIY air filter#Usage and how multiple videos are being used as part of the documentation. Is there any possible way to make both annotations work independently? If not, what is the best way to tell our users about this limitation?—Emilio (talk) 17:46, 26 April 2021 (UTC)

@Emilio Done! I just finished improving the relevant video script at MediaWiki:Common.js. Now if you visit the videos you linked and click on the anchors, they should work fine. The only limitation to the new system is that you cannot link from other pages to videos other than the first. For example FiltAirs DIY air filter#0:20 will jump to 0:20 of the first video and there's no way to jump to 0:20 of the second video. However I think this is a very minor limitation that few if any users will miss, and adding it would require complications to the UX, so I wouldn't implement it unless it becomes necessary. Cheers! Sophivorus (talk) 15:53, 27 April 2021 (UTC)
@Emilio I just restored the new version of the video script, after fixing the GSTC bug. Now, if a time anchor is not in the "description" field of the Template:Video (like in GSTC pages) then the script will infer that the anchor refers to the first video in the page. Sophivorus (talk) 20:24, 29 April 2021 (UTC)

## Search errors

I feel like our search in broken in some unique ways. Please let me know if you have questions on the errors shown below or feedback on what is going on or how to fix it.

--Lonny (talk) 04:18, 28 April 2021 (UTC)

Hi, just to clarify: other than Zane 2021 (I suppose it's not a project per se), should the other searches lead to Snowboard benches and Zane middle school math path? Emilio (talk) 04:28, 28 April 2021 (UTC)
I would expect searching for Zane 2021 or Zane middle school math path to find this page Zane Middle School math path 2021. Also, when searching for numbers, weird numbers are suggested instead.
I would expect snowboard benches to find Zane Middle School snowboard benches.
Instead these searches are finding other pages. Maybe it is due to these pages being relatively new. Have we changed our engine to be based on google or a cache instead of our own db? --Lonny (talk) 04:40, 28 April 2021 (UTC)
@Emilio It looks like the issue only affects new pages (search for example "multijunction photovoltaic"). This suggests that the problem is that the search index is not updating. I tried rebuilding the search index but no luck. I guess that script rebuilds the search index used by the default MediaWiki search engine, but we're currently using ElasticSearch + CirrusSearch. The CirrusSearch extension includes a maintenance folder with several maintenance scripts, one of which may help, but there's no obvious one to me, and in any case one thing is to manually update the index, and another is to ensure it updates itself in the future. Since Ike set up the search engine and he's currently doing some work for Appropedia, maybe it's most efficient to ask him to take a look? Sophivorus (talk) 19:59, 29 April 2021 (UTC)
@Emilio, Please do that. New editors lose their page and can't find it when searching. They often don't know they could look in their contributions and think they lost their page when it doesn't show up in search. --Lonny (talk) 21:09, 30 April 2021 (UTC)

## No more than 9 items in a BOM

I can't get more than 9 items to load in the BOM table. See the source below for a tenth thing that doesn't show up.

Item Amount Cost per unit Total
First thing — Get at the thing store 3 USD 5.75 USD 17.25
Second thing — 3' x 2', yellow 1 USD 150.00 USD 150.00
Third thing — 3' x 2', yellow 1 USD 150.00 USD 150.00
Fourth thing — 3' x 2', yellow 1 USD 150.00 USD 150.00
Fifth thing — 3' x 2', yellow 1 USD 150.00 USD 150.00
Sixth thing — 3' x 2', yellow 1 USD 150.00 USD 150.00
Seventh thing — 3' x 2', yellow 1 USD 150.00 USD 150.00
eighth thing — 3' x 2', yellow 1 USD 150.00 USD 150.00
ninth thing — 3' x 2', yellow 1 USD 150.00 USD 150.00
tenth thing - This one isn't showing up — 3' x 2', yellow 1 USD 150.00 USD 150.00
Grand total USD 1367.25EUR 1,175.84 <br />GBP 998.09 <br />CAD 1,695.39 <br />MXN 28,507.16 <br />INR 102,338.66 <br />

--Lonny (talk) 04:24, 28 April 2021 (UTC)

@Lonny Hi! I just extended support for up to 30 items. Let me know if you ever need more! Sophivorus (talk) 19:29, 29 April 2021 (UTC)
Thanks! Lonny (talk) 21:09, 30 April 2021 (UTC)

## Video with timestamp bot fix problem

It looks like the bot that fixes video links might have a bug. See https://www.appropedia.org/w/index.php?title=How_to_make_Block_Fill&type=revision&diff=496894&oldid=440466 for an embedded video that I had to 'fix' so that the video worked. Currently it no longer links to a specific timestamp in the video, but the video does show up. --Lonny (talk)

@Lonny I just did a search for similar errors, found two and fixed them. There're probably no more. :-) Thanks for noticing! Sophivorus (talk) 17:30, 3 May 2021 (UTC)
Great. Thanks! Lonny (talk) 18:30, 3 May 2021 (UTC)

## Wrong link from visual editor to MediaWiki VE help

A person noted that there is a forwarding error on the visual editor link. here is a possible solution but I didn't want to edit it without asking first. —Emilio (talk) 22:30, 3 May 2021 (UTC)

Fixed! Sophivorus (talk) 14:06, 17 May 2021 (UTC)
Cookies help us deliver our services. By using our services, you agree to our use of cookies.