BoldMinded

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: Publisher, Structure and relationship field

Status Resolved
Add-on / Version 1.3.2
Severity Critical
EE Version 2.8.1

Sharkbyte

Apr 28, 2014

Hi,
Couldn’t choose the Add-on above. It only shows {support_addon_name}. So I put it here.
Add-on: Publisher v1.3.2

I’ve got a channel with a structure field for internal linking. On a other channel I’ve set this field up as a relationship field.
I think that Publisher is not working correct with structure combined with relationship fields. The output should be something like “/home/about/” but instead I’m getting a number.
When I output the channel with the internal links in channel entry loop the output is good. 

//  This outputs a correct link e.a."/home/about/"
{exp:channel:entries channel="call_to_action" }
  {title}<br/>
                {cta_link}<br/><br/>
{/exp:channel:entries}

// This output a number
{exp:channel:entries channel="standard"}
 {call_to_action}
           {call_to_action:title}
  {call_to_action:cta_link}<br/><br/>
 {/call_to_action}<br/><br/>
{/exp:channel:entries}

I hope you could help me out here. If so I’ve got a second question which problably als has to do with relationshipfields but is easier to explain when you are logged in.

Cheers

#1

BoldMinded (Brian)

Are you running the latest version of Structure?

#2

Sharkbyte

I’m using v3.3.14. I see the latest version is 3.3.14.4. But the latest version on Devot-ee is 3.3.14, where I bought it. Do I need version 3.3.14.4?

Little update. When I create a new entry for internal linking. It shows a correct link on the not translated version. When I open it for translation and save it the link turns into a number again.

#3

Sharkbyte

Oh, It just got updated to the latest version, how about that? Almost bought a new version.

#4

Sharkbyte

Hi, I was wondering if you had the time to look into this yet? We are a couple of days before going live.

As I mentioned before that when a entry is not translated yet the link works on the non translated version. On the default language it doesn’t work. When an entry has a translated version it also doesn’t work but when I delete the translation it works again.

Maybe this helps to find the problem and fix it.

Hope so. Tnx

#5

BoldMinded (Brian)

I haven’t had a chance to take a look, sorry. Did you disable Publisher and see if it works that way? I have an idea of why it wouldn’t be working, but it might not be Publisher specific. Its possible that the relationships parser isn’t parsing the number, which I assume is the entry_id of the page you’re expecting to see the URL for?

#6

Sharkbyte

No problem. Do I lose content if I disable Publisher? The number is indeed the entry_id.

#7

BoldMinded (Brian)

Make sure you use the disable option in the Publisher settings page (first option), it just turns off all the hooks and other stuff. Your data will be fine. DON’T uninstall it 😊

#8

Sharkbyte

Ok did it. Now I don’t see any related entries anymore. Added one for testing and works.

#9

Sharkbyte

Can I turn it back on or do you need to take a look with Publisher disabled? The site isn’t fully working with Publisher disabled and I must continue working on it.

#10

BoldMinded (Brian)

I took a look at this and I’m not sure what the issue is. It seems like EE is not parsing the field again after the value is modified via the hook in Publisher.

#11

Sharkbyte

I’ve found a solution that works for me. If you use an embed then the field is parsed as it should be. So inside an entry loop, I’ve put the relationship field, just like the code above in my question. Instead of outputting the fields I embedded a template and grab the entry with the entry_id. Just like any normal entry loop.

{call_to_action}
  {embed="global/cta" the_id="{call_to_action:entry_id}"}
 {/call_to_action}

And this is the embedded template

{exp:channel:entries channel="call_to_action" dynamic="no" entry_id="{embed:the_id}"  disable="categories|member_data|pagination" limit='1'  }
  {title} <a href="http://{cta_link}">{phrase:click}</a>
 {/exp:channel:entries}

If you should solve this or know what might be the problem then I like to hear from you. Tnx

#12

BoldMinded (Brian)

Glad you found a work around. I submitted this to EllisLab as a bug report… things just don’t seem to be operating as expected. You can follow the ticket here: https://support.ellislab.com/bugs/detail/20349

Login to reply