Fluida 1.5 update changes

As mentioned in the update announcement, Fluida 1.5 changes some basic functional elements in a way that can change how your site looks and behaves after the update.

1. Landing Page
   It is now necessary to assign a static home page from WordPress’ Reading settings (A) or through the customizer Homepage panel (B) for the landing page to activate. You can use any static page and assign it as the homepage (even a completely empty one).
   Note that for SEO purposes, this page’s attributes (title, meta description, meta keywords) will be used by most SEO plugins for your homepage so adjust these values as necessary.
   
   If you were previously displaying the posts list at the bottom of the landing page, you’ll notice that after assigning a static homepage this is displayed instead. You can return to the posts list from the theme’s Landing Page options panel in the customizer (C)
2. Style enqueuing
   We have updated the code handling the style enqueues to better support the current WordPress recommended way of using child themes. This means that if you are using our old way of enqueuing (hooking to wp_head) in your child theme, the styles may end up being loaded in the wrong order and render incorrectly. You can use the code below in your child theme to update to the 1.5-compatible way:

   // enqueue parent theme styling
   function child_parent_styling(){
         wp_enqueue_style( 'fluida-main', get_template_directory_uri() . '/style.css', array(), _CRYOUT_THEME_VERSION );  // enqueue parent stylesheet
         wp_enqueue_style( 'fluida-child', get_stylesheet_directory_uri() . '/style.css', array( 'fluida-main' ) );       // enqueue child stylesheet
   }
   add_action( 'wp_enqueue_scripts', 'child_parent__styling' );

   Note: Updated 08.02.2018 to correct an issue with RTL compatibility.

3. Style relocation
   This shouldn’t cause any problems with your site unless you are using some form of caching (plugin or CDN network) which doesn’t clear properly after the theme update. You can clear the cache manually after the update if you notice any styling issues or elements missing. We have reverted this change in 1.5.0.1
4. Sidebars rename
   We’ve renamed the sidebar identifiers for consistency between our themes and demo content support. This shouldn’t pose issues in most cases as WordPress is capable of guessing the sidebar structure after such changes, but if you find your widgets are missing after the update, you should find them in an “Inactive Sidebar” in the Appearance > Widgets screen. To restore them, drag these widgets back to the desired sidebar location.
   

If you’re still having trouble restoring your site to previous behaviour and appearance, don’t hesitate to create a support ticket or start a topic in this forum.

• This topic was modified 6 years ago by Zed. Reason: Updated to reflect changes in v1.5.0.1
• This topic was modified 6 years ago by Zed. Reason: Updated enqueue code
• This topic was modified 6 years ago by Zed.
• This topic was modified 6 years ago by Zed.