Wordpress, sub-domains and UNIX file permissions..

[camelCase]

I don't really know how sub-domains and UNIX file permissions work but I suspect that my problem has to do with those.

I have a web-host service subscription and, at the nagging of my girlfriend, decided to get wordpress installed. So, I placed the files under "/public_html/wordpress" and added a sub-domain (blog.mysite.com) to point to that folder.

It works fine when I go to "mysite.com/wordpress" but when I go to "blog.mysite.com", all images show up as blanks. So I did a few tests and tried to access the images using "mysite.com/wordpress/<path to image>" and "blog.mysite.com/<path to image>".

On the first address, I can access the image but on the second address, I get a 403 forbidden access error. The file permissions are all 644.

So..
Long story short, the sub-domain causes images to be inaccessible; how would I fix it?

 

[GetTriggerUnit-]

I would think that this is not a UNIX error but an Apache error. It seems like the configuration for the folder it wrong, this could help you http://www.cyberciti.biz/faq/apache-403-forbidden-error-and-solution/ (the e) point)

 

[camelCase]

I have no idea how I would implement that fix.
I thought to blindly copy and paste the entire <Directory> tag into the .htaccess file at the public_html folder but it only caused every page to reach a 500 internal server error.

I thought to modify the "home/domain/www" part to the wordpress directory but it also caused everything else to reach the 500 error.

I obviously don't know how Apache works.

 

[GetTriggerUnit-]

I'm not 100% sure but you should try putting

Options +Indexes FollowSymLinks +ExecCGI
AllowOverride AuthConfig FileInfo
Order allow,deny
Allow from all

in the .htaccess file in the directory.

 

[camelCase]

Didn't work.
But at least the 500 internal server error got isolated to just that directory.

 

[camelCase]

Strange..
Now, even accessing the images via "mysite.com/wordpress" fails..

Buh, screw it; imma' use photobucket >.>

 

[GetTriggerUnit-]

Hum, you might want to ask there, it's like stackoverflow, but for servers. http://serverfault.com/

 

[camelCase]

oo..
Thanks for the tip!

Though, I just brought it up with tech-support for the web-host and they're still figuring it out.
If they take too long, I'll ask there.

 

[Ghan]

I usually avoid trying to host different sites under the same web root directory. That being said, it's probably not much of an option if you're using shared hosting because you only get one account, but if it's a small site, I'd be happy to host it for you. (Assuming that the Wordpress doesn't need to see the rest of the files and can really be on its own.)

 

[camelCase]

The problem was just resolved but thanks for that offer; that's really kind.
Apparently, it wasn't my fault!

I had hotlink protection turned on last time but decided it was too much of a hassle and disabled it.
So, my cpanel *said* it was off but, in fact, it was still on. So, when I modified my .htaccess file to disable hotlinking and saved it, it got over-written immediately every time.

After two tickets, they found the problem and fixed it for me; phew!