All add-ons currently require PHP 7.4 or greater.
On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.
Please read about the changes to BoldMinded add-on licensing.
Ticket: Entry Statuses Changed On Import
| Status | Resolved |
| Add-on / Version | DataGrab 4.0.5 |
| Severity | |
| EE Version | 6.3.4 |
Gregory Maher
Oct 27, 2022When importing a set of Entries to update specific fields, without a Status column in the CSV and not expecting the Status to change, all Statuses were changed to Open from previously set values of “Closed” or “private”. No errors were received, but Statuses are now incorrect on all imported entries. Previously, Statuses did not change if not specified.
The dropdown for Status under Other Settings should contain a “Do Not Change” option, I’d imagine?
We see there a change to Statuses in Version 4.1.0, but we’re not sure if this addresses the above unexpected behavior.
BoldMinded (Brian)
A you share a screenshot of the import config? Specifically the value of the status setting near the bottom?
Gregory Maher
Comment has been marked private.
BoldMinded (Brian)
And what is the channel default set to?
Gregory Maher
The Channel Default is set to Open.
But, if there are 100 Entries, with 30 set to “private” and we update a few fields on the 100 Entries, those 30 should not revert to “Open”.
Am I missing a setting?
BoldMinded (Brian)
Comment has been marked private.
BoldMinded (Brian)
I’m not sure I’ve changed anything that would cause this error. Looking at the code it seems to have always used the channel default status when importing new or existing entries if it can’t find another valid status to use.
BoldMinded (Brian)
Comment has been marked private.
Gregory Maher
Hi Brian, The last update you shared worked for us just fine. But, I’ll replace with this latest build, as needed.
Thanks so much for staying on top of it!
Greg