extracting data from url
| Project: | Facelift Image Replacement Integration |
| Version: | 5.x-1.0 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Great module! I can get the standalone version of facelift working on my server, but the Drupal plugin doesn't seem to correctly extract the data for the style from the serialized url. In IE6 I end up with a broken image where the replaced element should be, and in Firefox it renders the alt text (in Times New Roman).
An example of the URL flir is generating:
/flir/generate/Flir/25/964/{"mode"%3A""%2C"resizeBox"%3A"true"%2C"useBackgroundMethod"%3A"false"%2C"inheritStyle"%3A"true"%2C"cssSize"%3A"19"%2C"cssColor"%3A"rgb(73%2C 73%2C 73)"%2C"cssFont"%3A"puritan_regular"%2C"cssAlign"%3A"start"%2C"realFontHeight"%3A"false"%2C"dpi"%3A"96"}
Which I'm guessing is supposed to be like the following but the : and , symbols get encoded:
/flir/generate/Flir/25/964/{"mode":"","resizeBox":"true","useBackgroundMethod":"false","inheritStyle":"true","cssSize":"19","cssColor":"rgb(73, 73, 73)","cssFont":"puritan_regular","cssAlign":"start","realFontHeight":"false","dpi":"96"}
I did have _some_ luck by copying the url into a text editor and replacing the : with = but all this did was make the images render with the default font. So the image replacement worked, but the style information serialized in the url obviously wasn't parsed.
I'd much prefer an image instead of flash replacement so I'm keen to get this working -- I'm willing to help with the coding/debugging if you're interested. As I mentioned above, the standalone version works fine on my server so it's obviously something minor, unless the standalone version is a lot different to the version included in the Drupal plugin :)
#1
ummm.... I've had no problems using this tool in 5 or 6 branches and haven't gotten any issue reports like this before so I'm not sure. Are you using a theme that doesn't run the js correctly maybe?
In the future the way it transforms the text to an image will change to a more compliant way of doing business (so to speak). There's a solution provided in another post that should alleviate most issues of this ilk. I'll mark this as postponed because I'm pretty sure the new way of rendering will handle this.
#2
No worries :)
I tried it on a default install with the default theme so I don't think the theme was messing with it. Tried it with and without clean URLs also. Hopefully the new techniques you've mentioned will indeed solve the issue.
#3
this stuff should be resolved now with the new 1.2 version. Let me know if not.
--project followup subject--
Automatically closed -- issue fixed for two weeks with no activity.
#4
Automatically closed -- issue fixed for two weeks with no activity.