When testing the code for an upcoming release of the Search plugin, I upgraded from 1.0.1 to 1.0.2 on my local workstation and immediately noticed some spurious characters between the last two words of all the titles in the search results. (See attached screenshot.) I assume those spurious characters are associated with the added by Typogrify’s widont feature.
So it seems that the json.dumps() method introduced via cc48d48 in #23 was sadly not without its side effects after all. That being the case, I intend to revert that change in the upcoming release and, for the moment, go back to the original fix provided in #15.
@maphew / @s3lph / @lioman: If any of you would like to look at how the json.dumps() method could be re-deployed in this plugin in a way that does not produce these spurious characters, that assistance would be most welcome and appreciated.
When testing the code for an upcoming release of the Search plugin, I upgraded from 1.0.1 to 1.0.2 on my local workstation and immediately noticed some spurious characters between the last two words of all the titles in the search results. (See attached screenshot.) I assume those spurious characters are associated with the
added by Typogrify’swidontfeature.So it seems that the
json.dumps()method introduced via cc48d48 in #23 was sadly not without its side effects after all. That being the case, I intend to revert that change in the upcoming release and, for the moment, go back to the original fix provided in #15.@maphew / @s3lph / @lioman: If any of you would like to look at how the
json.dumps()method could be re-deployed in this plugin in a way that does not produce these spurious characters, that assistance would be most welcome and appreciated.