Hi!
Did you solved this already? Because I found something that could be related
Lets see this query
github.com/FLEXIcontent/flexicontent-cck...tent.fields.php#L344
I have a custom field that copy a core field. I have it assigned to mytypeA and it appears on mytemplate1. Nowadays, when I´m looking a mytypeB article, the field appears again, why?
If you haven´t solved the social toolbar problem (can´t confirm, I haven´t installed last versions), I think is the same problem. I executed a similar query and got something like
Code:
SELECT fi.name, ftrel.*
FROM joom_flexicontent_fields AS fi
LEFT JOIN joom_flexicontent_fields_type_relations AS ftrel ON (ftrel.field_id = fi.id) AND ftrel.type_id = 5
WHERE fi.published = 1
GROUP BY fi.id
ORDER BY ftrel.ordering, fi.ordering, fi.name
Code:
name, field_id, type_id
field1, null, null
fieldcorrectlyassigned, 80, 5
So on the fields assigned, it appears "fieldcorrectlyassigned", but also "field1", that is not assigned. Why that nulls? Because is a left join and the "AND ftrel.type_id = 5" criteria is on the "on" clause
If I do instead
Code:
SELECT fi.name, ftrel.*
FROM joom_flexicontent_fields AS fi
LEFT JOIN joom_flexicontent_fields_type_relations AS ftrel ON (ftrel.field_id = fi.id)
WHERE fi.published = 1
AND ftrel.type_id = 5
GROUP BY fi.id
ORDER BY ftrel.ordering, fi.ordering, fi.name
The results are
Code:
name, field_id, type_id
fieldcorrectlyassigned, 80, 5
More info here:
www.tech-recipes.com/rx/47637/inner-and-...clause-vs-on-clause/
What do you think? I´m correct about this? I guess that this normally is not an issue because there are other checks (the templates are differents, have different assignations, have empty values...)
