* All CMS assets including the necessary CKeditor files should get compiled. * ckeditor_rails gem adds a chained 'asset:precompile' task that runs after main precompile. It creates nondigest versions of ALL ckeditor files since CKEditor doesn't want/need digested files. * Streamlined inline/standard editors so toolbar files are not loaded via separate calls. * [FEATURE Removal] Removed the ability to change the toolbar (for now). This feature didn't work with asset:precompiling and we need to reimplement it correctly.
…s pass. Next commits will fix additional tests
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
…led via cucumber instead.
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.
…cing of models.
… not being added to portlets/blocks.