Forum Replies Created
-
Posts
-
Hey Debbie. Thanks for the follow-up, and apologies on my end for the delay in responding again. Are you still having questions here? On our end, we have made a lot of progress on filtering options the past few weeks and, to give you a sneak peek of what’s in store for 2.1, we’ve got these basic options built already: http://d.pr/i/6Lcp. We’re also working on a more specific geo-search that I don’t have a screenshot of yet, but is in the works and should allow even more specific geographic filtering.
If you want to check in on the status of those over the coming months, feel free to email pro /a/ tri.be. Otherwise we do have 2.1 – in which the bulk of this should be included – on track to launch before the end of the year, so if you were waiting to update until then know these are in the broader queue.
Hope that helps and apologies once more for the delay. If you’re still reading this and need anything else, do let me know.
Hey there Ray. As my colleague Leah noted above, our apologies for letting this one slip through the cracks. Happy to get you the answers you need here…and I’m going to keep an eye on this thread in case you post any follow-up questions as well.
On your specific points:
1. “non-members can browse and purchase tickets to events” – this is absolutely doable. So long as you don’t have some restriction on your site (via a third-party plugin or something you built) that requires membership to see events, anyone will be able to view the calendar and buy tickets…regardless of whether they have an account or not.
2. “upon purchase, new ( WP ) membership account added ( from submitted ticket details – email & name.. )” – this is a good idea and probably a logical next step for the plugin, but as it stands we don’t yet have this ability…largely because the purchase itself is handled entirely on the Eventbrite webpage, so once they begin their purchase pretty much the entire order happens offsite. (This, too, will change in a future build but isn’t on the immediate horizon).
3. “new member can now log-in and view purchased tickets on our website in a designated and secured “member area”” – This too would probably require some custom development, as it’s outside the scope of what the plugin offers at this point.
4. “these same users will be encouraged to submit their own events ( future plan.. )” – Frontend event submission is definitely possible, and you have the option to elect whether just members or anonymous users can submit. However this is done with our Community Events add-on (https://theeventscalendar.com/wordpress-community-events/), rather than the Eventbrite Tickets one.That help? Let me know if not, and I can elaborate as needed. Thanks again for your interest.
Hey again Sandro. As this also relates to WPML, I’m going to have Daniel (who I noted in https://theeventscalendar.com/support/forums/topic/weir-get_comments-behaviour-not-expected-at-all/#post-25552) take a look upon his return Monday. As Leah noted above, thanks for being patient!
Hey there Sandro. Just wanted to follow-up to show that we haven’t forgotten about this; we actually have a WPML expert on the team here who I’m specifically waiting to have address this issue for you. However he was out this entire week and not addressing support as a result.
I’ve added this as the top priority support thread for him to hit on his return Monday, so know that relief is in sight. Thanks for your patience on this end so far and please let me know what else you need here.
Hey Alex. Just sent you an email as well to follow-up on this, so feel free to respond to that as to the specifics. Awesome to hear that you’re enjoying the recurrence functionality…that’s definitely one of the main selling points for PRO and we’re looking to take it even further with more random recurrence options in 2.1, when that is released over the next couple months. We think you’ll like it.
Let me know what else we can do here, and thanks again for your updates and troubleshooting of this issue.
Since there hasn’t been any activity here in 2 weeks, I’m going to mark Jonah’s solution as the answer and close out the thread. If anyone finds they’re still having problems shoot an email to pro a/ tri.be and we can re-open the thread as needed. Cheers!
Fantastic to hear Matt. Glad that the update got you where you needed to be. If you find down the road that any issues related to this return, let me know. I’m going to close this thread for now though. Cheers, and thanks again for your support/patience so far.
Hey there Paula. Just wanted to follow-up on this one again, as I haven’t heard from you since my post last week. Any thoughts or additional questions arise as a result of that? Let me know if so, and we’ll do what we can to get you what you need.
Hi folks. Thanks for the follow-ups here. There have been a number of folks commenting and so I’m going to do my best to address each of yours – going forward let’s break whatever remains as open issues out into their own threads, so we can get members of the support team to take a look directly.
*Andy*: sorry to mess up your alarm plugin 🙁 I hope it doesn’t create too much of a headache for you in that regard. You are absolutely correct about the template resetting, and that should be fixed for the next release. Where are you seeing 2.0.8 in the HELP tab? It’s showing 2.0.9 on my end (http://d.pr/i/qvy1), but I may be looking in the wrong spot.
*Antonio:* Glad to hear you got this sorted. As I noted to Andy there, the template / settings reset issue is a known one that we’re working to patch for the next release. Good to know other users have a workaround as needed based on the tip you provided, though.
*Marc:* I definitely feel your pain on the Settings reset issue, and apologize for the inconvenience on that end. Rest assured that is a top priority for the next build. In terms of the widget, that’s also a bug we introduced this go-around but have a fix available. You’ll want to use this file: http://cl.ly/code/2g3x3R0c0z1s. Just replace the code in the file or the file itself in /wp-content/plugins/events-calendar-pro/views/events-advanced-list-load-widget-display.php. Basically, the problem was that we reintroduced some code that doesn’t respond to the checkbox setting to not show the end date. If you find that you’re having problems with this new code (it’s working fine on my end), let me know.
*Jacob:* your widget settings should be fixed via the item I shared with Marc above. Let me know if not. the 500 error you’re receiving isn’t something we’ve had other reports of or been able to recreate…I’m wondering if something specific to your install is at play here. It is inevitable that the more events there are, the more impact that’s going to have on load time…but things shouldn’t time out by any means unless there is a limitation on your server. We can help out here but please open a new thread with a link to the site so we can check it out directly.
*David:* I believe your issue, too, is the same one that my suggestion to Marc above ought to remedy. Let me know if I’ve misunderstood you there, though.
*Angelia:* It sounds like, if I understand correctly, you’re all set in terms of updating the plugins. Great to hear on that end (sometimes the update prompt takes a few days to hit). The issue you’re noting here doesn’t sound to be specific to the plugin, though, which makes me think something else is at play – a conflict of some kind, for example. Have you re-configured your Events -> Settings page (specifically the events SLUG and the TEMPLATE) and find that this issue still persists? If so, do you mind posting a new thread with a link so we can try to assist directly?
Happy Monday, Matt. I saw that Tim sent you an email with some guidance and best I can tell you should be in a good spot here – can you confirm that you received the last note and whether you need anything else as a result of it?
Hi again Paula. After some troubleshooting this morning with our dev – in which he too was able to import your events without issue – we’re of the belief that this is being caused by a server configuration issue. Possibly that the site is blocking remote HTTP requests or something similar. Who is your web host? Do you have a contact there who you can check with to confirm if remote HTTP requests are being processed or blocked?
Thanks Paula. I’ve recreated your settings pretty much exactly, and weirdly everything related to this account is working fine: both events import without issue (without using the App ID; just plugging in the username on Settings), and I see all the available events to import on the IMPORT FB EVENTS screen.
I’ve asked our dev Paul to take a look, as I’m out of ideas here, and he’ll be replying directly shortly. Please leave the backend credentials you previously provided active while he takes a look (we won’t change anything without asking you first).
If you can, I’d say go ahead and update WordPress + your theme, since I see updates are available for both, and it’d be good to get those current in the off-chance they have bearing here. Thanks again for your continued patience on this. Please let me know what else I can do in the interim.
Hey CoachB. The renewal fee for the Developer license, while still not actually something we’ve officially defined, should be cheaper than the initial cost you paid (the same is intended to apply to all license types).
Based on how the license works: it is required for plugin updates & access to support. The plugin doesn’t stop working without a license, beyond that — all the features remain in place. This quickly can become obsolete without a key, though, since we release monthly maintenance updates and you need a key to update to the latest PRO release. Once you start running the plugins out of sync (say, you update the free The Events Calendar to 2.0.9 but don’t have a key for PRO, so it stays on 2.0.8) there are going to be bugs and other unintended quirks. Similarly, if our support team is going to help resolve an issue on a site, that site does need to have a valid license in place.
As the account holder, you do have the option to disconnect keys at will (from here on the tri.be site, meaning you wouldn’t need access to the site-in-question). So if a client stopped using your services, you could disconnect their key.
