BoldMinded

All add-ons currently require PHP 7.4 or greater.

On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.

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: Entry not translating properly

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

Jason McCallister

Mar 17, 2016

Description:

I have an entry with a fairly straight forward template tag sets - I have verified that the Spanish translation is present and resaved both entries - however this specific section of the site is not translating, the rest of the page is though.

https://gist.github.com/themccallister/9339710312ecaaf92a72

 

 

#1

Jason McCallister

Comment has been marked private.

#2

BoldMinded (Brian)

What have you done to debug the issue so far?

#3

BoldMinded (Brian)

Did you simplify the template? Did you try removing the limit parameter? Is there caching anywhere? Can you replicate this with any other content? If not what makes this one unique?

#4

Jason McCallister

The template is simplified.

I have reserved the entry which caused a few other similar issues to resolve. There is no caching on the site, but the cache has been cleared.

#5

BoldMinded (Brian)

By simplified I mean just this.

{exp:channel:entries channel="accounts_landing" limit="1"}
{title}
{account_landing_box_quote}
{account_landing_box_text}
{/exp:channel:entries}

What do you mean by “reserved the entry”? What about the limit parameter? Is this happening on any other content? Based on what you’re reporting I’m fairly confident its probably not a bug b/c I would be having similar issues from other people, and I would be able to replicate it myself locally. So I’m thinking its either a conflict with another add-on, which may be using the same extension hooks, or that data just doesn’t exist in the other language (does the translation show in the CP)? Did you try disabling all other extensions/add-ons? This is why I ask what have you done so far to debug the issue.

#6

BoldMinded (Brian)

Following up on this. Will close the ticket soon if I don’t hear anything back.

Login to reply