HOME ➔ SUPPORT ➔ Community ➔ General CourseLab issues ... CSS style problem
CSS style problem
  View type:
Hi,

I'm reveling against the fact that CourseLab always tends to duplicate images, although you are using the same one throughout your slides. LOL, I thought I'll be smart and place all the repetitive images inside the Clipart folder but NO! CourseLab still duplicated the file. Why?! It could easily reference the Clipart folder upon publishing!.

Anyways, I've created a css file (global.css) and placed it, let's say, inside folder 1/images (next to default course.css). I have linked this file inside start.html

One of the styles I've created is a table background image, always using absolute paths towards the image location.

I have created a table, and called this style by using the traditional method "class=table_background".

This doesn't work. Can somebody who has gone through this before, point me towards the right direction.

Thanks

Sebastian.
 
The duplication at creation is a quirk for sure, I must look and see if the clean up (remove unused) routine changes that in any way.
As for the CSS, [:D]I've got a very smooth 3 column fluid CSS layout on one of my memory sticks but this page isn't using it why?? [:mad:].. this page isn't referenced to it which is dumbly obvious and I suspect what you have run up against.
I would think that the CSS file you have defined isn't being used because the pages aren't referencing it either. I suspect that this is another of those default behavior things that Courselab writes and refreshes the html files you are changing at a few points, ?at saving and ?on publication.

The easiest work around has to be to work with this so I'd add the classes or pseudo classes into the css definitions used are in the folder 1/images/ as course.css. These I'd reference normally in the page html content. This should mean you don't have to modify anything else.

It might be worth flagging this as a future change to the software but as most users are probably not going to understand CSS and it is easy to break pages I don't see it's going to earn a high priority.
Extending the functionality of the table device would be easier and suit the majority of users.
 
 
BTW You'd want to do this after the files have been 'fixed' which would be post publication in whatever form you've opted for.

I fixed the same kind of issue by defining the table without CSS directly into the html view of the text field. The file size overhead for one or two occurances in a module is quite small.
Subject:
Message options
No additional options