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: Unable to browse translated url title

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

Dennis Gandasoebrata

Dec 07, 2015

 

Hi,
I have a fresh and clean EE v2.10.1 environment. I have created two channels 1. page   2. content block
In the page channel you can select one or more content blocks.
Publisher config ‘Enable URL translations?’ = Yes

Translated url_title can’t be found, only url_title in default language.

I have created a couple of content blocks and created a page in the default language (English):
Title: New page
Url title: new-page
Page title: New page here
Select content blocks.

After this page is published I translate it to Dutch
Title: Nieuwe pagina
Url title: nieuwe-pagina
Page title: Nieuwe pagina hier

Browsing the page via url http://testee.dev/new-page shows the results:
Current language id: 1
{url_title_path=""}: http://testee.dev/index.php/new-page
{title}: New page
{url_title}: new-page
{publisher:last_segment}: new-page
{page_title}: New page here

Browsing the page via url http://testee.dev/nl/nieuwe-pagina shows the results:
Current language id: 2

But when I browse the NL page with English url title http://testee.dev/nl/new-page I get the results:
Current language id: 2
{url_title_path=""}: http://testee.dev/index.php/nl/nieuwe-pagina
{title}: Nieuwe pagina
{url_title}: nieuwe-pagina
{publisher:last_segment}: new-page
{page_title}: Nieuwe pagina hier

The stange part is that the {url_title_path} shows me the URL I would like to use for getting the dutch page but it does not work.

This is the code which I use to query the content:

Current language id: {publisher:current_language_id}<br>


    Url title path: <a href="https://boldminded.com/""/unable-to-browse-translated-url-title">https://boldminded.com/""/unable-to-browse-translated-url-title</a><br>
    Title: Unable to browse translated url title<br>
    Url title: unable-to-browse-translated-url-title<br>
    Publisher last_segment: {publisher:last_segment} <br>
    Page title: {page_title}<br>

I have read the instructions on the URL translations page, but this does not help me.

Best regards,
Stan

 

 

 

 

#1

BoldMinded (Brian)

Can you identify what parts of the URL are? Is new-page an entry URL title or is it template group?

#2

BoldMinded (Brian)

Also, you don’t need to add this to your entries tag. publisher_lang_id=”{publisher:current_language_id}”

#3

BoldMinded (Brian)

Try taking out url_title=”{publisher:last_segment}” too

#4

Dennis Gandasoebrata

Hi Brian,

Thank you for your reply.

‘new-page’ is the URL title and not a template group I have removed the publiser_lang_tag and the our_title but this still does not show dutch content with the dutch URL title ‘nieuwe-pagina’ This results in the following code:

Current language id: {publisher:current_language_id}

{exp:channel:entries dynamic="no"}
    Url title path: {url_title_path=""}

    Title: {title}

    Url title: {url_title}

    Publisher last_segment: {publisher:last_segment} 

    Page title: {page_title}

{/exp:channel:entries}

Also left out the dynamic=”no” since I do not give any url_title parameter but also gives the same no-result with the URL http://testee.dev/index.php/nl/nieuwe-pagina

This is a simple and easy example to have the URL title translated, right? I do not understand why this is not working and what I miss to get it fixed.

Best regards, Stan

#5

BoldMinded (Brian)

Can you provide CP login info?

#6

BoldMinded (Brian)

Ok, I’m not sure how this bug has existed for as long as it has without anyone else noticing, but I think its fixed now. Try the build in the next comment.

#7

BoldMinded (Brian)

Comment has been marked private.

#8

Dennis Gandasoebrata

Hi Brian,

Thank you for the new build. unfortunately a new problem occurs. The language prefix does not work anymore at all. http://testee.dev/new-page works fine http://testee.dev/nl/new-page automatically redirect to http://testee.dev/new-page http://testee.dev/nl/nieuwe-pagina automatically redirect to http://testee.dev/nieuwe-pagina

I have set up a dev environment online. In the next post I will send the location and the credentials.

#9

Dennis Gandasoebrata

–edit– credentials are submitted in ticket

#10

BoldMinded (Brian)

You CP isn’t loading for some reason. Check the language prefix options on the settings page (its the 2nd or 3rd field group) and take a screenshot of it and share it with me.

#11

Dennis Gandasoebrata

Strange that it is not loading. Checked it and I don’t have any issues to load.

Screen shot is added.

#12

BoldMinded (Brian)

Turn off the hide prefix for default language setting. Read the setting descriptions, sounds like you just need to tweak them a bit.

#13

Dennis Gandasoebrata

Comment has been marked private.

#14

BoldMinded (Brian)

I disabled Publisher Language Control and it appears to be working correctly now. It looks like it might be an issue with setting the default language in PLC. I may need to change the setting wording on that b/c its not really setting the default language. Publisher sets the default. PLC forces the default language, so if you try to go to a page in another language it’ll continue to force it to the one you set as the default in PLC.

Leave it disabled for now and I’ll try to make some updates in the next few days.

#15

Dennis Gandasoebrata

Thank you for finding the issue. I hoop to hear from you soon with an update.

Best regards, Stan

#16

BoldMinded (Brian)

Comment has been marked private.

#17

BoldMinded (Brian)

The latest Publisher build should fix the redirect issue when using Publisher Language Control.

Login to reply