Kyle D. Skrinak

Insanity is doing the same thing and expected different results. I’m not sure why I keep doing this, but I do: when including a jQuery script into an xHTML page, be sure to declare the script properly: “text/javascript” not “application/javascript”

Now to create a repeat loop: for (i=0;i<=100;i++); echo “use “text/javascript” \n.

I use a LAMP-based web application to track my projects. I had been using Todoist.com, a great on-line to-do list for many years but I needed better accommodation. My hosting provider at the time had a “click-and-go” installer for dotproject so I installed it and moved all my data over and started using it. However, I had continual technical and UI issues with it, (namely, dp doesn’t like MySQL instances with temporary table creation disabled) and I noticed there was a 2 year lag between what I installed and the then current version (2.1.12, which it is still at; more on that in a second) but the hosting company wouldn’t upgrade. So I de-installed the canned version and uploaded 2.1.12, which helped reliability, at least a little bit. However, the “temporary tables” issue remained, and dp would choke on creating the main status page.

A little research, starting from how to work-around the lack of temporary tables, led me to a fork of dp, “Web2Project.” It appears that the w2p fork was fostered by the lack of development at dp. While I don’t use w2p as well as I could, I am greatly pleased with the reliability and better over performance and UI. You can’t miss the similarities, but gone are the in-line error messages and incomplete pages.

Installing w2p (which allowed me to start by using my dp data) was a bit of a hurdle. First things, check your requirements. W2P doesn’t like php4, and I didn’t confirm mysql requirements but I am running 5.x without issues. I first tried to work from my web server, but the typical network latency made this process cumbersome, so I decided to migrate firstly in my MAMP setup, which turns out (in hindsight) to be the best way to perform this process. I had to change the install script so that the case statement defaulted to a single option: upgrade an existing dp database into w2p. After the install script had no choice, it moved my dp data into a w2p schema, ready for work. There is one issue. They have dropped “ticketsmith” support. I used this feature for a brief period and found it’s lack of integration problematic. Apparently the w2p team agrees. However, why not remove this data if unsupported?