Profile: nopadmin

Hi Stefan,

Excellent.   That pretty much what I was anticipating and hoping for.
Thanks for your information!

Shawn

Hi, just a general question here.  I have a client whose manager selected the shop all theme to be applied to the project when the project first got started.  The project has many view files and such in the shop all theme that have been modified to provide custom functionality.  However, the manager has been let go and the company owner would rather use another theme.  

How complex would this task be?  Do many of your themes roughly share the same set of view files and the look and feel are changed primarily in the css files?  Would it work to get the new theme and replace the shop all css files with the new theme css files?  I understand it may not be a perfect drag and drop replacement but it seems like it would have to be easier than putting in all the custom functionality into the new theme's view files.

Thanks for any help you can provide.

Regards,
Shawn

Hi Boyko,








  Thanks for your fast reply.  Indeed, I share your thoughts on why these UI folks just don't want the project or truly don't understand how your themes are designed and what you get when you purchase one.   They are worth every penny in my opinion, so it is not surprising that 30-40% of all nop sites use your themes.      I appreciate the time you took to answer my theoretical question.  

  That was me just thinking out loud I suppose.   :-)    Regards

Since I don't really do theme and UI modifications for my clients, I recommended early on to one client that they should hire someone else to do the theme css tweaks and UI/UX work.  We built the site on Shop All 3.50 and modified out of the box nop functionality fairly extensively.  We added plugins and modified many of the view files in the Shop All theme.  Yesterday my client called me and said that he has talked to now 3 people who refused to take on the project because we used the Shop All theme.  One told him 'that was the worst thing you could do is to use a third party theme'.  I replied that the Shop All theme, like any of your themes, are MEANT to be customized and there are thousands of sites on nop using your themes that are very heavily customized with css tweaks, plugins, moving elements around the pages, and more.  I know that you cannot customize the logic behind some of the plugins, however if a plugin does not do what you want then don't install it and either find another that behaves the way you want or write your own.    Am I missing something here?  Why would a so called 'nop expert' say that?  Ignorance?   Misinformation or unfamiliarity with your themes ?  

By the way, if anyone reading this does nop-template theme customizations and would like to take on a project for a US company, my client would love to talk to you.  Please PM me.  

Thanks
Shawn at NopAdmin

Never mind.  I see I just need to make a modification to the foreach in the AttributeFilter.cshtml file to exclude the ones I want.   Thanks for giving us access to the Razor files!!  

Hi, is there a way to exclude filtering on just some attributes on the Ajax Filter that is included in the Shop All theme?   We have some that do not apply to being able to be filtered by attribute value.

Thanks
Shawn

Hi Boyko, thanks for the assistance.  Yep, I found the problem.  The stored proc that loads the Product Pages for Ajax filters was missing.  Uninstalling and reinstalling ajax filters plugin fixed it.

Thanks

Hi Guys

I implemented the ajax filters in the shopall theme to a client site and the filters appear as you would expect on the category pages.  However when selecting a filter the page displays an error that says 'The Page Failed To Load' and does not filter.   The site is pretty heavily customized on some of the product controllers and such.  How can I debug and fix what is going on with the Ajax filters?   Any suggestions?

Thanks for your help

Shawn

Never mind....just saw that all of the configuration settings I needed are in the Settings table.  I had searched there but expected to find names with the SevenSpikes prefix.   Anyway, I updated all of the settings in the 'stage' db with those from the source dev db with this sql:

  --see what will be changed first
SELECT  source.[Id]
      ,source.[Name]
      ,source.[Value] as SourceValue
    , stage.[value] as Stagevalue
      ,source.[StoreId]
  FROM [MySource].[dbo].[Setting] source 
  join [MyStage].dbo.setting stage on source.name = stage.name
  where stage.value <> source.value
  order by stage.name



--update the shopall theme settings in the staging db with the values
--from dev source db

  update stage
  set stage.[value] = source.[value]     
  FROM [MySource].[dbo].[Setting] source 
  join [MyStage].dbo.setting stage on source.name = stage.name
  where stage.value <> source.value

Hi, 

I have been working on configuring a staging database and site based on nop 3.60 and need to apply all of the same settings to the 'live' db when the upgrade is complete. Where are all of the ShopAll configuration options stored in the database.....ie what do I need to copy from the staging db to the new live db so I don't have to reconfigure everything in the Seven Spike plugins section in the admin backend?
I have moved all of the SS_ tables but that is not all as there are many differences.

Thank you
Shawn