Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: Publisher and Resource Router

Status Resolved
Add-on / Version Publisher 2.9
Severity
EE Version 4.3.6

Aaron Jay

Oct 10, 2018

Hi there,

I raised a similar issue a little while ago, but didn’t really have the time to follow up on it.  But is Publisher compatible with the Resource Router add on?

We’re trying to route out the template name and have set up a route as follows:

‘committees’ => ‘committees/index’,
‘committees/:any’ => ‘committees/detail’,

The url we want is: http://policingauthority.emagination.ie/en/committees/audit-and-risk-committee

This works fine for the english version, but the Irish version: http://policingauthority.emagination.ie/ga/committees/an-coiste-iniuchoireachta-agus-riosca

does not work.

In our template we have: {exp:channel:entries channel="committee_details" url_title="{publisher:segment_2}” limit=“1” dynamic=“no”}

Adding back in the template name:

http://policingauthority.emagination.ie/ga/committees/detail/an-coiste-iniuchoireachta-agus-riosca and changing it to:

{exp:channel:entries channel="committee_details" url_title="{publisher:segment_3}” limit=“1” dynamic=“no”}

does work

#1

BoldMinded (Brian)

I’ve only tested Publisher with the native routes, not Resource Router. Based on what I know about Resource Router and what you’re describing it probably won’t work. Have you tried the native Routes?

#2

Aaron Jay

Hi Brian,

Thanks for your help. I havn’t as I’m not sure how to set it up to be honest. The documentation on the EE site is not clear on how to do that. Based on what I’ve described above, would it be possible to give me an example that you’ve tested?

#3

BoldMinded (Brian)

The syntax is nearly the same, you just have to define the routes in the control panel instead of in the config file. Then in Publisher’s Template Translations settings page there is an option to provide a translated route for the non-default languages, which follows the same thing as EE’s routes definitions, but provides a way to translate the non-dynamic parts of the route.

#4

BoldMinded (Brian)

Aaron, I assume you’ve figured this out b/c its been a month with no response. I’m going to close this ticket.

Login to reply