Discussion in 'Website Design' started by Dan Allen, Jan 4, 2016.
I understand what you did with the background image and why, but don't we need to make a change to my cloned copy as well? I'm thinking that since we are updating Holly's site from the cloned copy that we don't want to overwrite the link from my copy back onto Holly's version.
The relative pathing solves that issue.
Okay, maybe not. And the thing is, I thought I totally understood this part.
Here is the image, right where it belongs on the clone of Holly's system on my server:
I even copied the url straight from Plesk to make sure I wasn't making a typo.
And this worked:
But if I try to put an 's' after http, the link breaks:
The relative path doesn't work for me either.
Obviously the link works on Holly's live site, but when I exported the live style and loaded it onto the clone, the link was broken again.
There must be something I'm not understanding about this. It seemed so easy when I looked at it earlier.
On Holly's server, every link has to be https://. On our servers, every link has to be http:// It is something that needs to be changed when the system is cloned from https: to non-https: I need to run https:// on solar-dev.work. I have learned how to do it, but have not done all the steps.
I am not sure of the status of the background imaage you are writing sbout. Apart from that file, there are two files that handle the https vs. http for the whole system. The two files are
I have been doing a global search/replace in those two files for changing http: to https: and visa versa when going between Holly's system and mine.
If you do the css with relative paths, then you don't have to worry about the https business, because it is taken care of automatically.
Relative paths for css works differently than other files. In css, the relative path always is from the css file. For php, the relative paths are from the program that is running. So, when /index.php includes a file from /down/the/directory/tree, the paths in the included file are going to run from the file that included it, the opposite of the way css works. I always put css and images together, so the url to an image from css will be ../images/file.png.
I think the css should refer to that background image by a relative path to avoid configuration problems. I don't know what directory stores the css made by the css engine in xf. I'd have to experiment or ask the folks at hq for a tip on that one.
One of the reasons I use the override.css file is to avoid the peculiarities of css paths in xf.
And the result is....
Yippee! Moving up the directory tree for the relative pathing worked!
And, better yet, I understand how this works now. So, I made this huge diagram from a screenshot of the Aptana set up so I won't forget. I don't know if all those arrows will help me, but this makes so much sense now that I don't think I'll forget anymore.
Thank you for going through how this works for me! This feels like a level up kind of moment. I thought I understood relative pathing, but I only had half the picture, which was that I need to point to where the file in question is hiding. The other half of the picture was that I need to start from where the program makes its home!
I updated the path for the logo to make it a relative path as well.
Separate names with a comma.