[Barry]

Hi there webmasterena,

That is a little strange :-/

I may be experiencing a theme conflict

Have you been able to confirm that it is a theme conflict – if you switch to a default theme for instance does the problem remedy itself? I’d just like to be sure we’re looking in the right area.

Thanks!

[Barry]

Hi there klikensteen,

That looks like a great start 🙂

I’m afraid though that custom development tasks like this are really something we have to leave in your hands – the best idea is to look at the code of existing filter classes and model your own work after those.

Good luck!

[Barry]

You’re right: there does seem to be a bug here.

I’ve reported this and we’ll do our best to fix it as quickly as we can. In the interim would it be viable to change any organizer names containing the & symbol so that they use and instead?

Similarly if any other special characters are in use would you be able to find a regular word that can take its place? That may provide you with a suitable workaround until we can deliver a fix.

[Barry]

Hmm, definitely possible. You’d need to define your criteria for these long running events first of all (any event running for 5 days or more, or whatever works for your use case) and do two things:

• Build a separate query to retrieve those events and list them above the month view grid
• Either modify the queries used to populate month view to do the opposite and not retrieve long running events, or, eliminate them from the result set before they are displayed

We do almost have a parallel to this behaviour in day view (where ongoing events are listed at the top) and, in a looser sense, in week view where all day events are separated out. So you could potentially look at the code and see how that is implemented – but I suspect you’d effectively need to build it out afresh for month view.

[Barry]

Hi there ideasandbox,

Interesting idea!

We’d be happy to consider putting together a tutorial for this if it’s something that could benefit other users, too … to that end, definitely feel free to post this as a feature request over on UserVoice 🙂

tribe.uservoice.com

In the short term you’d need to implement this as a customization. The Themer’s Guide is indeed a great starting point though you may alternatively wish to consider setting up a filter via the tribe_events_get_current_month_day hook if you’re comfortable working with actions and filters and modify the day’s data that way.

It would however be a customization we’d need to leave you to drive forward at this time, I’m afraid.

[Barry]

Actually you don’t.

Thanks for clarifying! Apologies on that count, the wording on their wordpress.org plugin page implied that there was a separate version available.

In any case, I can now replicate and the problem is as I originally pictured.

In their function submitTestimonialForm() (found in easy-testimonials/easy-testimonials.php lines 455-607) they are doing the following:

do_action('wp_insert_post', 'wp_insert_post');

This is not the same thing at all as doing:

$new_id = wp_insert_post($post);

(As indicated in the response you copied, a few replies ago.)

The wp_insert_post action is ordinarily fired by core WordPress code – not by plugins – and it’s a reasonable expectation made by our own plugin to expect at least two arguments to be passed, whereas the way Easy Testimonials is doing things just one argument – a string – is passed.

I’m not quite sure why they need to do things this way but if they really must I’d recommend they follow the same pattern as WordPress itself and pass three arguments – the first being an integer (post ID) rather than a string, the second being the post object and the third a boolean value indicating if the post was actually updated.

Otherwise, conflicts like this one can and will happen, I’m afraid.

 

[Barry]

Hi! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

[Barry]

Hi! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

[Barry]

Hi! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

[Barry]

Hi! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

[Barry]

Hi! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

[Barry]

Hi! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

[Barry]

The link you have provided is the same plugin. The Pro Version just allows more sites for the plugin to be utilized.

I actually believe I’d need the PRO version of that plugin to replicate – at least if the problem relates to the form generated by the [submit_testimonial] shortcode – as noted in their installation instructions.

If you could share a copy I can certainly take a quick look (trying to replicate on your site won’t really give me any insights into the underlying problem, unfortunately – I’d really need to test this out locally) 🙂

[Barry]

I took this sentence to mean that they are doing it directly:
Yes, we do call wp_insert_post, on the New Testimonial Submission form.

I think they mean they are calling the function (which is perfectly fine), what I meant was they might be doing something atypical like firing the action of the same name directly – but without passing the required number of arguments. That was just a theory, though 🙂

I’ll take a look and see if I can replicate, please bear with me a little longer.

[Barry]

Hmm, interesting – that’s not quite what I meant but I’ll take their answer to mean they aren’t doing it directly. Can you confirm if this is the same plugin you are using?

https://wordpress.org/plugins/easy-testimonials/

Or do you have a pro/premium version (and/or is it possible to replicate the same problem with the version I linked to alone)?

[Author]

Posts