[George]

Hey @charrame,

Apologies for the delayed reply, we had a three-day holiday in the US and I’m just coming back from that today! Thank you so much for your patience.

As for your issues, I’m curious:

1.  how exactly did you make the “organizer” URL be /organizador instead of the default /organizer ? And the default /venue be /lugar ?

2. If you temporarily disable this method on your site, and then go to Settings > Permalinks in your admin area, and just click “Save Changes” without actually making any changes, do your organizer and venue URLs work correctly?

Thank you!
George

[George]

Thank you so much for your continued patience with this! I am so sorry that this issue persists even after all that testing.

I can still not reproduce this issue, so unfortunately the best recommendation I can think of at this moment to hold off for a bit and wait for our next plugin release – it will be happening this week, barring some weird alien invasion or other catastrophe that prevents us from launching 🙂

Once this new version is released, I’d recommend updating to it on your site and see if that improves the behavior of recurring events at all.

Let me know what you think about this! If you don’t want to wait for the official release, you can get “Release Candidates” and manually install them at any time by going to http://theeventscalendar.com/my-account/downloads and scrolling down to the “Early Access” section. It just might be a lot simpler to wait for the auto-update option, and that “official release” code will include even more improvements than the release candidates, so it might be worth waiting. Your call though, of course 🙂

I’m very sorry about the frustrations with this issue and hope our new 3.12 code helps it in some way.

Thank you,
George

[George]

Cool, thanks for the update Gerry.

Best of luck with your site! 🙂
George

[George]

Sounds good Gerry, thanks for the update here!

Best of luck with your site,
George

[George]

Thanks for the code @Jako, and for your patience with my delayed reply over the three-day weekend here in the US – I’m curious about this because your file and code both look fine to me, but this works well for me on my testing site…

One thing worth trying is to modify the code so that, where you see me use this code:
strtotime( 'now' );

You replace those instances with this:
new DateTime();

Try doing that and see if that helps at all! e.g.:


add_filter( 'tribe_events_list_widget_query_args', 'tribe_support_1001539' );

function tribe_support_1001539( $args ) {
$args['eventDisplay'] = 'custom';
$args['start_date'] = new DateTime();
$args['end_date'] = new DateTime();

return $args;
}


I’m sorry that this hasn’t worked immediately for you thus far, and am sorry that I don’t quite know why. Hopefully this change helps!

— George

[George]

Hey Mark,

Multilingual plans can be hard to work with – I don’t mean to reiterate something I already said! Just wanted to highlight the fact that this category of plugins in general is notoriously problem-causing, so I would not necessarily recommend switching to another multilingual plugin for example (because there’s no guarantee it would work better, and would likely not work any better).

I think the best step forward to query the qTranslate support forums / channels, or alternatively look for help online about how to prevent their multilingual processing from affecting the “Ticket” object and thus, hopefully, keeping it from affecting the security code specifically. There may or may not be a way to do this – I am sorry to admit it, but I am not familiar enough with the qTranslate codebase to be certain about this.

But, essentially, if you can just exclude the tickets from being “qTranslated” then you may have some luck here! And for what it’s worth, despite multilingual plugins in general being problem-causers, qTranslate itself is one of the best ones out there and could probably work here.

Is this information helpful at all? Let me know!

— George

[George]

Hey Ruud,

I’m sorry, but I unfortunately do not understand your question here! 🙁 I’m so sorry about that! Can you rephrase your question, and perhaps provide some screenshots for example of what you mean here?

I’m really sorry Ruud, I just want to make sure I understand your question so that I can best help you out.

Thank you!
George

[George]

Hey @Laughmasters,

There should be no visible difference as far as users are concerned, in any view. This is because, let’s say you have a recurring event that recurs “daily”, so in other words it happens on Monday, then Tuesday, then Wednesday, and then its last date is on Thursday.

On any calendar view, there will be one event on Monday, Tuesday, Wednesday and on Thursday. 4 events listed, in other words, regardless of what view you’re in. And each event, if you go to the “single event” view for it, will say “Recurring event” and have the “View All” link.

Now, let’s say you split Monday off of the series. After doing this, nothing will change to the user: there will still be one event each on Monday, Tuesday, Wednesday and on Thursday. 4 events listed, in other words, regardless of what view you’re in.

The only difference is that if you go Tuesday’s event, or Wednesday’s, or Thursday’s, that “Recurring Event” and “View All” link will show up. But on Monday, that link won’t be there.

This example illustrates the feature, it will work the same whether the recurring event is daily, weekly, monthly, yearly, anything at all.

I hope that helps! Play around with this directly on your site and see for yourself how it all looks – it hopefully works well for you and meets your needs.

Cheers!
George

[George]

Hey Michal,

Thank you for the update here!

Unfortunately, there have long been compatibility issues with The Events Calendar and WPML. Buying the upgrade for WPML does not mean that these issues will be fixed on your site, nor will downgrading the version of Events Calendar Pro.

I’m sorry about this bad news Michal 🙁 The only action step I can think of from here would be to try running through our complete set of troubleshooting steps here → https://theeventscalendar.com/knowledgebase/testing-for-conflicts/

The whole time, however, leave The Events Calendar, Events Calendar Pro, and WPML active on your site.

Then, with those three plugins active, just check on the behavior of things after each step in the testing process. This process might reveal other potential conflicts on your site, which might be contributing to things and making them worse on your site. WPML indeed has compatibility issues but the recurrence type selectors and such should still work regardless, so there might be additional conflicts on your site…

I’m sorry for the disappointing news Michal.

Sincerely,
George

[George]

Hey Douglas,

Sorry you’re still having issues with things here – just to be clear, did you update the Release Candidates for all of your Tribe plugins or just Facebook events? If the latter, be sure to update all the rest of the Tribe plugins and see if this makes any difference with things…

I don’t mean to reiterate that point if you’ve already made sure to do so, just wanted to note that in case you hadn’t updated the other Tribe plugins.

Regardless of this, based on your note about your changed URLs you might also want to be sure to go to Settings > Permalinks in your admin area, and just click “Save Changes” without actually making any changes. This may seem like an odd thing to do but is a little “trick” within WordPress to get the permalinks across your site to refresh, which might help here.

Thank you for your patience! I’ll investigate these issues with our recent Facebook improvements because this lack of venue/organizer import was a big issue for me, too, and I’ve recently found it to be fixed.

— George

[George]

Good point @xrossglobalgroup, I forgot about the requirement of yours to keep it out of the query and am sorry about forgetting that detail!

Definitely do make your voice heard about this, we’d love your feedback on our official “UserVoice” page and anything you post here can get votes from other users → http://tribe.uservoice.com. We take that page and those votes seriously so please do post your feedback.

In the meantime, before closing out this thread, I just wanted to note that if you’re savvy with code a bit, you might be able to hide events that require passwords from various events views by using the WordPress filter pre_get_posts and using the array( ‘has_password’ => false ) parameter within the Query to only show events that explicitly do not require a password to view.

You can learn more about both things here:

• https://codex.wordpress.org/Plugin_API/Action_Reference/pre_get_posts
• https://codex.wordpress.org/Class_Reference/WP_Query#Password_Parameters

Just an idea, in case you’re able to write the necessary code there.

Sorry that you didn’t find quite what you needed “out-of-the-box” with our plugins – stay tuned for plugin updates and check the readme file “Changelogs” to see if any improvements in this area of the plugin are ever included in a release!

Cheers,
George

[George]

Hey Anthony,

No need to apologize at all – in fact, I sorry for here for misunderstanding your issue so thoroughly. Sorry about that! I appreciate your update and your clarification of things within it.

One thing left that’s worth clarifying is exactly how many events are all being imported…for example, you wrote this up above in your second post on this thread:

So it appears as though there is a problem with the ical export because there should have been significantly more (there are a lot, like well over 100 on the calendar).

If you have 100 events in the month of September alone, then there is indeed a problem in some sense and all 100 should be getting pulled in. If, however, those 100 events are over the whole year, and only 21 events are in September, then the importing of only those 21 events is not the result of an issue.

Further, the iCal “feed” is not quite a “feed” but actually just an auto-generated .ics file. So, as you noted, this will update on a monthly basis, instead of a true “feed” that is just a real-time stream of new content – does this distinction make sense?

I appreciate your patience with this issue and with my misunderstanding of things at first – hopefully we’re converging on some common ground here though, which I hope is the case so I can actually be helpful! 🙂

In closing, I’m wondering if you can clarify exactly what you meant in your last note here:

It is worth noting (and this might just be a setting, but it has now imported all of September’s events). So, it appears to only be updating iCal one month at a time.

This seems to be in line with the functionality I described above – in other words, that:

• The events/ical “feed” URL is really an endpoint for a generated, static .ics file, not a real-time stream of new events.
• This feed is a month-by-month thing, so if you have 100 events all year but only 21 events in September then only those 21 events will be in the .ics file for September.

I hope this all helps – let me know what your thoughts are on all of this and if I can help with anything else!

Thanks,
George

[George]

Nice! Thanks for the update regarding that (and for your patience with my delayed reply over the three-day weekend here in the US!).

As for your followup question here:

is there an option somewhere to position the next/previous month navigation in the Tribe Header instead of the Tribe footer?

There is unfortunately not an option to do this 🙁 It would, at this time, require template changes as described in our Themer’s Guide. Just in case you haven’t seen that guide already, it’s this one: https://theeventscalendar.com/knowledgebase/themers-guide/

Sorry to disappoint there! Let me know if you have further questions on this matter or anything else I can help with.

— George

[George]

Hey Tommy,

I appreciate the additional information here – and your patience with my delayed response over the three-day weekend here in the US!

Unfortunately, this seems to be the essence of your customization request and it leads to a bit of bad news:

I would like it to instead output the date and three additional fields that the user input when he/she creates the event in eventbrite.

The “bad news” here that achieving what you wrote, what I quoted right above, is actually much more complicated than it might seem and it involves adding a lot of extra code to our Eventbrite add-on, to pull in information from the Eventbrite API which itself might not allow the addition of extra information like this 🙁

I’m sorry to bear this bad news, but hope that some sort of consolation can come from the fact that there are many Customizers and developers out there who could probably help you pull this off. We have a list of them here, for example → https://theeventscalendar.com/find-a-customizer

Let me know what your thoughts are on all of this, and if there’s anything else I can help with.

George

[George]

Thanks for the update @littleshiva! I’m sorry that you had to go through that process anyways to achieve this, but am glad it’s finally working a bit more normally 🙂

Best of luck with your site,
George

[Author]

Posts