Extension talk:JSKitComments

Can this be setup to use the USERS name if they are logged in?--Rovo 20:45, 18 January 2008 (UTC)
 * There is no interface, to my knowledge, to do that. This is a 'limitation' of the Js-Kit Comments tool itself. Jean-Lou Dupont 21:11, 18 January 2008 (UTC)

Strange..
Hi Jean. This extension is nice and useful but this extension is used only once for all the site ? I putted the code : on 1 page, it worked, but if i put the code on other page it's using the same posts from the first page. So if i put this code on any page it will use the first page. I want to use this extension for each page i have. If i have 1000 pages and i want to put comments on .. let say 500 of them, i want to unique on each page. How do i do that ?
 * Hi - I believe you need to use the path parameter for this - it instructs JSKit to associate a page (path) with a set of comments. Jean-Lou Dupont 12:12, 22 June 2008 (UTC)

Any idea on how to enable this for the entire site without requesting you to put a code for every page? Also it should use the page id not the page path/url in order to keep the comments in case you move/rename the page.

Bad svn usage [CLOSED]
The SNV of this extension is not well configured, there is no trunk folder and the 1.0 release should be created as a branch not an archive in the root.
 * I don't see any issue with the SVN link I have provided. Jean-Lou Dupont 02:19, 13 July 2008 (UTC)
 * Sorry but, a normal SVN repository is not used to keep zip files of the source code, also it should contain a folder named /trunk/ where there is the current code. In your case there is on /1.0.0/ - think that someone wants to update the software if needed, you can use the /trunk/ for this or create another folder /release/ where you put the release. This way running "svn update" will upgrade the software. For more information just google for svn repository structure, thanks.--Sorin Sbarnea 21:17, 4 September 2008 (UTC)
 * 1) there is a trunk folder in my SVN
 * 2) the ZIPs are maintained in a separate branch folder called tags
 * 3) the primary means I offer my extensions through is PEAR - I provide the ZIP & the TAGS SVN for convenience only.
 * Hope this clarifies things. Cheers, Jean-Lou Dupont 12:36, 5 September 2008 (UTC)

Additional functionality?
This is a great extension and I like it!

I'm just wondering whether it is easy to extend its functionality to include the following:


 * . Comment on specific sections (by adding a anchor/button beside section heading saying "Leave a comment", and show a symbol beside a section heading when there're comments about it.
 * . Collapsible comments, individually or as a whole.
 * . Allow wikitext in comment text.

Thanks! --Liyf 06:32, 9 March 2009 (UTC)

Multiple comment blocks?
I have another question. How do I enable multiple comment blocks? On the extension page it says I can use the "path" parameter. I added the following code on the sandbox but only the first comment block shows up.

Am I using the correct syntax? Thanks! -- Liyf 08:14, 9 March 2009 (UTC)

Update: I found out how this can work. In the original source code, the js-kit javascript is only added once. It actually needs to be added every time when you want a comment block. So, the function mg_jskitcomments needs to be changed to this:

Note that the commented-out code was previously uncommented. Replace the function with above code and now you can have multiple comment blocks in one HTML page.

--Liyf 04:34, 16 March 2009 (UTC)