Forum Replies Created
-
AuthorPosts
-
August 13, 2018 at 4:19 pm in reply to: Events Imported via Aggregator Aren't Properly Navigable #1596648
Barry
MemberOK – I believe 3.12 is the current version – have you tested with that?
Barry
MemberHi Dustin,
Yes: Event Aggregator facilitates ongoing imports from Google Calendar — the following resources will give you a pretty good overview:
- theeventscalendar.com/knowledgebase/new-user-primer-event-aggregator
- theeventscalendar.com/knowledgebase/import-from-feed-or-url
Is there another option to reach this goal without the paid extension?
We do have a non-profit program, but I’m afraid that Event Aggregator is not a part of it and that is currently our only supported means of importing from Google Calendar.
I hope that answers your questions, but let me know if I can clarify anything 🙂
Barry
MemberThanks, Michael.
Both our bug tickets are still open so though it’s great to hear some progress has been made, we’ll still make time to investigate further as soon as we have a window to do so 🙂
Barry
MemberAs a note, within the test site, we can use the Email Log option to see and inspect any emails that have been sent out to customers 🙂
Barry
MemberThis reply is private.
Barry
MemberCan you please delete the first reply with system information( not marked as private )?
Of course, done 🙂
With regards to the core problem, I can’t seem to replicate the same thing – so it does seem like this is specific to your site.
I’ve created a clean WordPress installation running Event Tickets, Event Tickets Plus, WooCommerce, The Events Calendar and Events Calendar PRO. I’ll share admin credentials below: I’m basically curious, can you replicate this problem there or identify any key differences between that installation and your own?
It could of course be that other plugins/your theme are in conflict and if nothing else, this might help to give us confidence that our own plugins are working as expected outside of your environment (or, indeed, you may be able to replicate in the test site and we’ll be better placed to debug further from there).
Barry
MemberIf you’re comfortable working with code (or have access to a developer who is at home with The Events Calendar and WordPress), I imagine you could use that extension as a starting point and tweak it to achieve that effect, yes 🙂
August 13, 2018 at 3:04 pm in reply to: Problem with display of ticket price on Success page (Thank You page) #1596597Barry
MemberI’m really sorry but I’m afraid we can’t commit to a specific timeline.
We generally ship maintenance releases every 3 weeks: the changes making up the very next such release have now entered the ‘code freeze’ stage as we conduct our final set of tests, and the next planned release after that is fully booked with other changes and improvements.
So, realistically, I don’t think we’re going to be able to fix this any earlier than September 11.
Barry
MemberThanks!
I see what you mean … and that is certainly less than ideal. I’ve logged a bug ticket for the development team to investigate further.
Once a fix is ready, we’ll drop an update in here 🙂
Barry
MemberGreat: once we have a substantive fix in place we’ll post an update (and you can then remove the Event Aggregator key).
Thanks for your patience in the meantime!
Barry
MemberI’m afraid we can’t offer a timeframe on this just yet, but I’ll add this topic to our bug report and then, once we’ve figured out how to proceed, we can update you.
One question: when I review your system information it does not include a list of your active plugins – but this could be really helpful for us in our efforts to reproduce and fix the problem.
To that end, can you share a list of active plugins with us, by private reply if you prefer?
Thanks!
Barry
MemberThank Gods! I found the root caused this. I don know why all default user roles(subscriber) is not allow to create ticket(i never activate any member plugin). But is ok, this problem can count as solve as long as ticket can be create.
Great!
Are there any further notes you can share on this, though? If there’s a bug when subscribers create tickets via Community Events, for instance, we’d love to fix it and so I’d like to be sure I understand correctly what caused the problem for you.
But, i found another issue, please see this http://prntscr.com/khmh3r . The system not allow me to set the ticket capacity, either backend or frontend also.
OK … if you click the edit icon (the pen or pencil icon to the right of each ticket) can you edit them? What happens when you try this?
Barry
MemberThis reply is private.
Barry
MemberHi Donna,
As a temporary measure I’ve generated an Event Aggregator license key for you, which I’ll share in a private reply.
Please visit the Events ‣ Settings ‣ License Keys screen and enter the key under Event Aggregator, then try importing a new event from Eventbrite.com and see if the images come across (this seems to work as a temporary solution for me, locally).
Unfortunately, for events that have already been imported without a featured image, once you have added the EA license key you will probably need to follow these steps for each of them:
- Use the hide & ignore link for each
- Once hidden and ignored, delete them permanently
- Re-import
I know that isn’t optimal and hopefully we’ll get a substantive fix in place soon (and we’ll keep you posted once we’re ready to ship a solution to this problem).
Barry
MemberHi Colm,
Given your end-of-day cutoff setting I would indeed expect a range like 00:00:00 → 23:59:59 … it’s odd that you aren’t seeing that and I seem unable to replicate the same problem locally.
- Are the impacted events being created by you/someone else operating in the admin environment, or are they frontend submissions coming through Community Events?
- I see that you indicated having tried deactivating all other plugins and switching to a default, unmodified theme (our core troubleshooting procedure, basically) when you opened this topic: I just want to confirm that when you took your site back to this basic state, you were able to create and replicate the issue then, too?
I wanted to check in on that second point specifically as if you followed those steps and looked at existing event data (ie, events which were already ‘damaged’) nothing would actually change.
That to say, in a case like this, you’d need to deactivate everything else, create a new event, and confirm that it is/is not also impacted by the same problem before reactivating things.
I hope that makes sense, but let me know if I can clarify things.
-
AuthorPosts
