Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By kvarnelis on
somewhere in the late beta cycle, something went awry with the parsing of ampersands in blocks rendered with input content of full html.
take this bit of code:
<param name="flashvars" value="stage_height=150&map_title=&xml_file=locations.xml&map_style=false&map_color=000000&date_format=mdy&node_limit=5&zoom=auto&grid_line_opacity=10&show_routes=true&route_thickness=1&route_curve_factor=false&tooltip_bg_color=aaaaaa&tooltip_shadow_opacity=5&mod=1.8&past_point_style=circle&future_point_style=diamond&future_route_opacity=35&past_route_opacity=55" />
it is broken in 4.7 with all of the ampersands converted into & amps. yes, the & amp is very nice and all, but it breaks the value for the flash animation effectively.
it did work during the early beta cycle. can't really pin down where it died though.
any thoughts before i file a bug report?
it seems like this is related to http://drupal.org/node/68477 and http://drupal.org/node/63895
Comments
Issue
Issue created
http://drupal.org/node/68484
Looks like you'll need to
Looks like you'll need to find a way around it. "by design" for standards-compliancy reasons.
Looking at your sample,
Looking at your sample, you'll need to separate the vars as separate parameters. You are using the url format. Both forms are described here:
http://probertson.com/articles/2005/02/14/flash-databases-urlvars-flashv...
that page is really
that page is really confusing.
i wish this hadn't been done to drupal. my page validated without any problems prior to this.
oh well. anyway, i guess all will be fine, but this simply does not work. what am i doing wrong?
yes, it's frustrating. but
yes, it's frustrating. but we do need to output text to the browser in a standard way. unfortunately I've used up all my flash param knowledge. You might need to go to a specialist forum and find out the situation there.