@kerri - Thanks for your advice, I'll give restart a try if I don't find a stable solution.
@Gabriel - " there's no need for most > of the code you've written so far to be in ApplicationController " I see now, you're absolutely right, it was just my first attempt at putting something together, and lots of controllers were using the code so I stuck it in App controller so everything could see it. I've got it a bit better organised now, it's within the class 'EventSearcher' which all then gets put on a queue to be done as a background job using the delayed_job gem, and I hope that's a better place for it. "you're running in > development mode locally. This generally means that all of your > ApplicationController code is reloaded on every request" I can see how this might cause a different behaviour between local app, and heroku app, I have not made any specifications as to which mode either the local or the heroku app is running in. Is the heroku app automatically set as production mode when I upload it? Would you recommend switching to production mode locally to test the app before uploading it? Having moved all the scraping functions to 'EventSearcher' I've discovered it's specifically one function, the one that opens and parses the html doc that needs a small change to be made before the heroku app works. I'd try and debug this when it doesn't work, but i cant get a print out of 'logger.debug' statements on the heroku logs, is it possible put in debug statements, and then look at them in the heroku logs?? Thanks for all your help! Mike -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
