Nice Lighthouse Pro update

I don't normally blog about every little update to my open source applications, but I thought I'd point out an update to Lighthouse Pro that I just released. Along with some bug fixes (thanks to Lincoln Milner), I finally added issue defaults for projects. What this means is you can specify a default project area, severity, status, and issue type at the project level. Any new issue will use these defaults. This also applies to issues created via email.

As always - any feedback or suggestions for LHP are welcome.

Comments

[Add Comment] [Subscribe to Comments]

Sean Ford said on 08-10-2010 at 5:35 AM #

Ray,

I was wondering if you've ever given any thought to allowing users to register themselves directly on the login screen. I was thinking of using Lighthouse as a simple way for my clients to file bugs in applications I develop for them. However, I don't want to have to manually create accounts for each employee.

How would I know what project to assign them to? (assuming that I use the same setup for multiple projects)...I was thinking of hard-coding the projectID in the Support link. If they register, they are automatically assigned to that project...if they are already registered, and the project is a new one (for clients with multiple projects), it would assign the new project to them upon a successful login.

Any thoughts on this? I have a few more, but want to get your feedback first.

Regards, Sean Ford

Raymond Camden said on 08-10-2010 at 8:35 AM #
	No, I've not consider auto registration. (Well, I did consider a hosted LHP solution that I'd charge for.) The closest LHP has is the email support. You can let users send email (or even build a form front end that sends the email) and it will auto create issues.

Andrew said on 08-17-2010 at 12:50 PM #

Hi Ray,

Love the site and LHP! New to Model-Glue and Coldspring and trying to make a few quick modifications to LHP.

I've noticed that the application does not appear to be updating after I make the code changes. For example, I can update a SQL statement in the authenticate function to always use a username that is not in the db (not that this is a change i'm planning on keeping, but rather an example of something that should make the site bomb;), and it will still let me login with appropriate credentials?

I've looked around your site for some help. I have trusted caching off and I've cleared the cache before reloading any of the pages.

Just wondering if you have any ideas as to why nothing seems to uptade. I have other coldfusion applications on the same server which will update.

Raymond Camden said on 08-17-2010 at 12:54 PM #
	MG caches a lot of stuff for performance. Look in ColdSpring.xml and you will see a reload key and password. I believe I left it at default: init and true In the browser, add &init=true And it should refresh.

Andrew said on 08-17-2010 at 6:19 PM #
	Awesome! Thanks Ray for the quick response. LHP is a great product!

Jack Ding said on 12-18-2010 at 8:38 AM #

Ray,

I am a CF application developer using LHP since its very earlier stage and I do love it and got used to it within my programming life.

However I have been working on many PHP projects recently due to more country specifics here (I am located in China where CF is less popular at this end). I am thinking of re-writing LHP in PHP. And of course it will remain open-sourced. Here I would like to ask for your permission and some help for that. If that is workable please let me know.

Regards,
Jack

Raymond Camden said on 12-18-2010 at 8:51 AM #
	Sounds ok to me.

Jack Ding said on 12-18-2010 at 10:41 PM #
	Great! Thanks very much for your prompt reply Ray.

Adam said on 03-02-2011 at 6:34 AM #

I have a user who is assigned to all of the projects that I have created. However, this user doesn't want any email alerts so I have opted them out of all 'Email projects'. This is on the User Edit screen.

When I update an issue then I get an undeliverable email alert as LHP still attempts to send an email. I have put a dummy email into the email field for this user as it is required.

I think this is a bug? Sorry I tried adding this to riaforge but couldn't log in after registering.

Thanks in advance,

Adam

Adam said on 03-02-2011 at 6:51 AM #
	I should add that this only happens when the issue was raised by the user in question. That is, it seems to send an update to the user who created the issue even if they are opted out of email alerts. Is this by design? Thanks, Adam

Adam said on 03-04-2011 at 11:19 AM #

Sorry for cluttering up this post with comments but not sure where else to post them.
Not sure that the above is a bug in as much that an undeliverable email message only gets triggered when the user email address is bogus. When you put in a valid email then no email is sent at all which is the correct behaviour based on the 'Email projects' setting.

So here is a feature request:

Have an email setting so that users only get email updates to tickets that they initially created or even better to those that they currently own. That way they wouldn't get all emails from a project just the ones that they are interested in. E.g. if issue gets marked as 'ready for testing' or whatever.

Any takers on that one?

Apologies for all the ramblings...

Raymond Camden said on 03-06-2011 at 12:37 AM #
	You can file bug reports, and requests, here: http://lighthousepro.riaforge.org. There is a Issues link you can follow. Please do so - it helps keep me organized. :)

Randy Smith said on 02-04-2012 at 1:01 PM #
	Ray, So far loving Lighthouse! Tried to load Mantis - what a pain. I have most things set up, but .... how do you get the email to bring in the issues? I am using my POP server address, do I need to use SMTP? And what triggers it to go look for the mail? Thanks for this product - saving my hide! RLS

Raymond Camden said on 02-04-2012 at 1:08 PM #
	The mail settings should point to a pop server. Then LHP uses cfpop to read in the mail. (Be sure it is ok for LHP to delete the mail.) The docs should - stress should - discuss this. ;) If not,ask more questions.

Randy Smith said on 02-04-2012 at 1:26 PM #

Wow! You are on top of the replies! Very impressed, thank you!

By "make sure LHP can delete the mail" I assume that just normal CFPOP add/delete functions are used so I don't need to go to great lengths to make sure unless I've already gone to great lengths to prohibit such activity.

I think the mail problem is on my side, looking into it. I've set up over a thousand emails, but something went kablooey inside the mail server this time... :-( Happens to even the mediocre of us.

I assume also that LHP is only going to pull from mail when *someone* (anyone) access the system and/or the projects, and that will be the trigger to check the mail as I don't think you auto-installed any automated processes to read the mail.

Thanks again for this product, reports, tools, forms, interfaces -- all are wonderful!

RLS

Raymond Camden said on 02-04-2012 at 1:30 PM #

"By "make sure LHP can delete the mail" I assume that just normal CFPOP add/delete functions are used so I don't need to go to great lengths to make sure unless I've already gone to great lengths to prohibit such activity."

Right, what I meant is, don't point a LHP project to your personal email. It will read, consume, and destroy. You would make a new email account for the project, like, project@foo.com.

" assume also that LHP is only going to pull from mail when *someone* (anyone) access the system and/or the projects, and that will be the trigger to check the mail as I don't think you auto-installed any automated processes to read the mail."

Actually it IS automatic. The code creates a ColdFusion Scheduled task. I think it runs once every 15 minutes. What's cool then is that if you (a LHP user) have subscribed to a project, then you would get notified.

Randy Smith said on 02-04-2012 at 1:35 PM #
	I need to step into that auto-create a scheduled task stuff. SO MUCH of ColdFusion goes unused, just like the human brain. SO MUCH more I could be doing, given time and training. The good news is that it's there for us when we're ready to "scale up"! Thanks for showing us the way (and for your LHP comments). RLS

[Add Comment] [Subscribe to Comments]