graphicgeek

Hi Marios,

I’m not sure exactly what you’re asking. What is it you want to show up in the pop up?

Hi Velvetgoldmine,

I’m sorry but I’m just not sure what you’re asking. Are you talking about the up/down arrows that appear on the pop up?

Try typing just a number in the box. So just “5” instead of “5 pixels”.

I think you could use event categories to specify which events were for which type of user, and then use the gg_event_widget_date_args hook to do something like this:

function my_event_dates_filter($args){
	$category = get_user_category();//you will need to write this function to return the category slug the user is allowed to see (or return false).

	if($category){
	$args['event_category'] = $category;
	}

	return $args;
}

add_filter('gg_event_widget_date_args', 'my_event_dates_filter');

That should make it so that the widget will only display events in the category for that user.

Then on your event listing page, you could use the template tag like this:

$category = get_user_category();
$args = array();
if($category){
	$args['category'] = $category;
}

event_geek_list($args);

I think you could use event categories to specify which events were for which type of user, and then use the gg_event_widget_date_args hook to do something like this:

function my_event_dates_filter($args){
	$category = get_user_category();//you will need to write this function to return the category slug the user is allowed to see (or return false).

	if($category){
	$args['event_category'] = $category;
	}

	return $args;
}

add_filter('gg_event_widget_date_args', 'my_event_dates_filter');

That should make it so that the widget will only display events in the category for that user.

Then on your event listing page, you could use the template tag like this:

$category = get_user_category();
$args = array();
if($category){
	$args['category'] = $category;
}

event_geek_list($args);

The arrows on the pop up window aren’t meant to show the next/previous events, they are meant to scroll up and down if there are more events than will fit in the window.

I’ll look in to the problem with the sliders on the options page, but in the mean time, I believe you can simply type a number into the box.

I think it might be possible, but it’s going to require some coding. Are you comfortable using WordPress hooks?

BTW, the site this is happening on is https://notetogibbs.com/

Hi Tintapixel,

I’ve seen one other person have this problem, and I believe it was caused by one of the start dates being after the end date for an event. So something like a start date of January 10th 2013, and and end date of January 5th 2013. If you send me a link to the site you’re working on, I can take a closer look.

Usually when the calendar doesn’t show up, it’s because of some kind of javascript error. But, unfortunately, it’s near impossible for me to guess what the issue might be without being able to look at the site where the problem is occurring.

I’m not having any issues. Can you send me a link to your site?

The testing link gives a 404.

For ordering, by default the shortcode will sort by start date. putting in the orderby=”name” will make them sort alphabetically by title.

Hi TommyBoy, those errors likely wouldn’t show up if error reporting were turned off. I will look into fixing them, but they aren’t “fatal” problems, if that makes sense. That is they “shouldn’t” prevent the plugin from working.

the shortcode [event_geek_list] is only meant to display the list of events, not the calendar. You can display it manually with this:

<?php gg_display_event_calendar (); ?>

See: https://eventgeek.graphicgeek.org/documentation/#displaying_calendar

If the popup isn’t showing, I there may be some issue with CSS, but I would have to look at the site to debug it further. Although, since you fixed the issue with adding the gg_event_window div, I suspect your theme may not be using the wp_footer() function, since that div should be created by the plugin where the wp_footer function is called.

I’m always happy to look at someone’s site and see if I can figure out what might be causing the issue.

Let me know if the problem persists after updating to 2.4.1