Plone.app.multilingual

Latest version: v8.1.4

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

Scan your dependencies

Page 10 of 17

5.0.5

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

Bug fixes:

- Remove travis integration because plone.app.mutlilingual is part of plonecore and should be tested there.
- Fix bug where form controls were overlapped by fields.
[agitator]

- Fix robot tests to work with improved related items widget.
[thet]

5.0.4

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

New features:

- Add a new view ``tg`` for translatable content. It will return the
current translation group of the content, matching the behavior of ``uuid``
of ``plone.app.uuid`` returning UUID of the content. [datakurre]

5.0.3

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

New features:

- Show Translate menu in INavigationRoot items and hide in ILanguageRootFolders
[erral]

Bug fixes:

- Remove deprecated __of__ calls on BrowserViews
[MrTango]

5.0.2

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

Bug fixes:

- Add new tests for sitemap.xml.gz (it is currently not listing any content)
[djowett]

5.0.1

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

Bug fixes:

- Allow to work in an Archetypes free Plone 5.1.
[jensens]

- Replace unittest2 with unittest.
[jensens]

5.0

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

Breaking changes:

- Support for Archetypes content is only installed if you install `archetypes.multilingual.
For Archetypes support, there is a new ``archetypes`` ``extras_require``, which you can depend upon.
[davisagli]

New features:

- Replaced add_translations and remove_translations with combined modify_translations.
Modify translations page gives you an overview of existing translations and has actions
to connect, disconnect existing translations, as well as actions to create or delete a translation for you content item.
[agitator]

- Moved stylesheet from legacy bundle to logged-in bundle
[agitator]

Bug fixes:

- Made robot tests more robust, I hope.
Before using 'Wait until element is visible',
first call 'Wait until page contains element'.
The first one only works reliably when the element was already on the page initially.
If the element was created dynamically, you need to use the 'page contains' call first,
otherwise you sometimes get an error:
'Element not found in the cache - perhaps the page has changed since it was looked up.'
[maurits]

Page 10 of 17

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.