Briefly unavailable for scheduled maintenance

I killed hundredvisions.com. Fortunately, it was only mostly dead.

I was updating the site, and I guess I got a little hasty, and the next thing I knew, I had the dreaded message showing:

Briefly unavailable for scheduled maintenance. Check back in a minute.

No matter what I tried, to do, that was the only message I had. I couldn’t go back to the dashboard, I couldn’t go to any page. No matter what page I went to, I either got the scheduled maintenance message.

So I did what any tech savvy person would do, I googled the message, and low and behold, I didn’t have to go through my WordPress site pockets and dig for loose change.

All I had to do was the following:

  1. FTP to the site
  2. Navigate to the same folder as the wp-config file, and
  3. delete the .maintenance file from the folder

And voilà, it was back among the living. The problem was that I began an upgrade process, and before it was completed, I navigated away. While it was doing the upgrading process, it put a lock on the site in the form of a file named “.maintenance,” which produced the maintenance note. Unfortunately, the last step of the upgrade process is to remove the .maintenance file. But interrupting the process prevented my WordPress site from removing the “lock.”

As long as that file was present in the folders, it would continue to produce the message, but once I removed the file, we got the site back.

Next time, I’ll make sure all upgrading is done before I try to navigate away.

Dude, What’s My User Agent?

I’m just wrapping up a 45+ hour WordPress project, and I’m in testing and refining mode, and lo and behold, iPads and iPhone browsers don’t want to display like the other browsers.

When I test on the iOS browsers, I have text that’s partially hidden and has to be raised 70 pixels. The odd thing is that the Galaxy S4’s default browser has the same issue.

The problem with these changes are that the mobile devices don’t have a way to show you the source code; there’s no right click and view source, no F12 key, and no menu items available for help. Without the source code, I can’t read the user agent.

What’s a front-end developer to do?

Behold, WhatsMyUserAgent.com!

When you are in the same situation, simply

  1. Go to What’s My User Agent, and you’ll get a huge string of information.
    1. For example, my Galaxy S4 Default browser showed me the following:
    2. Mozilla/5.0 (Linux; Android 4.3; en-us; SAMSUNG SGH-M919 Build/JSS15J) AppleWebKit/537.36 (KHTML, like Gecko) Version/1.5 Chrome/28.0.1500.94 Mobile Safari/537.3
  2. Choose a string that will be unique for the device you are trying to hack adjust,
    1. In my case, I targeted SGH-M919
  3. Target your selector by preceding the tag, class, etc. with the following data-useragent attribute selector like so:
html[data-useragent*='SGH-M919'] div.classIWantToChange { }

Caveats!

Be careful of the following:

  • When choosing a string from the user agent to target, be careful not to select something that might target other devices and browsers (for example, KHTML also appears on my Chrome browser on Windows, and I don’t need to adjust it.
  • Be sure to test on as many devices and browsers as you can (within some reason–are you getting paid for the testing? is the remuneration commensurate with the migraine inducing testing and fixing?
  • Are you ready for all the new browsers to be? How about new devices?