Is it possible to add what is listed in the uc_product_table list? I would like to show manufacturer as well as a Designer category.
Change and add columns/fields in the uc_product_table
|
|
install views? Maybe then you can filter by that already?
@Ryan, how far is ubercart linked/tied with views anyhow in 7e and 8 alpha?
I'm finding that the reliance on uc_product_table to display the product catalog is very limiting. I would like to add a number of things, like a teaser, a selection box for options, and a few other things, but it seems the only way I can do that is to throw out the product table and create my own view. Others have done it that way. So why doesn't Ubercart just use Views to begin with?
I'm on the most recent uc release and views is supported basically. The uc_views which was an add-on before, is added to core since 7c (cfr this)
I added a few things as well, (over here. Imho, it will be nescessary to implement more views compatibility into the basic uc setup, but the product table 'as is' provides a very nice out of the box availability.
In our shop, we use taxonomy_menu in combination with views. We had to rewrite/hack taxonomy_menu a little as it seems no longer maintained and not really compatible with pathauto. The catalog included in uc has this functionality from the start...
I agree that the default product table is great place to start. But what I'm finding is that if you want to do any customization at all, you need to throw it out and start from scratch? If so, I would argue that this indicates the architecture is wrong - it should be designed to be easy to extend or customize, because a large percentage of stores will need to do something other than the default.
I like the idea of the /products just being a default View, too. Mostly b/c we have the catalog module if people want an out of the box product listing, and if a newbie comes along and just wants a product list, it would be better for us and them if they used the Views module from the start (less support for us, more options for them as they get more comfortable with Drupal/Views). I'd like to see this on a to-do list somewhere unless there are any good objections. 
The only objection I can see is that it adds another requirement to using Übercart. It's not a big objection because I think everyone should learn how to use Views anyway, but it's there.
The reason we didn't start off using Views is because I didn't know what it was. I was still learning Drupal at that point, and Ryan was working on TAPIr, so I decided to use that.
hehe "I didn't know what it was." Inconceivable. We've learned a lot working on this project, eh? Well, I'd say it wouldn't add another requirement. Project nodes would still show up in the list at /node like any other module's nodes. And the catalog module could still be used to list them specially. For everything else, there's Views.
"You keep using that word. I do not think it means what you think it means."
I thought we were talking about replacing the uc_product_table on the catalog pages with a View. If not, I won't worry about it. If I need to change something, just let me know.
Nein - referring to /products. Making that a default View instead of a TAPIr thingummy.
I was talking about the catalog. I personally don't use /products, I present my products to the customer through the catalog. So it's the catalog I'd like to have the ability to customize a lot, and I'm finding the current scheme to be a little rigid.
My bad, then. 
Sorry for hijacking the thread.
I would like to have more flexability in customizing the Catalog as well.
|
|
Joined: 09/09/2007