Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix imports #30436

Open
wants to merge 1 commit into
base: 18.0
Choose a base branch
from
Open

fix imports #30436

wants to merge 1 commit into from

Conversation

altairis-tof
Copy link
Contributor

keyfield may content any field defined in import_fieldshidden_array so the present code dont do updates !

@@ -929,9 +929,9 @@ public function import_insert($arrayrecord, $array_match_file_to_database, $obji
// Note: For extrafield tablename, we have in importfieldshidden_array an enty 'extra.fk_object'=>'lastrowid-tableparent' so $keyfield is 'fk_object'
$sqlSelect = "SELECT rowid FROM ".$tablename;

if (empty($keyfield)) {
//if (empty($keyfield)) { keyfield may content any hidden update field !!!
Copy link
Member

@eldy eldy Jul 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which value of keyfield did yo get.
Also can you describe the process to reproduce the bug with example of selected/entered values ?
Do you experience the trouble in v19 ?

@eldy eldy added PR waiting more user feedbacks We are waiting feedback of someone or more testers to validate this PR Bug or PR need more information This bug or PR needs more information (answer to a question or more accurate description) and removed PR waiting more user feedbacks We are waiting feedback of someone or more testers to validate this PR labels Jul 23, 2024
@rycks
Copy link
Contributor

rycks commented Jul 25, 2024

@altairis-tof i need more informations too ...

for information in 20.0 you seems to made a different fix : #29553 no ?

and in case of fix for that bug, i think xls import will be concerned too

@eldy could a backport of 20.0 fix be a better solution in same situation ?

@eldy
Copy link
Member

eldy commented Jul 25, 2024

@altairis-tof i need more informations too ...

for information in 20.0 you seems to made a different fix : #29553 no ?

and in case of fix for that bug, i think xls import will be concerned too

@eldy could a backport of 20.0 fix be a better solution in same situation ?

@rycks Yes, if a bug is already fixed in a higher version, a fix for a backport should use the same way to fix than the fix in higher version. It is always a better solution, as long as it is possible. This may not be possible if backport/cherry-pick is not possible because the fix in recent version is based on other changes done by other PR available only into the recent version.

@rycks
Copy link
Contributor

rycks commented Sep 12, 2024

@altairis-tof what do you think about that ? different solution with #29553 looks strange and make me trouble ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug or PR need more information This bug or PR needs more information (answer to a question or more accurate description)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants