Page data
Aliases A:SD
Published by Chris Watkins
Published 2009
License CC BY-SA 4.0

This page is Appropedia's site development tasks and bug reports.

New task

Look into implementing site-wide citations and DOI for pages[edit source]

See Appropedia:Village pump#Following up on references display. --Emilio (talk)

Metadata and default license for image uploaders (visual/source editor)[edit source]

Is this normal? Check this image for example. Recommended: set up a disclaimer, for examples: "Images uploaded are licensed as CC-BY-SA 4.0. For other licenses, use Special:Upload." --Emilio (talk)

@Emilio: I just modified MediaWiki:Copyright so that the footer of all pages (including images) now reads "All content is available under CC-BY-SA unless otherwise specified". What do you think? Is it worth allowing images under a different license? Sophivorus (talk) 13:00, 17 December 2020 (UTC)
@Scann, Sophivorus: I think that works for now, and probably Scann may have some ideas. Emilio (talk) 15:43, 17 December 2020 (UTC)
I think we need to clarify the license version (so I'd make it a CC BY 4.0, with a link to the unported/international version), but that should also be accompanied with the overhaul of the Copyrights page (which frankly doesn't make sense). Additionally I'd be very clear that other TOS might apply, we need to make that clear for folks. A safe bet would be to copy a similar footer to what Wikipedia currently has, even if we haven't written those pages yet. Also I wonder why we're putting CC BY SA as the recommended license. It might be tricky to recommend licenses. We probably want to generate a blurb that says: "don't know what the CC licenses are? Check here" or something in that line. Scann (talk) 13:04, 18 December 2020 (UTC)

Make our images appear in Google image search for Creative Commons images[edit source]

It may be as simple as some udata or data tag attached to our cc template in images. --Emilio (talk)

Update: I believe we need to enable the {{Information}} template for the File namespace. —Emilio (talk) 03:12, 22 December 2020 (UTC)
@Emilio Following and after quite a while of trying, today I was able to hardcode the licensing data for one specific file (File:Lubetkin Highpoint II December 2005.jpg), test it out at Google's Rich Results Test. Next I'll generalize and integrate the markup to the Template:Information so that all new files benefit from it. Also, while researching this issue, I found a compilation of advanced google search features that we could progressively take advantage of. Check it out! Sophivorus (talk) 15:50, 4 January 2021 (UTC)
@Emilio Hi! Today I managed to generalize the image metadata via a new Template:Image license metadata and integrated it to most of the file licensing templates (such as Template:CC BY-SA 4.0) rather than the Template:Information. Now all files using these templates should be understandable by Google (though it will take a few days for Google to catch on). I also normalized and improved the text of said licensing templates and organized the licensing categories. Tomorrow I'll try to finish with this task, since there're still a few loose ends. Sophivorus (talk) 16:45, 7 January 2021 (UTC)
Oh wow, thanks so much! This is beautiful. Emilio (talk) 17:57, 7 January 2021 (UTC)
@Emilio Hi again! Today I finished updating the licensing templates. I also renamed all the "images" categories to the more general and appropriate term "files" (so Category:US images is now Category:US files, etc) and simplified and organized a great deal the file categories, as can be seen from Category:Files. This brings us another step closer to a simple, useful, scalable and maintainable file management system! Sophivorus (talk) 15:55, 8 January 2021 (UTC)
@Emilio It looks like Google is starting to notice the new licencing metadata! Sophivorus (talk) 20:12, 30 January 2021 (UTC)
@Emilio @Kathy Nativi Hi! I just noticed that the new images indexed don't link to the basic image page, but to weird non-canonical URLs. This is because Google is crawling all links on Appropedia, rather than the basic canonical URLs. In other words, Google is crawling links like:
when it should only crawl:
To fix this, I just created following the recommendations at mw:Manual:Robots.txt#With short URLs
I tested the rules at and and it's all looking fine, but we should still keep an eye open on Analytics and Search Console for any issues. Sophivorus (talk) 11:59, 10 February 2021 (UTC)
@Sophivorus: Hi! I checked the Google Search Console, and I think is causing problems because it couldn't read the sitemap. Also, the health score has dropped drastically to zero, and we now have several orphan pages. Kathy Nativi (talk) 19:23, 15 February 2021 (UTC)
@Kathy Nativi Hi, thanks for noticing! I just added an exception to the robots.txt file for the sitemap. Search Console hasn't caught on yet and I think I cannot force it, but I trust in a few minutes or hours it will. Let me know if you notice anything on your side! Sophivorus (talk) 19:47, 15 February 2021 (UTC)
@Sophivorus Thanks! Let's give it a couple of minutes or hours. I'll keep an eye on it ;) Kathy Nativi (talk) 19:49, 15 February 2021 (UTC)
@Kathy Nativi It looks like Search Console has already found the sitemap. Did the "heath score" recover? Not sure where to look for that. Sophivorus (talk) 13:26, 17 February 2021 (UTC)
@Sophivorus Yep! We're back at 55 :) Kathy Nativi (talk) 15:27, 17 February 2021 (UTC)

Improve Help:Creating a page#Get started with a page template to use forms and visual editor[edit source]

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

Accept ToS when creating account[edit source]

Is it possible that we create a ToS (Terms of Service) were we also include the information about the copyrights? I'm working on the Copyrights page now, but I think it would be useful if when people create an account they directly agree to releasing their content under a CC BY SA 4.0. The same is true for the "save changes" section, that needs to be improved:

Appropedia copyright.png

I'd put a different text there, it should read:

"By saving changes, you agree to the Terms of Use, and you irrevocably agree to release your contribution under the CC BY-SA 4.0 License. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license."

Terms of Use should link to a page we don't have yet but that we should create, where we explain that users a) should not upload copyrighted stuff and b) that Appropedia might decide unilaterally and on its own to update the CC license version to the most updated one, etc., among other things.

Also, happy new year folks!

(also I can't find the signature button anywhere but who else could be talking about copyright & tos)

Poncho skin[edit source]

@Emilio Hi! I just improved the Poncho skin so that the menu (top-right) now supports submenus, check it out! You'll notice that one of the submenus is just too long for this design, but I actually think the problem in this case is that the submenu is just too long in general, and it may be better to shorten it rather than expecting Poncho to support such long menus. Other than that, what do you think of this submenu strategy? Sophivorus (talk) 14:07, 17 February 2021 (UTC)

@Emilio Hi again! I did some more tweaks to the skin based on what we talked, check it out at for example CCAT greenhouse, GSTC and Category:Medical courses. Feel free to play with the skin at MediaWiki:Poncho.css and let me know your thoughts and any issues you notice. Also, let me know when you settle on a color palette so I can start experimenting too, cheers! Sophivorus (talk) 13:19, 1 March 2021 (UTC)
@Emilio Hi yet again! I just improved Poncho with some styling for the Talk namespace and Help link, as we discussed. Looking forward to those colors! Sophivorus (talk) 13:51, 10 March 2021 (UTC)
I was looking at a subpage and noticed that the breadcrumb and the talk button create two lines. Is it possible to align them to avoid them taking up vertical space? I'll try to show you an example later. Emilio (talk) 18:42, 10 March 2021 (UTC)
@Emilio Hi! I think I know what you mean. I moved the breadcrumbs above the title. However, because of the way floating works, the breadcrumbs still push the title a bit down, compare for example User:Sophivorus with User:Sophivorus/sandbox. Also, notice that the position of the breadcrumbs is necessarily the same as the redirect messages (and others, probably), see for example Template:Step. I'm still not 100% satisfied with the look/position of the talk page link, help link, page indicators, breadcrumbs, redirect messages, etc. There're so many and varied elements that it's difficult to find a coherent and simple solution. However I think the current situation is probably good enough. What do you think? Sophivorus (talk) 14:09, 29 March 2021 (UTC)

Progress or checklist template[edit source]

Develop a template that detects and communicates to users the missing elements of a proper documentation. Sophivorus (talk) 17:05, 18 February 2021 (UTC)

@Emilio First version at Template:Project checklist. Waiting for some feedback from Catherine or you. :-) Sophivorus (talk) 13:21, 1 March 2021 (UTC)

Update Template:Event[edit source]

I was looking at mw:Template:Event and wanted to hear your opinion on the best way to implement it since Template:Event exists for a different purpose. What do you think? I'm looking to implement a template to track events happening on our platform (such as by Fashion Revolution or GSTC. —Emilio (talk) 00:57, 4 March 2021 (UTC)

@Emilio Our Template:Event isn't really used anywhere in the wiki, so we may replace it. But before I do, I'd like to know, where would the template be used? On the main page? Sophivorus (talk) 11:31, 4 March 2021 (UTC)
I was thinking of using them to show future events at portals such as the FR, maybe as a sort of "upcoming events" widget. Emilio (talk) 17:56, 4 March 2021 (UTC)

Databoxes[edit source]

@Emilio Hi! I'm creating this task to track the progress regarding the transition from infoboxes to databoxes. Today I did some improvements to Template:Databox. I also created Template:Recipe data and added it to Preload:Recipe and to Chucrut. While doing so, I realized that the image, caption, keywords and authors parameters were exactly the same as in Template:Project data and that they would be exactly the same in all other equivalent databoxes (say Template:Device data, Template:Medical device data, etc). So I went ahead and created Template:Page data, the idea behind this databox being to hold the most generic page information, common to all or almost all pages, such as the image, caption, keywords, maybe the language code (not sure if to keep that at Template:Language data) and author information (though this will probably merit a Template:Author data of its own). Anyway I'm not sure if this will be the best approach in the end, but I think it's something we'll have to grapple with more sooner than later. Looking forward to your reply! Sophivorus (talk) 15:13, 29 March 2021 (UTC)

@Sophivorus, Cassandreces: Hi! This is so cool. Julieta and I will meet next Monday and speak a bit about use cases and the metadata for each of these. Then we can have a discussion about what could work. What do you think? — Emilio (talk) 00:53, 30 March 2021 (UTC)
@Emilio, Cassandreces: Great! Can I join the meeting? Sophivorus (talk) 14:19, 30 March 2021 (UTC)
Of course! Cassandreces (talk) 17:04, 1 April 2021 (UTC)

Contact info[edit source]

@Emilio Hi! Today I normalized a few projects and in one of them I encountered contact information. There're many many pages with such contact information, so I just created Template:Contact so we can start giving them some structure, functionality, semantics, etc. I also wrote some documentation and included a link to it on Appropedia:Toolbox. I suspect it may become a popular template if we encourage it, but should we? Sophivorus (talk) 15:31, 30 March 2021 (UTC)

Hmm, not sure why I didn't think of this before, but obviously the contact template should've been a databox! So I just renamed and remade Template:Contact into Template:Contact data and updated Tablet chlorinators to stop waterborne disease in Haiti to make use of it. We may need to talk about what to do with pages that have multiple contact details (there're a few of those) but in any case I think it's quite clear that this is another use case for databoxes. Also, I updated Appropedia:Toolbox with a new section for databoxes. Cheers! Sophivorus (talk) 17:49, 30 March 2021 (UTC)

Add dropdown options to some databox options[edit source]

@Sophivorus, Lonny: One example that Lonny pointed out was Status. Is it possible to show these options when filling them out? —Emilio (talk) 23:14, 20 April 2021 (UTC)

@Emilio @Lonny Hi! Unfortunately this isn't possible yet, but there's work being done on this front so I'm optimistic we'll have this feature eventually, see Sophivorus (talk) 11:19, 21 April 2021 (UTC)

Improve h2 and h3 readability[edit source]

Hi all! I've noticed that text-heavy pages are hard to read so I added some CSS formatting at User:Emilio/common.js, and I'd like to hear your thoughts on how it can be improved further. One example is the horizontal line that Wikipedia uses, but I am not yet sure about it. What do you think? —Emilio (talk) 17:06, 14 May 2021 (UTC)

@Emilio: Do you mean the h2 and h3 CSS rules at User:Emilio/poncho.css? I think the main difference introduced by these rules is the bold text of the headers, would you agree? I think they do help, but before implementing the changes or suggesting further ones, do you have an example of one of those "text-heavy pages" that would benefit from the improvements? Thanks! Sophivorus (talk) 14:37, 17 May 2021 (UTC)
@Sophivorus: Sorry for not responding before. I think that most pages have this problem, but OpenClimate is a good example of how a mix of h2 and h3 can become a soup. I have added a couple of rules (larger bottom margin and a lighter color for h3 basically). As I mentioned before, Vector solves this problem by using a horizontal border below h2 but I don't know if we should go there yet, as there are other ways to make the visual hierarchy noticeable. Emilio (talk) 16:38, 25 May 2021 (UTC)
@Emilio Looking at OpenClimate under your new styling, I don't think there's any confusion at all between the hierarchies. I wouldn't go for the horizontal border either because I think it's unnecessary and kind of inconsistent with the rest of the skin. I think your solution works very well, if you agree let me know and I'll be happy to integrate part of it to Poncho (the rest will stay at MediaWiki:Poncho.css per being Appropedia-specific). Also, as a sidenote, I'm of the opinion that "flat is better than nested" and that titles shouldn't generally go beyond the h3 level. Cheers! Sophivorus (talk) 15:02, 1 June 2021 (UTC)
I agree with everything! If you think this is good, let me just think of a couple more changes before rolling it out. Maybe a left or bottom margin or something of the sort might be useful since I do feel like something is missing and I can't put my finger on it. —Emilio (talk) 17:49, 1 June 2021 (UTC)

Dead links script[edit source]

@Sophivorus: Hi Felipe! I wanted to know what the status of the dead links script is? Is it still "under maintenance"? :)

@Kathy Nativi, Emilio: Hi! Some time ago, we run the fixDeadLinks.php script over the entire wiki and later found that it replaced thousands of perfectly live and valid links for archived versions. So I made another script, called fixArchivedLinks.php, to replace archived links for live links (when the live links were actually alive, obviously). Today I finished running this second script and I believe it has fixed most of the misdeeds of the first script. I also improved the first script, made it more robust and cautious than before, which means it will be less likely to replace valid links for archived links. However, we should all be aware that some errors are inevitable, because some websites return incorrect status codes and thus confuse the scripts. So for example, a website may return a 403 forbidden error code, triggering the fixDeadLinks.php script, but when you actually visit the site, you find it's not forbidden but perfectly accessible. Likewise, a site may return a 200 ok code, but when you visit the site, find a blank page or some sort of DIY 404 page. In short, making a script that is 100% reliable is unfeasible, but I think the current version is quite reliable now. That being said, I don't think it's necessary to re-run the fixDeadLinks.php script, since most of the dead links have been fixed already. But maybe Kathy has some stats on the actual number of dead links? Kind regards, Sophivorus (talk) 16:11, 31 May 2021 (UTC)
@Kathy Nativi, Sophivorus, J.M.Pearce: Thanks a lot! I'm copying Joshua since he requested this as well. —Emilio (talk) 17:47, 1 June 2021 (UTC)

Appropedia Foundation site[edit source]

@Lonny, Emilio: Hi! Today I started to set up the site at I accessed WHM and created a new account for it, all good. However when I accessed the cPanel of the new account, I noticed an error message related to the SSL certificate that said " isn't resolving to an IP address on the Internet". Then I visited and got a similar error. I'm not extremely familiar with WHM so I may have missed some step, but it may also be that the new subdomain needs to be somehow registered at the registrar. May this be the case? Or have you never had to register subdomains at the registar before, for example when setting up ? Looking forward to your reply, cheers! Sophivorus (talk) 17:48, 26 May 2021 (UTC)

Solved! is up! Sophivorus (talk) 17:36, 25 June 2021 (UTC)

Sitemap couldn't fetch[edit source]

@Sophivorus: Hi! For the last couple of days, I've been getting the following errors when Google tries to index the sitemap: "Your Sitemap contains too many URLs. Please create multiple Sitemaps with up to 50000 URLs each and submit all Sitemaps." And "We encountered an error while trying to access your Sitemap. Please ensure your Sitemap follows our guidelines and can be accessed at the location you provided and then resubmit."

@Kathy Nativi, Emilio: Hi! I've been wanting to one-up our old sitemap solution for a while, and finally today I did. Before we had mw:Extension:AutoSitemap that regenerated the sitemap after every edit. Now I set up a cronjob that runs once a day and regenerates the sitemap using the standard generateSitemap.php maintenance script. This new sitemap, unlike the old one, consists of an index pointing to 5 different sitemaps, one per namespace, so I think we won't get the "too many links" error we had before. FIY, the sitemap now lives in the /sitemap subdirectory, so for example the index can be found at I already updated its location at the Google Search Console, but we should be watchful of any issues these changes may cause. Kind regards, Sophivorus (talk) 14:22, 1 June 2021 (UTC)
@Sophivorus, Kathy Nativi: I know virtually nothing about sitemaps, but this looks really, really cool! Thanks for your support! —Emilio (talk) 17:46, 1 June 2021 (UTC)
@Emilio @Sophivorus: Thank you! I checked it in Google Search Console, and yeah, the sitemap actually loaded and processed correctly with no errors. Kathy Nativi (talk) 18:00, 1 June 2021 (UTC)

Some pages appear as existing but cannot be deleted[edit source]

@Sophivorus, Irene92: Hi! User:Irene92 Found that some pages (she can only recall Baby Delivery for now appear on Special:UncategorizedPages but don't render when opened, and cannot be deleted either. Is this normal? —Emilio (talk) 15:24, 14 June 2021 (UTC)

@Emilio @Irene92 Good catch, definitely not normal. I haven't been able to fix it yet but I've taken note of the bug and will fix it eventually, thanks for the report! Sophivorus (talk) 15:41, 14 June 2021 (UTC)
@Sophivorus, Irene92: Thanks a lot! Now that I think of it, this might be what is causing these 404 errors on Google Search Console.—Emilio (talk) 19:51, 16 June 2021 (UTC)
No problem, happy to help! Irene92 (talk) 07:47, 24 June 2021 (UTC)

Request for specific language support[edit source]

@Sophivorus: One of the GSTC teams has requested support for the six UN languages plus Swahili (English, French, Spanish, Chinese, Russian, and Arabic and Swahili). They looked at's Google translate function. Is it possible to create an extra language template for users who need their content to be translated into all possible languages using Google Translate? I think this will be useful for this team and others in the future.--Emilio (talk) 02:57, 22 June 2021 (UTC)

@Emilio Sure! I just updated the default language list in Template:Page data to the requested languages and added an "other" option. I also created Template:Google translate to link to additional languages. Anybody can easily add new languages by editing the template and replicating the link pattern. Will this do? Cheers! Sophivorus (talk) 12:00, 22 June 2021 (UTC)
I think it will definitely do! This is pretty cool, thanks! Emilio (talk) 22:17, 22 June 2021 (UTC)

Links shortening[edit source]

@Sophivorus: I've implemented User:Emilio/links.js as an alternative to the link shortening on databoxes and wanted to show it to you. See how it's used here. What do you think? —Emilio (talk) 00:13, 26 June 2021 (UTC)

As mentioned via phone, the problem with this kind of solution is that the user may and will often think that the shortened link leads to the home page of the website, rather than to a specific resource within it. Less confusing is to trim the link with an elipsis "..." like it's currently done. Sophivorus (talk) 12:30, 16 July 2021 (UTC)

Safari not rendering video annotation example[edit source]

@Sophivorus: Hello! While doing a video annotation tutorial using Safari, I noticed the video example is not rendering. Perhaps you can take a look at it when you have time? I'm not an expert in the field, but could it be related to the file type? Kathy Nativi (talk)

Plagiarism checker[edit source]

@Sophivorus: Hi! Do you know of any way to implement this or any other tool of the sort? —Emilio (talk) 18:43, 13 July 2021 (UTC)

PageSpeed[edit source]

@Sophivorus: Hello! Could you take a look at the data that PageSpeed provides? It seems that there are some things that we need to improve and we need your help. Kathy Nativi (talk)