Bad news. The Internal Server Error seems to be back... Good luck, Markus
On Sep 20, 1:13 pm, The Editor <[email protected]> wrote: > On Sun, Sep 20, 2009 at 6:49 AM, Kevin <[email protected]> wrote: > > > On Sun, Sep 20, 2009 at 1:17 AM, The Editor <[email protected]> wrote: > > >> ... I usually take Saturdays off > >> from BoltWire so didn't get to really work on it till last night. > > > A day off... hmmm... that is a new concept... I typically work 8 days a week > > (Its like 4 something in the morning now) ... I have thought of creating a > > clone to do all the extra work so I could take off time from time to time, > > but realized that if I made the clone just like me, it would revolt and > > refuse to do more work that I did. Still might get twice as much work done > > though and collaboration would be kind of neat as we could bounce ideas off > > of each other and have a clue what we were thinking. I have problems > > getting others to think like I do sometimes. > > You must be a character Kevin. We'll have to meet some time in > person... I actually like the way you think. Both of you. > > > This would be hard to replicate offline as it is the interaction of the live > > site and the server that causes it. It is/was wierd how it would sometimes > > work great, and then bam, nothing worked. > > Actually I think it was just that <em> that got in my favicon link. > That was caused by some problems in the recent reworking of the > snippets code and the fact I had a different configuration online than > off. Most people use ../ for their system paths, I had to use a hard > path with :// to get my images to work. And I broke one of the markup > rules that should have caught this. Evidently that problem completely > threw my server out--crashing everything and generating no error > messages. I need to remember that. I think it is what happened the > last time. Just as frustrating then as now. > > > It does help sometimes to have a development site so you can experiment and > > test before moving over to production though. I did that on the last > > upgrade as I wanted to see what a completely new install looked like and > > then slowly moved over the other sections of the site until I had it back > > up. I then just switched the sites. > > I guess I'm just in too much of a rush. Our development is pretty fast > here at BoltWire, but a bit bumpy at the same time. My solution is to > often wait a few days if the release is at all experimental to see if > anyone complains about anything, and then I upgrade my own site. So > sometimes BoltWire is ahead, sometimes behind the current release. > > But I feel good enough about how things are running now, I think I'll > go back to bed. I've been up trying to fix this since about 3:00 am. > > Cheers, > Dan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BoltWire" 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/boltwire?hl=en -~----------~----~----~----~------~----~------~--~---
