Collective.indexing

Latest version: v2.1

Safety actively analyzes 682457 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 5

1.0rc3

-------------------------------------

* Also patch `unrestrictedSearchResults` to flush queued indexing
operations before querying the catalog. This fixes
http://plone.org/products/collective.indexing/issues/2
[mr_savage]

1.0rc2

-------------------------------------

* Fix issue where, when the "auto flush" feature is enabled, an indexing
helper could cause an infinite loop by using the catalog.
[witsch]

* Restore and extend test regarding package installation.
[witsch]

1.0rc1

------------------------------------

* Restored processQueue function as it is conceptually important.
[stefan]

1.0b5

-----------------------------------

* Fix transaction handling to properly abort indexing operations.
[witsch]

* Refactor helper method for auto-flushing the queue to make it more easily
re-usable.
[witsch]

* Enable the monkey patch for `PloneTool.reindexOnReorder` in all versions
of Plone 3.x as it's not been ported upstream yet. This fixes
http://plone.org/products/collective.indexing/issues/1
[witsch]

* Refactor auto-flush monkey-patch to not interfere with testing.
[witsch]

* Patched CatalogTool.searchResults to process the indexing queue before
issuing a query (aka auto-flush).
[stefan]

* Fix test isolation issues and improve test setup.
[witsch]

* Made sure QueueReducer sorts results by opcode. Unindex operations must
be handled before (re)index operations.
[stefan]

* Added processQueue function to process a queue immediately.
[stefan]

* Fixed testModifyObject in Plone 3.1 by clearing the file's creation flag
in afterSetUp.
[stefan]

* Fixed testQueuesOnTwoThreads on Linux by sleeping for a moment so threads
can do their work.
[stefan]

1.0b4

--------------------------------

* Perform processing of the queue during "active" state of the transaction
as additional changes are forbidden in "committing" state. Those changes
can for example be caused by indexes writing back data to content items,
such as the modification time.
[witsch, mj]

1.0b3

--------------------------------

* Fix an issue where objects providing their own `__setattr__` could
potentially not be deleted.
[witsch]

Page 4 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.