Hi @uncovery,
Great question!
I’m afraid that here in the free support forums we’re rather limited in terms of how much depth we can go into on items like this, but I’d definitely like to at least steer you in the right direction if I can.
When certain conditions are met, Twenty Seventeen adds various body classes to the page. One of these – .twentyseventeen-front-page – is needed to trigger the larger header image you are asking about.
With that in mind, adding your own logic to get that extra body class in place when the event page is used as a static front page is probably going to be a great starting point for any tweaks you might want to make.
I hope that helps!
Hey there, thanks for the “pointing in the right direction”. While I still need to figure out how to do this, I have to say that the issue at hand here, from my perspective, is a bug.
A plugin that is offering to be a front page for wordpress should – in my opinion – not change that front page’s layout. If a “normal” static page would be at the front, the theme uses the correct template. Only your “virtual” page does not use it.
I have to admit that I am not 100% sure if the bug is in the theme or your plugin, and most likely either author will point at the other, but to me this is a bug that should be fixed.
-
This reply was modified 7 years, 4 months ago by
uncovery.
-
This reply was modified 7 years, 4 months ago by
uncovery.
And one more thing: The template HTML that you can add under “Advanced Template Settings” don’t work with the static frontpage.
-
This reply was modified 7 years, 4 months ago by
uncovery.
“… when the event page is used as a static front page … ” if detecting this would be so easy…
I have to admit that I am not 100% sure if the bug is in the theme or your plugin, and most likely either author will point at the other, but to me this is a bug that should be fixed.
I think statements like “either author will point at the other” are a little unfair.
In my last reply, for instance, I didn’t suggest this was the result of ineffective coding on the part of the Twenty Seventeen authors or that the onus was on them to fix it.
Personally, I disagree that it is a bug (I see it as an integration issue), but I don’t really want to argue over definitions of what is and isn’t a bug, either 🙂
It would certainly be smoother if we took care of adding the missing body class and I’ll log a ticket on our internal ticket to make that happen in a future release.
And one more thing: The template HTML that you can add under “Advanced Template Settings” don’t work with the static frontpage.
Seems to work for me, but I’d be happy to take a further look at this if you can provide more notes and a link I can look at.
Creating a fresh forum topic for this separate issue would be best, though.
Thanks for the feedback!
I think statements like “either author will point at the other” are a little unfair.
Look, I did not mean to be nasty, please don’t feel accused by that.
Anyhow, in the end I had to move to a different calendar plugin. The site I did this for does not need such a sophisticated plugin and I had too many issues with this template topic.
I was not able to insert the calendar into a page and put that on the frontpage and I was not able to reliably fix the frontpage template. Paying for the shortcode implementation would have been the only way, but there are other free plugins that have less features and for the small site I need it for the price is too high.
thanks a lot for the support you have given here, I understand that you don’t go further than you did. It’s a great plugin.
OK – well sorry to hear that you’ve moved on (though it’s great to hear you found something that is a good fit for your needs).
Perhaps you’ll be able to revisit The Events Calendar in the future.
We released an update for this issue. Can you update your plugins (preferrably on a staging site) and see if that resolves the issue.
https://theeventscalendar.com/maintenance-release-week-13-november-2017/
Thanks
Courtney 🙂