Work out what to include in the first stable release of Scanner v2.

Comments

damienmckenna created an issue. See original summary.

damienmckenna’s picture

FYI in #3462717: Node logic only processes first value, looses other values in multi-value text fields I discovered some kinda critical problems with the current architecture that result in data loss, so I'm working on some refactoring before the full release. Stay tuned for more details.

damienmckenna’s picture

I recently tagged 2.0.0-beta2, which includes a significant number of fixes and improvements: https://www.drupal.org/project/scanner/releases/2.0.0-beta2

Work is continuing on improvements, on both coding standards and functionality, hopefully we'll be able to tag an rc soon.

damienmckenna’s picture

I tagged 2.0.0-beta3 where it now shows the matched results on the replacement confirmation page and completion page: https://www.drupal.org/project/scanner/releases/2.0.0-beta3

There's still a little bit of work to go towards making v2 stable, it's almost there.

smustgrave’s picture

Just did a beta4 release with a few fixes including the D12 stuff.

smustgrave’s picture

Had a good chunk of contrib time and got a number of items merged. I updated our test structure to hopefully avoid duplicate snippets. Added a few items I'd also like to see get done before we mark 2.0.0. Specifically #3364450: Improve the field selection UI and #3560456: When I try to perform a replace operation in the Search and Replace Scanner module, the Search button is triggered instead (better title needed)

smustgrave’s picture

Status: Active » Fixed

I'm going to self merge #3364450: Improve the field selection UI think we can fine tune after a stable release. But by not having one means we aren't really covered by security. Had to fix the latest finding directly and not with a planned security advisory.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.