Alvaro Degives-Mas

Not sure if this is it, but… If you have a caching plugin, check (double check) that all requests from mobile clients supported (identified) by WP Mobile Edition are NOT cached. Else, one mobile client may “set” the viewing mode in the cache, which the next mobile client will be shown too.

I.e., clear the cache of your site – again, if you have one. Then, see above: exclude mobile UAs from triggering the cache.

Hope that’s it…

I have 48 running side by side… On a live site. Should I hire a shrink?

I think he really meant to type:

“This is a killer plugin! Makes websites run like greased s…!”

(This topic actually piqued my curiosity enough to install it on two WP sites I run and… holy cow. It really is a great plugin.)

There are two types of watermarks: ones that are “burned in” on the picture (permanently) and those that are overlaid on the picture in a slideshow.

The permanent ones work always, i.e. also outside a slideshow; no further tweaks necessary.

The “during showtime” version only works for images when shown in a slideshow.

I have two non-profit orgs with their sites hosted on a BH shared plan and I’m not looking back. But I also think results vary according to needs:

• There’s the content enforcement issue – already mentioned.
• If the big chunk of your audience is in the left half of the US, their location helps in low response time.
• If your traffic is moderate, you’ll be fine with their traffic limits. If you’re picking up consistently above that, start looking for an upgrade.
• The more you do on your end to make the site efficient (good caching settings, streamlined consolidated CSS and JS, etc.) the less trouble you’ll have.
• You can even use a CDN to offload, to postpone the upgrade jump.
• Another thing BH has a zero tolerance policy for is filesharing. Just don’t do it.
• I like to speak to real human beings, preferably sharing the same language as I do, as that makes interaction all the more efficient; BH does that, and I’ve never ran into an impolite or arrogant engineer to help me out.
• Price-wise I think they’re in the very decent category.
• Most important of all though: it really depends on what you want. In “my” two cases they’re more a serious, business-like CMS than a flashy hot stuff blog; streamlining for performance is much easier to do in my cases.
• They do offer a lot of storage space, but if your game is a massive repository of video files with lots of simultaneous streams, look for a CDN or look simply elsewhere.
• If you’re into mass-mailing your thousands of subscribers, look elsewhere. They’re allergic to mass email sent from their own servers. You have to have a stellar track record with them – and a demonstrably legit case – to get a more flexible email sending regime. Oddly enough I see this as a plus.
• The more you do on your end to keep spammers and bots out and tighten traffic (good caching, again…) the more they’ll accommodate you, too. But: content restrictions and filesharing and generally “risque” applications remain cut off.

As I said: I’m a happy customer of BH, but I think my sites fit very well in their “target” market.

Oh, about one-click installations: yeah, they have it. I’ve tried it and it works. The thing is, with their server permission settings there’s never been a plugin or theme or upgrade that went wrong. It’s the one hosting provider for WP where I least have trouble with permissions and still have a safe default setup (i.e. with 755/644 perms) while updates and new themes / plugins / installs work like a charm.

I recommend them as a solid option – but then again, several of them on the WP hosting page that are up there, as far as I’m concerned, for the lower-to-midrange traffic WP sites.

That implies a separate conversion of text to image… There are some PHP scripts out there (i.e. outside WP) that do that; title-to-image conversion is not so straightforward as it sounds though. Can’t help you with that, sorry.

Sorry about your troubles Martyn, but I think you’re looking for support with the dbug plugin – this topic here is about WP Super Cache, a different plugin…

One simple way to deactivate the dbug plugin (assuming it’s the one giving you trouble, and not something else brought to the light by dbug) is to log into your server using FTP and delete the entire dbug plugin folder, i.e. this one:

/home/survivor/public_html/wp-content/plugins/dbug

Once your site is back up, however, you have to look at whether your problem is caused by dbug or something else. Ask for support for the dbug plugin, in that case, in a separate topic. Good luck!