Forum Replies Created
-
Posts
-
Could you please share your System Information in a Private Reply. That will give me a lot of extra information to help troubleshoot this.
Additionally, could you please follow our Testing for Conflicts Guide (basically switch to Twenty Seventeen theme and deactivate all plugins and custom code other than Modern Tribe plugins) and see if that helps narrow down the cause of this?
Of course, we always recommend restorable database and file backups before modifying anything on your site.
Thanks for the additional information. We do not provide CSS and template customizations, per our Scope of Support / Terms, but I can suggest you customize Month View’s templates, including the tooltips (what the popups are called). These links might be helpful:
You can add custom CSS code via your child theme’s style.css file, via WordPress 4.7’s Customizer CSS settings, or via a third-party plugin (not guaranteed or supported by us), like:
- SiteOrigin CSS (helps you visually build CSS selectors via its Inspector and Visual Editor, if that’ll help you)
- Simple Custom CSS
- Jetpack (supports regular CSS and the LESS and Sass pre-processors)
If you’re not a CSS expert, Jetpack’s Custom Design reference may prove helpful.
Please let me know how it goes for you.
Sorry, Kyle, but I’m confused by “want to hide, not remove, the ability for certain users” and then by “I know how to do this by role”
Would you mind clarifying?
Sorry for the delay here, Rocky. Our developers have asked for a database dump if that’s possible. You can send a link in a Private Reply (which cannot be done via email).
Adam, I tested your code with Twenty Seventeen and clicked about a dozen events–some recurring, some not–from Month View, and they all loaded the Event Single Page just fine.
As far as failing with Avada goes, all I can suggest is that you enable WP_DEBUG and WP_DEBUG_LOG (which will create a file on your server at /wp-content/debug.log if there are any WP_DEBUG messages) and share any debug messages you see while trying to replicate this issue.
According to WooCommerce’s definition (and the general definition) our tickets are Virtual products–they are not physical/shipped products. WooCommerce does not force virtual products to have hidden Visibility, though; our plugin does this (only for tickets, not all Virtual products).
Therefore, this snippet says “get all the ticket products for this event, find the one that has the lowest cost and set its visibility to Show and its name to the event’s title, then set all the other ticket products for this event to Hidden”
If it’s not doing that, let me know.
Thanks for your patience.
Turns out there’s not a straight-forward way to do exactly what you’re asking. Therefore, an alternative idea to modify the map view JS to avoid the initial Ajax request is to alter the result of it (i.e. alter the query that is performed when the request is processed).
By using the wp_ajax_tribe_geosearch and wp_ajax_nopriv_tribe_geosearch hooks — early, like priority 5 — you could completely override what we do.
Or you could use those to listen for the request and then hook into the various event query actions to modify things there.
Or you could use the tribe_events_ajax_response hook to alter what comes back.
Hopefully this is enough technical information for you to get moving forward on this.
Please let me know how this goes for you.
Hi, Abi.
Community Events doesn’t have integration with any membership plugins, but you could very likely wrap some of its code with shortcodes or leverage some action hooks to accomplish the integration.
You could also request specific integrations as a new feature (or maybe search to see if the idea was already posted by someone else) at our plugins’ UserVoice page.
This allows others who are interested in that feature to easily voice their support. We frequently review suggestions there to find out which ones are popular, then we implement as many of them as we can.
If you post it / find it, feel free to link to it from here in case anyone comes across this forum thread in the future.
Last but not least, we have a pretty great Refund Policy so you can buy one or many of our add-ons and thoroughly test them.
I hope this info helps. Let me know if you have any follow-up questions.
Hi, Kyle.
If you want Event Categories fully removed, you would need to use https://developer.wordpress.org/reference/functions/unregister_taxonomy/
If you just want them hidden from the wp-admin sidebar menu and some other places, you could use the tribe_events_register_event_cat_type_args filter. For example, you might want to change “public” and/or “show_ui” from true to false.
Please let me know how this goes for you.
Hi, Derek.
You can follow our Themer’s Guide to customize the /wp-content/plugins/the-events-calendar-community-events/src/views/community/edit-event.php file. You’ll want to comment out or delete this line:
tribe_get_template_part( 'community/modules/description' );You may also need to reference https://theeventscalendar.com/knowledgebase/required-fields-for-events-submission-form/ for the required part of things.
Please let me know how this goes for you.
Hi, Jo / Kay.
You are correct. This functionality is not currently available.
I believe you’re requesting the same thing as one of our existing feature requests: https://tribe.uservoice.com/forums/195723-feature-ideas/suggestions/3825421-reusable-ticket-defaults-profiles-as-per-venues-a
Please do add your vote there.
This allows us to gauge interest in this particular feature request, which helps us prioritize our development efforts.
Thank you.
Hi, Ivan.
Thanks for your interest in our plugin suite.
Because we cannot exchange Private Replies in our Pre-Sales Forum–and due to the nature of your individualized inquiry–our Products Director will be emailing you today to discuss this with you.
There’s no need to reply back here unless you end up not getting an email from Zach.
Thanks! 🙂
