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

"Import strategy" checkboxes can't be changed with feed-me version 4.3.0 #769

Closed
thijskaspers opened this issue Nov 8, 2020 · 3 comments
Labels

Comments

@thijskaspers
Copy link

thijskaspers commented Nov 8, 2020

Description

I've updated to the latest version and I can no longer change the "Import strategy" checkboxes. No matter what I select, after saving the settings, only the first checkbox remains checked (Create new elements).

Steps to reproduce

  1. Have the newest feed-me plugin (4.3.0)
  2. Create a new feed
  3. Set element type to "Entry"
  4. Change the "Import strategy", e.g. select "Create new elements", "Update existing elements" and "Delete missing elements")
  5. Hit save

Schermafbeelding 2020-11-08 om 18 03 01

Additional info

  • Craft version: 3.5.15.1
  • PHP version: 7.3
  • Database driver & version: MariaDB 10.4
  • Plugins & versions: Feed-me 4.3.0
@thijskaspers thijskaspers changed the title "Import Strategy" checkboxes can't be saved with feed-me version 4.3.0 "Import Strategy" checkboxes can't be changed with feed-me version 4.3.0 Nov 8, 2020
@thijskaspers thijskaspers changed the title "Import Strategy" checkboxes can't be changed with feed-me version 4.3.0 "Import strategy" checkboxes can't be changed with feed-me version 4.3.0 Nov 8, 2020
@thijskaspers
Copy link
Author

Addition: found out this only happens when element type is set to "Entry"

@johndwells
Copy link

Came here to report this - however it isn't that the values aren't being saved, it is that the checkboxes are not re-checked when you re-visit the settings page. So it means that EVERY time you want to edit a field, you have to be sure to re-check those boxes desired.

@brandonkelly
Copy link
Member

Sorry about that. Just released 4.3.1 with a fix for this.

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

3 participants