Yeah, I can see the homepage. But the images are not showing up; images from the style sheet and uploaded via the admin area.
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
November 19, 2009 2:27pm
Subscribe [4]#16 / Dec 01, 2009 11:37am
Yeah, I can see the homepage. But the images are not showing up; images from the style sheet and uploaded via the admin area.
#17 / Dec 01, 2009 11:41am
OK, can you show me one of your style sheet images links?
#18 / Dec 01, 2009 11:48am
Sure thing, here is what I’ve got:
#header {
background: #fff url(/images/background-header.jpg) no-repeat;
}#19 / Dec 01, 2009 11:59am
Sure thing, here is what I’ve got:
#header { background: #fff url(/images/background-header.jpg) no-repeat; }
Hmm, there should be quotes around the url; also, I always use an absolute path. Try changing your background rule to this
background: #fff url('{site_url}images/background-header.jpg') no-repeat;to see if that has any effect.
#20 / Dec 01, 2009 12:01pm
One other thought - wondering if maybe the original developer saved templates as files?
#21 / Dec 01, 2009 12:05pm
You modification to the style sheet worked, good idea. 😊 But my only concern is on the remote site the “{site_url}” is not being used in the style sheet. Why should I need to change it now? (just curious)
I looked the through files/directories and didn’t see any files that jumped out at me as individual template files.
#22 / Dec 01, 2009 12:20pm
It may have something to do with the old site using an earlier version of EE. I just tired removing {site_url} from my CSS on a local server and sure enough, it broke, so I would suggest you update all of your CSS rules to include {site_map}.
Re: you other issue of not being able to get to About Us - can you show me the link to that page as it appears in your home page template?
#23 / Dec 01, 2009 12:25pm
Ok, that could make sense. Could we get a Moderator to clarify this by chance? (just to be sure)
For my navigation, I’m assuming I might need to add the same thing? Here’s what it looks like:
<ul id="nav">
<li id="home"><a href="/">Home</a></li>
<li id="about"><a href="/about/">Health</a></li>
etc….
</ul>#24 / Dec 01, 2009 12:25pm
Thanks for all you’re help on this by the way. Much appreciated.
#25 / Dec 01, 2009 12:34pm
Ok, that could make sense. Could we get a Moderator to clarify this by chance? (just to be sure)
For my navigation, I’m assuming I might need to add the same thing? Here’s what it looks like:
<ul id="nav"> <li id="home"><a href="/">Home</a></li> <li id="about"><a href="/about/">Health</a></li> etc…. </ul>
No wonder it does not work! Change it to this:
<ul id="nav">
<li id="home"><a href="/">Home</a></li>
<li id="about"><a href="http://{path=about}">Health</a></li>
etc….
</ul>#26 / Dec 01, 2009 12:36pm
Hmm.. this is strange as it works perfectly on the remote site. And the version of EE is the same on my local environment as the remote site. What you suggested makes total sense, but I am still wondering why/how it works on the remote site without “{path='about'}”
#27 / Dec 01, 2009 12:52pm
Ok - so I updated the link with the {path…} and that didn’t fix my problem in going to the specified page. The url is correct, but the page being displayed is a 404 page..
man… I am getting some funky results right off the bat. Not off to a good start. haha Something so simple as running locally should be a fairly easy task.
#28 / Dec 01, 2009 1:09pm
I can download the EE Core version and get the running locally with no problem at all.
#29 / Dec 01, 2009 1:16pm
..any chance some of these problems could be coming from my .htaccess file?
#30 / Dec 01, 2009 2:14pm
Absolutely - I assume you are talking about an .htaccess on your remote server? If, so make a copy and I will take a look. You may have redirects that explain why things work on the remote but not on your local