Closed (fixed)
Project:
Pirate
Version:
6.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Sep 2010 at 12:06 UTC
Updated:
14 Sep 2011 at 17:21 UTC
Jump to comment: Most recent file
I'm looking around our site, and I can only find one blog post that actually got converted, even though I checked the Input Formats, and everything is set to use the Pirate filter. (Drupal 6)
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | 916148-format-date-pirate-6.patch.txt | 579 bytes | sillygwailo |
| #7 | 916148-format-date-pirate.patch.txt | 571 bytes | sillygwailo |
Comments
Comment #1
lsommerer commentedI was having the same problem, but looking the module over a bit more, I think that it only effects individual nodes that have the input format set to whatever you decided to call the pirate filter. Not quite what we thought it would do. Oh well, still a neat idea.
Comment #2
doulos12 commentedWe have the input filter set to Pirate for both Filtered & Raw HTML.
Comment #3
doulos12 commentedIt's working now. Today. Site-wide. Um, that was yesterday. It shouldn't be working any more. Had to disable it, but it still hasn't changed back to normal. Is there a cache I can clear or something?
Comment #4
doulos12 commented/admin/settings/performance "Clear Caches" cleaned things up.
Is this module tapping into the server's clock instead of Drupal's?
Comment #5
sillygwailoIt's tapping into
date(). That it doesn't tap into Drupal's date specifically can be considered a bug. I'll look into replacingdate()withformat_date().Comment #6
sillygwailoSince the original issue was "works as designed", I'm going to rename this to the last comment's issue. I'll also make a note in the README.txt that clearing the cache on September 20th alleviates the pirate talk after the day that the module takes effect.
Comment #7
sillygwailoHere's a patch for 7.x-dev, which will get into the beta for that branch.
Comment #8
sillygwailoAnd here's a patch for 6.x-dev, which needs review.
Comment #9
sillygwailoI've committed this for 6.x. Re-open if still an issue.