Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Jan 21, 2012
Commits on Dec 29, 2011
  1. @peakpg

    [#460] Improve CLI help

    peakpg authored
    * Provide better error messaging for `bcms new`, `bcms demo` and `bcms module` when a project name isn't provided.
  2. @peakpg
Commits on Dec 28, 2011
  1. @peakpg

    [Engines] Modules should be generated as Engines

    peakpg authored
    * `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.
Commits on Dec 9, 2011
  1. @peakpg

    [3.4 Upgrade Script] Writing migrations for v3.4

    peakpg authored
    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
Commits on Nov 30, 2011
  1. @peakpg
  2. @peakpg

    [Ruby 1.9.3] Upgrade to work w/ Ruby 1.9.3

    peakpg authored
    * 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.
Commits on Nov 4, 2011
  1. Updated seeds to specify number of elements in the password rand arra…

    authored
    …y - when deploying in production (i.e. db setup) it tries to call #rand on Array, which doesn't exist.
  2. Added begin/rescue block around tasks requiring deps like yard and cu…

    authored
    …cumber to prevent issues from being raised in production
Commits on Oct 13, 2011
  1. @peakpg

    Updating todo list.

    peakpg authored
  2. @peakpg

    More public directory cleanup

    peakpg authored
  3. @peakpg
  4. @peakpg

    Remove unnecessary static files from the gem, since rails will genera…

    peakpg authored
    …te these as needed for projects.
  5. @peakpg

    Remove selenium tests since they were way out of date and better hand…

    peakpg authored
    …led via cucumber instead.
  6. @peakpg

    Removed bespin editor features

    peakpg authored
    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.
  7. @peakpg

    Match Rails 3.1 default config options. XSendfile and serve_static_as…

    peakpg authored
    …sets can remain disabled.
  8. @peakpg

    Merge 3.3.x into master.

    peakpg authored
  9. @peakpg

    [#446] 301 Redirects

    peakpg authored
    Merging this from 3.1.x branch into master.
  10. @peakpg

    [#416] Add browsercms to Gemfiles via :git

    peakpg authored
    Confirmed that changes for #448 allow BrowserCMS to be added to project using :git rather than released gem.
  11. @peakpg
  12. @peakpg

    [#448] Make BrowserCMS a Mountable Engine

    peakpg authored
    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.
Commits on Sep 26, 2011
  1. @peakpg
  2. @peakpg

    [#3] Make use of the Asset Pipeline

    peakpg authored
    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).
Commits on Sep 22, 2011
  1. @peakpg
  2. @peakpg
  3. @peakpg

    Write release notes for 3.3.2

    peakpg authored
Commits on Sep 20, 2011
  1. @peakpg
Commits on Sep 16, 2011
  1. @peakpg
  2. @peakpg

    Update versions of gems.

    peakpg authored
  3. @peakpg

    Prep for 3.3.2 release

    peakpg authored
  4. @peakpg
  5. @alce @peakpg

    Merge fixes for cache directory

    alce authored peakpg committed
  6. @peakpg

    Updating TODO for 3.1

    peakpg authored
  7. @peakpg

    Merge pull request #439 from alce/link_or_page

    peakpg authored
    Do not call hidden? on Link objects
Something went wrong with that request. Please try again.