Jump to content



Member Since 29 Nov 2008
Offline Last Active Jun 30 2014 09:12 PM

#146347 TAGs what are they ?

Posted by jagorny on 04 October 2012 - 04:07 PM

This is a frustrating topic for me personally, because tags on a store are fantastic if implemented correctly, but I have never been able to get enough interest from the developers to actually implement them in a useful way.

Right now, tags are nothing more than bookmarks for users. That's their vastly underutilized potential right now. A customer can tag stuff and go to that tag later to view what they tagged. How is this any better than a wishlist?! Oh because you can have more than one. It would make more sense to let customer create and name multiple wishlists.

Tags are supposed to serve as an alternative navigation structure - so that, for example, if I see a product has a given tag, I should be able to click on that tag and view other related products, etc. This does work, although it is laid out in a clumsy and buried way.

But from a product catalog design perspective, this system should be available across the board on the administrative backend but it is not. For example, why can't you use this as a population criteria for product blocks? Or daily deals? Or setting up a seasonal menu? Or anything else? Make tags public or private, etc... Tags in a proper content management system are much more flexible - you could allow conditional content based on tags - e.g. show or hide a block based on a product tag - why not? There are a lot of batch processes that could be simplified if tags were better implemented. You could try to set up invisible product features to accomplish this, but this is pretty clumsy and adds a lot of bloat.

I've added a few tag recommendations to user voice and gotten feedback on developers that they were good ideas, but no implementation roadmap. One day I'll end up coding add-ins myself for it I suppose...

#91310 Switching to email for login instead of affiliates...

Posted by jagorny on 06 October 2010 - 06:03 PM

That title should be: "Switching to email for login instead of login ID for customers and affiliates"

So I have a question regarding the potential conflicts between affiliate accounts and customer accounts.

Up until the 15th, we've used logins, but I have found that a lot of folks have had problem remembering their login and so I want to shift to the email as login model.

That being said, we have a handful of affiliates who also have customer purchasing accounts - this is left over from when we were using X-C and had separate partner and customer logins.

How does this work on CS-Cart? For example, if I have a customer who is part of the bookstore discount usergroup and also an affiliate, can they still purchase as if they were a customer when logging in to their account?

Does logging in as an affiliate have any other impact?

I ask this because many of my promotions are disabled for affiliate accounts because I assumed that if they logged in as an affiliate, their affiliate code automatically was getting applied to their order.

Is this not the case? If someone logs in and tries to apply their own affiliate code to the session, will the affiliate commission automatically be cancelled?