Forum Replies Created
-
Posts
-
Thank you so much! I have tested all functions that were problems for me, and everything now works perfectly. I appreciate the prompt fix for the exetension, because this function really is important to our site which often lists multiple same venue events and dates. It makes it so easy for our users to be able to hover over the location and review the list.
Thanks for the clarification — I hope that in a future release there will be a clear way to disable printing of the VR code. We are an educational site using the Events ticketing system to manage course enrollment, so rather than a “ticket” we want to issue an “Enrollment Confirmation”. So the QR code is superfluous and potentially confusing.
I have now been able to get this issue resolved, but only by looking up the longitude and latitute coordinates of the venue and entering them. I don’t know why this would be a problem, because address details without coordinate properly showed venue location on the inset map for the venue. I hope that his will not be a problem on other events. (I will keep an eye on this for the future).
Sorry, I realize now that I’m reporting this under the wrong topic. The problem now is with the updated to Events Calendar Pro. … so same issue, different premium plugin
This error still persists with attempted update to version 4.4.20:
Download failed. cURL error 61: Unrecognized content encoding type. libcurl understands deflate, gzip content encodings.
I realize I can do a manual update, but I am reporting this because I shouldn’t have to do manual updates every time– so I hope that you can address this problem in the future.
Raphael,
I found this thread because I have users complaining of the same problem, but I was able to easily remedy this, leaving the default currency setting in place.
All I had to do was customize the template and the correct HTML code was already in place. It’s just that the distribution file has the fields for data entry hidden and disabled.
I copied the community/modules/cost.php template to the appropriate location in my theme:
[your-theme]/tribe-events/community/modules/cost.phpOn line 61, <tr class=”tribe-section-content-row” — I removed the style specification: style=”display: none;”
On line 67 and 76, under <td class=”tribe-section-content-field”>, I deleted the words “disabled”.
Then tested everything and it all worked fine. Displayed as intended on the front end in both list and single event views, and information was reflected accurately in the administrative dashboard edit panel for the event.
There wasn’t any need to write extra code, as the code was already there — it just was hidden from view because of the style being set to display:none and the proper fields being disabled.
I don’t use WooCommerce or have the Community Tickets plugin — so I am not sure why this would tie into WooCommerce as Shelby wrote. I’m thinking that Shelby must have misunderstood your question, because her answer seems geared to a function relatd to ticke sales as opposed to event data entry and display.
I’m guessing that there might be a reason the developers chose to disable those fields– perhaps some sort of blug or glitch. Given Shelby’s answer, I am guessing that it might not be compatible with the Community Tickets plugin. But if all you want to do is control display, it seems like a very easy fix.
EDD is used ONLY for Event Tickets on my site — so I have no clue about other product types. EDD tickets was installed solely for use with Event Ticket Plus.
Could you please send me a copy of the latest version of your WordPress theme / child theme via a link to a .zip file link (stored Dropbox or Google Drive) so that I can run some tests on my end ?
This isn’t necessary because I tested with Twenty Fifteen and the problem I noted persisted. So it wasn’t related to the theme.
Thank you for the info about the Event Rocket plugin — I have disabled that plugin and tested, and the error with the tickets.php template persisted.
As noted, there is no problem with the previous template and I am currently using that on my site.
