… sense to unify.
…ded any of the right paths that would actually make this work (I had been saving the wrong files -- the ones in my test directory). So here they are.
… application (this is applicable if you're running from a gem). To run the Refinery tests use the new command rake test:refinery which runs all unit, functional, integration and performance tests inside Refinery core without having to copy them to the current directory. This is also compatible with having your own tests in your own test directory so you could run rake test && rake test:refinery to have full coverage. rake test:refinery does respond whether you're running from gem or not, however if you're not running a gem then rake test achieves the same goal.
…ght now it is more trouble keeping up than it is worth. Moved a lot of config that is troublesome into refinery core so that we don't have to manage updates. config/application.rb now uses a simpler format (which no doubt will change with Rails3). Added deprecation warnings for constants that have been replaced - REFINERY_ROOT is now Refinery.root and USE_S3_BACKEND is now Refinery.s3_backend
…s? is false.
…the dialog is opened. Fixes (mostly) issue 44 (http://github.com/resolve/refinerycms/issues/#issue/44)
…e or any of its decendants
…e and changing the theme will switch to a new fragment cache key for the site menu because the theme name is now appended to the fragment cache key. (thanks stevenheidel for the tip). Also cleaned up whitespace (for some reason there was diff cruft)
…e the requirement for PagePart to use has_friendly_id as it wasn't really needed.
…d as a gem vs as a clone. This solves some problems that people were having with friendly_id (among other plugins installed via gems) being included by plugins that complained before it was possible to run rake gems:install to fix it.
…he developer specifying the theme name in Refinery Settings (We've had a lot of requests to get rid of the UI for this which we do tend to agree with as clients don't really need it). Themes are now hot-swappable EXCEPT for any controllers you have inside there won't be reloaded which may give you some grief unless you restart your webserver after swapping the active theme. This was a necessary caveat unless anyone can figure out how to swap out controllers at runtime?
… update to version 1.3.6 of rubygems by typing: gem update --system
… work cross-platform now so we don't have to exclude Windows (thanks to sdsykes)