[Dirk]

Hi Brian,

Thanks, that worked!

Cheers,

[Dirk]

Hi,

Yes, all tickets are woocommerce. Both events have two different woocommerce tickets with corresponding products. On one even the report is correct and on the other one not. The report (as seen above) without global stock enabled shows all adds the total tickets sold and gives that number on 1 ticket instead of separated. De total revenue is correct.

Since I thought it might be caused from the even existing pre-patch I was going to republish it and then something occurred to me: both tickets had the same name! So I guess the report from Tribe looks at the name instead of product ID. Is that something that might be possible? When I named the tickets differently the report seperated them effectively.

Since it might happen again that community members name the tickets the same but with different descriptions it would be nice if they can still be separated in the report. 🙂

It’s funny that in the end, a cause can always be found.

Cheers,

edit: unfortunatly we found out that total revenue was not solved and was not deducting the refunds. The ticket sales did take it into account so it is easy to calculate total revenue but it was not the same as shown in the report. Screeny:

• This reply was modified 8 years, 1 month ago by Dirk. Reason: Adding the total revenue part

[Dirk]

Hi guys,

I ‘fixed’ it by putting this custom CSS. It seems to work hiding it succesfully.

.tribe-attendees-list-container {
	display: none !important;
}
.tribe-tickets-attendees-list-optout {
	display: none !important;
}

Oh, and don’t forget to clear cache and (hard) refresh on computer/mobile device.

Hope it works for you,

Cheers,

• This reply was modified 8 years, 1 month ago by Dirk. Reason: Adding the cache part

[Dirk]

Hi Geoff,

Thanks for comming back to me so quickly. I think I sorted it out although some of the steps from your post didn’t work for me.

1. Download the complete plugin folder for both Event Tickets and Event Tickets Plus (done)
2. Open the .pot file in Poedit from your downloaded folder (done)
3. Using the Catalog menu, click on “Update from sources”. You should see the missing strings added.(Couldn’t do that, was greyed out in the menu…)
4. NA
5. I opened the .po files and then did the update from .pot, using the .pot file from the recent download. It seemed to add the missings strings and I could translate them. So I’m a little confused what the first couple steps are for and if i’m still missing something, haha

Most of the strings are translated now, so thanks.

Cheers,

[Dirk]

Same problems over here!

[Dirk]

Hi Geoff,

Thanks for comming back to me about it. For now we’ll CSS hide everything about it to prevent confusion. Looking forward to frontend availability but can also do without it. 🙂

We noticed some other stuff and minor bugs but will report it elsewhere in seperate posts.

Thanks,
Dirk

[Dirk]

Hi Geoff,

Thanks for keeping with me… 🙂

Somehow it does work with older versions, all very confusing! There’s probably something wrong on my end with the latests versions, my apologies.

I did however discover that it also happens, on all versions, when an event is set to ‘ private ‘. So when the owner of a ‘ private’ event logs in the frontend, he or she cannot go to sales. Would be interesting to know if you can replicate that result.

Cheers,
Dirk

[Dirk]

Hi Geoff,

It is indeed the ‘sales’ button on the frontend. We had issues in the past but those were resolved. Suddenly, after the latest updates, the error is back. We didn’t change anything else about the website.

I tried all the testing procedures, but it didn’t help. With the registered products I can download previous versions but the free core plugings I can’t. Is it possible to donwload the previous versions of the free core products?

Thanks,
Dirk

[Dirk]

Hi Geoff B,

Thank you for anwsering the questions. But I don’t think we’re both referring to a newly submitted event.

The problem is that when someone edits an already existing event on the frontend (community) the organizer is blanked out while it was set during the initial creation.

Cheers!

[Dirk]

Oh, the error is the following:

Fatal error: Cannot use object of type WP_Error as array in /home/…/plugins/event-tickets-plus/src/Tribe/Commerce/WooCommerce/Orders/Table.php on line 389

[Dirk]

Was just going on the forums to post a thread about this!

[Dirk]

Hi,

Does this also make it work on the frontend so it is actually useful for community tickets? Or is that something for future release?

Cheers,

Dirk

[Dirk]

Hi guys,

Today I suddenly received an e-mail tag about this subject. Is it working completely?

Cheers,
Dirk

[Dirk]

Hi Brian,

Thank you for the quick respons, it worked!
Since we’re on a shared hosting provide we cannot update our PHP to 5.5. Hopefully this will not become an issue.

Cheers,
Dirk

[Dirk]

Hi,

Not sure if new users also have the option to download old editions but if so you can download it here:

My Account

Just select the 4.0.1 from the dropdown menu. 🙂

[Author]

Posts