Permalink
Commits on Dec 9, 2011
  1. [3.4 Upgrade Script] Writing migrations for v3.4

    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
    peakpg committed Nov 30, 2011
Commits on Nov 30, 2011
  1. [Ruby 1.9.3] Upgrade to work w/ Ruby 1.9.3

    * 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.
    peakpg committed Nov 30, 2011
Commits on Oct 13, 2011
  1. Updating todo list.

    peakpg committed Oct 13, 2011
  2. More public directory cleanup

    peakpg committed Oct 13, 2011
  3. Since FCKeditor is no longer the default, remove the custom config.js…

    … from the project.
    peakpg committed Oct 13, 2011
  4. Remove unnecessary static files from the gem, since rails will genera…

    …te these as needed for projects.
    peakpg committed Oct 13, 2011
  5. Remove selenium tests since they were way out of date and better hand…

    …led via cucumber instead.
    peakpg committed Oct 13, 2011
  6. Removed bespin editor features

    This was accidently merged in as part of the namespacing commits and was not working with Rails 3.1. Having this is desirable, but it should be a separate module probably.
    peakpg committed Oct 13, 2011
  7. Match Rails 3.1 default config options. XSendfile and serve_static_as…

    …sets can remain disabled.
    peakpg committed Oct 13, 2011
  8. Merge 3.3.x into master.

    peakpg committed Oct 13, 2011
  9. [#446] 301 Redirects

    Merging this from 3.1.x branch into master.
    peakpg committed Oct 13, 2011
  10. [#416] Add browsercms to Gemfiles via :git

    Confirmed that changes for #448 allow BrowserCMS to be added to project using :git rather than released gem.
    peakpg committed Oct 13, 2011
  11. [#448] Make BrowserCMS a Mountable Engine

    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.
    peakpg committed Sep 27, 2011
Commits on Sep 26, 2011
  1. [#3] Make use of the Asset Pipeline

    BrowserCMS now uses the Rails 3.1 Asset pipeline to serve it's javascript, images and stylesheets for core files.
    
    * Moved CSS to assets folder. Internal CMS templates now use the cms/application.css
    * Moved core CMS images to Assets directory.
    * Added dependency on jquery-rails
    * Moved all JS to asset pipeline.
    * Make cms/application.js into a pure manifest file.
    * CKEditor now loads through Asset Pipeline and is configurable by gems.
    * Moved external jquery libraries (cookie and selectbox) to vendor, since they are external dependencies.
    * Deleted rails.js since that's no longer used (jquery-ujs is used via asset pipeline now)
    * Removed (broken) bespin editor from dynamic portlets.
    * [#443] Removed require_javascript_include and require_stylesheet_link from project (Use asset pipeline instead).
    peakpg committed Sep 26, 2011
Commits on Sep 22, 2011
  1. Write release notes for 3.3.2

    peakpg committed Sep 22, 2011
Commits on Sep 20, 2011
Commits on Sep 16, 2011
  1. Update versions of gems.

    peakpg committed Sep 16, 2011
  2. Prep for 3.3.2 release

    peakpg committed Sep 16, 2011
  3. Merge fixes for cache directory

    alce committed with peakpg Sep 7, 2011
  4. Updating TODO for 3.1

    peakpg committed Sep 16, 2011
  5. Merge pull request #439 from alce/link_or_page

    Do not call hidden? on Link objects
    peakpg committed Sep 16, 2011
Commits on Sep 15, 2011
  1. Fix bundler

    peakpg committed Sep 15, 2011
  2. [RAILS 3.1] Fix all tests

    peakpg committed Sep 15, 2011
  3. Update gemfile

    peakpg committed Jun 16, 2011
  4. update gemfile

    peakpg committed Jun 16, 2011
  5. Update goals and additional bugs.

    peakpg committed Sep 15, 2011
  6. * Fixed broken integration test for Reset Password

    * Fixed broken integration test for CKEditor
    peakpg committed Sep 15, 2011