[George]

Give this a try instead; if it fails, then waiting for a future release is indeed the next best option:


add_action( 'init', 'tribe_remove_customizer_style_tags' );

function tribe_remove_customizer_style_tags() {

if ( class_exists( 'Tribe__Events__Pro__Customizer__Main' ) ) {
remove_action( 'wp_print_footer_scripts', array( Tribe__Events__Pro__Customizer__Main::instance(), 'print_css_template' ), 15 );
}
}


[George]

Hey Jeanine,

Thank you for this information!

I took a look but found that the “system information” you shared was just an image, not the text itself, and it was only a cropped image of the information—not the whole thing.

Sorry to add another step here, but to help my investigate, can you please copy and paste the full, un-edited text of that System Information into a reply here on this thread?

Thank you so much—sorry for the trouble here!
George

[George]

Sorry for the trouble here, @Rob. I took a look and confirm that, while the fieldset seems correctly configured, it is not displaying on your front end.

To help investigate, can you post your system information here? This article shows how to do so → https://theeventscalendar.com/knowledgebase/sharing-sys-info/

I will take a look and try to see what’s going on.

Thank you!
George

[George]

Thank you for this information, @Sean. I’m sorry to admit this but I remain puzzled by the behavior. I cannot recreate any of your issues.

I will continue investigating and will rope in a developer to assist me, but in the meantime, I would recommend opening a support ticket with your web host. At this point in the issue, I’m wondering if there might be an issue with your server configuration that is interfering with the functionality of those recurring event links.

Sorry for the continued trouble and lack of succinct resolution here!

---

PS

You say that you changed the start time to 8am instead of 8pm—can you clarify what the details of the event were originally?

1. What was its start time originally?
2. When was its end time originally?

Thank you!
George

[George]

Glad to hear it!

Best of luck with your project,
George

[George]

Hey Abraham,

Thank you for updating things and for the follow-up. I’m glad some progress has been made here. In regards to your other issues, I would like to first address the Visual Composer widget ordering issue—this is an issue best brought to the Visual Composer support folks themselves, as the issue with the Visual Composer widget ordering things. We don’t make that widget so unfortunately cannot speak to what it’s doing in terms of ordering things.

---

As for the incorrect ordering of things in your events view when you filter by date, I cannot recreate this on my own site, and this sort of issue is most often the result of a conflict on your site arising from your theme and/or another plugin.

To test for that, I would recommend doing ALL of the steps here → https://theeventscalendar.com/knowledgebase/testing-for-conflicts/

After EACH STEP in that process, go back to your main events view and filter by date. Does the same behavior persist? Or do events order properly anywhere along the way?

Thank you,
George

[George]

Hey Greg,

I’m glad that tip helped.

For further design refinement, you will unfortunately have to take the reins since we cannot help with custom coding. This is elaborated on here → https://theeventscalendar.com/knowledgebase/what-support-is-provided-for-license-holders/

This is especially true for the element in your screenshot (the “lower box”), as this seems to be something added by the “Fusion” theme, not The Events Calendar itself.

---

Now, I mention this policy just to set your expectation and uphold our standards fairly on the forums. However, if you can share a link to the event in the screenshot with these boxes, I will take a quick look and try to recommend some CSS. 🙂

I unfortunately cannot ascertain the exact necessary code from your screenshots, so if possible, share a link to the event in them and I will do what I can.

If you’re using a development site that is hidden from public view, then since we cannot log into customer sites for any reason, could you make things temporarily visible to the public so I could see them without logging in?

Thank you!
George

[George]

Hey Stuart,

Thank you for following up. I investigated this with a developer and we have confirmed that there is a bug here where those tags are showing up even if there are no Customizer styles. We do not intend for this to happen—those tags should only ever load if there are actual Customizer styles.

I’m sorry about this! We will work on a fix for this for a future maintenance release.

---

As for why the tags are outside the document HEAD in the first place, this is unfortunately because we’re in a bit of a Catch-22 with how to generate those styles. Let’s assume there were Customizer styles on your site—if we stuck to HTML standards and put those styles in the HEAD, then what we’ve found is that the styles often get overridden by other styles on the page that come after that.

Folks complained, rightfully so, so we moved the styles even lower on the page to ensure they “stuck.”

The style tags outside the HEAD is supported by all modern browsers without issue. But it’s technically not valid, so yes, you will have the validation errors you discover….

I just wanted to give some backstory there. It’s a bit of a “damned if you do, damned if you don’t” situation, but we’re working on a better solution for this.

---

In the meantime, if you do not need to use Customizer styles, then you should be able to remove those tags altogether by adding the following code snippet to your theme’s functions.php file:


add_action( 'init', 'tribe_remove_customizer_style_tags' );

function tribe_remove_customizer_style_tags() {
remove_action( 'wp_print_footer_scripts', array( 'Tribe__Events__Pro__Customizer__Main', 'print_css_template' ), 15 );
}


That should remove the tags from your document, thus allowing for validation. (Or rather, it will remove this one thing that is in the way of validation–if there are other issues with your document not related to The Events Calendar, those issues are separate from this).

Cheers,
George

[George]

Thanks for sharing, Dirk!

[George]

Excellent!

Can you share what your solution to this problem was?

Thank you,
George

[George]

Thanks for sharing this Mike—I’m sorry to see that they weren’t quite able to help here, either.

Modifying search within WordPress is unfortunately a tricky thing to do, and so no, we don’t have any specific pointers on modifying search in regards to The Events Calendar specifically. 🙁

There are numerous search-related plugins out there, but we cannot speak to any of them and don’t make any special integrations for any search plugins. If you stumble across a search plugin that looks promising, the best I can recommend would be to run these sorts of questions by them to see if their plugin will do the job you’re looking for.

I wish you the best of luck with your searching!

Sincerely,
George

[George]

Hey @Birgit,

This unfortunately requires a bit of custom code at this time. Try adding the following code to your theme’s functions.php file:


add_action( 'init', 'tribe_dont_send_tickets_email' );

function tribe_dont_send_tickets_email() {
remove_action( 'wootickets-send-tickets-email', array( 'Tribe__Tickets_Plus__Commerce__WooCommerce__Email', 'trigger' ) );
}


Cheers!
George

[George]

Hey @Li,

Thanks for reaching out!

There is unfortunately no specific integration with our plugins and Constant Contact. You would need other software and/or a specific process to pull that off, but it does not relate to our software. I would recommend searching online for a WooCommerce Extension that integrates with Constant Contact or something like that.

Let me know if you any further questions here!

Sincerely,
George

[George]

Hey @rubeez,

Thanks for reaching out!

tribe_is_event() should be working on single-event pages, and it does for me when I test on my local site, so I’m not quite sure what’s going wrong on your site. In the meantime, though, this might work well as an alternative:

is_singular( 'tribe_events' )

You can use this as a replacement for both is_single() and tribe_is_event(). Learn more about is_singular() here → https://codex.wordpress.org/Function_Reference/is_singular

I hope this helps!
George

[George]

Hey Simon,

Thanks for reaching out. What you describe sounds like a JavaScript issue, which I’m happy to help investigate here.

To help investigate, can you post your “system information” in this thread? Here’s how to do that → https://theeventscalendar.com/knowledgebase/sharing-sys-info/

I’ll take a closer look and see if I can recreate your issue any better.

Thank you!
George

[Author]

Posts