[Barry]

Hi! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

[Barry]

Hi! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

[Barry]

Hi! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

[Barry]

Hi! It’s been a while so I’m going to go ahead and close this thread. If we can help with anything else, though, please don’t hesitate to create new threads as needed. Thanks!

[Barry]

Our pleasure 🙂

I’ll go ahead and close this thread – but we’ll do our best to re-open and post an update as work on the bug progresses.

Thanks again!

[Barry]

Hi flawlessvictory – that’s a great question.

It’s not all that unusual to do things this way and such a model makes for cleaner, more maintainable code with fewer conflicts: remember that it isn’t only Events Calendar PRO that depends on and uses the core functionality offered up by The Events Calendar but several other plugins written by us and various third parties, too.

This is far from an ideal setup from a clients usage point of view – i.e. having to update two plugins simultaneously, enable two seperate plugins etc.

That’s definitely a potential downside, but given how easy WordPress makes it to activate and update plugins – most often, it’s a matter of a few mouseclicks – I’m not sure that it’s too arduous a process for the majority of our users.

Also, let’s imagine a user has installed WooCommerce Tickets, Eventbrite Tickets and Community Events and each integrates our core framework within it: if a bug fix is needed for a piece of core functionality we’re going to have to make them update all of those plugins.

For those users that do find updates to be a challenge that obviously isn’t optimal – whereas under our current system, in such a situation, they need only update a single plugin (The Events Calendar).

With all that said, we’re always open to new ideas and requests and if you want to post one over on UserVoice – which is our preferred channel for requests as it lets others comment on ideas and show their support – you are more than welcome to do so 🙂

 

[Barry]

Hi!

I’m sorry you are experiencing difficulties.

It looks like you are using a theme called Enfold by Kriesi: I’m afraid that this particular theme deliberately removes a number of our settings.

If that’s a problem then I’d encourage you to contact the theme author: regrettably there isn’t much we can do to help as this is an intentional facet of that theme.

[Barry]

…Just to add, if you want those links to display regardless you can try adding this snippet to your theme’s functions.php file:

/**
 * Allows visitors to page forward/backwards in any direction within month view
 * an "infinite" number of times (ie, outwith the populated range of months).
 */
class ContinualMonthViewPagination {
	public function __construct() {
		add_filter( 'tribe_events_the_next_month_link', array( $this, 'next_month' ) );
		add_filter( 'tribe_events_the_previous_month_link', array( $this, 'previous_month' ) );
	}

	public function next_month() {
		$url = tribe_get_next_month_link();
		$text = tribe_get_next_month_text();
		$date = TribeEvents::instance()->nextMonth( tribe_get_month_view_date() );
		return '<a data-month="' . $date . '" href="' . $url . '" rel="next">' . $text . ' <span>&raquo;</span></a>';
	}

	public function previous_month() {
		$url = tribe_get_previous_month_link();
		$text = tribe_get_previous_month_text();
		$date = TribeEvents::instance()->previousMonth( tribe_get_month_view_date() );
		return '<a data-month="' . $date . '" href="' . $url . '" rel="prev"><span>&laquo;</span> ' . $text . ' </a>';
	}
}

new ContinualMonthViewPagination;

(If there’s a bug though and you’re not seeing the links appear when they should – ie, when there are future events – it would be awesome to see it first hand and potentially fix it as I can’t seem to replicate the same thing locally and we’d love to get a little more insight if it’s a bug that might impact others.)

Thanks again!

[Barry]

Hi there ronanoleary,

It shouldn’t hide the next month link unless there truly are no events in the future.

In other words, if you have events in October then nothing in November or December but you do have a further event in January, it will still let you cycle through the months as far as January (if that is when the furthest-in-the-future event within your calendar is taking place).

Are you experiencing something other than this/can you point me to an example?

Thanks!

[Barry]

Hi littlemountainlion,

You definitely should be able to enter a license – but please note WooCommerce Tickets will not cause an additional settings tab to appear.

I’ve deactivated plugins but it doesn’t help

Just for the avoidance of doubt – did you follow these steps in their entirety (and so also switch to a default theme)? What we’ve occasionally found in the past is that other plugins or even themes use a conflicting version of a piece of software called Plugin Update Engine which can cause some difficulties with the license tab.

I can see the video may be a little out of date, is there anything newer I can use as a reference point?

It should still be pretty much up-to-date – and that is still the best reference to use 🙂

[Barry]

Awesome 🙂

I’ll go ahead and close this thread but if we can help with anything else please don’t hesitate to open a new one and let us know – one of the team will be only too happy to help.

Last but not least, if you have a moment to spare we’d love to hear your thoughts on The Events Calendar so far over on our plugin review page – thanks again!

[Barry]

It would be awesome if you could.

Something like Duplicator makes it nice and easy to do this (and copies across your entire database, too) so that would almost certainly allow us to capture the problem and move it across to a test site where we could run through further troubleshooting without disrupting your live site.

[Barry]

Hi louisecote,

Customizations are really something we need to leave in your hands, but I’d be happy to point you in the right direction if I can 🙂

I’ve added two custom meta fields (‘_EventCreationDate’,’_EventAdPeriod’,) to The Events Calendar Class (the-events-calendar.class.php).

Modifying core plugin code is rarely a good idea and not something we’d generally recommend. Perhaps you could implement your modifications without doing this?

I want to set these fields, when user clicks Submit button on Community Events page (/events/community/add).

WordPress itself has some useful hooks you can use such as save_post_{post_type} so you could consider listening out for the appropriate action firing and add your logic to a plugin of its own (or possibly to your theme’s functions.php file).

Since you probably only want to add these fields to events submitted via Community Events you could additionally test against the ecp_event_submission nonce which is used to protect that form, ie:

add_action( 'init', 'setup_community_submissions_marker' );

function setup_community_submissions_marker() {
	if ( class_exists( 'TribeEvents' ) )
		add_action( 'save_post_' . TribeEvents::POSTTYPE, 'mark_community_submissions' );
}

function mark_community_submissions( $post_id ) {
	if ( ! wp_verify_nonce( @$_POST['_wpnonce'], 'ecp_event_submission' ) ) return;
	update_post_meta( $post_id, 'your_custom_field', 'some_value' );
}

Would that work for you?

[Barry]

Hi Thomas,

I’m sorry you’ve experienced difficulties with this.

My bet is that there is some custom code in your Karma theme’s functions.php file. Is that a possibility/is there anything you added there, perhaps something you received help with here on the forum?

It may be you need to (temporarily) remove those lines of code if so.

[Barry]

Apologies Sean, I somehow missed that. A slightly wider change is probably going to be needed then. Assuming an unmodified version of the same template the idea would be to change this section:

<select name="recurrence[end-type]">
	<option value="On" <?php selected( $recEndType, 'None' ); ?>><?php _e( 'On', 'tribe-events-community' ); ?></option>
	<option value="After" <?php selected( $recEndType, 'After' ); ?>><?php _e( 'After', 'tribe-events-community' ); ?></option>
	<option value="Never" <?php selected($recEndType, "Never") ?>><?php _e('Never','tribe-events-community'); ?></option>
</select>

<input autocomplete="off" placeholder="<?php echo TribeDateUtils::dateOnly( date( TribeDateUtils::DBDATEFORMAT ) ); ?>" type="text" id="recurrence_end" class="tribe-datepicker" name="recurrence[end]" value="<?php esc_attr_e($recEnd); ?>" style="display:<?php echo !$recEndType || $recEndType == 'On' ? 'inline' : 'none'; ?>"/>

<span id="rec-count" style="display:<?php echo $recEndType == 'After' ? 'inline' : 'none'; ?>">
	<input autocomplete="off" type="text" name="recurrence[end-count]" id="recurrence_end_count"  value="<?php echo $recEndCount ? intval($recEndCount) : 1 ?>" style="width: 40px;"/>
	<span id="occurence-count-text">
		<?php echo isset( $recOccurrenceCountText ) ? esc_html($recOccurrenceCountText) : ''; ?>
	</span><!-- #occurence-count-text -->
</span><!-- #rec-count -->

To:

<select name="recurrence[end-type]">
	<option value="After" <?php selected( $recEndType, 'After' ); ?>><?php _e( 'After', 'tribe-events-community' ); ?></option>
	<option value="Never" <?php selected($recEndType, "Never") ?>><?php _e('Never','tribe-events-community'); ?></option>
</select>

<span id="rec-count" style="display:inline">
	<input autocomplete="off" type="text" name="recurrence[end-count]" id="recurrence_end_count"  value="<?php echo $recEndCount ? intval($recEndCount) : 1 ?>" style="width: 40px;"/>
	<span id="occurence-count-text">
		<?php echo isset( $recOccurrenceCountText ) ? esc_html($recOccurrenceCountText) : ''; ?>
	</span><!-- #occurence-count-text -->
</span><!-- #rec-count -->

It’s not perfect but it may suffice until we release a substantive fix.

[Author]

Posts