The call to the print stylesheet is not correct and generates a 404 in the logs
<style type="text/css" media="print">@import "/modules/sifr/sifr/sifr-print.css";</style>
It should be
<style type="text/css" media="print">@import "/modules/sifr/sifr/sIFR-print.css";</style>
| Comment | File | Size | Author |
|---|---|---|---|
| #12 | sifr_2.patch | 807 bytes | ac |
| sifr_1.patch | 842 bytes | ac |
Comments
Comment #1
canadrian commentedI was experiencing this as well. I did a find/replace on all the sifr module files to replace sifr-print.css with sIFR-print.css, and sifr-screen.css with sIFR-screen.css. However, the module still appears to do nothing at all. None of the text is replaced, and my watchdog is still kicking up the error:
This module would be fantastic if I could get it to work. :) Any ideas?
Comment #2
acUse the patch I provided
Comment #3
canadrian commentedLOL I haven't the foggiest idea how to apply a patch file. :)
Comment #4
canadrian commentedOk, I found how to apply patch files in the Drupal handbook. I downloaded a nice, fresh, steaming copy of this module, and applied the patch with the command-line. I uploaded it to the module directory (I'm using sites/default/modules/sifr), and I refreshed the "Add a new sIFR rule" page. Still no dice - all I get is plain text, and the watchdog is still recording the error I posted above. Hmm....
Comment #5
acYou did also download the external sIFR library and put that in your modules/sifr directory right? sIFR Module relies on the functionality provided by the sIFR JavaScript/Flash library (downloaded separately). http://www.mikeindustries.com/blog/files/sifr/2.0/sIFR2.0.2.zip
Comment #6
canadrian commentedYes, I did realize I had to download that package, no thanks to the readm--- oh wait, there was no readme. But I did figure it out when the modules page kicked up an error telling me to install it. Anyhoo, the contents of the sifr package (minus the uncompressed source files) are in sites/defailt/modules/sifr/sifr
Comment #7
acHmm, not sure what the issue is. I would suggest either creating a new ticket or a forum post. Might even want to jump on #drupal-support. Due to the name of this issue I don't think you will get anyone else helping here.
Comment #8
jjeff commentedThis has been fixed in both DRUPAL-5 and DRUPAL-4-7 branches.
Comment #9
(not verified) commentedComment #10
sunhmmm... not really. DRUPAL-4-7 says:
Comment #11
sunComitted to 5.x-dev and 4.7.x-dev.
Comment #12
acThis is still active in 5.x-dev. Please commit. The naming of the files by Mike Industries is very confusing with the uneeded capitals.
Comment #13
sunAwkward. Thanks, ac!
Comment #14
(not verified) commented