46 replies to this topic

[WillyC]

with .htaccess try.to this add will.it disabale mod_security:

<IfModule mod_security.c>
SecFilterEngine Off
SecFilterScanPOST Off
</IfModule>

[AnotherAndrew]

Thanks WillyC, but that didn't work. Is there disadvantage of leaving that in place?

Also, I am on a shared host. So maybe that is why your code won't help.

BTW, your avatar gives me the creeps!

[ryan]

Assuming this is a mod_security thing, which it sounds like, I would ask the hosting company how to disable it. If they can't or won't, that web host probably doesn't meet the minimum requirements to run anything but a very basic CMS. It would be a good reason to switch. That code that WillyC posted should disable mod security from the htaccess (even on a shared host, if supported), but I think the exact method of doing it depends somewhat on the apache/mod_security version. It's possible that such a method may work, but the one he posted might not be the right one in your case... still worth investigating further, just in case. But probably best to check with the web host to see what method they recommend.

[diogo]

BTW, your avatar gives me the creeps!

says the floating head

[AnotherAndrew]

Thanks Ryan, I asked my host and they said they wouldn't allow it since I am on a shared host. Is this something that is pretty common to disable on other shared hosts? Just wondering if I should change hosts. Can anyone recommend a decent U.S. host? It seems everyone I try, there is a problem!

EDIT my host did resolve this by whitelisting just one of the rules for mod_security.

[ryan]

That's great! Glad they got it resolved. It sounds like the company is a good one if they found a solution for you on this. But to answer your question about a good US host, stick with a VPS (or something like it) so that you don't have to play the shared host games like this. You want to have control over your hosting environment. I've found ProcessWire runs great on every shared host I've tried it with. But stepping outside just ProcessWire for the moment, if you need to handle real traffic or run something beyond static HTML files, shared hosts are painful. They work well enough to make you think it's a good deal, but if web development is your job, then using a shared host is like being a chef limited to a pocket knife. Everything takes longer and you regularly have to improvise. The only shared host I was ever really happy with was Pair Networks (http://pair.com), but that was years ago and I have no idea what they are like now. They don't do shared hosting, but ServInt (http://servint.net) is the only hosting company I would trust my clients to. And obviously, that's who hosts processwire.com too. If you can step up from shared hosting to go the VPS (or more) route, they are fantastic and their servers are well optimized for ProcessWire. There are other good ones too. I know Pete has also mentioned he's had a good experience with a company called StormOnDemand. I've also heard good things about KnownHost and PowerVPS in the past. If you need something dirt cheap, don't need to handle real traffic and don't mind all the throttling and crap, BlueHost and HostGator are not bad for the price (both use cPanel, which I like), but use them for stuff you don't care about too much.

[AnotherAndrew]

Thanks Ryan, that is just the advice I need for hosting. I've always used shared hosting since it is cheap, and I've never had a site that gets tons of hits to warrant anything bigger. It sounds like you can have a VPS that could host several of these small fry sites. I might consider moving to one...maybe KnownHost.