Kim Paulissen

@svx can we close this issue or is it needed as a gentle reminder 😄

There are still some references to paster in the docs, I can start a cleanup Can I remove this zopeskel exception from the common exceptions list?https://docs.plone.org/manage/troubleshooting/exceptions.html#from-zopeskel-basic-namespace-import-basicnamespace @svx, @polyester opnions?

new list of editors on https://www.jetbrains.com/lp/python-developers-survey-2020/ unsure if you should continue this if for Plone 6 we're moving to a markdown based setup?

We also have this issue on production sites. I agree with the renaming being a good fix option, maybe be aware that it might break honeypot solutions since they use...

@frapell sure. - https://admin.kuleuven.be/icts/english/services/wms/content/forms_PloneFormGen (look for honeypot in page) - https://sixfeetup.com/blog/captchas-plone-site-honeypot-fields In easyform there is a custom class field for this, in pfg I guess this honeypot field would be...

Maybe useful to note that we usually have this issue with old and new style fieldsets, and not with folders

For consistency, we might consider using validation as in easyform?