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
Copy file name to clipboardExpand all lines: upgrading_to_3_1.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,10 @@
8
8
* Update a few modules (like bcms_news) to test module generation
9
9
* Test this on a production environment prior to releasing (things like assets and/or config options might be wonky)
10
10
11
-
Wants (Taking advantage of 3.1)
12
-
-----
11
+
# Wants (Taking advantage of 3.1)
13
12
13
+
* Verify that instances of Acts::As::ContentPage in projects can correctly load CMS templates
14
+
* Get Aruba working to test the bcms and other functions
14
15
* Internal CMS layouts (like _head.html.erb) do not take advantage of the asset pipeline to join all css or js files (most are compiled into cms/application.css though)
15
16
* Improve generators for assets from engines (Review http://bibwild.wordpress.com/2011/09/20/design-for-including-rails-engine-assets-into-pipeline-manifest/)
16
17
* Remove the styled_file_field (no longer maintained)
0 commit comments