Assorted changes: no more acts_as_solr, webadmin replaced with Capistrano, updated libraries, robot exceptions, better tagcloud, etc

[Igal Koshevoy]

I've deployed a bunch of changes to Calagator. After a week or so of
making sure they're fine, I'll publish a new stable release.

Here's what's new:
* Removed "acts_as_solr" search engine, that library been troublesome
and abandoned for years, please use "sunspot" instead.
* Changed Gemfile to only enable debugger and code coverage gems if
you ask for them, see the Gemfile for details.
* Fixed RCov code coverage tasks, they seem to have broken during an
earlier RSpec upgrade.
* Fixed exceptions caused by robots stumbling around the site.
* Improved tagcloud to show only the top 100 tags and format them nicer.
* Upgraded tons of libraries.
* Wrote more specs.
* Fixed production serving of static theme assets under newer Apache versions.
* Removed webadmin and marshal, which have been broken since the Rails
3 upgrade, and replaced them with Capistrano and Rake tasks.

-igal

[Igal Koshevoy]

And also added travis-ci support to ensure that we leave the branches
in a good state and that the code works with Ruby 1.8.7 and 1.9.3:
http://travis-ci.org/#!/calagator/calagator

-igal

[Reid Beels]

Yay! Thanks for these changes.

I just got a report that http://calagator.org/events/1250462567 isn't showing up on the front page or events list. It's in the change feed and search results, but not the indexes. I added another new event and found the same thing to be true.

Could any of these changes affected caching?

— Reid

--

You received this message because you are subscribed to the Google Groups "Calagator Development" group.

To post to this group, send email to calagator-...@googlegroups.com.

To unsubscribe from this group, send email to calagator-develo...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/calagator-development?hl=en.

[Igal Koshevoy]

Weird, thanks for the details. Caching shouldn't have been affected by
these changes, but sure sounds like it was. I'm debugging to figure
out what happened and will update once I know.

-igal

[Igal Koshevoy]

Phew, I'm very glad someone reported this caching bug. Thanks!

I deployed a fix for this soon after my last email and confirmed that
newly-created events show up.

The underlying problem is that Rails changed the behavior of the
Observer's "observe" call in incompatible ways. As of Rails 3.0.14, it
must be called once for all models, with each call replacing the
previous values. In the earlier version that I tested my changes
against supported calling it multiple times to add values and I saw
documentation claiming that this was the better way to use it. Lame.

-igal