Further to another ticket I have raised, I have found the problem appears to be with FK Relations

I have created three cross ref tables, made sure there is data available, and dragged those three fields types into a form

In the BACKEND two work seamlessly, one just doesnt pull in any data (I have removed and recreated), just asks me to choose some options.. which are not there to choose

IN the FRONT END, none of the fields pull in data

This is also confirmed in SANDBOX

Project BidS...e (name is a brand not yet ready for release)

Main table - Films
xRef tables - Four in total, all used in the LEGAL form section


Front end - PLEase use the My Portfoilio view and click NEW, legal section again

I had a table called RIGHTS which is one of the affected FK, and I though maybe due to the word right being protected as a SQL term it may be the problems.

Changed instances of this word.. made no difference..

I am currently checking.

Much appreciated, this is the only thing actually stopping me signing off a project over for user testing this evening!

Fixed.

Much better now.
Right ?

BooYA!

Works beautifully!

Should I ideally download a new install package for these fixes?

Only

models/fil..s.php :

__construct() :

Remove the suffixes in the relation name:
ex : myrelation_1 > myrelation.

It is because Cook has planned to manage multiple instances of the same XRef on different fields, but in future...
At the moment nobody is asking that. It was just messing up because you instance twice the same relation (back and front)
But it should not do that. It was a Bug.