[wp-meta] [Making WordPress.org] #140: Plugin changelog truncation can break WordPress.org site layout

Making WordPress.org noreply at wordpress.org
Fri Aug 30 17:17:03 UTC 2013


#140: Plugin changelog truncation can break WordPress.org site layout
-------------------------+-------------------------------
Reporter:  JohnLamansky  |      Owner:
    Type:  defect        |     Status:  new
Priority:  normal        |  Component:  api.wordpress.org
Keywords:                |
-------------------------+-------------------------------
 Migrating from #wp21550:
 > WordPress.org appears to truncate plugin changelogs after a certain
 number of characters. However, if the truncation occurs in an inconvenient
 place -- such as the middle of an HTML tag -- it can cause browser
 rendering issues in other parts of the page.
 >
 > For example, on the [http://wordpress.org/extend/plugins/seo-
 ultimate/changelog/ changelog page] for my plugin SEO Ultimate, the plugin
 page sidebar is currently showing up below the changelog
 ([http://img405.imageshack.us/img405/7557/brokenchangelogscreen.png
 screenshot]). This is because the changelog is being truncated in the
 middle of an <li> tag, apparently leading my browser (Chrome) to fail to
 recognize a </div> closing tag:
 >
 > {{{
 > <l</div><!-- block-content--></div>
 > }}}
 >
 > I would suggest that the easiest and perhaps best solution would be
 simply to stop truncating plugin changelogs. Layout breakage possibilities
 aside, I would prefer it if my plugin's changelog were not cut off after a
 certain point.

 Otto noted that this is something that could be fixed in the API by
 detecting and not sending back bad data.

--
Ticket URL: <http://meta.trac.wordpress.org/ticket/140>
Making WordPress.org <http://meta.trac.wordpress.org/>
WordPress blogging software


More information about the wp-meta mailing list