* `bcms module` generates a project using an isolated engine. * Added Aruba tests to ensure CLI tools works, including `bcms -v`, `bcms new` and `bcms module` * Clean up old templates that weren't needed for generating new modules. * Add an option for `bcms` to skip bundler (to speed up things) * Ensure cms:content_block generator works correctly in projects (add Aruba scenarios) * Fix bugs from earlier namespacing that prevented unnamespaced blocks from working.
Developers should be able to use migrations to move their bcms 3.3/earlier sites to v3.4. Add migrations for v3.4. * Correct database to add namespacing to models/types that have class names in the database. * Fixed issue where projects with no cms table namespacing couldn't create portlets. * Define migration for upgrading to v3.4.0 * Changed naming convention of migration upgrades since Rails 3.1.x automatically compresses files names like browsercms_3_4_0 into browsercms340 (uses camelize) when it copies. * Use cms:install:migrations instead of copying using a generator * Update tests for generators
* Use mysql2 v0.3.10 gem - Fixes issues with Lion/Ruby 1.9.3 bugs. * Setup the test database automatically each time `rake test` is run. * Fix issue with where temp files were written out as absolute paths. * Write todo plan for 3.4 release.
… from the project.
…te these as needed for projects.
…led via cucumber instead.
…sets can remain disabled.
Reworked the entire project so it works as an isolated mountable engine. Rather than using paths like cms_dashboard_path, within the engine users can call _dashboard_ and from outside they can call cms.dashboard_path. Includes the following updates: * Regenerated project files to use a test/dummy application, like a typical engine would. * Changed most of the paths so they aren't namespaced via convention (i.e. no more cms_dashboard_path) * Completely removed all fixtures in favor of FactoryGirl * Updated unit/functional tests to use new path patterns as well as factories. * Started the process of replacing functional and integration with Cucumber features (both for improved documentation and fixing brittle tests) * Improve cucumber coverage of more areas of the admin site. * Moving config (like initializers) and other testing code (like sample controllers) may help solve [#416] which should allow bcms to be specified in a Gemfile using :git=> syntax * Removed the namespacing of attributes on forms (i.e params[:html_block] rather than params[:cms_html_block]) * Added new method for adding the bcms routes to a project (mount_browsercms rather than routes_for_browser_cms). Old method is deprecated, and new projects will be generated with the new syntax.