Forum Replies Created
-
Posts
-
Hi. I appreciate your question and the desire to customize it for your use. However, we cannot provide such in-depth customization help, per our Scope of Support / Terms.
If there’s a code snippet you’d like me to put some eyes on or something else I can help you with, please update this ticket or create a new ticket if it’s a separate issue.
Thank you very much for your understanding.
If you need some coding help, you may want to ask your developer or reference our documentation and list of known customizers.
Hi Gregg.
Sorry you’re seeing these issues.
Could you please provide a link to a single event that is causing the error in https://developers.google.com/structured-data/testing-tool/?
Hi Alexandros.
Here’s the documentation for the tribe_events shortcode: https://theeventscalendar.com/knowledgebase/embedding-calendar-views-tribe_events-shortcode/
While we don’t currently have documentation for the tribe_community_events shortcode, I tested it in a new WordPress Page and the form displayed just fine. Basically what happens is that if you create a page with that shortcode in it, visiting that page will just redirect you to /events/community/add (or /night/events/community/add in your case)
This is the text from Community Events’ readme file:
= Shortcodes =
Shortcodes are only available for users who have permalinks turned off; this method will NOT work if you’re running with a pretty permalinks structure. These will only work on pages, so don’t try them in posts/events/widgets/etc.
Shortcode information
Create a page and use the following:
[tribe_community_events_title] as title
[tribe_community_events] in contentYou can add this page to the menu.
This behavior may be different than what you were expecting.
If anything, I’d guess having “night” in your permalinks (assuming because WordPress is installed in that sub-domain’s sub-directory) could be at play here too, but that’s just a guess.
Please let me know if you need anything further with this and I’ll do my best to help.
Ariela, sorry for the mixup there. This thread was assigned to a bug that we ultimately couldn’t reproduce and therefore these follow-up notifications from Geoff came through. Although the content of his message (regarding iCal file export) wasn’t applicable to this thread, the result is the same: we tried to reproduce several different DST-related bugs that you and 7 other threads reported but we realized they weren’t all the same bug and we weren’t able to reproduce your bug.
All that being said, I know this isn’t pleasant news and I apologize for the miscommunication. I can confirm, though, that multiple team members worked on this, including myself, and so I know a lot of effort went into trying to reproduce and discover any and all DST-related bugs but we weren’t able to on our vanilla setups with WordPress, our plugins, and Twenty Sixteen theme. We tried multiple time zone settings and were eager to reproduce it because it’s a nasty result, but we weren’t able to.
Therefore, to move forward, please provide step-by-step instructions on a fresh install of WordPress, TEC, TEC PRO, and Twenty Sixteen. If we can reproduce it, we will surely fix it. Thanks for your understanding and effort here. I look forward to hearing back from you soon.
Dan, sorry for the mixup there. This thread was assigned to a bug that we ultimately couldn’t reproduce and therefore these follow-up notifications from Geoff came through. Although the content of his message (regarding iCal file export) wasn’t applicable to this thread, the result is the same: we tried to reproduce several different DST-related bugs that you and 7 other threads reported but we realized they weren’t all the same bug and we weren’t able to reproduce your bug.
All that being said, I know this isn’t pleasant news and I apologize for the miscommunication. I can confirm, though, that multiple team members worked on this, including myself, and so I know a lot of effort went into trying to reproduce and discover any and all DST-related bugs but we weren’t able to on our vanilla setups with WordPress, our plugins, and Twenty Sixteen theme. We tried multiple time zone settings and were eager to reproduce it because it’s a nasty result, but we weren’t able to.
Therefore, to move forward, please provide step-by-step instructions on a fresh install of WordPress, TEC, TEC PRO, and Twenty Sixteen. If we can reproduce it, we will surely fix it. Thanks for your understanding and effort here. I look forward to hearing back from you soon.
Thanks for all the details. Sorry you’re receiving this incorrect messaging. I see from your screenshot that those 3 plugins are at their latest versions.
I see from your https://theeventscalendar.com/license-keys/ page that your license keys for PRO and Eventbrite Tickets plugins are attached to “events.stcwdc.org”
Without re-assigning / moving any licenses, please share your System Information for both of your 2 sites. That will give me a lot of extra information to help diagnose the problem.
Thanks.
Ganga / Venkat,
Our tickets get sent via wp_mail() or WooCommerce’s email code. Therefore, if your tickets are being delivered inconsistently, you might need to install an SMTP plugin: https://wordpress.org/plugins/search.php?q=smtp (none are supported or guaranteed by us)
To be clear, this isn’t an issue specific to our plugin; email deliverability is an issue at the WordPress-level of your site or possibly even at the domain-level or IP address (if associated with SPAM, accurately or not).
Please let us know if you find out what solution worked for you.
Thanks!
Michael, you’ll need to submit that form to be considered at all. Obviously, I cannot guarantee anything, but you should complete the form to get that discussion started with the team that handles those requests. Thank you for your understanding.
For sure; no offense intended. Sometimes users appreciate being able to write in other languages if we’re not seeming to be on the same page.
We’ll close this thread; sorry I couldn’t be more help here.
Feel free to open a new thread if you feel the need to in the future.
Sorry if I didn’t fully answer your question. If you’d like, you’re welcome to clarify. (If you’re not a native English speaker, it may help to write it in your native language and we may be able to figure it out.)
Please note that threads get Closed automatically after a couple weeks of inactivity. If it does get Closed, please open a new thread, adding your current problem description and also linking back to this thread.
Thank you!
It currently gets that new permalink of /event/slug-2016-11-07/
However, I personally consider it a bug that /event/slug/2016-11-07/ continues to work and displays as if it isn’t broken out from the recurrence series. I reported/suggested to our developers that this is a bug (it shouldn’t display incorrectly like it’s part of a recurrence series), and that a valid resolution to the issue besides throwing a 404 error would be to redirect to the new permalink (e.g. /event/slug-2016-11-07/)
I cannot guarantee that’s the solution that will eventually be implemented, but I’d be surprised if our management team and developers disagreed this is a bug and that this is a valid solution.
Basically, if the event’s end datetime is greater than (not equal to) the current time, it is not a past event.
For further details, I’ll refer you to our tribe_is_past_event() function — github code at https://github.com/moderntribe/the-events-calendar/blob/4.3.2/src/functions/template-tags/general.php#L290-L315
Excellent. It turned out to be more work than I expected it would be, but I’m very glad it was worth it for you!
Yes. If you have a Personal license, only 1 site can be connected to https://theeventscalendar.com/license-keys/ at a time and the site that’s connected is the one that will receive the automatic updates.
If you disconnect Site A and then connect Site B, Site A will still continue to work properly and there won’t be any issue/change/error on Site A. It’s just that Site B will be the one that is allowed to receive the automatic updates.
I hope this clears things up for you.
