2015-08-19 12:15:24 +02:00
|
|
|
# Translation of Odoo Server.
|
|
|
|
# This file contains the translation of the following modules:
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
# * mass_mailing_custom_unsubscribe
|
2018-06-16 09:56:30 +02:00
|
|
|
#
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
# Translators:
|
|
|
|
# OCA Transbot <transbot@odoo-community.org>, 2017
|
2017-07-05 11:07:28 +02:00
|
|
|
# enjolras <yo@miguelrevilla.com>, 2017
|
2015-08-19 12:15:24 +02:00
|
|
|
msgid ""
|
|
|
|
msgstr ""
|
2017-07-05 11:07:28 +02:00
|
|
|
"Project-Id-Version: Odoo Server 10.0\n"
|
2015-08-19 12:15:24 +02:00
|
|
|
"Report-Msgid-Bugs-To: \n"
|
2017-07-05 11:07:28 +02:00
|
|
|
"POT-Creation-Date: 2018-02-26 01:46+0000\n"
|
|
|
|
"PO-Revision-Date: 2018-02-26 01:46+0000\n"
|
|
|
|
"Last-Translator: enjolras <yo@miguelrevilla.com>, 2017\n"
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
"Language-Team: Spanish (https://www.transifex.com/oca/teams/23907/es/)\n"
|
2018-06-16 09:56:30 +02:00
|
|
|
"Language: es\n"
|
2015-08-19 12:15:24 +02:00
|
|
|
"MIME-Version: 1.0\n"
|
|
|
|
"Content-Type: text/plain; charset=UTF-8\n"
|
|
|
|
"Content-Transfer-Encoding: \n"
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
|
2015-08-19 12:15:24 +02:00
|
|
|
|
2018-06-16 09:56:30 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__mailing_list_ids
|
|
|
|
msgid "(Un)subscribed mass mailing lists, if any."
|
2018-06-16 09:56:30 +02:00
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__unsubscriber_id
|
2018-06-16 09:56:30 +02:00
|
|
|
#, fuzzy
|
|
|
|
msgid "(Un)subscriber"
|
|
|
|
msgstr "Se da de baja"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.actions.act_window,name:mass_mailing_custom_unsubscribe.mail_unsubscription_action
|
|
|
|
#: model:ir.ui.menu,name:mass_mailing_custom_unsubscribe.mail_unsubscription_menu
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model_terms:ir.ui.view,arch_db:mass_mailing_custom_unsubscribe.mail_unsubscription_view_graph
|
|
|
|
#: model_terms:ir.ui.view,arch_db:mass_mailing_custom_unsubscribe.mail_unsubscription_view_pivot
|
2018-06-16 09:56:30 +02:00
|
|
|
#, fuzzy
|
|
|
|
msgid "(Un)subscriptions"
|
|
|
|
msgstr "Dados de baja"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__action
|
|
|
|
#: model_terms:ir.ui.view,arch_db:mass_mailing_custom_unsubscribe.mail_unsubscription_view_search
|
2018-06-16 09:56:30 +02:00
|
|
|
msgid "Action"
|
|
|
|
msgstr ""
|
|
|
|
|
2016-07-25 12:50:32 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_needaction
|
|
|
|
msgid "Action Needed"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#. openerp-web
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:89
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:94
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:221
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:230
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:260
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:270
|
|
|
|
#, python-format
|
|
|
|
msgid "An error occured. Please try again later or contact us."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#. openerp-web
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:163
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:169
|
|
|
|
#, fuzzy, python-format
|
|
|
|
#| msgid "Your changes have not been saved, try again later."
|
|
|
|
msgid "An error occurred. Your changes have not been saved, try again later."
|
|
|
|
msgstr "Los cambios no se han guardado, vuelva a intentarlo."
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_attachment_count
|
|
|
|
msgid "Attachment Count"
|
|
|
|
msgstr ""
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: selection:mail.unsubscription,action:0
|
|
|
|
msgid "Blacklisting"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__details_required
|
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription_reason__details_required
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Check to ask for more details when this reason is selected."
|
2017-07-05 11:07:28 +02:00
|
|
|
msgstr "Marcar para pedir más detalles cuando se selecciona este motivo."
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__create_uid
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription_reason__create_uid
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Created by"
|
|
|
|
msgstr "Creado por"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__create_date
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription_reason__create_date
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Created on"
|
2017-07-05 11:07:28 +02:00
|
|
|
msgstr "Creado el"
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__date
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Date"
|
|
|
|
msgstr "Fecha"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: selection:mail.unsubscription,action:0
|
|
|
|
msgid "De-blacklisting"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__details
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Details"
|
|
|
|
msgstr "Detalles"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__details_required
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription_reason__details_required
|
2018-06-16 09:56:30 +02:00
|
|
|
#, fuzzy
|
|
|
|
msgid "Details Required"
|
2017-07-05 11:07:28 +02:00
|
|
|
msgstr "Detalles obligatorios"
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__display_name
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription_reason__display_name
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Display Name"
|
|
|
|
msgstr "Nombre mostrado"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__email
|
|
|
|
#: model_terms:ir.ui.view,arch_db:mass_mailing_custom_unsubscribe.mail_unsubscription_view_search
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Email"
|
2017-07-05 11:07:28 +02:00
|
|
|
msgstr "Emai"
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__failed_message_ids
|
|
|
|
msgid "Failed Messages"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_follower_ids
|
|
|
|
msgid "Followers"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_channel_ids
|
|
|
|
msgid "Followers (Channels)"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_partner_ids
|
|
|
|
msgid "Followers (Partners)"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model_terms:ir.ui.view,arch_db:mass_mailing_custom_unsubscribe.mail_unsubscription_view_search
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
msgid "Group by"
|
|
|
|
msgstr "Agrupar por"
|
2016-07-25 12:50:32 +02:00
|
|
|
|
2018-06-16 09:56:30 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__metadata
|
2018-06-16 09:56:30 +02:00
|
|
|
msgid "HTTP request metadata used when creating this record."
|
|
|
|
msgstr ""
|
|
|
|
|
2016-07-25 12:50:32 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:mail.unsubscription.reason,name:mass_mailing_custom_unsubscribe.reason_not_requested
|
|
|
|
msgid "I did not request this"
|
|
|
|
msgstr "No lo solicité"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:mail.unsubscription.reason,name:mass_mailing_custom_unsubscribe.reason_too_many
|
|
|
|
msgid "I get too many emails"
|
2017-07-05 11:07:28 +02:00
|
|
|
msgstr "Recibo demasiados correos electrónicos"
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:mail.unsubscription.reason,name:mass_mailing_custom_unsubscribe.reason_not_interested
|
|
|
|
msgid "I'm not interested"
|
|
|
|
msgstr "No estoy interesado"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__id
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription_reason__id
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "ID"
|
|
|
|
msgstr "ID"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_unread
|
|
|
|
msgid "If checked new messages require your attention."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_needaction
|
|
|
|
msgid "If checked, new messages require your attention."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_has_error
|
|
|
|
msgid "If checked, some messages have a delivery error."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_mass_mailing_list__not_cross_unsubscriptable
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
msgid ""
|
|
|
|
"If you mark this field, this list won't be shown when unsubscribing from "
|
|
|
|
"other mailing list, in the section: 'Is there any other mailing list you "
|
|
|
|
"want to leave?'"
|
|
|
|
msgstr ""
|
|
|
|
"Si marca esta casilla, esta lista no será mostrada cuando se dé de baja de "
|
|
|
|
"otra lista de correo, en la sección: '¿Hay alguna otra lista de correo que "
|
|
|
|
"quiera dejar?'"
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_is_follower
|
|
|
|
msgid "Is Follower"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription____last_update
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription_reason____last_update
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Last Modified on"
|
2017-07-05 11:07:28 +02:00
|
|
|
msgstr "Última modificación el"
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__write_uid
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription_reason__write_uid
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Last Updated by"
|
|
|
|
msgstr "Última actualización por"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__write_date
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription_reason__write_date
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Last Updated on"
|
2017-07-05 11:07:28 +02:00
|
|
|
msgstr "Última actualización el"
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model,name:mass_mailing_custom_unsubscribe.model_mail_blacklist
|
|
|
|
#, fuzzy
|
|
|
|
msgid "Mail Blacklist"
|
2016-07-25 12:50:32 +02:00
|
|
|
msgstr "Lista de correo"
|
|
|
|
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model,name:mass_mailing_custom_unsubscribe.model_mail_unsubscription
|
|
|
|
#, fuzzy
|
|
|
|
#| msgid "mail.unsubscription"
|
|
|
|
msgid "Mail unsubscription"
|
|
|
|
msgstr "mail.unsubscription"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model,name:mass_mailing_custom_unsubscribe.model_mail_unsubscription_reason
|
|
|
|
#, fuzzy
|
|
|
|
#| msgid "mail.unsubscription.reason"
|
|
|
|
msgid "Mail unsubscription reason"
|
|
|
|
msgstr "mail.unsubscription.reason"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model,name:mass_mailing_custom_unsubscribe.model_mail_mass_mailing_list
|
|
|
|
msgid "Mailing List"
|
|
|
|
msgstr "Lista de correo"
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
|
2018-06-16 09:56:30 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__mailing_list_ids
|
2018-06-16 09:56:30 +02:00
|
|
|
#, fuzzy
|
2019-04-06 01:39:55 +02:00
|
|
|
msgid "Mailing lists"
|
2018-06-16 09:56:30 +02:00
|
|
|
msgstr "Lista de correo"
|
|
|
|
|
2016-07-25 12:50:32 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_main_attachment_id
|
|
|
|
msgid "Main Attachment"
|
|
|
|
msgstr ""
|
2016-07-25 12:50:32 +02:00
|
|
|
|
2018-06-16 09:56:30 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model,name:mass_mailing_custom_unsubscribe.model_mail_mass_mailing
|
|
|
|
msgid "Mass Mailing"
|
2018-06-16 09:56:30 +02:00
|
|
|
msgstr "Envío masivo"
|
|
|
|
|
2016-07-25 12:50:32 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__mass_mailing_id
|
|
|
|
#: model_terms:ir.ui.view,arch_db:mass_mailing_custom_unsubscribe.mail_unsubscription_view_search
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Mass mailing"
|
|
|
|
msgstr "Envío masivo"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__mass_mailing_id
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Mass mailing from which he was unsubscribed."
|
|
|
|
msgstr "Envío masivo del que ha sido dado de baja."
|
|
|
|
|
2018-06-16 09:56:30 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_content
|
|
|
|
#, fuzzy
|
|
|
|
msgid "Message Content"
|
|
|
|
msgstr "Envío masivo"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_has_error
|
|
|
|
msgid "Message Delivery error"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_content
|
|
|
|
msgid "Message content, to be used only in searches"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_ids
|
|
|
|
msgid "Messages"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__metadata
|
2018-06-16 09:56:30 +02:00
|
|
|
msgid "Metadata"
|
|
|
|
msgstr ""
|
|
|
|
|
2016-07-25 12:50:32 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model_terms:ir.ui.view,arch_db:mass_mailing_custom_unsubscribe.mail_unsubscription_view_search
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Month"
|
|
|
|
msgstr "Mes"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__details
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "More details on why the unsubscription was made."
|
|
|
|
msgstr "Más detalles de por qué se dio de baja."
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription_reason__name
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Name"
|
|
|
|
msgstr "Nombre"
|
|
|
|
|
2019-04-06 01:39:55 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_mass_mailing_list__not_cross_unsubscriptable
|
|
|
|
msgid "Not cross unsubscriptable"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_needaction_counter
|
|
|
|
msgid "Number of Actions"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_has_error_counter
|
|
|
|
msgid "Number of error"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_needaction_counter
|
|
|
|
msgid "Number of messages which requires an action"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_has_error_counter
|
|
|
|
msgid "Number of messages with delivery error"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_unread_counter
|
|
|
|
msgid "Number of unread messages"
|
|
|
|
msgstr ""
|
|
|
|
|
2016-07-25 12:50:32 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:mail.unsubscription.reason,name:mass_mailing_custom_unsubscribe.reason_other
|
|
|
|
msgid "Other reason"
|
2017-07-05 11:07:28 +02:00
|
|
|
msgstr "Otro motivo"
|
2015-08-19 12:15:24 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2018-06-16 09:56:30 +02:00
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/models/mail_unsubscription.py:89
|
|
|
|
#, fuzzy, python-format
|
|
|
|
msgid "Please indicate why are you unsubscribing."
|
|
|
|
msgstr "Por favor, indique más detalles de por qué se da de baja."
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2018-06-16 09:56:30 +02:00
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/models/mail_unsubscription.py:98
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
#, python-format
|
|
|
|
msgid "Please provide details on why you are unsubscribing."
|
2017-07-05 11:07:28 +02:00
|
|
|
msgstr "Por favor, indique más detalles de por qué se da de baja."
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription_reason__sequence
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Position of the reason in the list."
|
2017-07-05 11:07:28 +02:00
|
|
|
msgstr "Posición del motivo en la lista."
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__reason_id
|
|
|
|
#: model_terms:ir.ui.view,arch_db:mass_mailing_custom_unsubscribe.mail_unsubscription_view_search
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Reason"
|
2017-07-05 11:07:28 +02:00
|
|
|
msgstr "Motivo"
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription_reason__sequence
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Sequence"
|
|
|
|
msgstr "Secuencia"
|
|
|
|
|
2018-06-16 09:56:30 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: selection:mail.unsubscription,action:0
|
|
|
|
#, fuzzy
|
|
|
|
msgid "Subscription"
|
|
|
|
msgstr "Dados de baja"
|
|
|
|
|
2016-07-25 12:50:32 +02:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model_terms:ir.ui.view,arch_db:mass_mailing_custom_unsubscribe.reason_form
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Thank you!"
|
|
|
|
msgstr "¡Gracias!"
|
|
|
|
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_unread
|
|
|
|
msgid "Unread Messages"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__message_unread_counter
|
|
|
|
msgid "Unread Messages Counter"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model_terms:ir.ui.view,arch_db:mass_mailing_custom_unsubscribe.reason_form
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Unsubscribe now"
|
|
|
|
msgstr "Darse de baja ahora"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2018-06-16 09:56:30 +02:00
|
|
|
#: selection:mail.unsubscription,action:0
|
|
|
|
#, fuzzy
|
|
|
|
msgid "Unsubscription"
|
|
|
|
msgstr "Dados de baja"
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.actions.act_window,name:mass_mailing_custom_unsubscribe.mail_unsubscription_reason_action
|
|
|
|
#: model:ir.ui.menu,name:mass_mailing_custom_unsubscribe.mail_unsubscription_reason_menu
|
|
|
|
msgid "Unsubscription Reasons"
|
2017-07-05 11:07:28 +02:00
|
|
|
msgstr "Motivos de la baja"
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model_terms:ir.ui.view,arch_db:mass_mailing_custom_unsubscribe.reason
|
|
|
|
msgid ""
|
|
|
|
"We would appreciate if you provide feedback about why you updated<br/>your "
|
|
|
|
"subscriptions"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,field_description:mass_mailing_custom_unsubscribe.field_mail_unsubscription__website_message_ids
|
|
|
|
msgid "Website Messages"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__website_message_ids
|
|
|
|
msgid "Website communication history"
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__action
|
2018-06-16 09:56:30 +02:00
|
|
|
msgid "What did the (un)subscriber choose to do."
|
|
|
|
msgstr ""
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__unsubscriber_id
|
2018-06-16 09:56:30 +02:00
|
|
|
#, fuzzy
|
|
|
|
msgid "Who was subscribed or unsubscribed."
|
2016-07-25 12:50:32 +02:00
|
|
|
msgstr "Quién se dio de baja."
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model:ir.model.fields,help:mass_mailing_custom_unsubscribe.field_mail_unsubscription__reason_id
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Why the unsubscription was made."
|
|
|
|
msgstr "Por qué se dio de baja."
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#: model_terms:ir.ui.view,arch_db:mass_mailing_custom_unsubscribe.mail_unsubscription_view_search
|
2016-07-25 12:50:32 +02:00
|
|
|
msgid "Year"
|
|
|
|
msgstr "Año"
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
#. openerp-web
|
2019-04-06 01:39:55 +02:00
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:147
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:199
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:247
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
#, python-format
|
2019-04-06 01:39:55 +02:00
|
|
|
msgid "You are not authorized to do this!"
|
|
|
|
msgstr ""
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
#. openerp-web
|
2019-04-06 01:39:55 +02:00
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:105
|
[9.0][MIG][mass_mailing_custom_unsubscribe] Migrate.
- Imported last updates from v8.
- Adapted to v9.
- Added a saner default to `mass_mailing.salt` configuration parameter by
reusing `database.secret` if available, hoping that some day
https://github.com/odoo/odoo/pull/12040 gets merged.
- Updated README.
- Increase security, drop backwards compatibility.
Security got improved upstream, which would again break compatibility among current addon and future master upstream.
I choose to break it now and keep it secured future-wise, so I drop the backwards compatibility features.
- Includes tour tests.
- Removes outdated tests.
- Extends the mailing list management form when unsubscriber is a contact.
- Adds a reason form even if he is not.
- Avoids all methods that were not model-agnostic.
[FIX][mass_mailing_custom_unsubscribe] Reasons noupdate
After this fix, when you update the addon, you will not lose your customized reasons.
[FIX] Compatibilize with mass_mailing_partner
Current test code was based on the assumption that the `@api.model` decorator on `create()` ensured an empty recordset when running the method, but that's not true. This was causing an incompatibility betwee these tests and the `mass_mailing_partner` addon, which works assuming 0-1 recordsets.
Now records are created from an empty recordset, and thus tests work everywhere.
Update instructions
If the user does not add the unsubscribe snippet, nothing will happen, so it's added to README to avoid confusion when testing/using the addon.
[FIX] Use the right operator to preserve recordsets order
Using `|=` sorts records at will each time (treating them as Python's `set`).
Using `+=` always appends a record to the end of the set.
Since we are using the record position in the set, this caused the test to work sometimes and fail other times. Now it works always.
2016-11-11 14:41:20 +01:00
|
|
|
#, python-format
|
2019-04-06 01:39:55 +02:00
|
|
|
msgid "You have been <strong>successfully unsubscribed from %s</strong>."
|
|
|
|
msgstr ""
|
2017-07-05 11:07:28 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#. openerp-web
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:110
|
|
|
|
#, python-format
|
|
|
|
msgid "You have been <strong>successfully unsubscribed</strong>."
|
|
|
|
msgstr ""
|
2016-07-25 12:50:32 +02:00
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
2019-04-06 01:39:55 +02:00
|
|
|
#. openerp-web
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:205
|
|
|
|
#, python-format
|
|
|
|
msgid ""
|
|
|
|
"You have been successfully <strong>added to our blacklist</strong>. You will "
|
|
|
|
"not be contacted anymore by our services."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#. openerp-web
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:253
|
|
|
|
#, python-format
|
|
|
|
msgid ""
|
|
|
|
"You have been successfully <strong>removed from our blacklist</strong>. You "
|
|
|
|
"are now able to be contacted by our services."
|
|
|
|
msgstr ""
|
|
|
|
|
|
|
|
#. module: mass_mailing_custom_unsubscribe
|
|
|
|
#. openerp-web
|
|
|
|
#: code:addons/mass_mailing_custom_unsubscribe/static/src/js/unsubscribe.js:152
|
|
|
|
#, python-format
|
|
|
|
msgid "Your changes have been saved."
|
|
|
|
msgstr "Se han guardado los cambios"
|
|
|
|
|
|
|
|
#~ msgid ""
|
|
|
|
#~ "Before unsubscribing, could you please tell us why do you want to "
|
|
|
|
#~ "unsubscribe?"
|
|
|
|
#~ msgstr "Antes de darse de baja, ¿podría indicarnos el motivo?"
|
|
|
|
|
|
|
|
#~ msgid "Don't show this list in the other unsubscriptions"
|
|
|
|
#~ msgstr "No mostrar esta lista en las otras bajas"
|
|
|
|
|
|
|
|
#~ msgid "I am unsubscribing because..."
|
|
|
|
#~ msgstr "Me doy de baja porque..."
|
|
|
|
|
|
|
|
#~ msgid "Mailing Unsubscription"
|
|
|
|
#~ msgstr "Baja de lista de correo"
|
2018-06-16 09:56:30 +02:00
|
|
|
|
|
|
|
#~ msgid "Outgoing Mails"
|
|
|
|
#~ msgstr "Correos salientes"
|