A co-worker and I are big supporters and promoters of mojoPortal on our campus; one more recruit and I think we win a toaster! Today we were talking about our lessons learned through mojoHardship. So here you go; I ask that you share with the mojoPortal community your mojoFails and your mojoSolutions so that we can all learn from our mistakes.

Here's one of mine -- recently rolled out a new skin but found the modal not working. After killing hours figuring out the problem I realized that I forgot to include the colorbox reference in the skins style.config.

Just to piggy back off of my colleague ("scrailsabck") above, I'll add the following sob story that happened to me a few weeks ago:

1. I added the following key to my user.config file for a large site I run using mojoPortal: 
   <add key="aspnet:MaxHttpCollectionKeys" value="1200"
2. I hit Save and then promptly moved on to other tasks
3. Sometime during the morning of the following day the app pool reset, crashing the above site because I forgot to close the above tag properly.  Since I had meetings all morning, I had a number of e-mails/phone calls to answer once I got back into the office.  Oops.

Lesson #1 - Always touch your web.config file anytime you make even the simplest of changes to your user.config file, just in case you do something stupid, like I did.

Lesson #2 - Do not use the default mojoPortal error page, since it doesn't provide web dev contact information.  In case it's useful to someone, I created a little blog post at http://code.colostate.edu/know-when-your-site-goes-down-before-your-clients-do.aspx with a sample error page and a means of (hopefully) ensuring that you know when your site goes down before most of your clients find out (using a free tool called Uptime Robot).