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: 404 error when getting on translated templates
| Status | Resolved |
| Add-on / Version | Publisher 1.0.14 |
| Severity | Critical |
| EE Version | 2.7.2 |
Ante Beljan
Nov 11, 2013Hello again,
I can’t get to the translated entries/templates when visiting the page “from outside” through direct links, it leads me to a 404 page.
When i access the site in the default language and browse through the translations everything is fine.
I’m not using the “Add URL prefix” setting, should I be? It caused me some problems so if there’s a solution that doesn’t require it that would be great.
I have included a link that will lead you to the 404 page.
BoldMinded (Brian)
Hi, Ante. I’m not sure what you mean by “from outside” - Have you tried disabling Publisher in its settings and seeing what happens? Also, you’ll need to provide more info… are you using translated URLs? Are you using Structure or Pages? Is the cnoveror-belts url a template? Do you have a translation for the template?
Ante Beljan
Yes, I’m using translated URLs. conveyor-belts is a translation of a template. All the URLs in the default language (Croatian) are accessible. I am not using Structure nor Pages. By “from outside” I meant when the page is visited via the translated link (the one I sent you).
BoldMinded (Brian)
Ante, I’m not going to lie… I’m really under the gun to launch a site tomorrow. I already worked part of the weekend and will be working late tonight, so I’m not sure I’ll have time to dig into this until Wed.
Ante Beljan
I understand. It can wait until Wed. Good luck with the launch. 😊
BoldMinded (Brian)
I just took a look at it and there isn’t a bug. The issue is that “conveyor-belts” is a translated value, not a template group name, and upon the first visit of the site the user does not have a valid language cookie, so EE doesn’t know what language the site should be displayed in, thus it doesn’t recognize a translated url value that doesn’t exist as far as EE is concerned. If you want to deep link directly to translated pages you’ll need to turn on the prefix and then link to it with that, e.g. site.com/en/conveyor-belts. EE will then know the language is English and can translate the URL. It looks like your server is throwing a 500 error though when this happens. I can do the same thing locally and the pages look fine. Should take a look at your logs and see what the issue might be.
Ante Beljan
Ok, the 500 error was because some scripts were using {site_url} and not linking properly. Everything is fine now, thank you very much!