Kira Schroder

Glad to hear it! No problem!

Thanks muchly for your report, and confirming that it fixed the bug for you.

If you run into further issues, please let me know!

A fix should be in core now. Would you mind updating to see if it resolves the issue?

Looks like, indeed, there was a bug with how WordPress was detecting whether Imagick was supported.

Imagick 2.2.0 or greater is necessary for it to work properly with our implementation.

This patch should solve the fatal error for you, and make WordPress default to GD.

I’ll ping back to the thread again when it’s in core.

Sorry, I see you’re running 3.5-1-22879 per your post’s info.
As of that revision, the patch above certainly should have fixed this.

Checking into how it might not be defaulting to GD like it should be.
What version of Imagick does phpinfo() say you are running?

What version are you running?

That happens because the version of the Imagick module isn’t new enough, but the fatal error it causes should have been fixed as of two weeks ago: [22581].

If you haven’t updated recently, please try updating to RC1, or the most recent nightly/trunk, and let me know if you’re still seeing the issue.

Looks like the new version uses namespaces, and hence requires PHP 5.3.

Try changing to PHP 5.3 in the DreamHost panel, by going to “Manage Domains” and clicking “Edit” next to your domain, then scroll down to the PHP section, change PHP to PHP 5.3 FastCGI or CGI, then “change settings.”

Within about 5-10 minutes, your domain should be using PHP 5.3. I haven’t personally used the Azure Storage plugin, but this will likely fix the syntax error.

It sounds like you’re probably looking at a CSS/HTML issue — perhaps in the way that your theme handles forms. It’s pretty normal for starting a form tag to add a bit of space, if it’s not corrected for. Given the actual site to take a look at, we can probably divine what’s up.

That said, what Modern Tribe said is spot on — while the DH form CGI will do the trick, you might want to look into Jetpack’s built in forms (free), Contact Form 7 (free), or Gravity Forms (paid), since it’ll probably give you and your users a bit better experience, and will certainly be simpler to customize.

Double-checked into this, and it does look like you should have received a detailed list of our findings, and ways that you can clean things up.

If you do have any more questions, I’d definitely suggest replying directly to the email from support so that our Abuse/Security team can help you further.

No problem — glad to hear it!

I’d definitely suggest contacting the theme’s author for support, and ask them how they suggest you upgrade to the “Pro” version that you’ve purchased.

Whether or not it works will be completely dependent on the theme that you’re using.

First, generally speaking, standard practice would be to download the appropriate files via FTP, edit them with whatever editor you prefer, then upload them again.

That’s what the FTP client will do, even if it “pretends” that it’s editing the file directly on the server.

As far as not seeing the file, even when enabling viewing of hidden files, that’s a bit confusing — I did some tests here, and the functionality certainly seems to work.

That said, are you sure there is already a .htaccess file there to edit?

WordPress does not create one in its home until pretty permalinks are enabled, and there definitely wouldn’t be one in the root of your domain unless you created one there manually.

If you want to edit your .htaccess, I’d suggest using a true FTP client that supports viewing/changing hidden files (any file that starts with a ‘.’ counts as “hidden” in *nix).

In CyberDuck, you can do it with View->Show Hidden Files
(you can find CyberDuck here: https://cyberduck.ch/)

Note that if you remove the parking altogether, you’ll need to click “add” to make the domain Fully Hosted, rather than clicking “edit”.

If you run into trouble with this, I highly suggest contacting DreamHost support, here, since this is a hosting issue rather than a WordPress-centric one. =)
https://panel.dreamhost.com/index.cgi?tree=support.msg&

It looks like your domain is parked.

I’m sure DreamHost support can help you with this as well, but essentially a parked domain does not point to your web directory, which is why you’d get a 404.

It needs to be “Fully Hosted” to show your site properly.

To fix this, go to “Manage Domains” in the panel, and click “edit” next to your domain.

Then, fill out the Fully Hosted section, and click “Fully Host this Domain”

Hopefully this helps!

DreamHost’s standard shared hosting does come with a domain name. If you selected one you didn’t mean to for your free one, though — within 5 days you might be able to have the “other” one cancelled. After that, ICANN makes it hard to go back.

Hopefully this helps, and super glad to hear you have things solved!