Please note that the forum isn't realy used anymore.

If you have questions, want support or just simply want to talk to us you can find us on slack.

 

Background images not displayed when turning debug to false

Using fork 3.6.5 Publishing a site In debug mode everything is ok. When I change debug background images don't show up. Changing back to debug mode everything is ok again. Background images are called in by css < background: url(..) >

Ps: when I copy the image url < in coda > there is a double . and a publichtml-folder in the www adress like this: http://www..www.broekmanfeijenadvocaten.nl/publichtml/frontend/themes/bootstrap/core/layout/img/headers/wortels.jpg

Does anybody have a tip? Thanx in advance

Site is < still in debug mode> www.broekmanfeijenadvocaten.nl

I think you must enter a relative path. If I look in the CSS which I use with Fork CMS I always use: background: url('../images/rest_of_the_image_path.png');.

Hopefully this helps.

Hello Jacob, I tried the relative path, but it's not working. What do you think of the remark of the double .. in the url of the image and the public_html folder in the url?

Can you disable the debug mode?

I don't know what you mean with the double dots in the URL? Do you mean what I use?

It looks ok when I am in Debug. < the relative path to place the image doesn't work>

I can disable debug in the config file <false>, then the background images are not displayed. If I check the url <copying the="" url=""> it looks like this: </copying></false>

http://www..broekmanfeijenadvocaten.nl/public_html/frontend/themes/bootstrap/core/layout/img/headers/wortels.jpg

Thats a strange url < www.. > never seen it before.

Hmm thats strange indeed. Can you paste the the contents of the custom.css into screen.css and remove the @import url("imports/customs.css");

I think I have tried that also, site is already online so I wil check this tonight ;-) Thanx for 'meekijken' GrG

Could the problem be caused by 'basedir'. While installing there was an issue with the basedir

No this is based on the browser. I get the same error about the basedir, for now it doesn't matter.

Usually I place all my CSS in screen.css and the images are stored in ../images (relative to the screen.css). If you handle this way of loading the images it wouldn't be a problem.

Don't use imports unless these are from external domains, like Google font. Fork CMS minifies the CSS and compresses the images while minifying. You can check: http://www.isowen.nl/ as an example.

ok, thanx, I will try this & let you know

Hoi Jacob, I am up and running. Removing the import was the solution. Thanx G

Try this one.... http://www.corelangs.com/css/text/image.html

Vayne

Comment

The forum is deprecated in favor of our Slack channel, which provides real-time support for your issues.

Join us on Slack here: https://fork-cms.herokuapp.com/