You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
0 commit comments