Projects / MyThreads-Links


MyThreads-Links is a Web-based links manager that looks similar to Yahoo but was written in PHP and uses MySQL. It uses PHPLib templates so that its very simple for anyone to change the look and feel of the program without having to edit the code. Custom database fields can be easily added and managed.


Recent releases

  •  02 Jan 2007 03:59

    Release Notes: Some very old input parsing bugs were fixed. The email function was improved to stop spam. A recently requested feature was added: allowing anonymous users to add links to the database with the 'anonymous_add' configuration option.

    •  07 May 2006 19:42

      Release Notes: A new security code feature has been added to secure the additions or updates of database entries.

      •  16 Aug 2004 10:28

        Release Notes: A bug preventing the migration from 0.9.x releases was fixed.

        •  17 May 2004 20:46

          Release Notes: A Slovak translation was added and a few bugs were fixed.

          •  01 May 2004 19:55

            Release Notes: This new stable release adds some important features, like easy database and forms customization, dynamic templates selection, a new "details" page for each entry, and new facilities to help the admins to validate and modify the entries.

            Recent comments

            16 Oct 2002 11:27 ldrolez

            Re: Design

            > Firstly, the
            > URLs are stored in the database and
            > keyed by the URL.

            This long dating flaw has been fixed for in the 0.9.0 release. Fixing this flaw will also allow the user to easily add its own fields to the links database (author info, images, ...) in the next releases.

            16 May 2002 22:45 qaexl


            I'd like to thank the open source community before I dig deeper into some of the issues with the program. They have been a great help to me. In any case, this program does what it set out to do: organize information in a Yahoo! like category. However, there's a couple flaws with the design that I found while modifying it for a client. Firstly, the URLs are stored in the database and keyed by the URL. I can understand wanting to have a unique URL. However, when the *client* tries to use it, they sometimes leave off the URL or add a space. Then, when they try clicking on the edit link, it doesn't appear. Go figure. Also, because it is keyed to the URL, that means the URL can only appear in one category at a time. Secondly, I don't like the Templates. Ok. That's more of a personal opinion, but, most of the code was written with an if-then-else step ladder that determines what template to use. A more elegant solution is to have a table or an array doing the matching. But since I'm lazy too :-) and the second is more of personal opinion, there's only one serious flaw.


            Project Spotlight


            A Fluent OpenStack client API for Java.


            Project Spotlight

            TurnKey TWiki Appliance

            A TWiki appliance that is easy to use and lightweight.