User talk:Daduxing/familytree.js

New owner
See
 * Wikipedia:Miscellany for deletion/User:GregU/familytree
 * Interface administrators' noticeboard/Archive 1
 * User:Daduxing/familytree and User:Daduxing/familytree.js

OK User:Daduxing I have now read the above and understand why you asked me for help. I am typing this on a tablet, which is not ideal. I will have a look on a computer in the next 24 hours. In the mean time I am going to recover an old copy of the documentation and edit it. Please take a look at User:Daduxing/familytree and improve it (but give me an hour). PBS (talk) 16:47, 25 January 2020 (UTC)
 * No problem, take your time and thank you very much for help.
 * I had a look at the code. It is more broken than I thought, as it does not seem to work for familytree templates. Do you know when it stopped working? -- PBS (talk) 16:29, 27 January 2020 (UTC)


 * I noticed when the Template:Chart was moved to Template:Tree chart because I suspected that it will not recognize the new naming, and verifying, I realized that I was right. For me it is still working with the old Templates ( chart and familytree), but it is true that it always had a strange error (you could see the last message from this discussion User talk:Daduxing). --Daduxing (talk) 17:43, 27 January 2020 (UTC)
 * Can you either provide a link to a tree on which familytree.js still works, or provide a simple tree here. -- PBS (talk) 17:49, 27 January 2020 (UTC)
 * See my User:Daduxing/sandbox. Especially the first two trees. The first is a familytree and the second is a chart. They all work. You can test there if you like.--Daduxing (talk) 17:59, 27 January 2020 (UTC)

New and modified code
I think I have solved the specific problem of various names for chart and familytree templates. There is now a working version at User:PBS/familytree.js. To test it please implement the following steps. and run tests. Please report any mistakes to me. Once you are satisfied with the changes then you can copy the code at  to User:Daduxing/familytree.js and then change the link back in User:Daduxing/vector.js to point to  -- PBS (talk) 11:20, 31 January 2020 (UTC)
 * 1) edit User:Daduxing/vector.js
 * 2) remove the line   -- it is redundant and confusing.
 * 3) alter the line    to


 * Looks good. Thank you very much for fixing it. --Daduxing (talk) 14:42, 31 January 2020 (UTC)

Looking at your code today you need to change the line: var Summary = "Edited  using familytree.js"; to: var Summary = "Edited  using familytree.js"; This is a semi cosmetic change it just affects the summary-- PBS (talk) 16:15, 30 May 2020 (UTC)

How
How can we use this familytree.js?--Kaiyr (talk) 08:33, 22 November 2021 (UTC)
 * Hi . To install, add:


 * to your common.js ( User:Kaiyr/common.js ) or vector.js page ( User:Kaiyr/vector.js ). This adds an option [Templates → Art] to the toolbox menu when editing familytrees. It is a two pass operation. 1. Press [Templates → Art] -- the template code is changed into an intermediate format and the menu option changes to [Art → Templates] 2. Press Art → Templates] --  converts the "Art" back in to cleaned up temlate code. See  and    --Daduxing (talk) 08:14, 23 November 2021 (UTC)

]
 * I did it. But I dont see any [Templates → Art].--Kaiyr (talk) 11:16, 28 February 2022 (UTC)


 * @Daduxing@Kaiyr I also have this issue, have either of you solved it? Immanuelle  💗  (please tag me)  21:08, 9 May 2022 (UTC)
 * @User:Immanuelle and @User:Kaiyr I was fooled by this initially. See the comments at the start of the script.

// To install, add:  importScript("User:Daduxing/familytree.js"); // to your common.js page. This adds an option [Templates → Art] // to the toolbox menu when editing familytrees.
 * The relevant comment is when editing familytrees. This is because the [Templates → Art] option only appears in your side menu when actually editing a familytree. Please comment back here to tell me if this fixed your problem. But please include my user name " @User:PBS " so I am pinged as I do not watch this page. -- PBS (talk) 09:44, 26 May 2022 (UTC)

Copying markup before publishing/previewing
A key issue that I have come across is the fact that the tool will not prompt you to copy over the translated code into the actual content box--I have lost progress a few times this way after either using the Preview function or publishing, having forgotten to move over the code. Not sure if this is an a common experience, and not entirely sure how the tool could possibly prompt you to do this, but making note of it here. — aoyma3 (talk) 23:56, 27 April 2024 (UTC)