Bug #34148
closedt3lib_loadDBGroup::start() does not recognize a multitable relationship if $MM_oppositeFieldConf['allowed'] is "*"
100%
Description
t3lib/class.t3lib_loaddbgroup.php:109-114
if ($this->MM_oppositeFieldConf['allowed']) {
$oppositeFieldConf_allowed = explode(',', $this->MM_oppositeFieldConf['allowed']);
if (count($oppositeFieldConf_allowed) > 1) {
$this->MM_isMultiTableRelationship = $oppositeFieldConf_allowed[0];
}
}
should be:
if ($this->MM_oppositeFieldConf['allowed']) {
$oppositeFieldConf_allowed = explode(',', $this->MM_oppositeFieldConf['allowed']);
if (count($oppositeFieldConf_allowed) > 1 || $this->MM_oppositeFieldConf['allowed']=='*') {
$this->MM_isMultiTableRelationship = $oppositeFieldConf_allowed[0];
}
}
Files
Updated by Markus Klein over 12 years ago
Hello Markus,
Do you mind pushing this patch to gerrit?
Thanks, Markus
Updated by Stefan Galinski over 12 years ago
Updated by Gerrit Code Review over 12 years ago
- Status changed from New to Under Review
Patch set 1 for branch TYPO3_4-5 has been pushed to the review server.
It is available at http://review.typo3.org/9150
Updated by Gerrit Code Review over 12 years ago
Patch set 2 for branch TYPO3_4-5 has been pushed to the review server.
It is available at http://review.typo3.org/9150
Updated by Gerrit Code Review over 12 years ago
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/9156
Updated by Steffen Gebert over 12 years ago
- Category set to Backend API
Could you please add information, how to easily repoduce this bug?
Updated by Markus Opahle over 12 years ago
Steps to reproduce:
1. Install the attached extension (it depends on dam to have a multitable mm relation)
2. The Extension provides 2 Models "Foo" and "Bar". Create one Record of each Model and add some images to the images field of these records.
3. Check that both Records have the same id
4. Make a copy of one of these records and check the images relation of the copy.
5. Note that the new copy has the images form both records (Foo and Bar), which is wrong.
Apply the patch and redo step 4 and 5 to see that this works as expected now.
Please note that the bug is not related to the dam extension. It is just used to keep the example simple. You can reproduce this with any other mm relation which uses a "tablenames" field to refer to multiple tables.
Updated by Markus Opahle over 12 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset ec212a7d9c07830985106f6c26afab7d99033931.
Updated by Gerrit Code Review over 12 years ago
- Status changed from Resolved to Under Review
Patch set 1 for branch TYPO3_4-7 has been pushed to the review server.
It is available at http://review.typo3.org/9580
Updated by Markus Opahle over 12 years ago
- Status changed from Under Review to Resolved
Applied in changeset 76d75d972f0e45753824848f0934abd7ee9b7e48.
Updated by Gerrit Code Review over 12 years ago
- Status changed from Resolved to Under Review
Patch set 1 for branch TYPO3_4-6 has been pushed to the review server.
It is available at http://review.typo3.org/13015
Updated by Markus Opahle over 12 years ago
- Status changed from Under Review to Resolved
Applied in changeset 66d5e439fffb80e066f5220bd109e82476cd0492.