[Barry]

Hi mediawire, all sorts of customizations are possible – we can’t always provide a complete drop-in solution but definitely create a new thread (so we can focus on the main problem in this one) and if it’s possible to point you in the right direction one of the team will happily do so 🙂

Regarding the drafts missing information, we’ve been unable to replicate this so far. I do note that you tried deactivating all other plugins (except for The Events Calendar and Community Events, hopefully!) – but can you also confirm if at the same time you tried running through this process with only a default, unmodified theme such as Twenty Twelve running?

Thanks!

[Barry]

Can you link us to a downloadable .zip containing your theme? Posting it on Dropbox, Droplr or a similar service – or just uploading it to your WordPress site – is one way of doing this.

[Barry]

Hi Tom,

Thanks for linking to those. It does seem to reinforce what I was saying earlier, however, with regard to this note from Paul (who I think is part of their support team):

i have to talk to kaptinlin if it is possible not to load that script while in the screens of the the events calendar.

It’s not the responsibility of our code to proactively tidy up after other plugins and stop their code from running where it shouldn’t be. We have already spent some time looking at compatibility with Striking and the result was that, at least for the foreseeable future, we simply view Striking as being incompatible with The Events Calendar.

We’re sorry we can’t do more to help with this one but we can definitely offer you a refund if you want to follow the steps I outlined above 🙂

Thanks again,

Barry

[Barry]

Hi Patrick, great idea! Please do consider making a feature request for this:

http://tribe.uservoice.com/

[Barry]

That is indeed our recommended workaround, Ulli, thanks for sharing. We are definitely aware of the issue and a forthcoming maintenance release should address it.

Thanks for your patience in the meantime!

[Barry]

Hi t3admin,

Actually, its up to plugins to be theme compatible not the other way around fyi.

That does imply we are responsible for the problem – but I don’t agree, especially when the problem affects the admin environment, as it seems to do here.

Whether we are talking about themes or plugins doesn’t really matter: if one component (Striking) impacts adversely on the admin screens of another (such as those that our own plugin generates and is responsible for) – perhaps by enqueuing scripts and styles that don’t belong there – then it would seem clear that the responsibility lies with the component which adds those unwanted scripts.

That said, we want to support you as best we can and if in this case it means providing a refund so you can move on to a plugin that isn’t affected in this way we will happily consider your request. Please email us, including a link to this thread, and one of the team will help you as quickly as they can: pro (at) tri (dot) be

Sorry it didn’t work out for you.

[Barry]

To confirm though, do you find this is present for pages and posts? If so, does switching your theme to a default one such as Twenty Thirteen resolve this (just so we can figure out what’s causing the problem)?

Thanks!

[Barry]

@mediawire it may not work in every single case, but for most people it has been successful so it definitely could be worth reviewing the steps outlined in earlier posts against the changes you made.

@Ryan: because you mention ecp-single-template.php I wonder if you are using an earlier version of our plugins, such as 2.0.11? This template is no longer in use in our current release (which this thread relates to).

@everyone! Once again please accept our apologies for the inconvenience this set of issues has caused. Based on feedback in this and other threads however the workarounds posted earlier seem to be successful for most people – in light of which (and bearing in mind substantive fixes will be making their way into our forthcoming maintenance releases) I’m going to close this thread.

If anyone needs further support on this or any other issues please create a new thread of your own and try to stick to one issue per thread – it makes it a lot easier for us to help you. Thanks!

[Barry]

OK, thanks for sharing. I don’t think either of those things would impact, but it’s definitely worth reviewing things like this.

What we’re doing right now is working with another customer who has reported a problem that is very similar in nature and hopefully that will turn up some answers about what is causing this. That may take a number of working days to complete – so this thread may ‘fall silent’ for a period, but do know that that doesn’t mean we’ve lost interest or have stopped working on it.

Thanks for your continued patience 🙂

[Barry]

Thank you, for your patience and understanding on this one. If anything else crops up do go ahead and create a new thread. Thanks!

[Barry]

I think you’re right, something is definitely out of kilter. May partly be confusion over recurring events – in any case I’ll report this and we’ll aim to investigate and get a fix out in one of our maintenance releases.

Thanks for digging in and reporting this 🙂

[Barry]

Excellent, thanks very much for your continued cooperation.

[Barry]

Hi Amanda!

Sorry for the delay, first of all.

So I can see the code you referred to in page.php (the bit of information I was missing was that a static front page had to be set up) however it does not work as expected when I test it – even if I quote the category slug (the slug in your code isn’t in quotes which could be causing a problem anyway) and change the category to one that’s valid in my own environment, or even if I remove that parameter completely – so I’m not entirely sure how you managed to get it working previously.

Without this starting point and without being able to see the code offered up in the other thread it’s really difficult to help.

So, since this sort of customization work in any case is generally outside the scope of what we can help with, unfortunately, I think on this occasion we’re going to have to bow out.

Sorry we can’t do more this time round.

[Barry]

@gracebiblechurch: can I just confirm if you are happy for another team member to access your site and perform some further troubleshooting steps?

[Barry]

OK – glad the first issue was solved. Would you mind breaking the second issue out into a separate thread? It helps us keep things organized, makes it easier for other users to research possible answers and actually allows us to help you as quickly as possible.

Thanks!

[Author]

Posts