[spree-user] Re: Spree Upgrade 1.1 to 2.1 - Best Practice && Issues

Hi All,

   I am looking for below extensions for the spree-2.0,

    spree_essentials,
    spree_essential_cms
    spree_essential_blog

    Shall expect your fork repo's - 1.2 will work with spree-2.0 ? I don't
think those won't work with spree-2.0

    Can you suggest me, any extensions that are available and best fit
similar to essential_blog, cms ?


     Thanks,
      Raju

Hi All,

   I am looking for below extensions for the spree-2.0,

    spree_essentials,
    spree_essential_cms
    spree_essential_blog

    Shall expect your fork repo's - 1.2 will work with spree-2.0 ? I don't
think those won't work with spree-2.0

    Can you suggest me, any extensions that are available and best fit
similar to essential_blog, cms ?


     Thanks,
      Raju

See my answer in the other thread.

Hi Nate and all,

    Any one have experience with upgradation from spree2.0 to spree2.1.

    I am upgrading the spree2.0 + rails 3.2.14 application to spree-2.1 +
Rails -4 where I am getting the issues with my customization code like
attr_acceble.

   I believed that for existed projects, we can go with protected_attributes
gem for this old fun.

   But still I am getting issues with protected_attribute gem as in check
out process its giving the

*can't blank error. *I am going this upgradation as created new rails4 app
with spree and placing my old customization code. Is this process correct?

   Please let me know your ideas on it.

How to add new fields for spree::user in Spree-2.1 + Rails4 ?

   Like my old customization:

  Spree::User.class_eval do
   attr_accessible :f_name, :l_name :gender
   validates :f_name, :presence => true, :length => {:maximum => 25}
   validates :l_name, :presence => true, :length => {:maximum => 20}
  end

   please let me know your comments.