[John Niernberger]

Sorry, but this is terrible advice. Editing core files which will just get overwritten in the next upgrade is not a proper answer to this issue.

Unfortunately a proper answer isn’t easy to come by because of the way this was implemented – template-tags files aren’t made to overwritten like the view files are, and there doesn’t seem to be a filter I could easily find to override that function in a theme’s functions.php file.

So CSS is the best solution to avoid javascript. Put something like this in your child-theme’s css file (or wherever you make CSS additions), changing ‘Register Now’ to whatever you’d like:

.tribe-events-event-cost button.tribe-button {
text-indent: -9999px;
line-height: 0;
}

.tribe-events-event-cost button.tribe-button:after {
visibility: visible;
content: “Register Now”;
display: block;
line-height: initial;
text-indent: 0;
}

[John Niernberger]

This reply is private.

[John Niernberger]

Yeah, a somewhat bizarre decision to add a feature like this with no way to disable it. There are actually privacy issues involved – some event attendees lists shouldn’t ever be made public, and the expectation by attendees is that they won’t be.

Anyway, a better option than overriding the template to remove the checkbox (since that override is going to require maintenance moving forward) is to add this to your theme’s css file:

.tribe-tickets-attendees-list-optout {
	display: none;
}

• This reply was modified 10 years ago by John Niernberger.

[John Niernberger]

Thanks for this @mmirus, the other code didn’t work for me but this does… though insane we have to do this… 🙂

[John Niernberger]

Actually, should have mentioned this – @eguidemagazine – you say you’re having to enter the info 3 times – I actually wrote a blog post about this, but the gist is use the “Post Duplicator” plugin (that specific one – there are many similar ones: http://wordpress.org/plugins/post-duplicator/).

This way you can create one event, duplicate it 2 more times, then tweak those. Will save u lots of time while waiting for an update if you’re doing this often.

[John Niernberger]

+1, looking forward to this. 🙂

[John Niernberger]

Hi Kelly —

Thank you. Really do appreciate your well-considered reply – it makes a lot of sense that this is a bit more subtle than I originally thought. You’re absolutely right. Let me mull this over – if I decide to take a crack at coding something, I’ll definitely reach out to the devs with questions…

And I’ll almost certainly post a suggestion as well, though as you say maybe one that is a little more broad than my original request.

We’re new to selling tickets on the site, so this “issue” might not even come up very often, or ever again, so it might be worth holding off for us – though it did come up in one of the first three purchases.

Best,
john.

[John Niernberger]

@Bernard – where were you yesterday when we needed you, lol. 🙂

[John Niernberger]

Didn’t fix mine actually… patched as @Peter said, then changed the single quotes to double as @viwedis suggested but don’t think that would matter in this case. Anyway, still no posts – either in the calendar or in the widgets (though at least I *have* a calendar and widgets, before it was blank. I’m thinking there’s more bad queries elsewhere as well. At least the code is nicely commented so we know who wrote them. And – smoking gun – these queries say ‘since 3.0.2’. 🙂

[John Niernberger]

+1, no events on front-end.

[John Niernberger]

I’m getting this too — the default URL for my calendar is:

http://domain.com/events/

Which returns the 404 in the page title but shows the July calendar (because we’re in July). But if you move forward a month (to August in this case) – this URL is fine:

http://domain.com/events/2013-08/

Then if you move back to July, this URL is fine too:

http://domain.com/events/2013-07/

So the base URL is having some issues… it’s displaying the calendar ok, but WordPress thinks there’s nothing there… at least in my case.

Is the same thing happening to you Cynthia?

[John Niernberger]

Thanks @sean — great to see an example. Yes, I don’t mind that at all. Appreciate the link!

[John Niernberger]

I’m getting an “events has passed” message on all venues — the time shown is the time the venue was entered, so therefore it’s naturally always in the past. I’m running 2.0.6.

Again, this isn’t for events, this is for venues, so “event has passed” has no relevance.

Thank you!

[John Niernberger]

Wow. From despair to success in one fell swoop. To make a long, sad story very short — just erase your /themes/thesis/events/ directory altogether. Carlos is right — with nothing in the way TECP 2.0.6 plays perfectly well with Thesis 1.8.3.

[John Niernberger]

That would be *huge* Rob – I think a lot of people would benefit (Platform Pro users and other theme frameworks).

I’m using 2.0.3, WP 3.3.1 and Thesis 1.8.2 – just haven’t upgraded to 1.8.3 yet (it’s relatively new) but don’t see how that would affect it.

Basically my issue was I was getting an incomplete header – it wasn’t pulling custom CSS files and some other important scripts.

Please keep my updated, happy to PM you a URL…

Best,
John

[Author]

Posts