[Ilkka]

Hi,

I think it is a problem with my own customisations in the child theme, i will let you know if this is not the case.

Thanks.

[Ilkka]

Hi,

It seems that it is not removing the quantity from other products. It leaves the stock unchanged from the other tickets with in same shared capacity.

thanks.

[Ilkka]

Hi,

What i have found out so far is that this only affecting front end. It is just showing wrong quota for the tickets. If it runs out i am not able to buy tickets over the shared capacity. And most interesting is that i have some old tickets where the capacity is working and showing correctly?

I will investigate more, hopefully you have some ideas for this.

thanks.

[Ilkka]

Hi,

This seems to be doing the trick. I defined the start sale date in csv file, and the end date started appearing correctly.

Also i found out that if i add manually shared capacity to the ticket and save it; the end date appears correctly to the ticket. I would have never expected this to happen, but this is exactly what happened.

So i think there is a minor bug somewhere, maybe. I am happy for this part now. Thanks for your help.

Please add shared capacity option for csv import options. !!

I will let you know if i experience same problems.

Ilkka

[Ilkka]

This reply is private.

[Ilkka]

Hi there, sorry it has taken some time. I will be making some tests in upcoming days and will let ypu know. Thanks!

[Ilkka]

Hi,

Sorry, but i do not see the point of disabling plugins and theme as this procedure will not create new information on database. I can see from the database that this information ticket_end_date is empty. And it should save there when the import from csv file is made. But are you suggesting that i should make the import again without any other plugins activated and some another theme on?

[Ilkka]

Hi,

Thanks for your answer. I could achieve this by using Custom field bulk editor. So i can add these lines to database with no problems. Thank you for your answers.

ilkka

[Ilkka]

Hi,

Just one more thing. Ideally these setting would be on the table and therefore it would be very easy to give whatever meta_values to these meta_keys.

I hope your r following what i try to achieve. So i am just looking for a convenient way to add this setting so i d not have to go through 1000 events and their tickets. As this will take a week. Before i was able to do this in easy way to the database, not anymore.

Thanks.

[Ilkka]

Hi,

This gives a more depth understanding of what is going on. But what i try to achieve is that i could be setting global ticket sales on for massive amount of events.

For example i have 100 event and all events have four different tickets with global stock. In a normal way. Clicking to the events and making these would acquire loads of time, pushing buttons and loading pages. I am looking for a solution that i can make these settings directly to the database in order to keep the working process smooth.

So my problem is that these attributes come available in database only after the global settings has been made in the backend for the event and the ticket. The event does not have these attributes before:

_tribe_ticket_global_stock_level
_tribe_ticket_use_global_stock

So i can not add values to these by database update. For example:

In database there is always an option for show map link (for event):
_EventShowMapLink

ANd It is empty by default. If i put 1 to the database. The frontend event page will start showing the maplink.

However this is not the case with these two settings.

_tribe_ticket_global_stock_level
_tribe_ticket_use_global_stock

They do not exist in the table before the settings have been turned on in the backend. And this makes it very hard (for me) to understand how these values could be added in the database, as these values have meta_id which is constantly changing. I could use insert into command in sql but i do not know how these meta_id’s are being created.

Check the image.

Thanks.

[Ilkka]

Hi,

Okay thanks. I will see it from there. Lets see what are the results.

ilkka

[Ilkka]

This reply is private.

[Ilkka]

This reply is private.

[Ilkka]

hi,

Thanks for your reply. Originally the error appeared on my stating site. I will try your suggested procedure.

Thanks.

[Ilkka]

Hi,

Thanks for your reply. Removing all !important does not have any effect on the pdf. The pdf still looks exactly same. Originally i think the important rules came from email.php template. However it does not have any effect. The Emailed ticket is 100% accurate and the pdf conversion is not. No rules are working for the pdf.

Being just curious how are your results turning out from pdf conversion. If you make a pdf ticket from your system is the generated pdf as it should be?

Any other suggestions for this…

ilkka

[Author]

Posts