Okay, then!
I have been informed this Urban Semiotic blog has been optimized by Media Temple — mainly by upgrading our MySQL database server — so please bang around here a bit and tell me if you find anything broken or ill-responding.
How is the speed?
Are comments and posts loading fast enough for you?
When you do a Live Search of our Archives do you get quick load times when you click on an article?
If anything is lagging for you please tell me what you were doing when the lagging bit you so I can provide a full report on Monday.
Thanks!

18 Comments

  1. Thanks for popping in and registering, simms!
    I appreciate your feedback and your friendship and I will make a note of your expressed pleasure with the speed.
    Things do seem immediately faster here and you were smart to clean out all the old stuff in your cache and reload the blog for fairer timing.
    You can always force a browser reload with CTRL F5 in Windows or using CTRL REFRESH/RELOAD button on your web browser.

  2. Thanks for checking in, clem! I’m glad you were able to get registered.
    I can register users myself or reset a password so if anyone gets stuck, drop me a note and we’ll fix it.
    How is the speed of the blog? Do you feel any changes?

  3. Thanks for checking in, clem! I’m glad you were able to get registered.
    I can register users myself or reset a password so if anyone gets stuck, drop me a note and we’ll fix it.
    How is the speed of the blog? Do you feel any changes?

  4. Just had a little database trouble where everything here died for a few minutes.
    Somehow some categories were merged and as I was fixing the problem the database puked a bit. I was able to fix things up and the site seems to be working and available again.
    We’ll keep an eye on it!
    Let me know if you have any trouble or if something here stops responding for you.

  5. Hi Chris —
    Yes, that was strange. Here’s what happened. I’ve had today’s post about Becoming an Urban Semiotic Author in my writing queue for two months:
    http://urbansemiotic.com/2006/03/13/become-an-urban-semiotic-author/
    When I hit “publish” today the post did not appear! I had database flashback panic and I looked everywhere for the post but did not see it. So I created a whole new fresh post and clicked “publish” and the post posted.
    Then I calmed down a bit and I checked my search box and — sure enough — there was the original post… but with a publication date of two months ago! Hmph!
    It used to be a post held in queue was always given the date of publication when you hit publish but that did not happen this time. I have to make sure to check the Timestamp from now on all my future saved posts and adjust them as necessary.
    So I had two articles that were identical but the newer one has a messed up permalinks structure so I deleted the old article and then I re-edited the permalinks for today’s article and that messed things up if you were fast to read — so you were clicking on a permalinks that I changed. A refresh of your browser should fix the problem.

  6. Hi Chris —
    Yes, that was strange. Here’s what happened. I’ve had today’s post about Becoming an Urban Semiotic Author in my writing queue for two months:
    http://urbansemiotic.com/2006/03/13/become-an-urban-semiotic-author/
    When I hit “publish” today the post did not appear! I had database flashback panic and I looked everywhere for the post but did not see it. So I created a whole new fresh post and clicked “publish” and the post posted.
    Then I calmed down a bit and I checked my search box and — sure enough — there was the original post… but with a publication date of two months ago! Hmph!
    It used to be a post held in queue was always given the date of publication when you hit publish but that did not happen this time. I have to make sure to check the Timestamp from now on all my future saved posts and adjust them as necessary.
    So I had two articles that were identical but the newer one has a messed up permalinks structure so I deleted the old article and then I re-edited the permalinks for today’s article and that messed things up if you were fast to read — so you were clicking on a permalinks that I changed. A refresh of your browser should fix the problem.