[Josh]

Hello screenrage,

Thanks for following up with us!

Having this constant defined should disable the deprecated file from loading. To verify:

1. <span style=”line-height: 13px;”>Ensure that the provide snippet was added to your site’s “wp-config.php” file. It would be best to add it right below the define( 'WP_DEBUG', false ) line of that file.</span>
2. <span style=”line-height: 13px;”>Did you clear your cache or do a hard refresh after making this change?</span>
3. <span style=”line-height: 13px;”>It may also help to deactivate/activate the Events Calendar plugin after making this change.</span>

<span style=”line-height: 13px;”>Let me know if this helps. </span>

Thanks!

[Josh]

Hello nkctribune,

Thanks for reaching out to us!

It sounds like the problem is that when the option to limit access is selected, the site blocks “wp-admin” for both the selected level as well as any visitor (logged out user) to the site?

On the surface, it sounds like this is working properly since you wouldn’t want visitors to access the admin either. When logging in, it may be best to switch to accessing that page via “oursite.com/wp-login.php” rather than “wp-admin” since “wp-admin” redirects to “wp-login.php” for logged out users anyway.

However, I do understand the potential confusion and think the ability for “wp-admin” to still redirect to “wp-login.php” for logged out users could warrant a feature request on our UserVoice page.

I’m sorry I wasn’t able to give you a direct response however I hope this was able to point you in the right direction.

Thanks!

[Josh]

Hello sfbike,

Thanks for reaching out to us!

I apologize for the inconvenience that this issue has caused. Hopefully I can help to get you pointed in the right direction.

Based on your comment, it sounds like your staging site and production site are currently identical and you took the same steps to get them to their current states. The problem is the production site has 404 issues that your staging site doesn’t have?

As an initial step, have you tried resaving the permalinks as well as clearing the cache on your production site to if this resolves the issue?

Let me know if this helps.

Thanks!

[Josh]

Hello jrtoy4311,

Thanks for reaching out to us!

I’ll try to hit all the points you’ve brought up. If I happen to miss one, please let me know in the follow-up.

1. <span style=”line-height: 13px;”>Currently, the map isn’t automatically selected for imported events but the location should be imported. You can try adding this function to your theme’s “functions.php” to get it to automatically select the map option on imported events.</span>
2. There are a couple of options here that can be pursued outside of modifying core plugin files. (1) You could delete the information after import or (2) you could use the Themer’s Guide to prevent this information from displaying on your site. This would be controlled with the modules -> meta ->organizer.php file.
3. Events will import and display based on the Timezone set for your site. The Events Calendar currently doesn’t have support for multiple timezones. It is something that has been reported in the past and you can vote for the feature on our UserVoice page. This will let our developers know there is demand for the feature and give priority for the feature to be reviewed for possible inclusion in a future update of the plugin.

I hope this helps.

Thanks!

– Josh

[Josh]

Hey,

Thanks for reaching out to us!

Unfortunately, this functionality isn’t available out of the box with either the WooTickets or Events Calendar Pro plugins. However, you could create a solution with a little bit of customization. In this example, you could follow our Themer’s Guide to modify the ticket form (wootickets -> views -> ticket.php) that displays on the event to include a field for “Name”. You could then hook this into some form of custom meta for the order that you would also need to create.

I’m sorry I wasn’t able to give you a direct response however I hope this was able to point you in the right direction.

Thanks!

[Josh]

Hello jaredtyson,

Thanks for reaching out to us!

The date for the single event is set using the “tribe_events_event_schedule_details” function found within the template-tags -> general.php file of the core plugin. Within that function you can see a filter at the bottom with the same name. Using this filter, you can add a custom function within your theme’s “functions.php” file to modify the way the date is output.

For this example, you can leave most of the function the same but just modify the “tribe_event_is_multiday” section to include the year after the second date of the event while leaving the setting within your dashboard set to “F j”.

Let me know if this helps.

Thanks!

[Josh]

Hello runroom,

Thanks for following up with us! Would you mind posting the exact code you used to generate the connection?

Again, I would like to restate that I’m happy to take a look at the code to see if I can reproduce and/or provide a quick look to see if there is something causing the conflict. However, I can’t guarantee that I’ll be able to support a complete resolution to this issue due to the nature of the conflict.

Thanks!

[Josh]

Hello swingcal,

Thanks for following up with us.

It looks like the plugin does require GD and FreeType Library per the FAQ page for the plugin. However, I don’t believe the error that you’ve shared above is due to these being lacking on the server.

It’s a potential that the primary class for Really Simple Captcha may already be included in an existing plugin or your theme. This is causing it to conflict when activating the plugin. Try disabling other plugins to see if this resolves the issue with activating the Captcha plugin.

Let me know if this helps.

Thanks!

[Josh]

Hello aehhub,

No problem. Happy to have been able to help!

If you have a few moments, we would definitely appreciate it if you took a second to rate our plugin on the WordPress.org repository.

I’ll go ahead and close this ticket. If you have any further questions please don’t hesitate to open a new one.

Thanks!

[Josh]

Hello klokwerk,

No problem! Thanks again for the feedback on the plugin. This stuff really helps us to ensure we keep providing a great plugin that is useful for our users.

Thanks!

[Josh]

This reply is private.

[Josh]

Hello sustainhawaii,

Thanks for reaching out to us!

I apologize for any inconvenience you’ve experienced with the compatibility between these two plugins. Currently, there is limited compatibility in the sense that tickets can not currently be created on the front end of the site using the community events add event page.

That being the case, you as the admin should still be able to go into any event, even those created by users via the front end form, and add tickets for that event. It sounds like this is the functionality that you’re having difficulty with?

If that is the case, there are a couple of things you can check:

1. <span style=”line-height: 13px;”>Ensure that there aren’t any “Start Sale” or “End Sale” dates for the tickets. If the current date isn’t within the window set there, the tickets won’t show on the front end of the site</span>
2. You can try the Testing for Conflicts procedures to see if there is a conflict on the page preventing the tickets from displaying.

Let me know if this helps. I’m sorry I wasn’t able to give you a direct response however I hope this was able to point you in the right direction.

Thanks!

[Josh]

Hello landrenic,

Thanks for reaching out to us!

It sounds like having a widgetized area for each of these pages might be the best approach. You could then use the Events Calendar widget to display a calendar of events just for the specific category for that page.

You could also try the Event Rocket plugin to see if any of the shortcodes provided within that plugin allow the calendar to display by category.

I apologize if I’m misunderstanding the exact functionality you’re looking for. Let me know if this helps.

Thanks!

[Josh]

Hello mattkluga,

Thanks for reaching out to us!

You can definitely customize the email by following the Themer’s Guide and copying the views -> tickets -> email.php file from the core plugin into your theme. You can then grab the iCal links from the buttons on your live site to include as a link within your updated email template.

Let me know if this helps.

Thanks!

[Josh]

Hello screenrage,

Thanks for reaching out to us!

I apologize for the inconvenience this issue is causing. The function creating the conflict is part of a deprecated file full of deprecated functions that we have left in place for backwards compatibility. All of our current functions use proper prefixing with the current plugin name.

However, we do have an easy way to disable this file from being included. You can fix the issue by adding the following to your wp-config.php file at the root of your WordPress install.

define('TRIBE_DISABLE_DEPRECATED_TAGS', true);

Let me know if this helps.

Thanks!

– Josh

[Author]

Posts