Hi

Yesterday I tried to change all my blogs to ../../header-images.

On 3 of my hosts, 15 blogs, all went well.

On WebHostingPad, when I tried to update the theme header option and save it kept switching to the live blog and telling me 'page not found'. I tried ../wp-content/header-images' but when I saved it froze. At the time I didn't connect it to the change I was making. WebHosting Pad suspended my account for overuse of CPU.

Today I got it re-instated and tried updating another website and the same thing happened.

So there is an environmental issue at this one host. You need to work with the host to find out why you can't use the ../../ in a file name - my 'off the cuff guess' it that it is deamed a security risk and being blocked. you will need to ask them about this and see if they can provide a work around.

UPDATE:
I've been playing with this on another host and hit the same issue. Talking with the host's support, it si a 'MOD SECURITY ISSUE' and I'm escallating it to their second level to see if there is a solution. I will keep you informed, but nothing will probably happen until next week.

I am waiting for an answer from support but I am not hopeful.

Can you think of any way round it?

it's is probably going to take a change to the theme code to allow a full url to the image folder maybe a check box that would indicate that you are using the direct path instead of a path relative to the theme folder.

for the time being, you can always keep the header images in the atahualpa/images/header' folder.

(interested in financing the time to make the change?)

I didn't expect much help from them - they are the worst Host I have ever had.

Here is what they replied:

"Some of the features disabled which is for security. You should have to follow that and we can't change server settings. You can purchase VPS plan if you want and you can configure the server as you wish."

I entered something it didn't like in the header directory area and something manage to show my total disk space as being completely used, even though it's supposed to be unlimited.

Next time I tried to access my site it froze and they suspended my account for high CPU usage.

How's that for customer service, to say nothing of English grammar.

One to avoid in the future I think.

I'm going to look into changing the option or adding a option to base the first part of the file path as the blog folder and not the theme folder.

That would be great.