Yeah, I was working on that yesterday. We are just letting the old, wrong images naturally flush from the cache. Look for them to update on Monday.
All new entries will be getting c9 smilies from now on. Old ones will gradually change to the correct images as they drop out of the cache. They have a really long cache time, so it could be a few weeks.
Ok, wait, how does that work, exactly?
Did you replace the images on the server? Wouldn't it have been easier to change the URLs in the reference file?
@Dodo: Yes, we replaced them on the server ... the way the code works in that we convert your text smiley into a <img> tag pointing at that location... we keep that converted html in the DB and only regenerate if you edit. So, changing the URL in our code would have fixed all new smileys (and it did), but changing the source images means that any old reference to the smiley in a comment or perhaps copied from within a comment will also be updated.
@Duncanma:To solve this kind of re-generation problems in the future (not just related to smileys, but also other situations where the HTML might need to be re-generated), you could make your code lazy: When a page wants to render a post, it gets the original text and the generated HTML from the database. If the HTML is empty, re-generate it and update the database record. When some new feature (or bug fix) requires the HTML of a lot of posts to be re-generated, you just "UPDATE Posts SET Html = NULL" and all the posts will be lazily re-populated (when they are requested).
@TommyCarlier: Yeah, we did think of that, but we decided that we'd build that in when we had a major reason to use it (like an update to the anti-xss code we run or something more serious like that) instead of building it in ahead of time
Just to wrap this up, the images are now dropping out of the cache and being replaced with the c9 versions.
In a few days, both of these lines will look the same.
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.