[Barry]

Hi Mickey, I’m not at all sure that is the same issue. Can you create a new thread of your own for this?

Warning: Missing argument 2 for TribeEventsRecurrenceMeta::addMinToStartDateInFields() in C:\xampp\htdocs\vivatou\wp-content\plugins\events-calendar-pro\lib\tribe-events-recurrence-meta.class.php on line 789

I’m not really sure how or why that would happen, however I wonder if something might have gone wrong during the update process. Are you in a position to create a new test installation of WordPress, with just our plugins running initially, and see if you can replicate at that point?

[Barry]

OK, great. That would definitely be problematic.

Can you post your System Information in here (it can be found in the Events > Help admin screen) and also confirm that – as well as deactivating your other plugins you switched to a default, unmodified theme such as Twenty Twelve and let me know if the problem still persisted under those conditions?

Thanks!

[Barry]

Hi Stéphane,

Happy to help!

I would love if you could point me to what I would need to check for in the code to catch a user selecting another view

In the snippet I provided you can see the following piece of code:

if (tribe_is_view('upcoming'))

So what you could do is add a set of tests to check if the requested view is something else (photo, week … etc) then set a variable to record that fact and display an appropriate message to the visitor to help them understand what’s happening (if that’s the reason you want to do this).

If you actually want to catch it before the request even hits the server you would have to do something with Javascript to listen for change or click events and take things from there – it’s difficult to be more specific than that because I’m not sure what the end goal would be in this particular scenario, but there are definitely lots of avenues to explore 🙂

Thank you so much again and you can consider this resolved.

Fantastic – good luck and have fun with this!

[Barry]

OK, of course that event is now in the past so it’s difficult to assess this (unless perhaps you could create a new test event?) – but can you confirm your WP and PHP date time settings are all in order. One other though, though it shouldn’t impact, is that you are using default or “ugly” permalinks.

In the past this has been known to trigger a range of issues – just to be safe would it be possible for you to switch to “pretty” permalinks?

http://codex.wordpress.org/Using_Permalinks

Thanks!

[Barry]

I certainly didn’t see your post as an insult and we welcome any feedback like this, it’s important we continue to build our understanding of your and all our customers’ needs and expectations. Really I only wanted to communicate our own position and I can definitely see that this in a way puts you between a rock and a hard place.

These situations can sometimes be painted as a conflict with theme vendors on one side and plugin vendors on the other. I don’t think that’s really the case and I’m sure most vendors in this sector strive to make their work compatible with an otherwise stock installation of WordPress and follow best practices to the best of their ability – at the point where additional components are pulled in (and potentially conflict) however I think the responsibility, certainly where the plugin or theme price point is similar to ours, really has to shift to the person doing the integration.

With all that said, this isn’t a blame game and again I just want to be sure you understand that we genuinely strive to do all that we reasonably can.

At any rate, looking at your site it seems you have disabled the event search bar: is that a solution/workaround you are happy with here?

[Barry]

Hi callanwolde,

There are definitely some areas of the forum that could do with a little TLC and we do hope to get on top of that at some point – it’s been a lower priority than product development and support though and unfortunately that means it doesn’t always offer an ideal environment to share code and troubleshoot issues – so please accept our apologies on that front.

You’ve asked what are really quite a few different questions so I’ll try my best to answer them in turn, but it may be best to break them out into separate threads (bearing in mind much of this comes down to custom development and so we can’t always offer too much help with everything you’ve detailed).

Event cost

The tribe_get_cost() function probably isn’t going to operate quite as you might expect if you are concerned with the price of a WooCommerce Tickets product since that field (the event cost) is really just intended as a way to communicate pricing when no ticketing add-ons are in use.

What you probably want to do here is obtain the WooCommerce product object and grab the price that way. Delving in to WooCommerce’s own documentation is probably a good idea here.

I wrote a set of helpers to make this sort of work easier and there are some sample recipes to show how it works. However, please do note that isn’t an official Modern Tribe project but simply some code that is available for you to try if you want (and at your own risk!) – but it might be helpful here.

Additional fields

You’ll find you can use a few HTML tags but others may be stripped. For example, a <strong> tag should work without any issue. The best thing to do here is experiment 🙂

echo tribe_get_custom_field('_ecp_custom_1', $event->ID)

This isn’t an uncommon mistake – but really you need to pass in the field label when working with tribe_get_custom_field() (in other words, the “human readable” name given to the field, such as “My special field”).

Hope that helps!

[Barry]

Am I correct in thinking your sister site is still using the older 2.0.11 release? The basic problem may be that on the site with the problem the widget structure has changed (in line with the update to 3.1) but the corresponding CSS rules you/your developer might have added have not been updated.

It doesn’t actually look too bad to me, but you can target it and tweak it to make it look how you want with rules like this (this example gives it a white background, as on the sister site):

.widget-wrap .tribe-mini-calendar-grid-wrapper { background: #fff; }

Which you might add to a custom tribe-events.css stylesheet. There are details about implementing this and more in our Themer’s Guide – does that help at all?

[Barry]

Hi theresajennings:

Just to be clear and using the events list widget on our widgets demo page as an example, do you mean you want the text “Upcoming Events” (or whatever the widget title is set to) to link to the main calendar page?

Thanks (I just want to be sure I give you the correct advice here)!

[Barry]

Can you confirm which URL I should use to see this? Although I could locate a calendar at the URL you provided when you opened this thread it did not seem to be one that is generated by our plugin.

Thanks!

[Barry]

Hi liblogger,

I can’t currently see map view on your site: have you temporarily disabled it and if so would you be able to enable it again and provide some notes about which venues are missing so we can take a look at the issue in situ?

Thanks!

[Barry]

Hi moneytalks: we’re equally keen for that plugin to reach its inaugural release – but I’m afraid at this point we cannot provide any definite dates and can only say that it should arrive shortly 🙂

Thanks for your continued support and interest in this latest plugin.

[Barry]

Hi jrascoe: sorry to hear you’ve experienced ongoing issues here.

Can you confirm if this happens with new events (ones created after the update) and does editing and re-saving affected events have any impact?

Beyond that, now that you have updated if you try our standard troubleshooting steps (deactivating all other plugins and switching to a default, unmodified theme) does that resolve this?

Thanks – we’d love to get to the bottom of this.

[Barry]

Hi Mike: that certainly sounds like it would save you a lot of time. I can think of a few challenges in implementing something like this – particularly with regards to ticketing data – so what I’d like to do is take this idea and discuss it with the team to consider what’s involved.

If you can bear with us a few days I’ll make sure to report back, even if that’s only to say it’s on our to-be-determined list. With that said, if you are also game to post this request on tribe.uservoice.com it might encourage some discussion and further ideas from others who are interested in this sort of thing, which could be valuable information.

Cheers!

[Barry]

I don’t believe it does, but that’s a great idea and I’d encourage you to post a feature request on our UserVoice page – that will ensure there is a record of the idea and also allows other users to voice their support – though not the only criteria by any means it can be a helpful tool to help us prioritize new features.

http://tribe.uservoice.com

Thanks!

[Barry]

Hi virtualdavis,

There isn’t actually any baked in means of doing this – that particular setting only impacts on The Events Calendar’s own list style views. However, you can probably tweak things if you’re happy to drop some code like this into your theme’s functions.php file.

Does that help at all?

[Author]

Posts