CMS Made Simple Forums

As always, I started programming by building the website on my local machine. Then, I transfer my design into CMSMS.

The ie png fix was working on my machine, I had the css code placed in the head tag versus in the linked stylesheet because I found this is the only way it would work. Then I placed the iepngfix.htc file in my css folder (which CMS doesn't have, but I did try creating one and placing it in that directory to no avail).

Here is the code in my head tag:

/* PNG IE FIX */
* { behavior: url(css/iepngfix.htc)}

I can't get the png fix to work in ie now that my files are in CMSMS. I have tried placing the css code in {literal} tags in my template and then the iepngfix.htc file in a css directory. I have also tried changing the url to :

url(css/uploads/iepngfix.htc)

and that doesn't work either.

Has anyone else used this fix successfully in CMSMS? If so, where did you place your file and your css code?

The png fix has worked perfectly on all sites that I didn't instally a cms for. Here is the link to the fix:
http://www.twinhelix.com/css/iepngfix/

Thanks

skim1114 wrote:

/* PNG IE FIX */
* { behavior: url(css/iepngfix.htc)}

Try with a absoute url: url(/path/cms/css/iepngfix.htc)

Alby

There's a definition for * in Layout stylesheet - maybe it's better to add it there (no separate style needed).

I've tried to use an absolute url. Doesn't work.

I have tried the style in a stylesheet and it doens't work either.

Anything else?

Thanks

What is the path to it?...

Here is what I did:

Placed the iepngfix.htc file in the uploads folder.
Added this code into the homepage template:

{literal}

/* PNG IE FIX */
* { behavior: url(http://www.sitename.com/uploads/iepngfix.htc)}

{/literal}

Then, on the other template, the one that is used on internal pages, I used this code:

{literal}

/* PNG IE FIX */
* { behavior: url(./uploads/iepngfix.htc)}

{/literal}

Not sure why I needed to change the url, but I did for the internal pages. I am using pretty urls...not sure if that makes any difference.

I did get it to work in IE5, finally, so I am a happy camper and I hope this helps out someone else in the same bind.

s.