Luis Martins

Oh, totally missed that.
Im sure there is likely a very good reason for this decision, but it seems way less intuitive now.

Thanks for clarifying though.
Cheers.

Thanks for the feedback Nate.
Cheers.

Cool. I like the way WordPress is moving towards having one central place for all translations. The workflow to submit translations is far from ideal though. At this point it would be cool if one could submit .po/.mo files to update, instead of using the current interface.
I believe for that I need to be a validator.
Will investigate it and I I cant find a better way to do it will submit via github.

Hum ok, something must be breaking on my sites then. It always redirects to the dashboard. Will have to look it up then.

Thanks for clarifying Justin.

Not really sure I follow your comment. Can we use the widget to pass the current page so that the login redirects to the current page after the user logs in?

Thank you Justin, that helped me figure it out.
Im am running the excerpt through a few functions because im using Relevanssi plugin for the search feature. That was what was causing it.
Cheers.

The search is working now.
I think it was related to the has_front parameter being different in the taxonomy and cpt configurations. Not really sure though.

Im also unsure what is causing the query string to be appended. Im using the same setup as in a different project that doesn’t add that.

Im closing this for now as im not really able to provide solid information on this atm.

The with_front parameter seems to be correct in this case:

‘with_front’ => bool Should the permalink structure be prepended with the front base. (example: if your permalink structure is /blog/, then your links will be: false->/news/, true->/blog/news/). Defaults to true

I’ve tried commenting it out but it doesn’t work. Will keep digging.

Btw, when I submit a search I get the following URL:
/location/location-categories/parceiros/?q=/location/

But when I remove the location from the url it does work:
/location-categories/parceiros/?q=/location/

Perhaps the problem resides in the taxonomy location-categories.

Will update if I find a solution.

Hi Jonathan,

Sorry for the delay here.
The CPT im using is created by a plugin, which is registering the post type like this:

/**
	* Register the Location Post Type
	*/
	public function registerLocation()
	{
		if ( $this->hideDefaultPostType() ) return;
		$labels = array(
			'name' => $this->pt_labels->label,
			'singular_name' => $this->pt_labels->singular,
			'add_new_item'=> $this->pt_labels->add_new,
			'edit_item' => $this->pt_labels->edit_item,
			'view_item' => $this->pt_labels->view_item
		);
		$args = array(
			'labels' => $labels,
			'public' => true,
			'show_ui' => true,
			'menu_position' => $this->pt_labels->menu_position,
			'menu_icon' => $this->pt_labels->menu_icon,
			'capability_type' => 'post',
			'hierarchical' => false,
			'has_archive' => true,
			'supports' => array('title','editor','thumbnail'),
			'rewrite' => array('slug' =>  $this->pt_labels->slug, 'with_front' => false)
		);
		register_post_type(  $this->pt_labels->name , $args );
	}

Can this be the reason for the problem?

Btw, this is a multisite install. Can it have any relation?

After checking the source it seems that this is not possible out-of-the-box.
I had to resort overriding some of the files, which will be problem the the plugin is updated.

Maybe something you could consider in the future.

Thanks.

Yup, as i’ve said. It sucks now.
It could be done in one step before.

Not sure what is the reasoning behind this decision, maybe because of mobile, but to me it just feels like a compromise, one that does not make sense.

Yup, that does the trick, thank you.

Thank you Stephen.

With the following code, with and without the group_occurrences_by attribute, I always get an array with 39 items:

$events = eo_get_events(array(
    'event_start_after'=> 'today',
    'group_occurrences_by' => 'series'
));
var_dump( $events );

I currently have 5 events, one of them recurring hence resulting in those 39 items. Shouldn’t the group_occurrences_by limite the query result to only 5 items?

Cool, good to know. I’ll mark this as closed then, while we wait for the new API.
Many thanks man.