I run into problems when using the gem because the cookie name (which is the created_at timestamp of the announcement). I've introduced a cookie_identifier attribute which does the trick.
Introducing cookie_identifier attribute on announcement model.
Fixes issue with cookie names.
Hi @kitto , what problem did you run into?
My browser (tried on latest Chrome and Safari under OSX) just didn't set the cookie. I guess because the string representation of the created_at attribute doesn't qualify as a valid cookie identifier (I'm using timezones, based in Europe,...).
@kitto, what was the string representation of the created_at attribute (the one that Chrome/Safari couldn't use)? Maybe we can reproduce it locally.
@kitto I'm going to close this, as it hasn't been updated in a while. Let us know if you can provide an example string representation that reproduces the bug and I'll reopen. Thanks.