Plone.app.testing

Latest version: v7.1.0

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

Scan your dependencies

Page 6 of 9

5.0b5

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

- Do not install CMFDefault.
[tomgross]

- Document PloneWithPackageLayer.
[gotcha]

5.0b4

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

- Do not install CMFFormController.
[timo]

- Do not install CMFDefault
[tomgross]

5.0b3

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

- Remove PloneLanguageTool from PloneFixture.
[timo]

5.0b2

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

- remove test of applying an extension profile, we don't have a good one to
test now.
[davidagli]

- fix test, plone.app.theming does not get recorded as installed .
[davisagli]

- fix: ``Products.CMFPlone`` needs the ``gopip`` index from
``plone.app.folder``. So latter has to be initialized before CMFPlones
profile is applied (which installs the index to catalog). At the moment
CMFPlone therefore registers the index itself, but plone.app.folder
registers it too, which resulted in plone/Products.CMFPlone313
"GopipIndex registered twice" In tests the registration does not succeed,
because plone.app.folder was never initialized as z2 products. In order to
remove the misleading regisatration from CMFPlone we must take care that the
index is available, which is achieved with this change. Also minor pep8
optimizations in the file touched.
[jensens]

- create memberfolder, if it is not there for testing.
[tomgross]

5.0b1

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

- Allow applyProfile to skip steps and all other options supported by
runAllImportStepsFromProfile of portal_setup-tool.
[pbauer, tomgross]

5.0a2

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

- Install Products.DateRecurringIndex for the PLONE_FIXTURE Layer.
[thet]

Page 6 of 9

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.