I tried to install collective.behavior.banner as Bauer wrote in
32. Using Third-Party Behaviors – Mastering Plone 5 development — Plone Training 2023 documentation,
but after running bin/buildout -vv it requries plone.app.imaging,
i added plone.app.imaging to buildout.cfg
the bin/buildout -vv gave info:
# Required by:
Products.Archetypes = 1.16.5
i dont know why plone.app.imaging in my Plone 5.2 need this Products.Archetypes?
when running bin/client fg i got error:
eggs/Products.Archetypes-1.16.5-py3.8.egg/Products/Archetypes/__init__.py", line 2, in <module>
ModuleNotFoundError: No module named 'bbb'
and no way i can surpass this error.
Please could you give any advice or better banner/slider system for Plone 5.2?
Many thanks for your time.
here is my buildout.cfg:
# added after collective.behavior.banner requires plone.app.imaging
collective.behavior.banner = git https://github.com/collective/collective.behavior.banner.git email@example.com:collective/collective.behavior.banner.git rev=84abbfd
#plone.app.imaging = git https://github.com/plone/plone.app.imaging.git rev=297520a
Instead of using a source checkout with a fixed revision of collective.behavior.banner better use a release. You are depending on a quite old version/revision of this package, but the current released one should be able to run with Plone 5.2. Just remove collective.behavior.banner from
auto-checkout. You might add it to the
[versions] section to make sure a specific version is picked.
plone.app.imaging source definition. It is not checked out anyways (the entry in
auto-checkout is missing) and should not be necessary.
The buildout file would look like:
collective.behavior.banner = 2.0
Then re-run buildout.
But I don't see that this would solve the problem when checking the revision of your checkout GitHub - collective/collective.behavior.banner at 84abbfd6a1afd617bf6235f66796d6ff1a6c15c0
The dependencies in setup.py look OK.
But give this a try. You got this error after adding collective.behavior.banner, so there is a good chance that this solves it.
Btw, @pbauer just released version 2.0 a few minutes ago
Thank you @thet for your help, your time!
it needs a little change in
thank you and @pbauer !!!