List view page header

[George]

Hey Paul,

I am so sorry about this issue here – I actually made a pretty big mistake!

I’m really sorry about that Paul – the mistake is that the code I shared for changing this text will not work until the next public release of the plugin. When that release comes out, the code I shared in my original Gist (the one here) will work fine, but in the meantime, to change the Event/s instances to Class/es your best option is to instead use the code in this knowledgebase article → https://theeventscalendar.com/knowledgebase/changing-the-word-events-to-something-else/

I’m sorry for the confusion on my part! I’d recommend removing any customizations you have made to the plugin files, and then using the code I linked to above. Then, when the new update comes out, use the code in the Gist I shared earlier instead (https://gist.github.com/momnt/8cb846ebd45369e38b27).

I hope this actually helps! I’m really sorry Paul, let us know if this new code works better for you.

Cheers, and thanks for your patience with this issue,
George

[Paul]

Hey George

That no problem at all! – That’s worked pretty perfectly now so thank you!

I don’t suppose you managed to figure out how to remove the grey top title bar in all the views? if not no worries lol

Cheers, Paul

[George]

Hey Paul,

I’m glad the code is working. As for hiding the header, the original CSS I shared with you does work. An alternative to that CSS is this:

body.events-archive .df-page-header {
    display: none !important;
}

This code will work, but depending on where you add it, it may not take effect (this is what it seems based on your feedback so far, at least). I’d recommend avoiding the Editor that is built into your WordPress admin area, and manually editing files over FTP and re-uploading them to your site after making edits. You can alternatively make a Child Theme.

I hope that information helps Paul! Since those are are related to some customizations, and your original queries here have been resolved, I’ll go ahead and close up this support ticket. If other issues arise, come back and open a new ticket at any time!

And remember – after the next plugin update, the original code I shared with you will work, and is better than the current solution. So for now, use the solution in place. But bookmark this ticket for future reference, or make note of that Gist link somewhere for yourself, and after updating to the next version, get rid of the code you added now and add the other, simpler code in its place. Should work just as well 🙂

Cheers!
George

[Author]

Posts