Post by Janet on Dec 11, 2008 7:47:44 GMT -5
I am having problems with my images showing. I'm pretty sure files aren't being found because the latest RB upgrade has moved all projects folder into one projects folder, adding an additional layer to relative paths. Before, I could back up one folder from the particular project to get into the public folder to get into the subfolders that contain images, text files, etc. The url would look something like
Url('../public/resources/GreenBurst.PNG')
Now, I think, the file path has to back out of two folders before it lands in the public folder to be able to move forward. I've been experimenting (unsuccessfully) with these approaches:
1. Find an html command that backs out of 2 folders to then move forward to the public folder
2. Use ResourcesRoot$ to begin the relative path
3. Redefine the Resources path in Preferences
What I can do is move the resources folder into the projects folder and change the relative path to
Url('/resources/GreenBurst.PNG')
so there's no backing out of the folder. I think, though, that there is a reason why resources are placed in a folder called public, so I'm not sure that's the best solution.
My questions then are --
Would there be any disadvantage in moving my resources folder inside the projects folder (the easy solution)?
If that's not the best solution, then, what changes would I make to either the url relative path or Preferences to find the public folder so that I can then direct to any folder within the public folder?
Thanks.
Url('../public/resources/GreenBurst.PNG')
Now, I think, the file path has to back out of two folders before it lands in the public folder to be able to move forward. I've been experimenting (unsuccessfully) with these approaches:
1. Find an html command that backs out of 2 folders to then move forward to the public folder
2. Use ResourcesRoot$ to begin the relative path
3. Redefine the Resources path in Preferences
What I can do is move the resources folder into the projects folder and change the relative path to
Url('/resources/GreenBurst.PNG')
so there's no backing out of the folder. I think, though, that there is a reason why resources are placed in a folder called public, so I'm not sure that's the best solution.
My questions then are --
Would there be any disadvantage in moving my resources folder inside the projects folder (the easy solution)?
If that's not the best solution, then, what changes would I make to either the url relative path or Preferences to find the public folder so that I can then direct to any folder within the public folder?
Thanks.
