[Barry]

Hi punctilio,

Unfortunately it looks like whatever code you might have posted has been stripped out by the forum software: for the time being it’s best to link to any code you want to share on a service like Pastebin or Gist.

In any case, I’m afraid we’re not going to be able to help with this one – you’re definitely welcome to customize the views (or even build new ones that meet your exact needs), but you will need to dive into the code and figure that sort of thing out for yourself. Sorry we can’t do more to help on this occasion, but in depth customizations are really something for you to tackle (and though some things like this may initially seem fairly simple I suspect there are a lot of changes on various levels you would need to make). That being the case I’ll go ahead and close this.

If we can help with anything else please do create a new thread and one of the team will see if they can assist 🙂

Thanks!

[Barry]

Hi David,

We do appreciate that puts you in a bit of a quandry, ultimately of course you are going to have to do what ever is best for you – at this point in time I don’t think we are going to spend a great deal of time on workarounds for NextGen since, from our standpoint, the issue lies with their code.

We also appreciate your opinion on operating within the WordPress ecosphere which can indeed present varied and unique challenges when integrating many and varied technologies from different vendors. From Modern Tribe’s perspective, all we can really do is strive to be as fair as possible in dealing with customers and fellow development shops/service providers.

Since the current incompatible status of NextGen sits at the crux of this thread and, unfortunately, we are unable to do a great deal about that I will now go ahead and close this thread.

Of course if you have any other issues please feel free to create new threads as required.

Thanks again!

[Barry]

That’s right – you’d need to do this at code-level – whether in a template or somewhere else, rather than pasting it into the post editor.

[Barry]

That does make sense and you’d have to pick between whichever of those approaches you are most comfortable with – I’m afraid assisting with customizations of this depth isn’t something we can do here on the support forum.

That said, do feel free to post a feature request over on tribe.uservoice.com – it certainly sounds like something that could make a worthy addition to the plugin 🙂

Thanks!

[Barry]

You could certainly give it a try 🙂

* events-calendar-pro/resources/widget-calendar.min.js
* events-calendar-pro/resources/widget-calendar.min.css
* events-calendar-pro/resources/widget-calendar-full.min.css
* events-calendar-pro/resources/tribe-events-pro-full.min.css

[Barry]

Yeah unfortunately it seems shortcodes in those fields aren’t currently parsed. I’ll log that as a separate issue to be addressed in a future release, in the interim you could add this snippet to your theme’s functions.php file and it should ensure any shortcodes are processed as expected.

[Barry]

Hi Steve – it seems not to be, unfortunately, at least not on your homepage – so it is pointing to perhaps some non-standard practices going on at theme level.

(Quick sidenote – I will probably be unable to check in and update this thread until working hours next week. Thanks for your patience!)

[Barry]

Hi Steve – right now if I visit your front page I can still see the mini calendar widget but it appears no JS whatsoever from The Events Calendar is being loaded (though our CSS is) … might that be the result of your troubleshooting activities above?

[Barry]

Definitely – here’s some code to get you started, you’ll probably need to play with it and tweak it slightly to get exactly what you want, but it should provide a starting point 🙂

[Barry]

Fantastic!

[Barry]

Hi David, thanks for digging in to this.

It seems you’ve already effectively narrowed this problem down to NextGen which we already knew was the cause of other conflicts, though the common thread in all cases is that it is filtering and modifying – and in this case breaking – database queries that it itself is not issuing.

When another plugin does that it’s very hard for us to write code to counter it and really it would be wrong for us to try and clean up after third party code.

For that reason, as it stands, I’m afraid there is little we can do to help with this. NextGen for the time being is firmly on the incompatible plugins list.

[Barry]

There are lots of different places that events are listed – do you want to change all of them (and have you tried changing the WordPress time format setting)?

[Barry]

Can you try something like this?

.tribe-mini-calendar .tribe-events-has-events:hover a:hover { background: #ff0; }

[Barry]

How are your $current_date and $end_date variables formatted? Are they in Y-m-d (yyyy-mm-dd) format?

[Barry]

Hi Derek, could be you just need to be a little more specific with your rules. Can you try:

.tribe-mini-calendar-nav span { color: #e8d8ad }

That should change the prev/next arrows and month name to a cream colour. To target the current day, try something like:

.tribe-mini-calendar .tribe-events-present { background: #c0f }

The numbers can be changed with rules along these lines:

.tribe-mini-calendar a { color: #450 }

Does that help?

[Author]

Posts