Zest-emailhider

Latest version: v3.1.3

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

Scan your dependencies

Page 1 of 3

3.1.4

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

- Nothing changed yet.

3.1.3

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

- Make 'No uids found in request.' a warning instead of an error.
I see bots requesting this url. [maurits]

3.1.2

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

- Do not render our javascript inline. It leads to display problems
when it is included on a 404 page or any other non 20x page:
an assertion in ``Products.ResourceRegistries`` fails, resulting in
the html being returned with mimetype javascript.
That seems a possible problem with any inline script.
Added upgrade step for this.
[maurits]

3.1.1

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

- Fixed javascript bug that caused a request even without any emails to reveal.
[maurits]

3.1

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

- Query and reveal all emails at once. If you have an employee
content type that you have hooked up to zest.emailhider, and you
have a page showing fifty employees, previously we would fire fifty
ajax requests. Now we gather everything into one request.
[maurits]

3.0

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

- Added Travis badge.
[maurits]

- Support Plone 5 by reading ``plone.email_from_address`` from the
registry. This loses compatibility with Plone 4.0. We try reading
any email (also your own additional emails) from the registry first,
with ``plone.`` prepended, and then look for a property on the
portal root.
[maurits]

- Use ``$`` instead of ``jq`` in our javascript. Now it works without
needing ``jquery-integration.js``. This loses compatibility with
Plone 3.
[maurits]

- Added ``test_emailhider`` page that hides the portal
``email_from_address``, so you can easily test it. When you disable
your javascript you should not see an email address.
[maurits]

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.