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: Problem with path tag after upgrade

Status	Resolved
Add-on / Version	Publisher 1.6.5
Severity
EE Version	2.10.1

Jason McCallister

Aug 06, 2015

Description:
We recently upgraded to EE 2.10.1 and Publisher 1.6.5. Prior to the upgrade we had static links (not wrapped in a tag) that are using {path='customer-service/contact'}.

After the upgrade the {path='customer-service/contact'} URLs are not being translated to the Spanish URL.

Some important notes:
1. We are using Structure.
2. The URI does not map directly to a template path (in this case its actually loading “contact/index” template).

Here is the full line of code from the site, again this is not wrapped in a exp tag.

{phrase:nav_contact_us}

Is there something that we are missing post upgrade, maybe a new setting for the plugin?

Jason McCallister

Did not see the code block on entering my ticket, here it is below:

<li class="contact"><a href="http://{path=%27customer-service/contact%27}" title="{phrase:nav_contact_us}">{phrase:nav_contact_us}</a></li>

BoldMinded (Brian)

Jason, what version did you upgrade from?

Jason McCallister

EE 2.6.x

This is a related ticket to the upgrade, for reference: http://boldminded.com/support/ticket/1134

BoldMinded (Brian)

Jason, try this. Replace the single quotes inside the {path} tag with double quotes and see what happens.

Jason McCallister

Well that solved it. I thought about that at first but did not think that would be it.. Is that an actual bug or working as intended?

BoldMinded (Brian)

No, its not intended, definitely a bug. Will have a fix soon.

BoldMinded (Brian)

Comment has been marked private.

BoldMinded (Brian)

Comment has been marked private.

BoldMinded (Brian)

Fixed in next release.