EnableABBREdit

By all means update the main Extension:EnableAbbrTags page if you so wish. I don't use mediawiki much these days so I won't have a chance to test your code, but if it works, please feel free. Thanks for your interest in the extension and mediawiki.

Cheers, --Jeffmcneill 13:37, 17 July 2009 (UTC)

ThanksEdit

Thanks for the edit on Special:Diff/2320418, I guess my knowledge on Composer is a little dusty! SamanthaNguyen (talk) 01:59, 22 December 2016 (UTC)

@SamanthaNguyen: no worries. :-) Yeah, Composer isn't really officially supported these days (although I'm not really sure why not). I use it for installing things though. :-) Sam Wilson 02:02, 22 December 2016 (UTC)

Autoblock info updateEdit

All of the mentioned autoblock features regarding local storage and cookies can be nullified by browser security settings / preferences. - DSquirrelGM𝓣𝓟𝓒 02:22, 3 March 2017 (UTC)

@DSquirrelGM: That's true, but there are plenty of vandals out there with browser setups that will retain the cookie, and who won't know how (or won't think) to delete it. The cookie isn't meant to be the only protection, but it is one. Sam Wilson 03:04, 3 March 2017 (UTC)

Wikistats 2.0 Prototype FeedbackEdit

Hello! Thank you for leaving feedback on the Wikistats - Future per report and Feedback/Round 1 pages. We used it to build an interactive prototype of the next version of Wikistats. We're now looking for feedback on the visual design, and we'd love your input. We have some follow-up questions but mostly an open discussion at Request for feedback/Round2 (if you prefer email, write to milimetric@wikimedia.org and please include "Wikistats Design" in the subject). Please comment by Monday, May 1st so we can include your feedback into the first release of Wikistats 2.0. Thank you very much!

Your Wikistats 2.0 Team, -13:38, 20 April 2017 (UTC)

Third party usersEdit

Re Wikimedia_Developer_Summit/2018/Participants, it would certainly be nice if there were more consultants making a living out of MediaWiki on third parties. It's not impossible! There's quite a lot of unmet market actually, as I quickly figured out by doing WikiTeam work and by asking people to upgrade their wikis. --Nemo 14:29, 3 December 2017 (UTC)

@Nemo bis: yeah, I agree, there's lots of installations out there looking for help! There are other FOSS projects out there that are much more inclusive of 3rd party users, I think. Sam Wilson 22:24, 3 December 2017 (UTC)

commons category downloaderEdit

Hi Sam,


regarding this

https://github.com/samwilson/commons-category-downloader

Is there an easier way for non-programmers to download items en masse in one category and subcategories? Artix Kreiger (talk) 15:05, 7 January 2018 (UTC)

@Artix Kreiger: not that I know of, sorry. Do you need just a one-off download, or is this a common thing? Maybe I should look at adding a web front-end to the above tool. There might be something else for doing this; I couldn't find anything obvious when I wrote this script though. Sam Wilson 23:17, 7 January 2018 (UTC)

MissedPages database errorEdit

Hi Sam, I'm seeing a database error with your MissedPages extension. I've reported it in the discussion page for https://www.mediawiki.org/wiki/Extension:MissedPages Vicarage (talk) 15:39, 18 May 2019 (UTC)

Not working in Mediawiki 1.34Edit

I still do not see Genealogy listed in the installed extensions. The only issue I can think of is that I'm using Mediawiki version 1.34. I see that Graphviz isn't compatible with this version.

Any ideas?

— Preceding unsigned comment added by Nicholaslue (talkcontribs) 07:52, 15 August 2019

  • Yes, unfortunately the GraphViz extension is not yet compatible. I've been trying to fix that, but also recently started adding support for Mermaid diagrams (which won't require any additional extension). However, the rest of the Genealogy extension should work correctly, and should certainly appear in Special:Version. Have you read through the how to debug manual page? That might help show up the error that's ocuring.

    Sam Wilson 22:57, 15 August 2019 (UTC)


I have turned on all debugging options. There's nothing on the page that's barking at me. I can see Genaeology/src/Hooks.php is loaded as a php included, but that's it. Changing the file name of Genealogy.i18n.magic.php creates a full site internal error so it appears the local settings file is pointing to the extension properly.

On a page where I use the person tag it shows up as: Template:Person

check out: http://colonialalbany.org

— Preceding unsigned comment added by Nicholaslue (talkcontribs) 08:33, 16 August 2019

  • @Nicholaslue: Sorry about the problems! I'm sure we can figure it out. Firstly, it looks like you've found a bug: the Genealogy extension is not correctly registering itself to display on Special:Version! I'll fix that now. But it doesn't matter for functionality, so you should still be able to get things working. The main point you raise is that the {{person}} template doesn't exist. This template isn't created by the extension, because every site will want it to be slightly different. There is an example template in the extension's directory (and here) that you can copy. I'd be happy to help you get it set up on the colonialalbany wiki!

    Sam Wilson 01:00, 19 August 2019 (UTC)

I granted you access to the site. I'm a bit new to Mediawiki but we thought it would be perfect for this kind of content. I appreciate you showing me how it's done.

  • @Nicholaslue: I've made a start on the 'person' template. See what you think. I'll reply more over there. Sam Wilson 06:02, 20 August 2019 (UTC)

Genealogy Extension PartnersEdit

Hello Sam,

Not to add to the Genealogy Extension issues, but I am having problems with the {{#genealogy:partners}} working. Both on my personal website and on the https://tools.wmflabs.org/genealogy/wiki/Main_Page website, I cannot seem to get the partners to display using partner1, partner2, etc. Is this something you are also seeing or are you able to use {{#genealogy:partners}} just fine? Mitchell316 (talk) 17:11, 29 August 2019 (UTC)

@Mitchell316: {{#genealogy:partners}} is for listing all partners; it won't display anything unless a page uses {{#genealogy:partner|Partner Name Here}} to define a partner (which can happen on either partner's page). Is your website public? I could have a look at your setup. Sorry it's not more straightforward! —Sam Wilson 04:32, 30 August 2019 (UTC)

Sam,

I should clarify that I have been defining the partners with {{#genealogy:partner|Partner Name Here}} before using {{#genealogy:partners}}. If I go to a page on Joe Smith and write:

 {{#genealogy:partner|Mary Smith}} {{#genealogy:partners}}  

I don't get any results. I haven't noticed this problem until recently, and I remember that it was working fine not too long ago, so that is why I reached out to you.

However, I have been tinkering with all sorts of templates, forms, etc., so it is very conceivable that it is on my end. By any chance, can you confirm that on your site the partners display is working fine?

Aside from this, I have been working on a website similar to what you have created on https://tools.wmflabs.org/genealogy/wiki/Main_Page . Currently, my site is public, but its mostly been back end work. I've read all about the wikimedia genealogy project and the current support and opposition. I think that there is a great potential for a genealogical based wiki project to succeed. I'm not sure how involved you are in actual genealogy as compared with the software engineering, but the only valid sites that use MediaWiki are Familypedia and WikiTree, both of which I feel are lacking. Currently, I have developed a template that automatically creates an infobox (similar to the aforementioned website) along with an adjacent Ahnentafel tree that automatically displays 4 generations using SMW.

Ultimately, I plan to develop a finalized version of what a Wiki-structured genealogy website should be, and then go live on some separate domain. I feel that it would be a lot easier to gain support with an already created site.

— Preceding unsigned comment added by Mitchell316 (talkcontribs) 16:03, 30 August 2019

@Mitchell316: That sounds like a great project! The issue you're having sounds like it could be related to caching. Does re-parsing a page (?action=purge) help? Are all jobs being run? Do you get correct output for {{#genealogy:siblings}} or {{#genealogy:children}}? I have the extension working on archives.org.au if you want to have a look at how it's set up there. —Sam Wilson 06:04, 1 September 2019 (UTC)

emailEdit

  • Hi, you have use e-mail?--Msnhinet8 (talk) 01:36, 9 October 2019 (UTC)
  • I have send e-mail give you, you has look?--Msnhinet8 (talk) 03:22, 9 October 2019 (UTC)
  • at home staff?--Msnhinet8 (talk) 03:33, 9 October 2019 (UTC)
  • my wiki farm want install skin:monaco.--Msnhinet8 (talk) 03:36, 9 October 2019 (UTC)
    • @Msnhinet8: I'm not going to log in to your VPS, nor install anything for you. Please ask actual questions about the troubles you're having! I'm only too happy to help. It sounds like you might not be very familiar with running a server, in which case you might be more interested in a managed wiki from somewhere like Miraheze. —Sam Wilson 03:40, 9 October 2019 (UTC)
  • so apart from miraheze and wikia, also the other free mediawiki farm?--Msnhinet8 (talk) 03:42, 9 October 2019 (UTC)

skinEdit

A barnstar for you!Edit

  The Original Barnstar
I am sorry for misclicking the rollback botton. Sorry for any confusion caused. 94rain Talk 00:04, 28 October 2019 (UTC)

@94rain: No worries! I figured something like that must have happened. —Sam Wilson 00:14, 28 October 2019 (UTC)

Re: Google Summer of Code task that your mentoring... :)Edit

Hey, I've got a few questions regarding how I'll have to work on the Index page-list editing widget. Can I contact you over email (or even IRC) regarding those questions? Also, could you take a look at the draft proposal T247157 that I have put together and provide some feedback or comments on how to improve it :)

P.S: Could you point me to some examples of like Javascript-based UI widgets that are currently being used by the community, I sort of want to get an intuition about the general architecture and implementation of these widgets and how the PHP and JS parts work together :) --Sohom data (talk) 18:19, 15 March 2020 (UTC)

@Sohom data: sure! I've replied on that ticket. I'm not in IRC much these days; Matrix is a better way to catch me for chat. I'm @samwilson:matrix.org. —Sam Wilson 03:34, 17 March 2020 (UTC)

Genealogy: Mermaid IntegrationEdit

Hey there! I've been tryin to use Mermaid with Genealogy since Miraheze got the newest update few days ago, and the explanation under Extension info is rather confusing. Talking specifically about this:

{{#genealogy:tree|ancestors=List|descendants=List|format=mermaid}}

You mention lists to be newline separated, but then ancestry list ends up like this:

Maternal Grandmother, Maternal Grandfather, Paternal Grandfather, Paternal Grandmother
Mother, Father

In this case it forces all the first line to be one new page, instead of four? How do you need to format it to properly link to separate entities per list? Is there anyway I can easily define people per list? Do I have to have pre-setup people pages to use that feature?

I've also played around with mermaid alone, and thought something like this could be more intuitive, though by mermaid alone I cannot link to the pages or use those as variables, so it still doesn't do it justice. Just thought maybe it would be a good inspiration for the future of the plugin.

{{#mermaid:graph TB;
maternalgrandfather["[[matgrandpa]]"] --- mother 
maternalgrandmother["[[matgrandma]]"] --- mother 
paternalgrandfather["[[patgrandpa]]"] --- father
paternalgrandmother["[[patgrandma]]"] --- father
mother["[[mother]]"]  --- person["[[person]]"]
father["[[father]]"] --- person
partner01("[[partner01]]") --- child01
person --- child01["[[child01a]]"]
person --- child02["[[child02a]], [[child02b]]"]
partner02("[[partner02]]") --- child02
}}

Maybe it's just me being dummy, but I'm struggling with figuring it all out. A more in-depth tutorial for sure would help with bringing more people to use the extension! Regardless, thank you for your time put into this. --Yevvieart (talk) 06:04, 1 August 2020 (UTC)

I was just thinking about that stuff actually! Good timing. The newline-delimited thing is a bit counter-intuitive; probably we should add an option to use a different delimiter (e.g. a semicolon). But anyway, your example should look something like the following:
{{#genealogy:tree
|ancestors=
Mother
Father
|descendants=
Maternal Grandmother
Maternal Grandfather
Paternal Grandfather
Paternal Grandmother
|format=mermaid}}
Does that work? By the way, I'm also working on improving the Diagrams extension so that it can be installed on Miraheze, and then Graphviz graphs will be possible as well as Mermaid. —Sam Wilson 06:13, 1 August 2020 (UTC) (oops, forgot to ping @Yevvieart: Sam Wilson 06:16, 1 August 2020 (UTC) )

That tosses them one after another in a line, but doesn't form any flowchart or anything resembling family tree. Just disconnected nodes thrown in one column. It's not 100% necessary for me to use it that way though, I was just wondering if it was the problem on my side or something with the newest mermaid update or what. I may just use hand-scripted mermaid for trees and genealogy for the tables and person profiles, as this way both are far more customizable. @Samwilson: --Yevvieart (talk) 06:43, 1 August 2020 (UTC)

@Yevvieart: are the page names you're entering for 'descendants' and 'ancestors' linked as relations of other pages? Are they red in the diagram? It might be that they've got the wrong letter case or something. The names you list there should be shown in a tree with the same relation nodes as they get listed with on their own pages (siblings, etc.). The demo wiki at toolforge:genealogy might be a useful place to test things, where I can come and help. —Sam Wilson