Raymond Camden's Blog Rss

LighthousePro Updated

5

Posted in ColdFusion | Posted on 04-28-2008 | 3,860 views

Just a quick note to let folks I released a small update to LighthousePro, my ColdFusion-based issue tracker. The updates include:

  • I finally got off my lazy rear and changed Loci/Locus to Areas/Area. I don't know why I took so long since no one knew what Loci meant.
  • In Application.cfc, I added code to check for the attachments folder and create it if it doesn't exist.
  • Fixed some bugs in the main project view, and I now allow you to filter to a ID number. So if you have a lot of bugs and the client says, find bug 212, you can now type 212 and see the bug.

Comments

[Add Comment] [Subscribe to Comments]

I'm having a hard time getting things fully working with bluedragon. I made a few minor adjustments and was able to login and add new issues. The only thing left is spry paging -nothing is showing up when i view the issues. If i view them in print mode they are all there.

I poked around with firebug, and data IS getting passed to spry, but it simply won't display on the page. Any suggestions? Since this is spry, it seems like it shouldn't be a bd/CF problem at all :(
I don't think it's a Spry issue or it would impact all. I'd bet BD is returning the data differently then CF does. Can you compare against a CF install? Or paste in some of the JSON?
Here is the JSON:

{"RECORDCOUNT":1,"COLUMNLIST":"description,id,issuetype,locusname,name,prettydate,prettyduedate,publicid

,severityname,severityrank,statusname,statusrank,username","data":{"description":["gf hh f hfhf h hf

fhh fh"],"id":["E92EFBA4-B76F-4B8E-B19396BEC049838D"],"issuetype":["Enhancement"],"locusname":["Administration"

],"name":["Test"],"prettydate":["6\/15\/08"],"prettyduedate":["8\/12\/08"],"publicid":[1],"severityname"

:["Low"],"severityrank":[1],"statusname":["Open"],"statusrank":[1],"username":["Produce Marketing Assn"

]}}


See anything interesting?
Looks to be case. The columns are uppercase in CFMX, lowercase in BD. You can edit the server side to use uppercase or edit the front end code. In this case, I'm putting the blame on BD for returning in a different case.
That did it, thanks ray!