Hi Chris, thanks for adding a ticket.  

 

I understand the "error rendering Menu" issue.  Basically the problem was that you needed to migrate the data.  See Updating.  I know that's not an issue any more, but it may come up again in future upgrades.

 

I'm not as clear on the signup issue, but my first guess is that it is a mail configuration issue.  Do you have access to log files?  (normalling stored in the log directory of the wagn root).  If you can paste the error trace, we've got a good chance of narrowing down the problem.  There's a good chance you'll need to play with the smtp setting in config/wagn.yml.

 

I've been wanting to play with Wagn on Heroku but haven't yet.  I do suspect that there might be some issues with file and image cards at present, because Wagn is designed for integrated file security, and the files and images are expected to be stored on the server handling requests.   If I understand correctly, Heroku won't support that; you have to store them remotely.  I may be able to spend some time making a configuration option for s3 and others in a couple of weeks.

 

Keep us posted!

 

---

If you're willing to post more about what you had to do to get this far, that would be much appreciated!