Home › Forums › Calendar Products › Events Calendar PRO › Multiple stock fields
- This topic has 9 replies, 2 voices, and was last updated 8 years, 7 months ago by
Daniel Phillips.
-
AuthorPosts
-
September 12, 2017 at 3:37 pm #1348309
Daniel Phillips
ParticipantSeems like some of our events have multiple stock fields for RSVP
September 13, 2017 at 12:25 pm #1348810Andras
KeymasterHello Daniel,
Thanks for using our plugins and welcome to the forums!
Sorry to hear about your issue. I’ll try to help you solve this one.
As a first step, please update all the Modern Tribe plugins, and possible WordPress as well to the latest version and check if that solves it.
If the issue is still there after the update, then please go through our guide for testing conflicts and see if that brings any change.
Let me know about the results and we’ll take it further from there if needed.
Cheers,
AndrasSeptember 13, 2017 at 1:49 pm #1348872Daniel Phillips
ParticipantWe are on our dev system and seem to be with Woo Ticket Plus
<tr class=”ticket_advanced ticket_advanced_Tribe__Tickets__RSVP”>
<td colspan=”2″ class=”tribe_sectionheader updated”>Selling tickets for recurring events <span class=”tribe-bumpdown-trigger dashicons dashicons-editor-help”
data-bumpdown=”Currently, tickets will only show up on the frontend once per full event. For PRO users this means the same ticket will appear across all events in the series. Please configure your events accordingly.”
data-bumpdown-class=”ticket_advanced ticket_advanced_Tribe__Tickets__RSVP”></span></td>
</tr>
<tr class=”ticket_advanced ticket_advanced_Tribe__Tickets_Plus__Commerce__WooCommerce__Main”>
<td>
<label for=”ticket_price”>Price:</label>
</td>
<td>
<input type=’text’ id=’ticket_price’ name=’ticket_price’ class=”ticket_field” size=’7′ value=” />
<p class=”description”>(0 or empty for free tickets)
</td>
</tr>
<tr class=”ticket_advanced ticket_advanced_Tribe__Tickets_Plus__Commerce__WooCommerce__Main sale_price”>
<td>
<label for=”ticket_sale_price”>Sale Price:</label>
</td>
<td>
<input type=’text’ id=’ticket_sale_price’ name=’ticket_sale_price’ class=”ticket_field” size=’7′ value=” readonly />
<p class=”description”>(Current sale price – this can be managed via the product editor)
</td>
</tr><tr class=”ticket_advanced ticket_advanced_Tribe__Tickets_Plus__Commerce__WooCommerce__Main global-stock-mode”>
<td><label for=”ticket_woo_global_stock”>Global stock mode:</label></td>
<td>
<select id=’ticket_global_stock’ name=’ticket_global_stock’ class=’ticket_field tribe-dropdown’>
<option value=’global’ > Use global stock </option>
<option value=’capped’ > Use global stock but cap sales </option>
<option value=’own’ selected=’selected’> Independent (do not use global stock) </option>
</select> </td>
</tr><tr class=”ticket_advanced ticket_advanced_Tribe__Tickets_Plus__Commerce__WooCommerce__Main global-stock-mode sales-cap-field”>
<td><label for=”ticket_woo_global_stock_cap”>Cap sales:</label></td>
<td>
<input type=’text’ id=’ticket_woo_global_stock_cap’ name=’ticket_woo_global_stock_cap’ class=”ticket_field” size=’7′
value=’0’/>
<p class=”description”>(This is the maximum allowed number of sales for this ticket.)
</td>
</tr><tr class=”ticket_advanced ticket_advanced_Tribe__Tickets_Plus__Commerce__WooCommerce__Main stock”>
<td><label for=”ticket_woo_stock”>Stock:</label></td>
<td>
<input type=’text’ id=’ticket_woo_stock’ name=’ticket_woo_stock’ class=”ticket_field” size=’7′
value=”/>
<p class=”description”>(Total available # of this ticket type. Once they're gone, ticket type is sold out.)
</td>
</tr>
<tr class=”ticket_advanced ticket_advanced_Tribe__Tickets_Plus__Commerce__WooCommerce__Main”>
<td><label for=”ticket_woo_sku”>SKU:</label></td>
<td>
<input type=’text’ id=’ticket_woo_sku’ name=’ticket_woo_sku’ class=”ticket_field” size=’7′ value=”/>
<p class=”description”>(A unique identifying code for each ticket type you're selling)
</td>
</tr>September 14, 2017 at 7:17 am #1349158Andras
KeymasterHi Daniel,
I’m not quite sure I understand. Can you please post again after updating your plugins to the latest versions and checking whether the issue still exists?
I’ll be here waiting.
Looking forward to helping you solve this.
Cheers,
AndrasSeptember 14, 2017 at 8:11 am #1349199Daniel Phillips
ParticipantHi Andras, We have updated to the latest version on our dev copy of our production server and the issue is still there. I think this issue maybe with ticket plus and RSVP? it’s displaying multiple stock fields.
September 14, 2017 at 10:08 am #1349368Daniel Phillips
Participantit’s looks like a display bug maybe. So it’s not adding duplicate to our database. Event 7091 links to ticket 7237. I set it to 66 for it’s stock, and there’s only one entry.
September 14, 2017 at 10:09 am #1349371Daniel Phillips
Participantforgot the front end screenshot
September 15, 2017 at 4:04 am #1349634Andras
KeymasterHi Daniel,
Thanks for the update!
We haven’t had any other reports of this behavior so let’s dig a bit deeper to find the source of the issue.
I see that you are using a lot of plugins, it can happen that one of them is causing this glitch. To find out please go through our guide on testing for conflicts and see if that uncovers anything.
It also can be that there is some custom code in your theme / functions.php file which causes this. The conflict test above / switching to a default theme like twentyseventeen will help in this.
Let me know what you find. I’ll be waiting.
Cheers,
AndrasOctober 7, 2017 at 9:35 am #1360734Support Droid
KeymasterHey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.
Thanks so much!
The Events Calendar Support Team -
AuthorPosts
- The topic ‘Multiple stock fields’ is closed to new replies.
