Playa Multi-Relationship REL error
Development and Programming
I’m starting a new thread dedicated to this error, because the other thread is just ridiculous and has a lot of different issues going on.
I had this working on a template with a lot going on…then it seemingly stopped working. So I made a bare-bones testing template. I’m using PHP 5.2.5 for the record, and as I said, this was working yesterday which makes me wonder if it’s an extension conflict of some kind. I have a Playa field in a complex weblog, and also in a very simple one. I don’t get any Firebug Javascript errors in the CP, and Playa appears to be working perfectly.
Here’s my template code for my Playa field from the super-simple weblog:
{exp:weblog:entries weblog="articles" entry_id="208"}
<h3>{title}</h3>
{article_body}
{article_playa}
<ol>
{related_entries id="article_playa"}
<li>{title}</li>
{/related_entries}
</ol>
{/exp:weblog:entries}This is what the above outputs on the template:
Sample Article Sample article for testing. article_playa [94] Related Title 1 [95] Meerkats and You [96] Without Playa, I Am Dead {REL[article_playa]9jICczdfREL}
So, when I just output the field name, I see the three entries that I related to, so I know they’re in there! But when I go to loop through them with the “related_entries” tag pair, I get the dreaded REL problem where the OL should be. I’ve emptied caches both through the CP and manually.
I tried uninstalling and reinstalling Playa. I’ve triedmaking a new playa field and testing with that. All to no avail as REL keeps showing up.
This extension is almost essential for moderately complex EE sites - I really need this to work. Anyone have any insight on how to fix this? Might it be an extension issue? I wouldn’t think so as everything seems to be going in to the DB OK, but the problem seems to be on the template side. I’m stumped!
Fonzie Effect: When you post a big forum entry about something and then figure it out a few minutes later.
I went into the exp_extensions table with Navicat (mySQL app for Mac), changed Playa priority for modify_template method from 9 to 10 and now Playa works again.
I am experiencing the same issue. I tried the above fix, but it did not resolve the problem. I am running EE 1.6.4 and PHP 5+
@vibe9: It might very well be an extension conflict. We might be able to help you if you tell us what extesnions you’re using.
Here are the extensions I currently have enabled:
Edit Tab AJAX (v.1.2.1) Multi Relationship (v.1.0.6) LG TinyMCE (v.1.3.2) Fresh Variables (v.1.0) Fielder Extension (v.1.0.0) User (v.1.0.0) Playa (v.1.0.9) Hidden Weblogs (v.1.0.3) File, by Mark Huot (v.3.1.1) Related Entries Extension (v.1.0.4) LG Add CP Tabs (v.1.1.0) Multi Drop-down List (v.1.1.1)
Ryan,
Thank you for this post. I’ve been going insane trying to figure this out. I had a site within 1 day of launch and then this happened.
If anyone can deduce what is causing it, that would be great. I initially thought this was because of 1.6.5 since I noticed the problem right after I upgraded. But now I realize that it was probably because I cleared the caches before I upgraded. God know what caused the problem before then.
For what it’s worth, I also have the following extensions enabled (I’m assuming there is a common extension causing this):
Edit Tab AJAX (v.1.2.2) Fresh Variables (v.1.0) Playa (v.1.0.9) File, by Mark Huot (v.3.1.1)
My guess is that it would be File. Edit Tab AJAX only works on the Edit page, and Fresh Variables is more of a front end thing - except for its setting page.
My guess is that it would be File. Edit Tab AJAX only works on the Edit page, and Fresh Variables is more of a front end thing - except for its setting page.
That was my thought too.
Hm- someone else was linking it back to Tag 2.5- and this thread. But doesn’t look like that’s a solid comonality. I’d look at anything that affects the session cache on the frontend. That could mess up the array.
Another thing to try- around line 440 in mod.weblog.php-
if ($reldata = @unserialize($row['rel_data']))If you remove the @ before unserialize and have errors showing- an unserialize error that might give us a hint.
Hi all,
I am having this problem with Playa as well, and I had it previously with Multi Relationship 1.0.6
I have the following extensions installed:
LG Better Meta (v.1.7.0) LG TinyMCE (v.1.2.1) REEOrder (v.1.0) Multi Relationship (v.1.0.6) LG Member Form Customiser (v.1.1.0) Playa (v.1.3.2)
Multi Relationship and LG Member Form Customiser are disabled because they where causing other problems, but I still get this {REL[]} instead of the related entry.
Any ideas?
Thanks
Hi all, I am having this problem with Playa as well, and I had it previously with Multi Relationship 1.0.6 I have the following extensions installed: LG Better Meta (v.1.7.0) LG TinyMCE (v.1.2.1) REEOrder (v.1.0) Multi Relationship (v.1.0.6) LG Member Form Customiser (v.1.1.0) Playa (v.1.3.2) Multi Relationship and LG Member Form Customiser are disabled because they where causing other problems, but I still get this {REL[]} instead of the related entry. Any ideas? Thanks
Have you tried Ryan’s suggestion from his second post? It worked for me.
Yes I have tried and it did not work.
I have completely uninstalled Multi relationships. It is clearly playa, because the relations field works well when Playa is disable, but as soon as I enable it, it get tha REL nightmare again.
Yes I cleared my cache and all this things…
All this started after I upgraded to 1.6.6 before that the multi-relationships extension was working.
I am on PHP Version 4.4.8, if that makes any difference.
Thanks
I am on PHP Version 4.4.8, if that makes any difference.
That’s the problem. Playa needs PHP5.
Is there any way to run it on 4.4.8?, I tried upgrading to php5 but it breaks my template
Thanks
BTW, I’m on PHP 5.2.6, I changed the priority, and this issue still happens, only with Playa.