- Rails 4 support has been deprecated in v2, please upgrade to Rails 5+. Fae 1.7.x will continue to be supported for bug fixes you're staying on Rails 4.
- Many CSS classes produced by v1.2 generators have been deprecated and restructuring views may be necessary. If you have any of the following class names, please refer to the structure in
spec/dummy/app/views/admin/releasesor rescaffold your views to update.- main_table-sort_columns
- main_content-sortable-handle
- main_content-section-area
- main_content-header
- main_content-header-section-links
- form_content-wrapper
Model#filter_allhas been deprecated. You can replace any calls to it with a custom method.translatehas been renamed tofae_translate. Please refer to the language documentation.- The RMagick gem has been replaced by MiniMagick. Any custom methods in the uploaders not supported by MiniMagick will have to be updated.
- The
form_headerpartial includes the errors previously rendered as a separate partial as well as the parent node markup (header.content-header.js-content-header). Please consolidate existing markup to use only the partial:
header.content-header.js-content-header
= render 'fae/shared/form_header', header: @klass_name, f: f, item: @item
= render 'fae/shared/errors'
/ to
= render 'fae/shared/form_header', header: @klass_name, f: f, item: @item- The
languageoption in theform_headerparial has been renamed tolanguages. - The
headeroption in thenested_tablepartial has been deprecated form_buttonshas been deprecated. Any admin still using this partial should removefae/shared/form_buttonsand only use fae/shared/form_header.form_headerstill supportssave_button_text,cancel_button_text,cloneable, andcloneable_textoptions.- The
dark_hintinput option has been deprecated. Please convert alldark_hintcalls tohint. attr_togglehas been deprecated. Usefae_togglein its place.
has_top_nav has been deprecated. Any admin still using side nav only will convert to using the top nav upon upgrade without any changes necessary.
Fae v1.3 has a new layout featuring a horizontal navigation across the top of the app. After updating, you may chose to enable the top nav or not.
If you choose to enable top nav, you need to do the following:
In config/initializers/fae.rb, uncomment
config.has_top_nav = trueYou will also need to remove the existing controllers/concerns/fae/nav_items file, and add the new file to models/concerns/fae/navigation_concern.rb
module Fae
module NavigationConcern
extend ActiveSupport::Concern
# define the navigation structure in this file
# navigation will default to the sidenav,
# unless you set the following in the Fae initializer:
#
# config.has_top_nav = true
# example structure with top nav:
#
# def structure
# [
# item('Top Nav Item 1', subitems: [
# item('Top Nav Dropdown Item 1', class: 'custom-class', path: some_named_route_path),
# item('Top Nav Dropdown Item 2', subitems: [
# item('Side Nav Item 1', subitems: [
# item('Side Nav Nested Item', path: some_named_route_path)
# ]),
# item('Side Nav Item 1', path: some_named_route_path)
# ]),
# ]),
# item('Pages', subitems: [
# item('Home', path: fae.edit_content_block_path('home')),
# item('About Us', path: fae.edit_content_block_path('about_us'))
# ])
# ]
# end
end
endIf you want the top level item for nav items with nested links to go to a specific path, pass in path: some_named_route_path to the top level after the name string, otherwise it will default to the first item in the list.
# def structure
# [
# item('Top Nav Item 1', path: some_named_route_path, subitems: [
# ...Fae v1.2 adds a new table Fae::Change to track changes on your objects. After updating you'll have to copy over and run the new migrations.
$ rake fae:install:migrations
$ rake db:migrate