spree_static_content
spree_static_content copied to clipboard
sidebar navigation gets replaced with taxon list (2-4-stable)
I'm running a store with the following.
gem 'spree', git: 'https://github.com/spree/spree.git', branch: '2-4-stable'
gem 'spree_gateway', github: 'spree/spree_gateway', branch: '2-4-stable'
gem 'spree_auth_devise', github: 'spree/spree_auth_devise', branch: '2-4-stable'
#
#Added Spree Extensions
#
gem 'spree_paypal_express', :github => "radar/better_spree_paypal_express", :branch => "2-4-stable"
gem 'spree_static_content', :github => 'spree/spree_static_content', :branch => '2-4-stable'
gem 'spree_editor', :github => 'spree/spree_editor', :branch => '2-4-stable'
gem 'spree_social_products', github: 'spree-contrib/spree_social_products', branch: '2-4-stable'
gem 'spree_postal_service', github: 'futhr/spree-postal-service', branch: '2-4-stable'
gem 'spree_mail_settings', github: 'spree-contrib/spree_mail_settings', branch: '2-4-stable'
When I create a static page such as "contact us" using slug /contact and click on that static page. The left hand search menu that contains categories
<div data-hook="homepage_sidebar_navigation">
is replaced by a list of taxons
<div class="navigation" data-hook="navigation"> <h6 class="filter-title"> All taxons </h6>..
How can I get the extension to just display the original categories menu ?
Some images to explain.
The Home pages is as below.
When I click on a contact us Static page the menu changes as in the image below,
I've tried changing the render instruction to force it to render taxonmies by using
<%= render :partial => 'spree/shared/taxonomies' %>
but for a reason I don't understand the code cannot see the @taxonmies object. so I get a nil object.
Looking at the code for the home page it has the same render instruction and it works fine.
Can anyone help me understand how the taxonmies object is loaded on the homepage but not in the static_content code ?
Thanks Andy
still an issue for me.
Hi all, Spree is as always evolving in a rapid phase, I do recommend you submit a PR for this issue if you want it resolved, continuous development of extensions happens in 99% on master
branch and latest stable version. Thanks!