Migration database connection timeout breaks css instead of showing friendly error message
-
expNinja
- Milestone changed from Beta 4 to Stable
- State changed from new to open
- Milestone order changed from 4 to 0
is it producing a fatal error? Can we get away with just putting a message on the page before running the script that they may need to bump up that time?
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.