How to capture multiple characteristics

  • Posts: 241
  • Thank you received: 5
11 years 7 months ago #98214

I am looking for a pointer as to best practices. I have a fitness event (product) where users can buy tickets to one of 6 Divisions (limited availibility in each division):

Men Scaled
Men Rx
Men Masters
Ladies Scaled
Ladies RX
Ladies Masters

Additionally each person will get a t-shirt at the event. When I include the t-shirt in characteristics the number of variants grows from 6 to 24 (6 divisions x 4 shirt size options). I have included this in the screenshot. This is not correct as I don't want to limit the availability of for example Men Rx + Small Shirt tickets, but only Men Rx.

How do i accomplish this? I have used custom fields in the past, but they get too burdensome on the system and cause a problem in hikashop. I could create another "product" called t-shirt" and sell it along with the tickets.

What works best in your experience?

Attachments:
Last edit: 11 years 6 months ago by cberry1971.

Please Log in or Create an account to join the conversation.

  • Posts: 82760
  • Thank you received: 13347
  • MODERATOR
11 years 6 months ago #98399

Hi,

I your case I would do like that:

I would have a characteristic for the Division, like you have, and then I would have an option for the Shirt size :
www.hikashop.com/en/support/documentatio...ct-form.html#options
That way, the short size does not interfere with the variants of the product.

Please Log in or Create an account to join the conversation.

  • Posts: 241
  • Thank you received: 5
11 years 6 months ago #100108

After Upgrading Hikashop i have lost the "options" on my products.

1. I have a product intro page here 184.154.228.9/~throwdow/live/index.php?o...ent&id=81&Itemid=118
2. I offer the ability to buy t-shirts as seen in the screenshot



But when you click "buy tickets" in the link above nothing shows as a t-shirt option.

Attachments:
Last edit: 11 years 6 months ago by cberry1971.

Please Log in or Create an account to join the conversation.

  • Posts: 82760
  • Thank you received: 13347
  • MODERATOR
11 years 6 months ago #100121

So you say that you still see the option added to your product on the backend, but not on the frontend ?

It could potentially be a database structure update issue.
Turn on the debug mode option of the configuration and see if you get an error on the product page after that.
If yes paste it here so that we can tell you what to do.
If not, then it's not a database issue and I don't see why the update would change anything and we would need a backend access to further assess the problem.

Please Log in or Create an account to join the conversation.

  • Posts: 241
  • Thank you received: 5
11 years 6 months ago #100154

Ok thanks for the quick reply. i have debug system = "On" and you can have a look here:

184.154.228.9/~throwdow/live/index.php?o...duct&task=show&cid=7

Please Log in or Create an account to join the conversation.

  • Posts: 82760
  • Thank you received: 13347
  • MODERATOR
11 years 6 months ago #100214

I don't see any bug on the page. We would need a backend access to further assess the problem.

Please Log in or Create an account to join the conversation.

  • Posts: 241
  • Thank you received: 5
11 years 6 months ago #100217

ok thanks. I will pm you credentials.

Please Log in or Create an account to join the conversation.

  • Posts: 82760
  • Thank you received: 13347
  • MODERATOR
11 years 6 months ago #100428

It's because for some reason you have 0 instead of "empty" in the end date field of your option.
I've changed the line:
if($variant->product_sale_end!='' && $variant->product_sale_end<time()) continue;

to:
if($variant->product_sale_end!='' && $variant->product_sale_end!='0' && $variant->product_sale_end<time()) continue;

in the "option" view file so that both work properly.

Please Log in or Create an account to join the conversation.

Time to create page: 0.080 seconds
Powered by Kunena Forum