Aaron, its going to be a few days until I can look into this due to the setup of trying to replicate it. It may help if you share the template code you’re using (remove all html, css etc, just bare bones EE template code). It would also help if you replicate this in your site in some debug/test templates, again removing all extra html and css, and keeping only the EE template code necessary to replicate the issue, and please share the template names used to do this so it’s clear to me when I login to the CP to take a look.

I was not able to replicate this. I had a channel setup with a Bloqs field, containing a block that has a Relationship atom field, linked to another entry, and that entry has a Relationship field to another entry, which contains a file field. The file field always displayed the correct file, regardless of what the save patterns were.

You said “whichever language is saved last in the back end, that version of the file is shown for both languages”, but you didn’t say which entry was being saved… was it the entry containing the file, or one of the other entries with the Relationship fields? Are you able to create a video of this issue as you’re seeing it so I can see exactly what you are seeing?

The easiest way is if you can put it on Dropbox or a similar service, and just link to the file here in a private comment.

Actually the CP login you provided looks like a full site, so you’d need to put the clean version of the site somewhere I can login to it.

The FTP info you provided doesn’t work.

Comment has been marked private.

Are you sure? I tested it again and it’s displaying the correct file. Did you re-save the entries? Just updating the file won’t fix anything if the DB values are still incorrect.

Did you click Update next to Publisher? Is the following hook in your exp_extensions table? after_channel_entry_update

Make sure to turn off all caching. I noticed in your environment that you have caching enabled. I just tested again, with the environment you sent me, and everything is saving and displaying fine. It took so long to isolate the bug b/c I could see the DB getting updated correctly when saving, then before the save process finished, the wrong data was put back into the database fields, which is why the new hook is needed. I’m pretty certain this fixes the issue, regardless if it’s a simple text field or a file field 2 levels deep in a bloqs relationship.

I see what you’re saying when I look at your test site, but locally I’m not experiencing that. I looked at your database and all the values are correct for each entry and field value. I’m not sure what else to look at.

I’d be surprised if PHP versions had anything to do with this, but my environment is running 7.1.

Have you tried it on a different server? And/Or, instead of just deleting those entries doing another fresh EE install, with default EE, Bloqs, and Publisher settings? Maybe start with uninstalling Bloqs and Publisher and re-installing before doing a whole new EE install. I don’t know if that will do anything, but if it fixes the behavior then we know what to take a closer look at.

In that new environment, delete everything in the exp_publisher_relationships table, then re-create the block in each entry (I deleted them already), and see if that makes a difference.

Ok, you may need to use an embed bc I think this might be a parsing issue. Try this:

{exp:channel:entries channel="pages" entry_id="3"}
  <h1>{title}</h1>
  {related_item}
    {related_publication_block}
        {embed="site/publication" entry_id="{related_publication:entry_ids}"}
    {/related_publication_block}
  {/related_item}
{/exp:channel:entries}

site/publication

{exp:channel:entries entry_id="{embed:entry_id}"}
    <h2>{title}</h2>
    {related_document}
        <h3>{related_document:title}</h3>
        file: {related_document:file}
    {/related_document}
{/exp:channel:entries}