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

Entry status not getting changed to "disabled" when updating entries from import #760

Closed
brimby opened this issue Nov 2, 2020 · 5 comments
Labels

Comments

@brimby
Copy link

brimby commented Nov 2, 2020

Description

If an already existing enabled entry is to be updated from an import to have a status of disabled, the status does not change.

Steps to reproduce

  1. Have an enabled entry.
  2. Run a json import with an entry that corresponds to the existing enabled entry, and the only changed value is a value of 0 on the property that is linked to the status attribute of the entry. You can have the default value of the field as either "Don't import" or "disabled" and the result should be the same.
  3. Run import which is set to "add and update and delete" entries. Status on updated entry should remain as enabled, in spite of the 0 value on the import.
  4. If you delete the entry and run the import again, the entry should be created as disabled (as it should), so the bug only seems to relate to updating entries and not when "adding" them.

Additional info

  • Craft version: 3.5.13.2
  • PHP version: 7.2
  • Database driver & version:
  • Plugins & versions: Feed Me 4.2.4
@brimby brimby added the bug label Nov 2, 2020
@kristiansp
Copy link
Contributor

@brimby If you explicitly give the status field the value of disabled, it would make sense that it also disables the entry when you have import strategy set to update, no? I mean, in this case the disabling of the entry is a side effect of the import (whereas disable as an import strategy will disable existing entries that don't appear in the feed). Or did I misunderstand?

@gstjohn
Copy link
Contributor

gstjohn commented Nov 6, 2020

Experiencing the same and have found a fix. PR incoming.

@brimby
Copy link
Author

brimby commented Nov 6, 2020 via email

@brimby
Copy link
Author

brimby commented Nov 6, 2020 via email

@brandonkelly
Copy link
Member

Feed Me 4.3.0 is out now @gstjohn’s PR #765.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants