move avatars path to external domain
 

Hi,

I'm having an issue moving avatars to an external domain www.domain.com where my vb board is on different domain www.myforum.com.

when I go to Admincp / Avatars / User Picture Storage Type

and change the file path like this:

Avatar File PathThis file path should be readable AND writeable by your web server (usually chmod 0777) --> ./customavatars

URL to avatars (Relative to your forums home page) --> http://www.domain.com/customavatars and so on for the other folders' paths...

now the process goes fine and the url shows up correct, but the image doesn't show up. The only thing I see is the username of the users instead of their avatars.

when I look at that avatar external path for example http://www.domain.com/customavatars, I don't see any avatar saved. That means the avatars are not being saved on the external domain...

I guess there is something wrong here, but not sure what it is...

anyone knows what's going on!! how do I get around this issue??

How did you actually move the files to the other server? The system doesn't allow remote storage like that.

I have seen some vb forums doing that, too. saving avatars on cookie-less domain while their board on a cookie domain.

for example, the main domain is http://www.vbulletin4.com and cookieless subdomain for avatars, http://vb.vbulletin4.com

I think it is possible, but not sure how!!

BTW, I'm talking about custom avatars!!

The same domain is on the server, and they're serving it via the same webserver.

ok, the point is clear then!!

if it is possible, how do I do that?

--------------- Added 30 Jul 2014 at 06:02 ---------------

ok, I created to my main domain say www.myforum.com a subdomain avatar.myforum.com and after testing, still the avatars are not showing!!!

I'm sure there is either a glitch in the vb board or something else need to be configured!!

any idea?

--------------- Added 30 Jul 2014 at 10:49 ---------------

ok, I got it solved myself. I had to have the same root path as my main domain on the new subdomain, and now things work fine. :)