Closed (cannot reproduce)
Project:
css3pie
Version:
7.x-2.0
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
3 Feb 2012 at 14:23 UTC
Updated:
29 Aug 2012 at 10:40 UTC
I've tried all the settings, re-read the README, checked the issue queue.
I'm using an omega sub-theme and I'm trying to get multiple backgrounds and transparent PNGs to work in IE 6,7,8. The head seems to have some code added as a result of enabling the module but nothing seems to be happening visually. I've double checked my selectors, cleared browser cache, flushed Drupal cache.
What gives?
Comments
Comment #1
iler commentedDo you get the css file created in ctools css cache? Path should be something like http://yoursite.com/sites/default/files/ctools/css/randomnumbersandlette.... If it's created what is there inside that file?
Comment #2
dddbbb commentedThere is indeed a CSS file that matches your description. Contents are as follows:
This looks OK to me but I'm not entirely sure what I should be expecting. Those are indeed the selectors that I specified in the GUI and the .htc file path looks good.
Still isn't working though. Will keep playing but if you have any bright ideas, please let me know.
Comment #3
iler commentedSo the module is working as supposed so your problem is actually with the PIE library itself not with this module. With these kind of problems the right place for support is http://css3pie.com/forum/.
Comment #4
dddbbb commentedAha, some progress...
I now have PNG alpha transparecny working in IE7 (using the #logo selector alone, other selectors we re removed for troubleshooting). This would suggest that there might be something dodgy about my sleectors - not sure what yet but will updte this thread with what I find.
One thing I noticed though: That ctools CSS file isn't updated when the settings are saved as the README suggests - I could only get it to update by clearing Drupal caches.
Comment #5
dddbbb commentedWhat am I talking about... IE7 supports PNG transparency :$
Retested in IE6 and I'm still getting the same issues. Will try the CSS3 Pie forum as you've suggested.
BTW - which particular cache do I need to refresh to get the ctools CSS file to update? Seems silly to clear ALL of the caches every time I want to check.
Comment #6
blackice2999 commentedComment #7
bcobin commentedI'm having the same issue - the module doesn't seem to do anything. In my case, I'm working in a development sandbox and instead of seeing
behavior: url(/sites/all/libraries/PIE/PIE.htc);in the generated file, I'm seeingbehavior: url(/[site]/);where [site] is the subdirectory of my MAMP Pro install where my site is living. I've tried changing it, but nothing seems to work.Any thoughts? Thanks much for any guidance!
Comment #8
iler commentedbcobin could you please start a new issue because your problem is not the same than the one that dixhuit had.
Comment #9
harri00413 commentedI have the same issue, also with Omega Subtheme. I think this is the right place to ask questions because css3pie works with just html, it inserts the wrapper but in Omega there is something with the order of events that I can't get my head around.
Must put site in production first, then I have some time to look if this is worth pursuing.
Help still appreciated though...
Comment #10
RAFA3L commentedI'm upgrading a site from 6 to 7 and the same problem with Css3pie, with Drupal 6 + Fusion 6 work perfect, but with Drupal 7 + Fusion 7 Doesn't
Comment #11
Mojomandd commentedI'm having a similar problem to the majority of users above. Although CSSpie does appear to be running in some shape or form I can't see anything happening when viewing the site in IE.
I've got the CSSpie module running with a single selector (.highlightbox) added via the module GUI. I've left the module set to use the .htc for the moment, although a quick experiment with using the .js file threw up an error:
Warning: Invalid argument supplied for foreach() in _css3pie_build_css3pie_css()
I can see the cache css in Ctools but there seems to be an issue with the path. This is what I've got:
I'm not sure what I've done (or not done) to get no path at all. Should I have set something in the module to point directly to the PIE file in sites/all/libraries/PIE/PIE.htc?
Thanks for any help you may be able to provide.
Comment #12
blackice2999 commentedHi,
You are right the path shows wrong. Did you use the libraries module ?
Comment #13
Mojomandd commentedThanks for getting back to me. At least I'm not going mad and that path is wrong...
The libraries module is installed and enabled. I didn't install it explicitly - it looks as though I've had it there for a while as I'm also using Views Slideshow which seems to need it.
Comment #14
Mojomandd commentedHi,
I was wondering whether anyone had any further feedback on my issue outlined above. I responded to #12 regarding the libraries module but wasn't sure whether I needed to include any further information.
I could really do with getting CSS3pie working this week. It must be something relatively simple...
Thanks
Dan
Comment #15
blackice2999 commentedHi,
i cant confirm any global problem here so you need to debug the code or use css3pie manually in your theme.
Comment #16
Mojomandd commentedNo worries. Thanks for getting back to me - I'll slot it in manually for the moment!
Comment #17
smfuture commentedHi all,
I thought I would share a potential fix for some of the problems like this one. I had just pushed my site up from localhost to live, and was getting the error " Invalid argument supplied for foreach()" and a few others, and a Ctools error. And the pie module was not creating any output.
Cause #1: Linux directory permissions were wrong. I had to CHOWN directories to include the apache user group and then CHMOD them accordingly.
Cause#2: the PIE directory in linux was lower case as pie, as it was pushed up from a WAMP server, and windows not being case sensitive.
Correcting both these resolved all errors and suddenly had output. Hope it helps.
Regards,
Matthew.
www.smfuture.com.au
Comment #17.0
smfuture commentedDodgy character stopping full text from displaying.