[Block] Linkit - A member submittable links block

[Thurnok]

@houston
What browser are you using?  I only test on Mozilla, FireFox, and IE.  I don't think I have any code that wouldn't specifically work for other browsers (like Opera, etc.) but you never know.

Try copying the code from the first post of this thread again and overwrite your block code with it, then set your specific settings again.  Just in case your original copy/paste missed something.

[houston]

houston ,
you need to enter an link first and then click on test. Can you add a link without testing it first?
Jim

Been there, done that and left the t-shirt behind.

Did not try to add a link without testing it though.

I will give it another go and maybe keep the t-shirt this time.

Cheers

[Thurnok]

Yes, you can add a link without first testing it.  I haven't enabled any URL validation, though someone asked me about that some time back.  I'm contemplating that for the future.

However, the test button at least allows your users to verify that the link they are about to add is valid (brings up a page) and is the one they intended, prior to actually submitting it.  This is a good idea in all cases, but certainly helpful to the admin if you are not allowing members to edit or delete their own links (an option).

[mietje]

Just what i needed.   

Thank you for this.

[Verve]

First of all, thank you.  This is a very useful block snippet!

I think I found a small bug.

The name that is displayed for a submitter when you mouse hover over a link is the submitter's "username" and not the submitter's "Display name."

I only noticed this because I had used some obscure name for my original login and then changed my username to 'Admin' for everyday use.  When I post links it shows the original name and not the 'Admin' name.

[Thurnok]

This is not a bug.  This is by design.  The reason being, a number of boards allow users to change their username.  The $user_info['username'] of the submitter is written to the Linkit table so that additional calls to the database do not need to be done when storing submitter info, as well as when reading the info.  In otherwords, my original intent was to minimize the db accesses.  This being the case, if I wrote the display name info, it would become inaccurate very quickly for sites allowing Display Name changes.

I'm planning a new version however, that will make it inevitable that more db access will be required, and as part of that the Admin will be able to choose whether to use username, or display name for mouse-overs.  The new version will allow various display modes (simple list, descriptive list, detailed list, category list) and will include categories/subcategories.

[Gargoyle]

Thurnok are you developing the link Module for TP ?? If your not perhaps you should. It seems like all we are missing is integration with the TP admin section..

Great work all the way around..

[Thurnok]

That would be Bloc's call.  TP is his baby, though I'd be happy to provide work in that area.  In the mean time, for those that want to have the admin configuration in the ACP, I could work that up.

[brianjw]

Maybe if you really wanted to make it easy and awesome. You can make it a mod and integrate it with TP kind of like Felblog And have its own TP Admin section...who knows...you can do anything with PHP

[Thurnok]

You can't get much easier than Blocks - copy/paste

Set a few simple variables the way you want them, and then you are off and running.  Modules are for things that are much more complicated, although I could certainly make this block very complicated if I put some time into it.

In any case, this is a Block, and since TP 1.0 will have a Link module, there is no reason for me to make Linkit into a module.