I'm currently having some issues with media urls between dev and staging environment.
In the dev. env. the media urls are all correct ([devEnvSitename/media/...])
however, when browsing the staging environment (which works flawlessly apart from media) all of the images get 404ed since the url to them is still [devEnvSitename/media/...] and not [stageEnvSitename/media/...]
From what I've been able to find, there seems to be a few ways around this, however they are not what i'd call elegant. One of them required you to run a SQL-update on the media paths etc.
How would one go about updating the media URLs so that they point to the actual file (manually going to [stageEnvSitename/media/...] displays the image, so the images actually exist, the path is just not configured correctly).
Changing media URLS between dev and staging
Hi.
I'm currently having some issues with media urls between dev and staging environment.
In the dev. env. the media urls are all correct ([devEnvSitename/media/...]) however, when browsing the staging environment (which works flawlessly apart from media) all of the images get 404ed since the url to them is still [devEnvSitename/media/...] and not [stageEnvSitename/media/...]
From what I've been able to find, there seems to be a few ways around this, however they are not what i'd call elegant. One of them required you to run a SQL-update on the media paths etc.
How would one go about updating the media URLs so that they point to the actual file (manually going to [stageEnvSitename/media/...] displays the image, so the images actually exist, the path is just not configured correctly).
Use relative pathing so you start the path from /media
Most media items are just being drag&dropped into imgs, RTEs etc by the content creators, how would i create relative pathing from this?
is working on a reply...