I was using your extension in my SAEF and everything worked perfect.
To make it work I just called the “modify_post” method with the “weblog_standalone_insert_entry” hook.

When I updated to 1.6.1(I think that was the reason) it stopped working. After banging my head a lot I found that the array “$submitted_mrel” is empty (it’s actually not empty, the array structure still exists, only the values are empty) when it is accessed in the method “submit_relation” so commenting out “unset($_POST[“field_id_”.$field[“field_id”]]);” around line 398 fixed it again.

It’s just that commenting out that line doesn’t feel very safe, so for certainty I duplicated the method just for the saef hook.

Now my question is if you have any idea why that array suddenly is empty and if it is safe to just comment out that line?

mArsmAn - 20 November 2007 04:27 AM

When I updated to 1.6.1(I think that was the reason) it stopped working.

A 1.6.1 fix would be very nice.

jonathanpoh - 03 October 2007 05:41 AM

Thanks! I’ll look for that plugin and see if it works. Cheers

Just wondering if you got switchplus working? I just did, having found myself in the same situation as you and it worked a treat.

Details are here - you can see my code in that thread, but as it’s relevant here too…

The trick is to make sure the switchplus tags are outside of the related entries tags.

Hope that helps. Thanks Mr. Wilson for the plugin : )

I’m unclear about something. Does this extension work with 1.6?

MediaGirl Inc. - 03 December 2007 12:17 PM

I’m unclear about something. Does this extension work with 1.6?

Do you mean multi relation because I use it on 1.61 ok.

Hmmm. Not sure why but I couldn’t getting it 100% working on v1.61. I could never get it to print out any data. I could see that it was getting pushed to the database correctly but it wasn’t getting called back out in the template.

Yeah, I’m not getting this to work for 1.6.1.  I’m trying to use it for reverse related but it’s not outputting the entries:

{exp:weblog:entries weblog=“navigation” status=“not closed|test”  orderby=“title”  disable=“member_data|pagination|trackbacks” dynamic=“off”}

{reverse_related_entries weblog=“about” sort=“desc” orderby=“title”}
{title}

{/reverse_related_entries}

{/exp:weblog:entries}

Using 1.06 on EE1.6.1 I’m getting a problem with relationships being deselected. If I have an entry where I’ve previously set up relationships and edit that entry then the previously selected relationships are highlighted as expected. If during the edit process I do not complete a required field and then click on the Update button the page refreshes and displays the relevant error message but all my selected relationships are now unselected.

Just wondering generally what would be involved in changing the multi relation dropdown list into checkboxes instead, much as the category checkbox extension works?  From a usability point of view it makes so much more sense to me. I’d just love to have checkboxes instead of a dropdown

Thanks Mark, this is just what I was looking for! awesome stuff

Not sure if anyone knows how to fix this yet but I read through the 6 pages after I got the same error as others:

{REL[64][shopping_rel]dcZtrmAHREL}{REL[65][shopping_rel]dcZtrmAHREL}

I’m trying to relate a set of alarm batteries with the alarm is goes with within the same weblog of “shopping”

Tried the mod.weblog.php hack as someone says it fixed there problem even though they had php5 (which i believe i have) and that gave me the error below

Parse error: syntax error, unexpected T_STRING in mod.weblog.php on line 3124

Any ideas? many thanks!

The Parse error looks like you missed a quote or a semi colon somewhere in the hack, so I’d double check that first. Then I’d clear all your caches in EE (sometimes that causes a problem if you’ve recently moved servers).

Legend Mark, all I had to do was clear the cache in EE and away it went thanks again

Not to be a pain but did anyone find a fix for the quick save button wiping the contents of the menu? thanks

Not to be a pain but did anyone find a fix for the quick save button wiping the contents of the menu? thanks

Likewise with all relationships being deselected if an entry is updated and reloads with an error message because a required field hasn’t been filled for example.

Is it possible to control the order the related entries (in this case, related gallery entries) appear? As far as I can see, they appear in a random order on the publish page (I have it set to sort by title and descending), and they appear in the same order on the actual website.

Another possible issue:

When I view the post with the relations after editing (as in, within EE’s control panel still), it lists a set if numbers at the end. One for each relation, it looks like. However, it appears they increment every time I edit; this is my first entry with relations, but they’re up to 20-27 now.

Andrew Munro - 13 December 2007 01:52 AM

Not to be a pain but did anyone find a fix for the quick save button wiping the contents of the menu? thanks

This is a well known issue and I don’t think there is a fix for it. I could be wrong, but I think you’ll find if you read deep enough that the Quick Save and Submit/Update use different hooks and there wasn’t a way to update this extension so that its info is saved if you use Quick Save.

Every site I’ve installed multi-relation on I’ve either had to inform th client not to use the “Quick Save” button, or I’ve had to install the Publish Improve extension to hide the Quick Save button.

Anyone else see the issues I described above with the sorting being random rather than following the setup and the odd incrementing of the numbers?