diff --git a/.github/styles/Mautic/FeatureList.yml b/.github/styles/Mautic/FeatureList.yml index 1a4dff00..a83f4872 100644 --- a/.github/styles/Mautic/FeatureList.yml +++ b/.github/styles/Mautic/FeatureList.yml @@ -45,6 +45,8 @@ swap: point actions: Point Actions point triggers: Point Triggers points: Points + group: Group + groups: Groups plugin: Plugin plugins: Plugins report: Report diff --git a/.readthedocs.yaml b/.readthedocs.yaml similarity index 94% rename from .readthedocs.yaml rename to .readthedocs.yaml index 416e26bf..e6f30f62 100644 --- a/.readthedocs.yaml +++ b/.readthedocs.yaml @@ -26,4 +26,4 @@ sphinx: # Optionally declare the Python requirements required to build your docs python: install: - - requirements: docs/requirements.txt \ No newline at end of file + - requirements: docs/requirements.txt diff --git a/.vscode/welcome.md b/.vscode/welcome.md index 0a805440..fca312be 100644 --- a/.vscode/welcome.md +++ b/.vscode/welcome.md @@ -1,9 +1,9 @@ -Welcome to the Mautic end user documentation editor! +Welcome to the Mautic End User documentation editor., open -We've already set up everything you need. To get started, follow these steps: -1. Open a file in the `docs/` folder (files that end with `.rst` are docs files) -2. Click the magnifier icon in the top right corner to see a LIVE preview of the file you're editing +Everything you need is already set up. To get started, follow these steps: +1. Open a file in the `docs/` folder - files that end with `.rst` are docs files. +2. Click the magnifier icon in the top right corner to see a live preview of the file you're editing. Pretty cool, right? -Happy writing! +Happy writing. diff --git a/README.md b/README.md index eed811a9..d2d8ea6f 100644 --- a/README.md +++ b/README.md @@ -62,9 +62,10 @@ The following provides instructions for how to build docs locally for visualizat 1. Install Python 3 for your OS if not already installed 2. Install Sphinx `pip install sphinx` 3. Install sphinx-rtd-theme `pip install sphinx-rtd-theme` -4. CD into the docs directory `cd [path to this repo]/docs` -5. Run `make html` -6. This will generate HTML in docs/build/html. Setup a web server with the web root as docs/build/html or open docs/build/html/index.html in a browser. +4. Install MyST Parser `pip install myst_parser` +5. CD into the docs directory `cd [path to this repo]/docs` +6. Run `make html` +7. This will generate HTML in docs/build/html. Setup a web server with the web root as docs/build/html or open docs/build/html/index.html in a browser. ### Vale Before pushing, run Vale and address suggestions and errors as applicable. diff --git a/docs/.tx/config b/docs/.tx/config deleted file mode 100644 index 4fdc0770..00000000 --- a/docs/.tx/config +++ /dev/null @@ -1,203 +0,0 @@ -[main] -host = https://www.transifex.com - -[o:mautic:p:mautic-end-user-docs-2:r:README] -file_filter = locale//LC_MESSAGES/README.po -source_file = docs_translations/README.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:authentication] -file_filter = locale//LC_MESSAGES/authentication.po -source_file = docs_translations/authentication.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:builders] -file_filter = locale//LC_MESSAGES/builders.po -source_file = docs_translations/builders.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:campaigns] -file_filter = locale//LC_MESSAGES/campaigns.po -source_file = docs_translations/campaigns.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:categories] -file_filter = locale//LC_MESSAGES/categories.po -source_file = docs_translations/categories.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:channels] -file_filter = locale//LC_MESSAGES/channels.po -source_file = docs_translations/channels.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:companies] -file_filter = locale//LC_MESSAGES/companies.po -source_file = docs_translations/companies.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:components] -file_filter = locale//LC_MESSAGES/components.po -source_file = docs_translations/components.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:configuration] -file_filter = locale//LC_MESSAGES/configuration.po -source_file = docs_translations/configuration.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:contacts] -file_filter = locale//LC_MESSAGES/contacts.po -source_file = docs_translations/contacts.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:dashboard] -file_filter = locale//LC_MESSAGES/dashboard.po -source_file = docs_translations/dashboard.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:getting_started] -file_filter = locale//LC_MESSAGES/getting_started.po -source_file = docs_translations/getting_started.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:index] -file_filter = locale//LC_MESSAGES/index.po -source_file = docs_translations/index.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:marketplace] -file_filter = locale//LC_MESSAGES/marketplace.po -source_file = docs_translations/marketplace.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:overview] -file_filter = locale//LC_MESSAGES/overview.po -source_file = docs_translations/overview.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:plugins] -file_filter = locale//LC_MESSAGES/plugins.po -source_file = docs_translations/plugins.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:points] -file_filter = locale//LC_MESSAGES/points.po -source_file = docs_translations/points.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:queue] -file_filter = locale//LC_MESSAGES/queue.po -source_file = docs_translations/queue.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:reports] -file_filter = locale//LC_MESSAGES/reports.po -source_file = docs_translations/reports.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:search] -file_filter = locale//LC_MESSAGES/search.po -source_file = docs_translations/search.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:segments] -file_filter = locale//LC_MESSAGES/segments.po -source_file = docs_translations/segments.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:stages] -file_filter = locale//LC_MESSAGES/stages.po -source_file = docs_translations/stages.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:themes] -file_filter = locale//LC_MESSAGES/themes.po -source_file = docs_translations/themes.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:translations] -file_filter = locale//LC_MESSAGES/translations.po -source_file = docs_translations/translations.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - -[o:mautic:p:mautic-end-user-docs-2:r:users_roles] -file_filter = locale//LC_MESSAGES/users_roles.po -source_file = docs_translations/users_roles.pot -type = PO -minimum_perc = 0 -replace_edited_strings = false -keep_translations = false - diff --git a/docs/campaigns/campaign_builder.rst b/docs/campaigns/campaign_builder.rst index 0f4781bc..ce629ed3 100644 --- a/docs/campaigns/campaign_builder.rst +++ b/docs/campaigns/campaign_builder.rst @@ -58,7 +58,7 @@ The actions that Mautic offers in a Campaign include: * - **Add Company action** - Associates a Contact with a Company and sets the Company as the primary Company for the Contact. * - **Adjust Contact Points** - - Adds or subtracts Points from the Contact’s Point total. + - Adds or subtracts Points from the Contact’s Point total or Group. * - **Change Campaigns** - Removes a Contact from the existing Campaign, moves them into another Campaign, restarts the current Campaign or a combination of these. You must remove a Contact from a Campaign before restarting the Campaign. * - **Change Contact's Stage** @@ -205,6 +205,8 @@ Here are the different conditions that Mautic offers in the Campaign Builder: - Checks if the Contact is a member of selected Segments. * - **Contact Tags** - Checks if specified Tags are on the Contact record. + * - **Contact points** + - Checks if the Contact has a certain number of Points or a Group score. * - **Form field value** - Checks if values submitted for a selected field on a selected Form matches specified criteria. * - **Has active notification** diff --git a/docs/channels/emails.rst b/docs/channels/emails.rst index 8fdda909..d1f33b1e 100644 --- a/docs/channels/emails.rst +++ b/docs/channels/emails.rst @@ -309,7 +309,7 @@ This is how it would be set up in Mautic's Email configuration: To replace the Sendgrid API key, add it to the relevant field in the Email configuration and save. Mautic now uses the Sendgrid API to send Emails. .. warning:: - It's a nice perk that Mautic can use any transport provided by Symfony Mailer. However, be aware that such transports (from Symfony) don't support batch sending, even via API. They only send one email per request, as opposed to a thousand emails per request as is the case with some Mautic transports, which can make them slow at scale. They also don't support transport callback handling used for bounce management. If you plan to send larger volumes of Emails or need to use features which require callback handling, please consider using Email transports built specifically for such use. These plugins are available in the :doc:`Mautic Marketplace `. + It's a nice perk that Mautic can use any transport provided by Symfony Mailer. However, be aware that such transports (from Symfony) don't support batch sending, even via API. They only send one email per request, as opposed to a thousand emails per request as is the case with some Mautic transports, which can make them slow at scale. They also don't support transport callback handling used for bounce management. If you plan to send larger volumes of Emails or need to use features which require callback handling, please consider using Email transports built specifically for such use. These plugins are available in the :doc:`Mautic Marketplace `. The system can either send Emails immediately or queue them for processing in batches by a :doc:`cron job `. diff --git a/docs/components/assets.rst b/docs/components/assets.rst index 3525d825..719e898a 100644 --- a/docs/components/assets.rst +++ b/docs/components/assets.rst @@ -137,5 +137,24 @@ It's possible to delete an Asset by clicking on the 'delete' button while viewin .. warning:: Once deleted, you can't retrieve an Asset, and statistics relating to the number of downloads for that Asset are no longer be available. Contact Points accumulated as a result of accessing the resource remain. It's recommended where possible to unpublish Assets which are no longer in use - in future there may be an archive feature. - +Display Assets directly in the browser +============================ + +By default, Mautic supports the following file types for direct display in the browser: + +.. vale off + +- gif +- jpg +- jpeg +- mpg +- mpeg +- mp3 +- pdf +- png +- wav + +.. vale on + +If you want to change this default behavior, you can modify the ``local.php`` file and set an array of extensions for the ``streamed_extensions`` parameter. diff --git a/docs/configuration/command_line_interface.rst b/docs/configuration/command_line_interface.rst index 8d2f0a62..889c9979 100644 --- a/docs/configuration/command_line_interface.rst +++ b/docs/configuration/command_line_interface.rst @@ -106,10 +106,13 @@ These are the commands you may need to use in relation to your Mautic instance. - * - ``mautic:custom-field:create-column`` - Creates the actual column in the table + - * - ``mautic:email:fetch`` - Fetch and process monitored Email. - * - messenger:consume email_transport + - + * - ``messenger:consume email`` - Processes mail queue + - * - ``mautic:import`` - If the CSV import is configured to run in background then this command will pick up the pending import jobs and imports the data from CSV files to Mautic. - diff --git a/docs/configuration/cron_jobs.rst b/docs/configuration/cron_jobs.rst index 0c543280..433d6f21 100644 --- a/docs/configuration/cron_jobs.rst +++ b/docs/configuration/cron_jobs.rst @@ -85,6 +85,19 @@ You can also limit the number of Contacts to process per script execution using that these messages are only added to the queue when frequency rules apply either system wide or per Contact. +.. vale off + +Custom Field cron jobs +======================= + +.. vale on + +**To keep Contacts and Company Custom Fields updated** + +.. code-block:: php + + php /path/to/mautic/bin/console mautic:custom-field:create-column + Optional ******** @@ -101,7 +114,7 @@ If the system configuration is queueing Emails, a cron job processes them. .. code-block:: php - php /path/to/mautic/bin/console messenger:consume email_transport + php /path/to/mautic/bin/console messenger:consume email .. vale off diff --git a/docs/configuration/images/queue-amazon-sqs.png b/docs/configuration/images/queue-amazon-sqs.png new file mode 100644 index 00000000..f86bde2c Binary files /dev/null and b/docs/configuration/images/queue-amazon-sqs.png differ diff --git a/docs/configuration/images/queue-amqp.png b/docs/configuration/images/queue-amqp.png new file mode 100644 index 00000000..040cecc4 Binary files /dev/null and b/docs/configuration/images/queue-amqp.png differ diff --git a/docs/configuration/images/queue-beanstalkd.png b/docs/configuration/images/queue-beanstalkd.png new file mode 100644 index 00000000..2025185c Binary files /dev/null and b/docs/configuration/images/queue-beanstalkd.png differ diff --git a/docs/configuration/images/queue-disabled.png b/docs/configuration/images/queue-disabled.png new file mode 100644 index 00000000..cd489cfe Binary files /dev/null and b/docs/configuration/images/queue-disabled.png differ diff --git a/docs/configuration/images/queue-doctrine.png b/docs/configuration/images/queue-doctrine.png new file mode 100644 index 00000000..33303089 Binary files /dev/null and b/docs/configuration/images/queue-doctrine.png differ diff --git a/docs/configuration/images/queue-failures.png b/docs/configuration/images/queue-failures.png new file mode 100644 index 00000000..636289fa Binary files /dev/null and b/docs/configuration/images/queue-failures.png differ diff --git a/docs/configuration/images/queue-redis.png b/docs/configuration/images/queue-redis.png new file mode 100644 index 00000000..7321c6c0 Binary files /dev/null and b/docs/configuration/images/queue-redis.png differ diff --git a/docs/configuration/images/queue-retry-strategy.png b/docs/configuration/images/queue-retry-strategy.png new file mode 100644 index 00000000..6bdefd91 Binary files /dev/null and b/docs/configuration/images/queue-retry-strategy.png differ diff --git a/docs/channels/images/emails/sendgrid-api-dsn.png b/docs/configuration/images/sendgrid-api-dsn.png similarity index 100% rename from docs/channels/images/emails/sendgrid-api-dsn.png rename to docs/configuration/images/sendgrid-api-dsn.png diff --git a/docs/channels/images/emails/smtp-dsn.png b/docs/configuration/images/smtp-dsn.png similarity index 100% rename from docs/channels/images/emails/smtp-dsn.png rename to docs/configuration/images/smtp-dsn.png diff --git a/docs/configuration/settings.rst b/docs/configuration/settings.rst index 46bd6d1d..5ef819cf 100644 --- a/docs/configuration/settings.rst +++ b/docs/configuration/settings.rst @@ -16,11 +16,11 @@ General settings * **Site URL** - This is where Mautic is physically installed. Set the URL for this site here. Cron jobs needs this to correctly determine absolute URLs when generating links for Emails, etc. It 's also called Mautic's 'base URL'. -* **Mautic’s root URL** - When a User signs in to their Mautic instance, they go to ``mautic.example.com``. However, that Landing Page is also accessible to the public. If a Contact visits that address, they see the Mautic login page for that instance. +* **Mautic's root URL** - When a User signs in to their Mautic instance, they go to ``mautic.example.com``. However, that Landing Page is also accessible to the public. If a Contact visits that address, they see the Mautic login page for that instance. - To brand that Landing Page, create a Mautic Landing Page that you’d want to greet any Contacts who visit your root ``URL``. Once you’ve done that, Users can sign in into Mautic by visiting ``mautic.example.com/s/login``. + To brand that Landing Page, create a Mautic Landing Page that you'd want to greet any Contacts who visit your root ``URL``. Once you've done that, Users can sign in into Mautic by visiting ``mautic.example.com/s/login``. -* **404 page** - Select the Landing Page that you want to use as the 404 Landing Page. If you don’t want to use Mautic’s default 404 error page, create a custom Landing Page and select that page here. If you don’t select any page, Mautic uses the default error page. +* **404 page** - Select the Landing Page that you want to use as the 404 Landing Page. If you don't want to use Mautic's default 404 error page, create a custom Landing Page and select that page here. If you don't select any page, Mautic uses the default error page. * **Path to the cache, log, and images directory** - These are the file system paths where the cache, logs, and images are saved. @@ -42,7 +42,7 @@ System defaults * **Cached data timeout (minutes)** - Mautic caches data to speed up page loads. Update this setting to change how long Mautic caches the data for. Mautic uses ``10 minutes`` as the default. -* **Date Range Filter Default** - Sets the default for how far back from the current date Mautic looks for data in Reports including Campaign and Email snapshots charts on the item page. This setting allows you to control the default for how far back from the current date Mautic looks for data. If you’ve changed the setting on a Report, Mautic uses what you’ve entered. Mautic’s default value is ``1 Month``. +* **Date Range Filter Default** - Sets the default for how far back from the current date Mautic looks for data in Reports including Campaign and Email snapshots charts on the item page. This setting allows you to control the default for how far back from the current date Mautic looks for data. If you've changed the setting on a Report, Mautic uses what you've entered. Mautic's default value is ``1 Month``. * **Default format for full dates, date only, short dates, and time only** - The default setting uses the standard US time format. The letters in the boxes are PHP code. See the :xref:`PHP manual for date functions`. @@ -57,11 +57,11 @@ Cross-Origin Resource Sharing (CORS) enables data to pass between your website a * **Restrict Domains** - When set to No, any web page can pass information to Mautic. Select Yes to limit communication with your Mautic instance to websites listed in Valid Domains strongly recommended. -* **Valid Domains** - A list of domains allowed to communicate with your Mautic instance. In the text box, list the exact URL of the top level domain you want to allow, one per line. For example: ``http://www.example.com`` tracks any activity on non-secure example.com pages, but ``https://www.example.com`` won’t because this is only tracking on a secure (``https://``) website. +* **Valid Domains** - A list of domains allowed to communicate with your Mautic instance. In the text box, list the exact URL of the top level domain you want to allow, one per line. For example: ``http://www.example.com`` tracks any activity on non-secure example.com pages, but ``https://www.example.com`` won't because this is only tracking on a secure (``https://``) website. .. note:: - In the Valid Domains field, don’t include a slash at the end. For example, use ``https://www.example.com`` instead of ``https://www.example.com/``. + In the Valid Domains field, don't include a slash at the end. For example, use ``https://www.example.com`` instead of ``https://www.example.com/``. Miscellaneous settings ====================== @@ -78,7 +78,7 @@ Miscellaneous settings * **IP lookup service authentication** - To use any IP lookup service which requires authentication, enter your credentials. -* **List of IPs not to track Contacts with** - To turn off tracking for particular IP addresses, enter the addresses, one per line. Mautic doesn’t recommend adding your office IP address. If you list your internal IP address, Mautic won’t track clicks, page hits, etc., from that IP, **including when you are testing functionality**. +* **List of IPs not to track Contacts with** - To turn off tracking for particular IP addresses, enter the addresses, one per line. Mautic doesn't recommend adding your office IP address. If you list your internal IP address, Mautic won't track clicks, page hits, etc., from that IP, **including when you are testing functionality**. * **List of known Bots** - Mautic has the feature to identify and turn-off tracking for several known bots. To track activity from those bots, remove them from this list. To turn off tracking for other bots, add them here (one per line). @@ -111,7 +111,7 @@ Theme settings :width: 600 :alt: Screenshot showing Theme Settings Configuration in Mautic -* **Default Theme** - Applies a Theme to any Form which doesn’t have a Theme already applied. If you don’t have a Landing Page for your Preference Center, but have preference settings turned on in Email settings, Mautic creates a default Preference Center page using the Form styling from the Theme selected here. +* **Default Theme** - Applies a Theme to any Form which doesn't have a Theme already applied. If you don't have a Landing Page for your Preference Center, but have preference settings turned on in Email settings, Mautic creates a default Preference Center page using the Form styling from the Theme selected here. API settings ************ @@ -124,11 +124,11 @@ Full API documentation is available :xref:`Mautic developer API`. * **API enabled** - Select Yes to pass data in and out of Mautic through the API. -* **Enable http basic auth?** - Enables basic authentication for Mautic’s API. It's recommended to only use this with secure sites (https). +* **Enable http basic auth?** - Enables basic authentication for Mautic's API. It's recommended to only use this with secure sites (https). * **Access token lifetime** - When authorizing a new app or Integration, this setting limits how long the access token is valid (in minutes). The default is ``60`` minutes. - For example - You add a new Integration to your SaaS platform. Enter 30 here to limit the access token validity to ``30`` minutes. If you haven’t completed the authentication in that period of time, you must revalidate. + For example - You add a new Integration to your SaaS platform. Enter 30 here to limit the access token validity to ``30`` minutes. If you haven't completed the authentication in that period of time, you must revalidate. * **Refresh token lifetime** - When using OAuth 2.0, the lifetime of the refresh token used to request a new access token once expired. Once the refresh token expires, you must reauthorize. The default is ``14`` days. @@ -161,6 +161,114 @@ Campaign settings Email settings ************** +Email transport settings +======================== + +As Mautic uses the :xref:`Symfony Mailer` library since v5, it supports all Symfony Mailer core plugins out of the box. Transports for other Email services might be found on GitHub or Packagist. + +SMTP transport +-------------- + +The SMTP transport is the default transport used for sending Emails with Mautic. It's configured in the Mautic configuration under the Email Settings tab. The configuration is the same as in the :xref:`Symfony Mailer` documentation. + +Mautic now uses a specific way of providing the connection details for Email transports to interpret, known as a Data Source Name, or DSN. This is the example Data Source Name configuration mentioned in the :xref:`Symfony Mailer` documentation for SMTP: + +.. code-block:: shell + + smtp://user:pass@smtp.example.com:port + +Mautic creates this automatically from the values entered in the Email configuration: + +.. image:: images/smtp-dsn.png + :width: 400 + :alt: SMTP API DSN example + +.. list-table:: Example DSN ``smtp://user:pass@smtp.example.com:port/path?option1=value1&option2=value2`` explained + :widths: 10 20 150 + :header-rows: 1 + :stub-columns: 1 + + * - DSN part + - Example + - Explanation + * - Scheme + - smtp + - Defines which email transport (plugin) will handle the email sending. It also defines which other DSN parts must be present. + * - User + - john + - Some transport wants username and password to authenticate the connection. Some public or private key. Some just API key. + * - Password + - pa$$word + - As mentioned above, read documentation for your particular transport and fill in the fields that are required. For SMPT this is for password. + * - Host + - smtp.mydomain.com + - For SMTP this is the domain name where your SMTP server is running. Other transports may have the domain handled inside it so many wants to put just ``default`` text here. + * - Path + - any/path + - This is usually empty. For SMTP this may be the path to the SMTP server. For other transports this may be the path to the API endpoint. + * - Port + - 465 + - Important for SMTP. The port value defines which encryption is used. This is usually 465 for SSL or 587 for TLS. Avoid using port 25 for security reasons. For other transports this may be the port to the API endpoint. + * - Options + - timeout=10 + - This is optional. This may be the timeout for the connection or similar configuration. The config form will allow you to create multiple options. + +.. note:: + Use the Mautic's global configuration to paste in the DSN information, especially the API keys and passwords. The values must be URL-encoded, and the configuration form does that for you. If you are pasting DSN settings directly into the config/local.php file, you must URL-encode the values yourself. + + +.. vale off + +Example API transport installation +---------------------------------- + +.. vale on + +.. warning:: + Installing Symfony Transports is possible when you've :doc:`installed Mautic via Composer `. + +If you want to use :xref:`Sendgrid` API instead of SMTP to send Emails, for example, you can install the official Symfony Sendgrid Transport by running the following command that is mentioned along others in the :xref:`Symfony Mailer` documentation. + +.. code-block:: shell + + composer require symfony/sendgrid-mailer + +After that, you can configure the transport in the Mautic configuration. The example DSN is again mentioned in the :xref:`Symfony Mailer` documentation along with other transports. In the example of using the Sendgrid API, the DSN looks like this: + +.. code-block:: shell + + sendgrid+api://KEY@default + +This is how it would be set up in Mautic's Email configuration: + + .. image:: images/sendgrid-api-dsn.png + :width: 400 + :alt: Sendgrid API DSN example + +To replace the SendGrid API key, add it to the relevant field in the Email configuration and save. Mautic now uses the SendGrid API to send Emails. + +.. warning:: + It's a nice perk that Mautic can use any transport provided by Symfony Mailer. However, be aware that such transports (from Symfony) don't support batch sending, even via API. They only send one email per request, as opposed to a thousand emails per request as is the case with some Mautic transports, which can make them slow at scale. They also don't support transport callback handling used for bounce management. If you plan to send larger volumes of Emails or need to use features which require callback handling, please consider using Email transports built specifically for such use. These plugins are available in the :doc:`Mautic Marketplace `. + +The system can either send Emails immediately or queue them for processing in batches by a :doc:`cron job `. + +Immediate delivery +------------------ + +This is the default means of delivery. As soon as an action in Mautic triggers an Email to send, it's sent immediately. If you expect to send a large number of Emails, you should use the queue. Sending Email immediately may slow the response time of Mautic if using a remote mail service, since Mautic has to establish a connection with that service before sending the mail. Also attempting to send large batches of Emails at once may hit your server's resource limits or Email sending limits if on a shared host. + +Queued delivery +--------------- + +Mautic works most effectively with high send volumes if you use the queued delivery method. Mautic stores the Email in the configured spool directory until the execution of the command to process the queue. Set up a :doc:`cron job ` at the desired interval to run the command: + +.. code-block:: shell + + php /path/to/mautic/bin/console messenger:consume email_transport + +Some hosts may have limits on the number of Emails sent during a specified time frame and/or limit the execution time of a script. If that's the case for you, or if you just want to moderate batch processing, you can configure batch numbers and time limits in Mautic's Configuration. See the :doc:`cron job documentation ` for more specifics. + + Mail send settings ================== @@ -170,7 +278,7 @@ Mail send settings * **Name to send mail as** - The default name Emails come from. This is typically something like ``{YourCompany Marketing Team}`` or ``{YourCompany}``. -* **Email address to send mail from** - The Email address for the name you’re sending mail from. The address displays in the ``From:`` field when your Contacts receive your Emails. +* **Email address to send mail from** - The Email address for the name you're sending mail from. The address displays in the ``From:`` field when your Contacts receive your Emails. .. note:: @@ -180,11 +288,11 @@ Mail send settings * **Custom return path (bounce) address** - Set a custom return path/bounce Email address for Emails sent from the system. Note that some mail transports, such as GMail, won't support this. -* **Mailer is owner** - If Contacts in Mautic have owners, select Yes to use the Contact owner as the sender of Emails to any Contacts they’re listed as the owner for. +* **Mailer is owner** - If Contacts in Mautic have owners, select Yes to use the Contact owner as the sender of Emails to any Contacts they're listed as the owner for. .. note:: - Mailer is owner overrides any other name or Email to send mail from, including the default and individual Emails. Every Contact owner’s domain must have ``SPF`` and ``DKIM`` records. You can see this configuration for individual Emails, rather than globally. + Mailer is owner overrides any other name or Email to send mail from, including the default and individual Emails. Every Contact owner's domain must have ``SPF`` and ``DKIM`` records. You can see this configuration for individual Emails, rather than globally. For more information see :doc:`Mailer is owner` * **Service to send mail through** - Select the Email service provider you use, and enter your credentials. @@ -194,7 +302,13 @@ See :ref:`here` to set the Contact's Em Default frequency rule ====================== -* **Do not contact more than each ** - This limits the number of Marketing Messages a Contact receives in a certain period of time day, week, month. Transactional messages don’t count towards this limit. You can adjust this at the individual Contact level, either manually or by Preference Center setting. + +.. vale off + +* **Do not contact more than each ** - This limits the number of Marketing Messages a Contact receives in a certain period of time day, week, month. Transactional messages don't count towards this limit. You can adjust this at the individual Contact level, either manually or by Preference Center setting. + +.. vale on + .. note:: @@ -232,7 +346,7 @@ Message settings * **Convert embed images to Base64** - Select **Yes** to display embedded images in Emails using embedded base64 code rather than as embedded images. -* **Disable trackable URLs** - Removes tracking from URLs in your Emails. Select Yes to prevent tracking, reporting on, and using decisions based on link clicks. Some Email service providers don’t like redirecting URLs. Using trackable URLs in your Emails may impact deliverability. +* **Disable trackable URLs** - Removes tracking from URLs in your Emails. Select Yes to prevent tracking, reporting on, and using decisions based on link clicks. Some Email service providers don't like redirecting URLs. Using trackable URLs in your Emails may impact deliverability. Unsubscribe settings ==================== @@ -243,21 +357,44 @@ Unsubscribe settings * **Text for the {unsubscribe_text} token** - Like the ``{webview_text}`` token, this allows you to customize the **Unsubscribe** link. - For example - Edit between the ```` and ```` tags. Don’t change the URL as it's tokenized. If you add ``{unsubscribe_url}`` as a token in the Email, you won’t see this text. + For example - Edit between the ```` and ```` tags. Don't change the URL as it's tokenized. If you add ``{unsubscribe_url}`` as a token in the Email, you won't see this text. -* **Unsubscribed and resubscribed confirmation message** - If a Contact unsubscribes or resubscribes, this message displays on the page after the respective action. Don’t edit the ``|EMAIL|`` or the ``|URL|`` token in the ```` tag. +* **Unsubscribed and resubscribed confirmation message** - If a Contact unsubscribes or resubscribes, this message displays on the page after the respective action. Don't edit the ``|EMAIL|`` or the ``|URL|`` token in the ```` tag. -* **Show Contact preference settings** - Select **Yes** to direct the unsubscribe link to your configured Preference enter. If you haven’t created a Preference Center, Mautic creates a default page based on the next 5 settings. The created page uses the default Theme for styling. +* **Show Contact preference settings** - Select **Yes** to direct the unsubscribe link to your configured Preference enter. If you haven't created a Preference Center, Mautic creates a default page based on the next 5 settings. The created page uses the default Theme for styling. -* **Show Contact Segment preferences** - Select **Yes** to allow a Contact to change which Segments they’re part of on the Preference Center page. Segments won’t display on the Preference Center page if they aren’t published and public. +* **Show Contact Segment preferences** - Select **Yes** to allow a Contact to change which Segments they're part of on the Preference Center page. Segments won't display on the Preference Center page if they aren't published and public. * **Show Contact frequency preferences** - Select **Yes** to allow an individual to limit the number of Marketing Messages they receive on each Channel from the Preference Center. -* **Show pause Contact preferences** - Select **Yes** to allow Contacts to turn-off messages from your Mautic account to their Email address for a specified date range. This action isn’t a full unsubscribe action, and at the end of the date range, In this case, it sends the message again after the date range ends, as this isn't a full unsubscribe action. +* **Show pause Contact preferences** - Select **Yes** to allow Contacts to turn-off messages from your Mautic account to their Email address for a specified date range. This action isn't a full unsubscribe action, and at the end of the date range, In this case, it sends the message again after the date range ends, as this isn't a full unsubscribe action. + +* **Show Contact's Categories** - If you have Categories set for Contacts, Campaigns, Emails, etc., select Yes to allow the Contact to opt out of the Categories they choose from the Preference Center page. + +* **Show Contact's preferred Channel option** - If you have multiple Channels available within your Mautic instance. For example; Email, ``SMS``, mobile push, web notifications, etc., Contacts can choose their preferred Channel. This can be useful if you are using the Marketing Messages feature of Mautic. More information about the Preference Center is available :doc:`here`. + + +.. vale off + +Tracking Opened Emails +====================== + +.. vale on + +Mautic automatically tags each Email with a tracking pixel image. This allows Mautic to track when a Contact opens the Email and execute actions accordingly. Note that there are limitations to this technology - the Contact's Email client supporting HTML and auto-loading of images, and not blocking the loading of pixels. If the Email client doesn't load the image, there's no way for Mautic to know the opened status of the Email. + +By default, Mautic adds the tracking pixel image at the end of the message, just before the ```` tag. If needed, one could use the ``{tracking_pixel}`` variable within the body content token to have it placed elsewhere. Beware that you shouldn't insert this directly after the opening ```` because this prevents correct display of pre-header text on some Email clients. + +It's possible to turn off the tracking pixel entirely if you don't need to use it, in the Global Settings. + +.. vale off + +Tracking links in Emails +======================== -* **Show Contact’s Categories** - If you have Categories set for Contacts, Campaigns, Emails, etc., select Yes to allow the Contact to opt out of the Categories they choose from the Preference Center page. +.. vale on -* **Show Contact’s preferred Channel option** - If you have multiple Channels available within your Mautic instance. For example; Email, ``SMS``, mobile push, web notifications, etc., Contacts can choose their preferred Channel. This can be useful if you are using the Marketing Messages feature of Mautic. More information about the Preference Center is available :doc:`here`. +Mautic tracks clicks of each link in an Email, with the stats displayed at the bottom of each Email detail view under the Click Counts tab. Form settings @@ -308,7 +445,7 @@ Segment settings :width: 600 :alt: Screenshot showing Segment Settings Configuration in Mautic -* **Show warning if Segment hasn’t been rebuilt for X hours** - Every time a :ref:`cron jobs` runs, Segments are rebuilt. If there is an error that prevents a Segment from rebuilding, Mautic displays a warning message. This field allows you to configure the allowable length of time between rebuilds, after which the warning message appears. +* **Show warning if Segment hasn't been rebuilt for X hours** - Every time a :ref:`cron jobs` runs, Segments are rebuilt. If there is an error that prevents a Segment from rebuilding, Mautic displays a warning message. This field allows you to configure the allowable length of time between rebuilds, after which the warning message appears. Company settings **************** @@ -318,7 +455,136 @@ Company settings :alt: Screenshot showing Company Merge Settings Configuration in Mautic * **Merge by unique fields with operator** - You can determine which operator to use when merging fields if there is more than one unique identifier. - + +Queue settings +**************** + +Purpose of the queuing +====================== + +Mautic can optionally use a queuing mechanism for sending Emails. This feature is essential when running Mautic **at large scale**. It's planned to extend the tasks that can utilize queuing in the future. + +When you enable queuing, Emails are no longer sent immediately - for example, within the browser - but instead, Mautic places them in a queue and sends them later using queue consumers - also known as workers. Using consumers helps to offload the workload of your server, and allows easier scaling of your Mautic instance. + +Mautic doesn't use queues by default +==================================== + +A fresh instance of Mautic has **the queuing feature turned off** (the queue DSN configuration is ``"sync://"``) as shown in the following screenshot. + +.. image:: images/queue-disabled.png + :width: 600 + :alt: Queue turned off + +How to enable the queuing +========================= + +First you need to decide on a queuing transport to drive your queue. There are several options available at the moment. It's up to you to choose which one fits your needs the best. + +**Currently available transports:** + +* :ref:`Doctrine` +* :ref:`Redis` +* :ref:`AMQP` +* :ref:`Beanstalkd` +* :ref:`Amazon SQS` + +Doctrine +-------- +This transport is easy to setup as it doesn't require installing any additional extension. + +It uses database table ``messenger_messages`` for storing messages - you can change the table name via options. The screenshot below shows the basic settings. + +.. image:: images/queue-doctrine.png + :width: 600 + :alt: Example of Doctrine transport + +See :xref:`queue-doctrine-transport` for the complete list of configuration options. + +Redis +----- +This transport requires the Redis PHP extension (>=4.3) and a running :xref:`Redis` server (^5.0). Once met, the typical configuration looks as follows. + +.. image:: images/queue-redis.png + :width: 600 + :alt: Example of Redis transport + +See :xref:`queue-redis-transport` for the complete list of configuration options. + +AMQP +---- +The AMQP transport requires the AMQP PHP extension and a running AMQP service like :xref:`RabbitMQ`. See the screenshot below for an example of the configuration. + +.. image:: images/queue-amqp.png + :width: 600 + :alt: Example of AMQP transport + +See :xref:`queue-amqp-transport` for the complete list of configuration options. + +Beanstalkd +---------- +The Beanstalkd transport requires a running :xref:`Beanstalkd` service and a Composer dependency installed via ``composer require symfony/beanstalkd-messenger``. +After installing the Composer dependency, you can fill in the configuration as follows. + +.. image:: images/queue-beanstalkd.png + :width: 600 + :alt: Example of Beanstalkd transport + + +.. vale off + +See :xref:`queue-beanstalkd-transport` for the complete list of configuration options. + +.. vale on + +Amazon SQS +---------- +The Amazon SQS transport is ideal when hosting your Mautic instance on AWS. You need to install a Composer dependency via ``composer require symfony/amazon-sqs-messenger``. See the example of the configuration below. + +.. image:: images/queue-amazon-sqs.png + :width: 600 + :alt: Example of Amazon SQS transport + +See :xref:`queue-amazon-sqs` for the complete list of configuration options. + +How to consume messages from the Queue +====================================== + +To start consuming the messages from the Queue, you need to run the following Symfony command. + +.. code-block:: + + php bin/console messenger:consume email + +If you don't use Kubernetes in your environment, use a process manager like ``Supervisor`` or ``systemd`` to keep your worker/s running. More on this at :xref:`queue-consuming-messages` + +Advanced setting +================ + +Retry strategy +-------------- + +When the processing of a message fails, Mautic sends the message back to the queue for another try. You can adjust this behaviour in this section. +See :xref:`queue-retries-failures` for more details. + +The screenshot below shows the default values. + +.. image:: images/queue-retry-strategy.png + :width: 600 + :alt: Retry strategy defaults + +Queue for failures +------------------ + +If a message fails all its retries, it's discarded by default. To avoid this happening, you can optionally configure a Queue for failures. + +For more details see the documentation on :xref:`queue-saving-retrying-failed-messages`. + +The screenshot below shows the example of configuring the failure queue using the Doctrine transport. + +.. image:: images/queue-failures.png + :width: 600 + :alt: Example of failure configuration + Notification settings ********************* @@ -341,7 +607,7 @@ Landing page settings :width: 600 :alt: Screenshot showing Landing Page Settings Configuration in Mautic -* **Show Category in page URL?** - If you use Categories, the Landing Page’s associated Category displays in the URL if you select Yes. +* **Show Category in Page URL?** - If you use Categories, the Landing Page's associated Category displays in the URL if you select Yes. * **Analytics script** - To track Landing Page visits and activity in other platforms such as Google Analytics, add those tracking scripts here. @@ -372,7 +638,7 @@ Mautic tracking settings .. note:: * The tracking code automatically detects the Preferred Timezone and Preferred Locale fields. - * Landing Pages including 4-byte UTF-8 characters, such as emojis and some Chinese or other non-Latin characters, in the Landing Page title or URL aren't tracked on a Contact’s activity history in Mautic. All Latin characters used in English and other western languages are of 1-byte and are tracked. + * Landing Pages including 4-byte UTF-8 characters, such as emojis and some Chinese or other non-Latin characters, in the Landing Page title or URL aren't tracked on a Contact's activity history in Mautic. All Latin characters used in English and other western languages are of 1-byte and are tracked. Facebook pixel ============== @@ -381,7 +647,7 @@ Facebook pixel :width: 600 :alt: Screenshot showing Facebook Pixel Settings Configuration in Mautic -* **Facebook Pixel ID** - Enter your Facebook Pixel ID and select the options you’d like to use the pixel for. +* **Facebook Pixel ID** - Enter your Facebook Pixel ID and select the options you'd like to use the pixel for. * **Enabled on your tracking landing page** - Select Yes to have Mautic append the Facebook Pixel to the Mautic tracking code to track Landing Pages where the tracking code exists. @@ -395,7 +661,7 @@ Google analytics :width: 600 :alt: Screenshot showing Google Analytics Settings Configuration in Mautic -* **Google Analytics ID** - Enter your Google Analytics ID and select the options you’d like to use the pixel for. +* **Google Analytics ID** - Enter your Google Analytics ID and select the options you'd like to use the pixel for. * **Enabled on your tracking landing page** - Select Yes to have Mautic append the Google Analytics script to the Mautic tracking code to track Landing Pages where the tracking code exists. diff --git a/docs/docs_translations/.doctrees/README.doctree b/docs/docs_translations/.doctrees/README.doctree deleted file mode 100644 index 9af41586..00000000 Binary files a/docs/docs_translations/.doctrees/README.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/authentication/authentication.doctree b/docs/docs_translations/.doctrees/authentication/authentication.doctree deleted file mode 100644 index b9091f9e..00000000 Binary files a/docs/docs_translations/.doctrees/authentication/authentication.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/builders/creating_themes.doctree b/docs/docs_translations/.doctrees/builders/creating_themes.doctree deleted file mode 100644 index 4df0d235..00000000 Binary files a/docs/docs_translations/.doctrees/builders/creating_themes.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/builders/email_landing_page.doctree b/docs/docs_translations/.doctrees/builders/email_landing_page.doctree deleted file mode 100644 index 057e8a7b..00000000 Binary files a/docs/docs_translations/.doctrees/builders/email_landing_page.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/campaigns/campaign_builder.doctree b/docs/docs_translations/.doctrees/campaigns/campaign_builder.doctree deleted file mode 100644 index fc7331d0..00000000 Binary files a/docs/docs_translations/.doctrees/campaigns/campaign_builder.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/campaigns/campaigns_overview.doctree b/docs/docs_translations/.doctrees/campaigns/campaigns_overview.doctree deleted file mode 100644 index 9b1626a4..00000000 Binary files a/docs/docs_translations/.doctrees/campaigns/campaigns_overview.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/campaigns/creating_campaigns.doctree b/docs/docs_translations/.doctrees/campaigns/creating_campaigns.doctree deleted file mode 100644 index c3887a33..00000000 Binary files a/docs/docs_translations/.doctrees/campaigns/creating_campaigns.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/campaigns/managing_campaigns.doctree b/docs/docs_translations/.doctrees/campaigns/managing_campaigns.doctree deleted file mode 100644 index b2fbb75c..00000000 Binary files a/docs/docs_translations/.doctrees/campaigns/managing_campaigns.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/campaigns/troubleshooting_campaigns.doctree b/docs/docs_translations/.doctrees/campaigns/troubleshooting_campaigns.doctree deleted file mode 100644 index a98b335f..00000000 Binary files a/docs/docs_translations/.doctrees/campaigns/troubleshooting_campaigns.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/categories/categories-overview.doctree b/docs/docs_translations/.doctrees/categories/categories-overview.doctree deleted file mode 100644 index a33f0a9b..00000000 Binary files a/docs/docs_translations/.doctrees/categories/categories-overview.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/channels/emails.doctree b/docs/docs_translations/.doctrees/channels/emails.doctree deleted file mode 100644 index 6a63cb20..00000000 Binary files a/docs/docs_translations/.doctrees/channels/emails.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/channels/focus_items.doctree b/docs/docs_translations/.doctrees/channels/focus_items.doctree deleted file mode 100644 index 1e1daf28..00000000 Binary files a/docs/docs_translations/.doctrees/channels/focus_items.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/channels/marketing_messages.doctree b/docs/docs_translations/.doctrees/channels/marketing_messages.doctree deleted file mode 100644 index 7918d565..00000000 Binary files a/docs/docs_translations/.doctrees/channels/marketing_messages.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/channels/push_notifications.doctree b/docs/docs_translations/.doctrees/channels/push_notifications.doctree deleted file mode 100644 index 3a7f5320..00000000 Binary files a/docs/docs_translations/.doctrees/channels/push_notifications.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/channels/sms.doctree b/docs/docs_translations/.doctrees/channels/sms.doctree deleted file mode 100644 index ff310ee2..00000000 Binary files a/docs/docs_translations/.doctrees/channels/sms.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/channels/social_monitoring.doctree b/docs/docs_translations/.doctrees/channels/social_monitoring.doctree deleted file mode 100644 index b0e3f4c4..00000000 Binary files a/docs/docs_translations/.doctrees/channels/social_monitoring.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/channels/utm_tags.doctree b/docs/docs_translations/.doctrees/channels/utm_tags.doctree deleted file mode 100644 index f6a46da7..00000000 Binary files a/docs/docs_translations/.doctrees/channels/utm_tags.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/channels/web_notifications.doctree b/docs/docs_translations/.doctrees/channels/web_notifications.doctree deleted file mode 100644 index 88d5c3d7..00000000 Binary files a/docs/docs_translations/.doctrees/channels/web_notifications.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/companies/companies_overview.doctree b/docs/docs_translations/.doctrees/companies/companies_overview.doctree deleted file mode 100644 index 4c6d3bda..00000000 Binary files a/docs/docs_translations/.doctrees/companies/companies_overview.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/components/assets.doctree b/docs/docs_translations/.doctrees/components/assets.doctree deleted file mode 100644 index 7277b6ef..00000000 Binary files a/docs/docs_translations/.doctrees/components/assets.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/components/dynamic_web_content.doctree b/docs/docs_translations/.doctrees/components/dynamic_web_content.doctree deleted file mode 100644 index 0a18bb74..00000000 Binary files a/docs/docs_translations/.doctrees/components/dynamic_web_content.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/components/forms.doctree b/docs/docs_translations/.doctrees/components/forms.doctree deleted file mode 100644 index 58989db4..00000000 Binary files a/docs/docs_translations/.doctrees/components/forms.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/components/landing_pages.doctree b/docs/docs_translations/.doctrees/components/landing_pages.doctree deleted file mode 100644 index a024c373..00000000 Binary files a/docs/docs_translations/.doctrees/components/landing_pages.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/configuration/command_line_interface.doctree b/docs/docs_translations/.doctrees/configuration/command_line_interface.doctree deleted file mode 100644 index a39f741a..00000000 Binary files a/docs/docs_translations/.doctrees/configuration/command_line_interface.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/configuration/cron_jobs.doctree b/docs/docs_translations/.doctrees/configuration/cron_jobs.doctree deleted file mode 100644 index 06f2a383..00000000 Binary files a/docs/docs_translations/.doctrees/configuration/cron_jobs.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/configuration/maxmind_license.doctree b/docs/docs_translations/.doctrees/configuration/maxmind_license.doctree deleted file mode 100644 index aff56bd1..00000000 Binary files a/docs/docs_translations/.doctrees/configuration/maxmind_license.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/configuration/settings.doctree b/docs/docs_translations/.doctrees/configuration/settings.doctree deleted file mode 100644 index 84dfd9d6..00000000 Binary files a/docs/docs_translations/.doctrees/configuration/settings.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/configuration/variables.doctree b/docs/docs_translations/.doctrees/configuration/variables.doctree deleted file mode 100644 index fbfc85e0..00000000 Binary files a/docs/docs_translations/.doctrees/configuration/variables.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/contacts/custom_fields.doctree b/docs/docs_translations/.doctrees/contacts/custom_fields.doctree deleted file mode 100644 index c164c20d..00000000 Binary files a/docs/docs_translations/.doctrees/contacts/custom_fields.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/contacts/frequency_rules.doctree b/docs/docs_translations/.doctrees/contacts/frequency_rules.doctree deleted file mode 100644 index 5425cf47..00000000 Binary files a/docs/docs_translations/.doctrees/contacts/frequency_rules.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/contacts/import_contacts.doctree b/docs/docs_translations/.doctrees/contacts/import_contacts.doctree deleted file mode 100644 index 78f105d1..00000000 Binary files a/docs/docs_translations/.doctrees/contacts/import_contacts.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/contacts/manage_contacts.doctree b/docs/docs_translations/.doctrees/contacts/manage_contacts.doctree deleted file mode 100644 index b1836248..00000000 Binary files a/docs/docs_translations/.doctrees/contacts/manage_contacts.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/contacts/preference_center.doctree b/docs/docs_translations/.doctrees/contacts/preference_center.doctree deleted file mode 100644 index ade6b057..00000000 Binary files a/docs/docs_translations/.doctrees/contacts/preference_center.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/dashboard/dashboard.doctree b/docs/docs_translations/.doctrees/dashboard/dashboard.doctree deleted file mode 100644 index 21769405..00000000 Binary files a/docs/docs_translations/.doctrees/dashboard/dashboard.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/environment.pickle b/docs/docs_translations/.doctrees/environment.pickle deleted file mode 100644 index 14012171..00000000 Binary files a/docs/docs_translations/.doctrees/environment.pickle and /dev/null differ diff --git a/docs/docs_translations/.doctrees/getting_started/how_to_install_mautic.doctree b/docs/docs_translations/.doctrees/getting_started/how_to_install_mautic.doctree deleted file mode 100644 index 8cc9c58e..00000000 Binary files a/docs/docs_translations/.doctrees/getting_started/how_to_install_mautic.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/getting_started/how_to_update_mautic.doctree b/docs/docs_translations/.doctrees/getting_started/how_to_update_mautic.doctree deleted file mode 100644 index 4123e9b1..00000000 Binary files a/docs/docs_translations/.doctrees/getting_started/how_to_update_mautic.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/getting_started/switching_composer.doctree b/docs/docs_translations/.doctrees/getting_started/switching_composer.doctree deleted file mode 100644 index 65ef133e..00000000 Binary files a/docs/docs_translations/.doctrees/getting_started/switching_composer.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/index.doctree b/docs/docs_translations/.doctrees/index.doctree deleted file mode 100644 index 09bd25c2..00000000 Binary files a/docs/docs_translations/.doctrees/index.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/marketplace/marketplace.doctree b/docs/docs_translations/.doctrees/marketplace/marketplace.doctree deleted file mode 100644 index 3444992d..00000000 Binary files a/docs/docs_translations/.doctrees/marketplace/marketplace.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/overview/overview.doctree b/docs/docs_translations/.doctrees/overview/overview.doctree deleted file mode 100644 index 6217683a..00000000 Binary files a/docs/docs_translations/.doctrees/overview/overview.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/amazon.doctree b/docs/docs_translations/.doctrees/plugins/amazon.doctree deleted file mode 100644 index 0febd179..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/amazon.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/citrix.doctree b/docs/docs_translations/.doctrees/plugins/citrix.doctree deleted file mode 100644 index 5af9932a..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/citrix.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/clearbit.doctree b/docs/docs_translations/.doctrees/plugins/clearbit.doctree deleted file mode 100644 index 92b55382..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/clearbit.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/connectwise.doctree b/docs/docs_translations/.doctrees/plugins/connectwise.doctree deleted file mode 100644 index 40c1abd9..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/connectwise.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/fullcontact.doctree b/docs/docs_translations/.doctrees/plugins/fullcontact.doctree deleted file mode 100644 index 46072c83..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/fullcontact.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/gmail.doctree b/docs/docs_translations/.doctrees/plugins/gmail.doctree deleted file mode 100644 index d74f13d3..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/gmail.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/hubspot.doctree b/docs/docs_translations/.doctrees/plugins/hubspot.doctree deleted file mode 100644 index 51d44654..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/hubspot.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/icontact.doctree b/docs/docs_translations/.doctrees/plugins/icontact.doctree deleted file mode 100644 index 3434d976..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/icontact.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/mailchimp.doctree b/docs/docs_translations/.doctrees/plugins/mailchimp.doctree deleted file mode 100644 index 0e0b819b..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/mailchimp.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/microsoft_dynamics_crm.doctree b/docs/docs_translations/.doctrees/plugins/microsoft_dynamics_crm.doctree deleted file mode 100644 index 47f240ce..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/microsoft_dynamics_crm.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/microsoft_outlook.doctree b/docs/docs_translations/.doctrees/plugins/microsoft_outlook.doctree deleted file mode 100644 index b1d05b84..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/microsoft_outlook.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/pipedrive.doctree b/docs/docs_translations/.doctrees/plugins/pipedrive.doctree deleted file mode 100644 index c59f1a61..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/pipedrive.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/plugin_resources.doctree b/docs/docs_translations/.doctrees/plugins/plugin_resources.doctree deleted file mode 100644 index 6be54a12..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/plugin_resources.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/salesforce.doctree b/docs/docs_translations/.doctrees/plugins/salesforce.doctree deleted file mode 100644 index ff34d4c5..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/salesforce.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/social_login.doctree b/docs/docs_translations/.doctrees/plugins/social_login.doctree deleted file mode 100644 index 30222342..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/social_login.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/sugar_crm.doctree b/docs/docs_translations/.doctrees/plugins/sugar_crm.doctree deleted file mode 100644 index feb07c74..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/sugar_crm.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/tag_manager.doctree b/docs/docs_translations/.doctrees/plugins/tag_manager.doctree deleted file mode 100644 index b6ced187..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/tag_manager.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/twilio.doctree b/docs/docs_translations/.doctrees/plugins/twilio.doctree deleted file mode 100644 index 36fdf496..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/twilio.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/twitter.doctree b/docs/docs_translations/.doctrees/plugins/twitter.doctree deleted file mode 100644 index ecf80f99..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/twitter.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/vtiger.doctree b/docs/docs_translations/.doctrees/plugins/vtiger.doctree deleted file mode 100644 index b5138c90..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/vtiger.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/zapier.doctree b/docs/docs_translations/.doctrees/plugins/zapier.doctree deleted file mode 100644 index 37118036..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/zapier.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/plugins/zoho_crm.doctree b/docs/docs_translations/.doctrees/plugins/zoho_crm.doctree deleted file mode 100644 index 15e840e0..00000000 Binary files a/docs/docs_translations/.doctrees/plugins/zoho_crm.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/points/points.doctree b/docs/docs_translations/.doctrees/points/points.doctree deleted file mode 100644 index f08bf550..00000000 Binary files a/docs/docs_translations/.doctrees/points/points.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/points/points_troubleshooting.doctree b/docs/docs_translations/.doctrees/points/points_troubleshooting.doctree deleted file mode 100644 index 85d8d41a..00000000 Binary files a/docs/docs_translations/.doctrees/points/points_troubleshooting.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/queue/message_queue.doctree b/docs/docs_translations/.doctrees/queue/message_queue.doctree deleted file mode 100644 index e9a86c49..00000000 Binary files a/docs/docs_translations/.doctrees/queue/message_queue.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/queue/queue.doctree b/docs/docs_translations/.doctrees/queue/queue.doctree deleted file mode 100644 index 9cb2e1bd..00000000 Binary files a/docs/docs_translations/.doctrees/queue/queue.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/reports/reports.doctree b/docs/docs_translations/.doctrees/reports/reports.doctree deleted file mode 100644 index 2208c5ac..00000000 Binary files a/docs/docs_translations/.doctrees/reports/reports.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/search/search_operators.doctree b/docs/docs_translations/.doctrees/search/search_operators.doctree deleted file mode 100644 index 8d6415bd..00000000 Binary files a/docs/docs_translations/.doctrees/search/search_operators.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/segments/manage_segments.doctree b/docs/docs_translations/.doctrees/segments/manage_segments.doctree deleted file mode 100644 index 55efa069..00000000 Binary files a/docs/docs_translations/.doctrees/segments/manage_segments.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/stages/stages.doctree b/docs/docs_translations/.doctrees/stages/stages.doctree deleted file mode 100644 index 4d69c08f..00000000 Binary files a/docs/docs_translations/.doctrees/stages/stages.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/themes/code_mode.doctree b/docs/docs_translations/.doctrees/themes/code_mode.doctree deleted file mode 100644 index dc5d9307..00000000 Binary files a/docs/docs_translations/.doctrees/themes/code_mode.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/themes/customizing_themes.doctree b/docs/docs_translations/.doctrees/themes/customizing_themes.doctree deleted file mode 100644 index 036c5f81..00000000 Binary files a/docs/docs_translations/.doctrees/themes/customizing_themes.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/themes/manage_themes.doctree b/docs/docs_translations/.doctrees/themes/manage_themes.doctree deleted file mode 100644 index c5bdd5b9..00000000 Binary files a/docs/docs_translations/.doctrees/themes/manage_themes.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/themes/theme_structure.doctree b/docs/docs_translations/.doctrees/themes/theme_structure.doctree deleted file mode 100644 index ed8df7ea..00000000 Binary files a/docs/docs_translations/.doctrees/themes/theme_structure.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/translations/translations.doctree b/docs/docs_translations/.doctrees/translations/translations.doctree deleted file mode 100644 index 2ace3ea0..00000000 Binary files a/docs/docs_translations/.doctrees/translations/translations.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/users_roles/managing_roles.doctree b/docs/docs_translations/.doctrees/users_roles/managing_roles.doctree deleted file mode 100644 index 1a0c474f..00000000 Binary files a/docs/docs_translations/.doctrees/users_roles/managing_roles.doctree and /dev/null differ diff --git a/docs/docs_translations/.doctrees/users_roles/managing_users.doctree b/docs/docs_translations/.doctrees/users_roles/managing_users.doctree deleted file mode 100644 index 8cc9bdcf..00000000 Binary files a/docs/docs_translations/.doctrees/users_roles/managing_users.doctree and /dev/null differ diff --git a/docs/docs_translations/README.pot b/docs/docs_translations/README.pot deleted file mode 100644 index 06427021..00000000 --- a/docs/docs_translations/README.pot +++ /dev/null @@ -1,750 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../README.md:1 -msgid "Transifex Client" -msgstr "" - -#: ../README.md:3 -msgid "Installation" -msgstr "" - -#: ../README.md:5 -msgid "Installing with a script (Linux/Mac)" -msgstr "" - -#: ../README.md:6 -msgid "You can install the latest Transifex CLI by executing:" -msgstr "" - -#: ../README.md:12 -msgid "Or you can isntall a specific version if you need by executing:" -msgstr "" - -#: ../README.md:19 -msgid "This script will:" -msgstr "" - -#: ../README.md:20 -msgid "Try to find the correct version for your system." -msgstr "" - -#: ../README.md:21 -msgid "Download & extract the CLI to the current folder." -msgstr "" - -#: ../README.md:22 -msgid "Check for a profile in one of `.profile, .bashrc, .bash_profile, .zshrc` and append `export PATH=\":$PATH\"`, so you can call 'tx' from any path." -msgstr "" - -#: ../README.md:24 -msgid "**Note:** You need to restart your terminal for the `PATH` changes to be applied." -msgstr "" - -#: ../README.md:26 -msgid "Download from Github Releases (Linux/Mac/Windows)" -msgstr "" - -#: ../README.md:28 -msgid "Another way to install the Transifex CLI is to download the latest version of the binary from GitHub [here](https://github.com/transifex/cli/releases)." -msgstr "" - -#: ../README.md:32 -msgid "Choose the binary according to your system, download it and unzip it. Copy the binary into the location you want and update the `PATH` variable of your system if necessary." -msgstr "" - -#: ../README.md:36 -msgid "The other way to install Transifex CLI in the system is to use the code." -msgstr "" - -#: ../README.md:38 -msgid "Clone the [repository](https://github.com/transifex/cli) and go into the directory" -msgstr "" - -#: ../README.md:43 -msgid "Building from source" -msgstr "" - -#: ../README.md:45 -msgid "The default way to build the binary is" -msgstr "" - -#: ../README.md:50 -msgid "This method requires to have golang in your system. It compiles Transifex CLI and moves it into the `./bin/` directory of the repository." -msgstr "" - -#: ../README.md:53 -msgid "If you don't have golang installed, but you have Docker enabled, you can use the following command:" -msgstr "" - -#: ../README.md:60 -msgid "This will build the binary and it will copy it at `./bin/` in the repository." -msgstr "" - -#: ../README.md:62 -msgid "Running from Docker (beta)" -msgstr "" - -#: ../README.md:64 -msgid "You can skip the installation and run the Transifex client from Docker if it is available in your system. All you have to do is put this line:" -msgstr "" - -#: ../README.md:71 -msgid "to your `~/.bashrc` / `~/.zshrc`. (The first time you use it you will have to wait for a ~5MB download)" -msgstr "" - -#: ../README.md:75 -msgid "Running from Github actions (beta)" -msgstr "" - -#: ../README.md:77 -msgid "You can invoke the CLI from within a Github workflow by using our Github action. See the instructions [here](https://github.com/transifex/cli-action)." -msgstr "" - -#: ../README.md:80 -msgid "Migrating from older versions of the client" -msgstr "" - -#: ../README.md:82 -msgid "The current version of the client maintains backwards compatibility for the `tx push` and `tx pull` commands. So, if you have a CI setup that uses them, you should not have to change anything. However, some things need to be different in the configuration files:" -msgstr "" - -#: ../README.md:86 -msgid "The section headers in `.tx/config` need to be different to also store the organization slug. So after the migration `.` should become `o::p::r:`. In case something fails during this process, we will provide a message with the failed migrated resource so that you can identify and change the section header manually." -msgstr "" - -#: ../README.md:91 -msgid "You will be prompted for an API token in case you are using a username/password pair in your `~/.transifexrc` file or if you are not using one." -msgstr "" - -#: ../README.md:94 -msgid "If you are migrating an existing software project from an older version of the Transifex client, you need to run:" -msgstr "" - -#: ../README.md:101 -msgid "This will take care of all the changes and create a back up file of the original config in the same folder as `config_yyyymmddhhss.bak` before we start the migration process." -msgstr "" - -#: ../README.md:104 -msgid "Differences With the Previous Version" -msgstr "" - -#: ../README.md:106 -msgid "The two clients have some distinct differences when looking under the hood. The new client is using Go instead of Python" -msgstr "" - -#: ../README.md:108 -msgid "for speed and" -msgstr "" - -#: ../README.md:109 -msgid "for the ability to produce binary files for multiple platforms." -msgstr "" - -#: ../README.md:112 -msgid "Additionally, client is using APIv3 instead of APIv2 because" -msgstr "" - -#: ../README.md:113 -msgid "it is faster (calls occur asynchronously and you don't have to wait for parsing to finish) and" -msgstr "" - -#: ../README.md:115 -msgid "APIv2 is getting deprecated." -msgstr "" - -#: ../README.md:117 -msgid "`Init`" -msgstr "" - -#: ../README.md:119 -msgid "The new client's init command creates the `.tx` folder in the current path, and the config file with the following content which is required for the configuration:" -msgstr "" - -#: ../README.md:127 -msgid "In case there is already a `.tx/config` file in the current directory, the users will get a prompt that informs them that, if they proceed, the contents of their `.tx/config` file will be overridden. A `y/n` answer, is needed to proceed or abort." -msgstr "" - -#: ../README.md:131 -msgid "`Add`" -msgstr "" - -#: ../README.md:133 -msgid "For the previous client, parts of functionality in `tx config` command adds resources locally." -msgstr "" - -#: ../README.md:136 -msgid "In the new client, this command is responsible to add a resource in the local config file. Note that it needs all `organization`, `project` and `resource` slugs in order to build the resource id for the APIv3." -msgstr "" - -#: ../README.md:140 -msgid "It will create a new section in the `.tx/config` file for a resource like:" -msgstr "" - -#: ../README.md:147 -msgid "`Push`" -msgstr "" - -#: ../README.md:149 -msgid "The differences of the new client, are summarized here:" -msgstr "" - -#: ../README.md:151 -#: ../README.md:162 -msgid "resource IDs, can be accepted without the `-r` flag" -msgstr "" - -#: ../README.md:152 -msgid "when neither `-s/-t` are set, `-s` is assumed" -msgstr "" - -#: ../README.md:153 -msgid "`--all` flag creates new languages on Transifex if local files exist for them (on previous client this was the default behavior, now it needs the `--all` flag)" -msgstr "" - -#: ../README.md:156 -#: ../README.md:164 -msgid "without `--all` or `--languages`, the only languages that are considered are the intersection of local and remote languages" -msgstr "" - -#: ../README.md:160 -msgid "`Pull`" -msgstr "" - -#: ../README.md:163 -msgid "when neither `-s/-t` are set, `-t` is assumed" -msgstr "" - -#: ../README.md:166 -msgid "`--json` download files (translations) as json files" -msgstr "" - -#: ../README.md:167 -msgid "`--content_encoding/-e` The encoding of the file. This can be one of the following:" -msgstr "" - -#: ../README.md:168 -msgid "text (default)" -msgstr "" - -#: ../README.md:169 -msgid "base64" -msgstr "" - -#: ../README.md:171 -msgid "Usage" -msgstr "" - -#: ../README.md:173 -msgid "Initialising a Project" -msgstr "" - -#: ../README.md:175 -msgid "The first thing we need to do is run:" -msgstr "" - -#: ../README.md:181 -msgid "This will simply create an empty `.tx/config` file to mark the current folder as a _Transifex project_. Your directory structure should now look like this:" -msgstr "" - -#: ../README.md:195 -msgid "Using Environment Variables" -msgstr "" - -#: ../README.md:196 -msgid "The available environment variables for the CLI:" -msgstr "" - -#: ../README.md:198 -msgid "`TX_TOKEN`: The api token to use" -msgstr "" - -#: ../README.md:199 -msgid "`TX_HOSTNAME`: The API hostname" -msgstr "" - -#: ../README.md:200 -msgid "`TX_CACERT`: Path to CA certificate bundle file" -msgstr "" - -#: ../README.md:202 -msgid "You can either add these variables in your CI settings, your profile file or when executing the commands like: `TX_TOKEN=myapitoken tx pull`" -msgstr "" - -#: ../README.md:205 -msgid "Adding Resources to Configuration" -msgstr "" - -#: ../README.md:207 -msgid "We will add the php file as a source language file in our local configuration. The simplest way to do this is with `tx add` which will start an interactive session:" -msgstr "" - -#: ../README.md:248 -msgid "Your `.tx/config` file should look like this:" -msgstr "" - -#: ../README.md:261 -msgid "You can skip steps from the interactive session by adding flags to the `tx add` command. In fact, you can skip the interactive session entirely if you provide all the flags:" -msgstr "" - -#: ../README.md:276 -msgid "Adding resources in bulk" -msgstr "" - -#: ../README.md:278 -msgid "With the old client I could add multiple resources at the same time with `tx config mapping-bulk`. What should I do now?" -msgstr "" - -#: ../README.md:281 -msgid "We decided not to implement this functionality in the new client because its usage was complicated and it couldn't satisfy every user's need anyway. You can add multiple resources with a relatively simple shell script. For example:" -msgstr "" - -#: ../README.md:285 -msgid "Add every subfolder of a `locale` folder as a resource:" -msgstr "" - -#: ../README.md:304 -msgid "Add specific folders as resources:" -msgstr "" - -#: ../README.md:322 -msgid "Turn every `.po` file into a configured resource:" -msgstr "" - -#: ../README.md:346 -msgid "Adding remote resources in bulk" -msgstr "" - -#: ../README.md:348 -msgid "If you have content already setup in Transifex, you may want to setup local resources in order to pull the language files on your system. In order to do that, you can run the following command with Linux or Mac OS:" -msgstr "" - -#: ../README.md:358 -msgid "The use of tx add remote appends the content in the .tx/config file and does not overwrite it. However, if the project and resource exist in the .tx/config file, then it will overwrite the previous information for the specific project & resource." -msgstr "" - -#: ../README.md:360 -msgid "For Windows OS, please use double quotes instead of single quotes in the following example." -msgstr "" - -#: ../README.md:362 -msgid "This will create entries in your configuration file for each resource in your remote project. ie the configuration file may look like this:" -msgstr "" - -#: ../README.md:391 -msgid "The options for this command are:" -msgstr "" - -#: ../README.md:393 -msgid "`--file-filter`: What to use as the file_filter and source_file options in the resulting configuration. This is a pattern that accepts the following parameters:" -msgstr "" - -#: ../README.md:397 -msgid "``" -msgstr "" - -#: ../README.md:398 -msgid "`` _(required)_" -msgstr "" - -#: ../README.md:399 -msgid "`` _(required)_ - can be used multiple times in the filter path" -msgstr "" - -#: ../README.md:400 -msgid "``" -msgstr "" - -#: ../README.md:402 -msgid "The default value for this option is `translations/./.` (the one we showed in our example)" -msgstr "" - -#: ../README.md:406 -msgid "`--minimum-perc`: What to use as the minimum_perc option in the resulting configuration" -msgstr "" - -#: ../README.md:408 -msgid "One or more project URLs." -msgstr "" - -#: ../README.md:410 -msgid "After setting things up, you can pull the source files with `tx pull --source`." -msgstr "" - -#: ../README.md:412 -msgid "Pushing Files to Transifex" -msgstr "" - -#: ../README.md:414 -msgid "`tx push` is used to push language files (usually source language files) from your machine to Transifex. You will most likely want to do that frequently during the lifetime of you project when new source strings are introduced or existing ones are changed. This will make the new strings available to translators as soon as possible." -msgstr "" - -#: ../README.md:420 -msgid "The simplest invocation of `tx push` is simply:" -msgstr "" - -#: ../README.md:426 -msgid "This will attempt to push the source file of all local resources that have been configured with `tx add`." -msgstr "" - -#: ../README.md:429 -#: ../README.md:617 -msgid "**Limiting resources:**" -msgstr "" - -#: ../README.md:431 -msgid "You can limit the resources you want to push with:" -msgstr "" - -#: ../README.md:437 -msgid "A resource ID must refer to a resource that has already been configured with `tx add` and has the form `.`. So, if the URL of your resource in Transifex is `https://app.transifex.com/myorganization/myproject/myresource`, then the resource ID will be `myproject.myresource`." -msgstr "" - -#: ../README.md:443 -#: ../README.md:628 -msgid "You can also use the `*` character to select multiple resources with the same pattern. So, for instance, if you have the `abc.def` resource ID in your configuration, you can select it with either `abc.*`, `*.def`, `ab*ef` or even `a*.d*f`." -msgstr "" - -#: ../README.md:448 -#: ../README.md:633 -#: ../README.md:819 -#: ../README.md:871 -msgid "Note: for backwards compatibility with previous versions of the client, you can also use the `-r/--resources` flag. You can also use both at the same time:" -msgstr "" - -#: ../README.md:458 -msgid "`tx push` will create the resources on Transifex if they are missing." -msgstr "" - -#: ../README.md:460 -#: ../README.md:643 -msgid "**Language management:**" -msgstr "" - -#: ../README.md:462 -msgid "By default, the client will push the source file (the file that's being pointed to by the `source_file` configuration option from `tx add`). If you use the `-t/--translation` flag, `tx push` will push translation files. This may be desirable if, for example, you previously pulled translation files with the `--mode translator` option, translated using an offline translation tool and now you want to push your work to Transifex, or if you are migrating from another localization management service to Transifex. If you use both the `-t` _and_ the `-s/--source` flags, then you will push both the source file and the translation files." -msgstr "" - -#: ../README.md:472 -msgid "When you use `-t`, the client will find all local files that match the `file-filter` configuration option. The files that are found, and their language codes constitute the _local_ languages. By default, the client will ask the Transifex API for the languages that are supported by the project you are pushing to (the _remote_ languages) and will only push languages that are both _local_ and _remote_ (aka the **intersection** of _local_ and _remote_ languages)." -msgstr "" - -#: ../README.md:480 -msgid "You can use the `-l/--languages` flag to handpick which languages you want to push. It only makes sense to include _local_ languages with the `-l` flag, ie languages for which a file exists according to the `file-filter` configuration option. The client will then push **only** the language files you have specified. If you specify _local_ languages that are not yet supported by the remote Transifex project, the client will attempt to add these languages to the project first. Be careful of this since it may affect your pricing if you are a paying customer." -msgstr "" - -#: ../README.md:493 -msgid "The `-a/--all` flag will attempt to push **all** _local_ languages to the remote Transifex project, adding them if necessary. Essentially, `-a` is equivalent to using `-l` with all the _local_ language codes." -msgstr "" - -#: ../README.md:497 -msgid "Transifex uses the _ISO/IEC 15897_ standard for language codes (for example `en_US`). If you use a different format for the _local_ language codes, you can define a mapping in your configuration file `.tx/config`. You can specify these mappings for all configured resources by adding them to the `[main]` section or you can specify mappings per resource. The \"per-resource\" mappings take precendence. Configuring a language mapping looks like this:" -msgstr "" - -#: ../README.md:512 -#: ../README.md:716 -msgid "This means that the _remote_ `pt_PT` language code maps to the _local_ `pt-pt` language code and the _remote_ `pt_BR` language code maps to the _local_ `pt-br` language code." -msgstr "" - -#: ../README.md:516 -msgid "The REMOTE_CODE is the language code supported by Transifex. And the LOCAL_CODE is your language code." -msgstr "" - -#: ../README.md:519 -msgid "The `-l` flag works with both _local_ and _remote_ language codes." -msgstr "" - -#: ../README.md:521 -msgid "**Skipping pushing older files:**" -msgstr "" - -#: ../README.md:523 -msgid "The default behavior of the `tx push` command is to skip pushing a file when the remote resource on Transifex has had a change more recently than when the local file was last edited. To make sure that the local files are pushed even if they are older than the remote resource, use the `-f/--force` flag." -msgstr "" - -#: ../README.md:528 -msgid "You can use the `--use-git-timestamps` flag to compare against the last time the local files were *committed* to the local git repository instead of the last modification time in the filesystem. This can be useful in cases where you have just cloned a repository or pulled a branch. In this case, the filesystem modification time will reflect the time you pulled and not the time the file was edited by an actual person. If you use the `--use-git-timestamps` flag and no information about a local git repository can be found, then the client will fall back to taking the filesystem timestamp into account." -msgstr "" - -#: ../README.md:537 -#: ../README.md:738 -#: ../README.md:827 -#: ../README.md:846 -msgid "**Other flags:**" -msgstr "" - -#: ../README.md:539 -msgid "`--xliff`: Push xliff files instead of regular ones. The files must be located **in the same place** as indicated by the `file-filter` configuration option, but with the added `.xlf` suffix (`tx pull`ing with the `--xliff` option will put xliff files in the correct positions so you will probably not have to do this by hand)" -msgstr "" - -#: ../README.md:545 -msgid "`--branch`: Using this flag, you can access copies of the regular remote resource that are tied to the provided branch. So if `tx push proj.res` pushes to the `https://app.transifex.com/org/proj/res` resource, then `tx push --branch foo proj.res` will push to the `https://app.transifex.com/org/proj/foo--res` resource. This way you can separate the localization effort across different branches. If you supply an empty string as the branch (`--branch ''`), then the client will attempt to figure out the currently active branch in the local git repository. For example:" -msgstr "" - -#: ../README.md:564 -msgid "This way, the \"regular\" `https://app.transifex.com/myorganization/myproject/myresource` resource will not be affected by the changes you did to the source strings and the localization effort can be done in parallel on the `https://app.transifex.com/myorganization/myproject/new_feature--myresource` resource." -msgstr "" - -#: ../README.md:571 -msgid "Note: Starting from version 1.5.0 resources created using the `--branch` flag, will have an enhanced functionality in transifex and will be able to automatically be merged into their bases. Resources created using the `--branch` prior to this version, need to be pushed again in order for the new functionality to be available." -msgstr "" - -#: ../README.md:580 -msgid "`--base`: Define the base branch when pushing a branch." -msgstr "" - -#: ../README.md:582 -msgid "`--skip`: Normally, if an upload fails, the client will abort. This may not be desirable if most uploads are expected to succeed. For example, the reason of the failed upload may be a syntax error in _one_ of the language files. If you set the `--skip` flag and an upload fails, then the client will simply print a warning and move on to the next language file." -msgstr "" - -#: ../README.md:588 -msgid "`--workers/-w` (default 5, max 30): The client will push files in parallel to improve speed. The `--workers` flag sets the number of concurrent uploads possible at any time." -msgstr "" - -#: ../README.md:591 -#: ../README.md:802 -msgid "`--silent`: Reduce verbosity of the output." -msgstr "" - -#: ../README.md:593 -msgid "`--replace-edited-strings`: If present, source strings that have been edited (in the editor UI or via the API) will not be protected from this source file push and will instead be replaced. This can also be set on a per-resource level in the configuration file." -msgstr "" - -#: ../README.md:598 -msgid "`--keep-transations`: If present, translations of source strings with the same key whose content changes will not be discarded. This can also be set on a per-resource level in the configuration file." -msgstr "" - -#: ../README.md:602 -msgid "Pulling Files from Transifex" -msgstr "" - -#: ../README.md:604 -msgid "`tx pull` is used to pull language files (usually translation language files) from Transifex to your machine. Most likely, you will do this regularly when you want to incorporate newly available translations from Transifex into it." -msgstr "" - -#: ../README.md:608 -msgid "The simplest invocation of `tx pull` is simply:" -msgstr "" - -#: ../README.md:614 -msgid "This will attempt to pull the translation files of all local resources that have been configured with `tx add`." -msgstr "" - -#: ../README.md:619 -msgid "You can limit the resources you want to pull with:" -msgstr "" - -#: ../README.md:625 -msgid "As stated in the `tx push` section, a resource ID must refer to a resource that has already been configured with `tx add` and has the form `.`." -msgstr "" - -#: ../README.md:645 -msgid "By default, the client will pull the translation files of the existing files in the paths that are defined in the `file_filter` configuration option from `tx add`." -msgstr "" - -#: ../README.md:648 -msgid "For instance, if the directory structure looks like this:" -msgstr "" - -#: ../README.md:662 -msgid "and the `.tx/config` contains:" -msgstr "" - -#: ../README.md:669 -msgid "If you use the `-s/--source` flag, `tx pull` will pull the source file that is pointed from the `source_file` option of the config file." -msgstr "" - -#: ../README.md:672 -msgid "If you use both the `-t/--translation` _and_ the `-s/--source` flags, then you will pull both the source file, and the translation files." -msgstr "" - -#: ../README.md:675 -msgid "Then the client will try to search for any existing language file located at the `locale/` path (where `` is the language code) and will try to update it, for example `locale/el.php`, `locale/fr.php`, etc." -msgstr "" - -#: ../README.md:679 -msgid "In case that there aren't any translation files, like in the structure above, then you must either use the `-l/--language` or the `-a/--all` flag." -msgstr "" - -#: ../README.md:682 -msgid "Use the `-l/--languages` flag to handpick which languages you want to pull. It only makes sense to include _remote_ languages with the `-l` flag, ie languages for which a file does not exist according to the `file_filter` configuration option. The client will then pull **only** the language files you have specified:" -msgstr "" - -#: ../README.md:692 -msgid "Note: The languages that are defined with the -l/--language flag should belong to the project for the client to download them." -msgstr "" - -#: ../README.md:696 -msgid "The `-a/--all` flag will attempt to pull **all** languages from the remote Transifex project. Essentially, `-a` is equivalent to using `-l` with all the project language codes." -msgstr "" - -#: ../README.md:700 -msgid "As stated before, Transifex uses the _ISO/IEC 15897_ standard for language codes. If you use a different format for the _local_ language codes, you can define a mapping in your configuration file `.tx/config`. You can specify these mappings for all configured resources by adding them to the `[main]` section or you can specify mappings per resource. The \"per-resource\" mappings take precendence. Configuring a language mapping looks like this:" -msgstr "" - -#: ../README.md:720 -msgid "The `-l` flag works with _remote_ language codes." -msgstr "" - -#: ../README.md:722 -msgid "**Skipping pulling older files:**" -msgstr "" - -#: ../README.md:724 -msgid "The default behavior of the `tx pull` command is to skip pulling a file when a local file on a machine has had a change more recently than when the remote resource was last edited. To make sure that the remote resources are pulled even if they are older than the local files, use the `-f/--force` flag." -msgstr "" - -#: ../README.md:729 -msgid "You can use the `--use-git-timestamps` flag to compare against the last time the local files were *committed* to the local git repository instead of the last modification time in the filesystem. This can be useful in cases where you have just cloned a repository or pulled a branch. In this case, the filesystem modification time will reflect the time you pulled and not the time the file was edited by an actual person. If you use the `--use-git-timestamps` flag and no information about a local git repository can be found, then the client will default to taking the filesystem timestamp into account." -msgstr "" - -#: ../README.md:740 -msgid "`--xliff`: Pull xliff files instead of regular ones. The files will be placed **in the same place** as indicated by the `source-file` and `file-filter` configuration options, but with the added `.xlf` suffix." -msgstr "" - -#: ../README.md:744 -msgid "`--json`: Pull translation files as json instead of regular ones. As above, the files will be placed **in the same place** as indicated by the `file-filter` configuration options, but with the added `.json` suffix. Currently, source files are not supporting json format." -msgstr "" - -#: ../README.md:749 -msgid "`--disable-overwrite`: If a file exists do not update it. This is useful when using `-a/--all` flag and you don't want to change the existing files but only download other language files." -msgstr "" - -#: ../README.md:753 -msgid "`--keep-new-files`: Used with `--disable-ovewrite` to create new files if file already exists locally with a '.new' extension." -msgstr "" - -#: ../README.md:756 -msgid "`--mode/-m`: The translation mode of the downloaded file. This can be one of the following: `'default', 'reviewed'`, `'proofread'`, `'translator'`, `'untranslated'`, `'onlytranslated'`, `'onlyreviewed'`, `'onlyproofread'`, `'sourceastranslation'` **(default mode is: **`'default'`). Use like` 'tx pull -m proofread'` to download only proofread translations." -msgstr "" - -#: ../README.md:762 -msgid "`--branch`: Using this flag, you can access copies of the regular remote resource that are tied to the provided branch. So if `tx pull proj.res` pulls from the `https://app.transifex.com/org/proj/res` resource, then `tx pull --branch foo proj.res` will pull from the `https://app.transifex.com/org/proj/foo--res` resource. This way you can separate the localization effort across different branches. If you supply an empty string as the branch (`--branch ''`), then the client will attempt to figure out the currently active branch in the local git repository. For example:" -msgstr "" - -#: ../README.md:780 -msgid "This way, the \"regular\" `https://app.transifex.com/myorganization/myproject/myresource` resource will not be affected by the changes one did, and the localization effort can be done in parallel on the `https://app.transifex.com/myorganization/myproject/new_feature--myresource` resource." -msgstr "" - -#: ../README.md:787 -msgid "`--skip`: Normally, if a download fails, the client will abort. This may not be desirable if most downloads are expected to succeed. For example, the reason of the failed download may be a syntax error in _one_ of the language files. If you set the `--skip` flag and an upload fails, then the client will simply print a warning and move on to the next language file." -msgstr "" - -#: ../README.md:793 -msgid "`--minimum-perc=MINIMUM_PERC` Specify the minimum translation completion threshold required in order for a file to be downloaded." -msgstr "" - -#: ../README.md:796 -msgid "`--workers/-w` (default 5, max 30): The client will pull files in parallel to improve speed. The `--workers` flag sets the number of concurrent downloads possible at any time." -msgstr "" - -#: ../README.md:800 -msgid "`--pseudo`: Generate mock string translations with a ~20% default length increase in characters." -msgstr "" - -#: ../README.md:804 -msgid "Removing resources from Transifex" -msgstr "" - -#: ../README.md:805 -msgid "The tx delete command lets you delete a resource that's in your `config` file and on Transifex." -msgstr "" - -#: ../README.md:807 -msgid "To delete a resource, use the following command:" -msgstr "" - -#: ../README.md:812 -msgid "To delete all resources in a specific project at once, instead of referring to a specific resource_slug, you can use the asterisk character as follows:" -msgstr "" - -#: ../README.md:828 -msgid "`--skip`: Normally, if a delete fails, the client will abort. This may not be desirable if most deletes are expected to succeed. For example, the reason of the failed delete may be a a resource that has translated content. If you set the `-s/--skip` flag and an delete fails, then the client will simply print a warning and move on to the next resource." -msgstr "" - -#: ../README.md:833 -msgid "`--force`: In case you want to proceed to a deletion even if resources have translations use the `-f/--force` flag." -msgstr "" - -#: ../README.md:835 -msgid "`--branch`: In case you want to delete a resource's branch that is on Transifex. If you supply an empty string as the branch (`--branch ''`), then the client will attempt to figure out the currently active branch in the local git repository." -msgstr "" - -#: ../README.md:839 -msgid "Merging Resource" -msgstr "" - -#: ../README.md:840 -msgid "The tx merge command lets you merge a branch resource with its base resource (applies only to resources created with the `--branch` flag)" -msgstr "" - -#: ../README.md:842 -msgid "To merge a resource to its base resource, use the following command:" -msgstr "" - -#: ../README.md:847 -msgid "`--conflict-resolution`: Set the conflict resolution strategy. Acceptable options are `USE_HEAD` (changes in the HEAD resource will be used) and `USE_BASE` (changes in the BASE resource will be used)" -msgstr "" - -#: ../README.md:848 -msgid "`--force`: In case you want to proceed with the merge even if the source strings are diverged, use the `-f/--force` flag." -msgstr "" - -#: ../README.md:850 -msgid "Getting the local status of the project" -msgstr "" - -#: ../README.md:851 -msgid "The status command displays the existing configuration in a human readable format. It lists all resources that have been initialized under the local repo/directory and all their associated translation files:" -msgstr "" - -#: ../README.md:865 -msgid "To get the status of specific resources just add the resources you want in your command:" -msgstr "" - -#: ../README.md:879 -msgid "Updating the CLI app" -msgstr "" - -#: ../README.md:880 -msgid "The `tx update` command provides a way to self update the application without going to Github releases page." -msgstr "" - -#: ../README.md:886 -msgid "**Flags:**" -msgstr "" - -#: ../README.md:887 -msgid "`--check`: Check if there is a new release. Nothing gets updated." -msgstr "" - -#: ../README.md:888 -msgid "`--no-interactive`: Proceed to update if there is a newer version without seeing the confirmation prompt." -msgstr "" - -#: ../README.md:889 -msgid "`--debug`: Enable logging for the binary update process." -msgstr "" - -#: ../README.md:890 -msgid "License" -msgstr "" - -#: ../README.md:892 -msgid "Licensed under Apache License 2.0, see [LICENSE](LICENSE) file." -msgstr "" diff --git a/docs/docs_translations/authentication.pot b/docs/docs_translations/authentication.pot deleted file mode 100644 index cc5bb5dd..00000000 --- a/docs/docs_translations/authentication.pot +++ /dev/null @@ -1,121 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../authentication/authentication.rst:2 -msgid "Authentication" -msgstr "" - -#: ../authentication/authentication.rst:4 -msgid "Mautic uses basic authentication for Users, however there is the ability to integrate with a SAML SSO - Single Sign-On - provider." -msgstr "" - -#: ../authentication/authentication.rst:9 -msgid "SAML Single Sign On" -msgstr "" - -#: ../authentication/authentication.rst:13 -msgid "SAML is a single sign on protocol that allows single sign on and User creation in Mautic using a third party User source called an identity provider (IDP)." -msgstr "" - -#: ../authentication/authentication.rst:16 -msgid "Turning on SAML" -msgstr "" - -#: ../authentication/authentication.rst:17 -msgid "To turn on SAML support in Mautic, you first need the IDP's metadata XML which they provide. If it's a URL, browse to the URL then save the content into an XML file." -msgstr "" - -#: ../authentication/authentication.rst:19 -msgid "Click the settings wheel in the top right corner to open the **Settings** menu." -msgstr "" - -#: ../authentication/authentication.rst:21 -msgid "Navigate to **Configuration** > **User/Authentication** Settings." -msgstr "" - -#: ../authentication/authentication.rst:None -msgid "Screenshot of SAML SSO Settings" -msgstr "" - -#: ../authentication/authentication.rst:27 -msgid "Upload this file as the Identity Provider Metadata file." -msgstr "" - -#: ../authentication/authentication.rst:29 -msgid "It's recommended to create a non-Admin Role as the default Role for created Users. Select this Role in the '**Default Role for created Users**' dropdown. For more information, see :doc:`Users and Roles`." -msgstr "" - -#: ../authentication/authentication.rst:None -msgid "Screenshot of the User Role Permission" -msgstr "" - -#: ../authentication/authentication.rst:36 -msgid "Configuring the IDP" -msgstr "" - -#: ../authentication/authentication.rst:37 -msgid "The IDP may ask for the following settings:" -msgstr "" - -#: ../authentication/authentication.rst:39 -msgid "Entity ID - this is site URL, displayed at the top of User/Authentication Settings. Copy this exactly 'as is' to the IDP." -msgstr "" - -#: ../authentication/authentication.rst:41 -msgid "Service Provider Metadata - if the provider requires a URL, use ``https://example.com/saml/metadata.xml``. To use as a file rather than a URL, browse to that URL and save the content as an XML file." -msgstr "" - -#: ../authentication/authentication.rst:43 -msgid "Assertion Consumer Service - Use ``https://example.com/s/saml/login_check``." -msgstr "" - -#: ../authentication/authentication.rst:45 -msgid "Issuer - this should come from the IDP but is often configurable. If it's a URL, be sure that the scheme - ``http://`` and ``https://`` - aren't part of it." -msgstr "" - -#: ../authentication/authentication.rst:47 -msgid "Verify request signatures or a SSL certificate - If the IDP supports encrypting and validating request signatures from Mautic to the IDP, generate a self signed SSL certificate. Upload the certificate and private key through Mautic's Configuration > User/Authentication Settings under the 'Use a custom X.509 certificate and private key to secure communication between Mautic and the IDP' section. Then upload the certificate to the IDP." -msgstr "" - -#: ../authentication/authentication.rst:49 -msgid "Custom attributes - Mautic requires three custom attributes in the IDP responses for the User Email, first name and last name. Username is also supported but is optional. Configure the attribute names used by the IDP in Mautic's Configuration > User/Authentication Settings under the 'Enter the names of the attributes the configured IDP uses for the following Mautic User fields' section." -msgstr "" - -#: ../authentication/authentication.rst:52 -msgid "Logging in" -msgstr "" - -#: ../authentication/authentication.rst:54 -msgid "Once configured with the IDP and the IDP with Mautic, Mautic redirects all logins to the IDP's login. ``/s/login`` is still available for direct logins but you have to access it directly." -msgstr "" - -#: ../authentication/authentication.rst:56 -msgid "Login to the IDP, which then redirects you back to Mautic. If the exchange is successful Mautic creates a User if it doesn't already exist, and logs the User into the system." -msgstr "" - -#: ../authentication/authentication.rst:59 -msgid "Turning off SAML" -msgstr "" - -#: ../authentication/authentication.rst:61 -msgid "To turn off SAML, click the Remove link to the right of the Identity provider metadata file label." -msgstr "" - -#: ../authentication/authentication.rst:None -msgid "Screenshot of the authentication settings section" -msgstr "" diff --git a/docs/docs_translations/builders.pot b/docs/docs_translations/builders.pot deleted file mode 100644 index 37eeecd3..00000000 --- a/docs/docs_translations/builders.pot +++ /dev/null @@ -1,413 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../builders/creating_themes.rst:4 -msgid "Creating Themes" -msgstr "" - -#: ../builders/creating_themes.rst:8 -msgid ":xref:`MJML` allows marketers to create and maintain beautiful and responsive Themes for Mautic easily." -msgstr "" - -#: ../builders/creating_themes.rst:13 -msgid "Why use email Themes?" -msgstr "" - -#: ../builders/creating_themes.rst:16 -msgid "Purpose of a Theme" -msgstr "" - -#: ../builders/creating_themes.rst:20 -msgid "The GrapesJS builder makes it possible to insert HTML code and edit it in a 'What You See Is What You Get' (WYSIWYG) environment." -msgstr "" - -#: ../builders/creating_themes.rst:22 -msgid "A Theme can feature a wide variety of predefined blocks and sections reflecting the desired Email design - a template from which to start." -msgstr "" - -#: ../builders/creating_themes.rst:24 -msgid "By choosing a Theme, you can create beautiful Emails very efficiently." -msgstr "" - -#: ../builders/creating_themes.rst:29 -msgid "Modifying legacy Themes" -msgstr "" - -#: ../builders/creating_themes.rst:33 -msgid "The GrapesJS Builder checks the Theme configuration file before listing the available Themes, to determine which are compatible with the Builder." -msgstr "" - -#: ../builders/creating_themes.rst:35 -msgid "Since :xref:`Mautic 3` a new line defines the compatible Builders:" -msgstr "" - -#: ../builders/creating_themes.rst:37 -msgid "File name: config.json" -msgstr "" - -#: ../builders/creating_themes.rst:51 -msgid "With the builder/s defined, the Theme shows in the Theme selection page." -msgstr "" - -#: ../builders/creating_themes.rst:53 -msgid "If you wish to support more than one Builder, specify them in an array: ``\"builder\": [\"legacy\", \"grapesjsbuilder\"],``" -msgstr "" - -#: ../builders/creating_themes.rst:58 -msgid "Creating a Theme from scratch" -msgstr "" - -#: ../builders/creating_themes.rst:63 -msgid "HTML markup" -msgstr "" - -#: ../builders/creating_themes.rst:65 -msgid "It's possible to use HTML for Themes, and the GrapesJS builder offers basic WYSIWYG editing capabilities." -msgstr "" - -#: ../builders/creating_themes.rst:67 -msgid "Once converted into HTML, however, the structure is table based, and the blocks are hard to move around. For this reason, MJML Themes are preferable." -msgstr "" - -#: ../builders/creating_themes.rst:70 -msgid "MJML markup" -msgstr "" - -#: ../builders/creating_themes.rst:72 -msgid "The MJML language allows the creation of blocks which can be freely moved around in the editor, changing the layout fundamentally without coding." -msgstr "" - -#: ../builders/creating_themes.rst:74 -msgid "In order to harness the power of MJML, you must code the whole Theme in MJML." -msgstr "" - -#: ../builders/creating_themes.rst:76 -msgid "The best place to do so is the online editor at :xref:`MJML`." -msgstr "" - -#: ../builders/creating_themes.rst:78 -msgid "Documentation on using sections, columns, and blocks is available in the :xref:`MJML Documentation`" -msgstr "" - -#: ../builders/creating_themes.rst:83 -msgid "Head Components" -msgstr "" - -#: ../builders/creating_themes.rst:87 -msgid "At present, Mautic won't process the ```` tags. None of the ```` run, so you have to do all styling inline." -msgstr "" - -#: ../builders/creating_themes.rst:92 -msgid "Body Components" -msgstr "" - -#: ../builders/creating_themes.rst:96 -msgid "At present, Mautic processes most ```` components." -msgstr "" - -#: ../builders/creating_themes.rst:98 -msgid "**Tested elements** are: mj-button, mj-column, mj-divider, mj-image, mj-navbar, mj-section, mj-spacer, mj-text" -msgstr "" - -#: ../builders/creating_themes.rst:103 -msgid "Image Asset relative URLs" -msgstr "" - -#: ../builders/creating_themes.rst:107 -msgid "Images have to refer to the Themes folder the following way:" -msgstr "" - -#: ../builders/creating_themes.rst:109 -msgid "````" -msgstr "" - -#: ../builders/creating_themes.rst:111 -msgid "File structure" -msgstr "" - -#: ../builders/creating_themes.rst:128 -msgid "Steps to save the Theme package" -msgstr "" - -#: ../builders/creating_themes.rst:130 -msgid "Once your design in MJML is finalized, go through the following steps to create the Theme package:" -msgstr "" - -#: ../builders/creating_themes.rst:132 -msgid "Save your images in the Assets folder." -msgstr "" - -#: ../builders/creating_themes.rst:134 -msgid "Save your MJML in the ``html`` folder as ``email.mjml.twig`` AND ``email.html.twig``." -msgstr "" - -#: ../builders/creating_themes.rst:136 -msgid "Use the ``base.html.twig`` and ``message.html.twig`` files from the basic Theme or make your changes there." -msgstr "" - -#: ../builders/creating_themes.rst:138 -msgid "Save your ``config.json`` as described previously" -msgstr "" - -#: ../builders/creating_themes.rst:140 -msgid "Create a thumbnail - use the dimensions of 400px wide, 600px high." -msgstr "" - -#: ../builders/creating_themes.rst:142 -msgid "Compress the contents of the folder as a Zip file - ensure that the files and folders aren't within a sub-folder in the Zip file." -msgstr "" - -#: ../builders/email_landing_page.rst:4 -msgid "Email & Landing Page Builder" -msgstr "" - -#: ../builders/email_landing_page.rst:8 -msgid "Since :xref:`Mautic 3`, Mautic has shipped with an updated, modern Builder for creating Emails and Landing Pages. In :xref:`Mautic 4` it's the default Builder." -msgstr "" - -#: ../builders/email_landing_page.rst:13 -msgid "To use your existing templates with the new Builder, you need to add one line to your configuration file. Read on for further details." -msgstr "" - -#: ../builders/email_landing_page.rst:18 -msgid "About GrapesJS" -msgstr "" - -#: ../builders/email_landing_page.rst:22 -msgid ":xref:`Webmecanik` initiated the new Email and landing page as an MVP. After developing and improving it using the open source :xref:`GrapesJS` framework, :xref:`Aivie` kindly made it available to the Mautic community." -msgstr "" - -#: ../builders/email_landing_page.rst:24 -msgid "GrapesJS is an open source, multi-purpose, Web Builder Framework which combines different tools and features with the goal to help build HTML templates without any knowledge of coding." -msgstr "" - -#: ../builders/email_landing_page.rst:29 -msgid "Available end-user features" -msgstr "" - -#: ../builders/email_landing_page.rst:32 -msgid "Drag & drop built-in blocks" -msgstr "" - -#: ../builders/email_landing_page.rst:36 -msgid "GrapesJS comes with a set of built-in blocks, in this way you're able to build your templates faster. If the default set isn't enough you can always add your own custom blocks." -msgstr "" - -#: ../builders/email_landing_page.rst:39 -msgid "Limitless styling" -msgstr "" - -#: ../builders/email_landing_page.rst:41 -msgid "GrapesJS implements a simple and powerful Style Manager module which enables independent styling of any Component inside the canvas. It's also possible to configure it to use any of the CSS properties." -msgstr "" - -#: ../builders/email_landing_page.rst:44 -msgid "Responsive design" -msgstr "" - -#: ../builders/email_landing_page.rst:46 -msgid "GrapesJS gives you all the necessary tools you need to optimize your templates to look awesomely on any device. In this way you're able to provide various viewing experiences. In case you require more device options, you can easily add them to the editor." -msgstr "" - -#: ../builders/email_landing_page.rst:49 -msgid "The structure always under control" -msgstr "" - -#: ../builders/email_landing_page.rst:51 -msgid "You can nest Components as much as you can but when the structure begins to grow the Layer Manager comes very handy. It allows you to manage and rearrange your elements extremely fast, focusing always on the architecture of your structure." -msgstr "" - -#: ../builders/email_landing_page.rst:54 -msgid "The code is there when you need it" -msgstr "" - -#: ../builders/email_landing_page.rst:56 -msgid "You don't have to care about the code, but it's always there, available for you. When it's done, you can grab it and use it wherever you want. Developers could also implement their own storage interfaces to use inside the editor." -msgstr "" - -#: ../builders/email_landing_page.rst:59 -msgid "Asset manager" -msgstr "" - -#: ../builders/email_landing_page.rst:61 -msgid "With the Asset Manager is easier to organize your media files and it's enough to double click the image to change it." -msgstr "" - -#: ../builders/email_landing_page.rst:64 -msgid "About the builder" -msgstr "" - -#: ../builders/email_landing_page.rst:67 -msgid "Enabling the builder" -msgstr "" - -#: ../builders/email_landing_page.rst:69 -msgid "Since Mautic 3.3-RC1 the Builder is available to enable in the Plugins section of Mautic. Go to the Settings by clicking the cog wheel at the top right > Plugins > GrapesJS and click the GrapesJS icon. Change the slider to Yes." -msgstr "" - -#: ../builders/email_landing_page.rst:71 -msgid "Now you need to **clear your Mautic cache** located in ``var/cache`` and refresh the Landing Page before you can work with the new GrapesJS Builder. Some browsers may also require you to clear the browser cache." -msgstr "" - -#: ../builders/email_landing_page.rst:73 -msgid "By default, Mautic 4 activates the new Builder. Follow the previous steps to revert to the legacy Builder, remembering to clear the cache and reload the Landing Page." -msgstr "" - -#: ../builders/email_landing_page.rst:76 -msgid "Email builder overview" -msgstr "" - -#: ../builders/email_landing_page.rst:None -msgid "Screenshot of the editor overview" -msgstr "" - -#: ../builders/email_landing_page.rst:82 -msgid "The functions of the Email Builder are as follows:" -msgstr "" - -#: ../builders/email_landing_page.rst:84 -msgid "You can select different screen size to preview your Emails." -msgstr "" - -#: ../builders/email_landing_page.rst:86 -msgid "You have the ability to undo and redo your changes." -msgstr "" - -#: ../builders/email_landing_page.rst:88 -msgid "Editor functions from left to right: display grids, Full screen view, export MJML / HTML code, Edit code, display customization options, display blocks, close editor." -msgstr "" - -#: ../builders/email_landing_page.rst:90 -msgid "Layout sections. These objects function as the basic structure of your design. Create your Email structure from sections, and pull in the different blocks you want to use." -msgstr "" - -#: ../builders/email_landing_page.rst:92 -msgid "Content blocks. You can populate your newsletter with these content blocks. Each block has specific layout, settings and design." -msgstr "" - -#: ../builders/email_landing_page.rst:95 -msgid "Templates" -msgstr "" - -#: ../builders/email_landing_page.rst:97 -msgid "To use your existing templates with the new Builder, you need to add one line to your configuration file in the template folder:" -msgstr "" - -#: ../builders/email_landing_page.rst:99 -msgid "``\"builder\": [\"grapesjsbuilder\"],``" -msgstr "" - -#: ../builders/email_landing_page.rst:101 -msgid "If you wish to use the Theme in multiple builders, you can use this syntax:" -msgstr "" - -#: ../builders/email_landing_page.rst:103 -msgid "``\"builder\": [\"legacy\", \"grapesjsbuilder\"],``" -msgstr "" - -#: ../builders/email_landing_page.rst:107 -msgid "This syntax changed between Mautic 3.3.* and Mautic 4 to enable support for multiple Builders - if you have been testing in the beta phase you need to update your configuration files to avoid a 500 error." -msgstr "" - -#: ../builders/email_landing_page.rst:109 -msgid "The blank Theme contains an example of a full configuration file:" -msgstr "" - -#: ../builders/email_landing_page.rst:121 -msgid "From the 3.3 General Availability release there are be three Email templates that support MJML." -msgstr "" - -#: ../builders/email_landing_page.rst:124 -msgid "Themes" -msgstr "" - -#: ../builders/email_landing_page.rst:126 -msgid "If you search through the list of available Themes, the new MJML Themes ``Brienz``, ``Paprika`` and ``Confirm Me`` display only with the new Builder." -msgstr "" - -#: ../builders/email_landing_page.rst:128 -msgid "To learn more about creating Themes please :doc:`check the documentation`." -msgstr "" - -#: ../builders/email_landing_page.rst:131 -msgid "Custom fonts" -msgstr "" - -#: ../builders/email_landing_page.rst:133 -msgid "From Mautic 5.x you can extend the Style Manager > Typography > Fonts list to include custom fonts." -msgstr "" - -#: ../builders/email_landing_page.rst:None -msgid "Screenshot of the Fonts in Style Manager > Typography" -msgstr "" - -#: ../builders/email_landing_page.rst:139 -msgid "You define options as elements of the ``'editor_fonts'`` array in the local configuration file - in most cases located in ``app/config/local.php``. The font should have a unique name and a valid CSS style URL. See example below:" -msgstr "" - -#: ../builders/email_landing_page.rst:160 -msgid "Reporting bugs" -msgstr "" - -#: ../builders/email_landing_page.rst:163 -msgid "Known bugs / issues" -msgstr "" - -#: ../builders/email_landing_page.rst:165 -msgid "Please use the issue queue on the :xref:`GitHub repository` to find the latest updates and Report bugs with the Plugin. Be sure to search first in case someone has already reported the bug." -msgstr "" - -#: ../builders/email_landing_page.rst:168 -msgid "Switching back to the legacy Builder" -msgstr "" - -#: ../builders/email_landing_page.rst:170 -msgid "In case you aren't happy with the Plugin at the moment, you can easily switch back to the legacy Builder (original Mautic Builder). You can do so very quickly:" -msgstr "" - -#: ../builders/email_landing_page.rst:172 -msgid "Go to Mautic Settings > Click the cogwheel on the right-hand top corner" -msgstr "" - -#: ../builders/email_landing_page.rst:174 -msgid "Open the Plugins Directory > click \"Plugins\" inside the menu" -msgstr "" - -#: ../builders/email_landing_page.rst:176 -msgid "Find the GrapesJs Plugin and click it > Click \"No\" and then \"Save and Close\"" -msgstr "" - -#: ../builders/email_landing_page.rst:178 -msgid "Clear the cache and reload the Landing Page - you may also need to clear your browser cache." -msgstr "" - -#: ../builders/email_landing_page.rst:180 -msgid "After unloading GrapesJs Plugin, the legacy Builder becomes active again." -msgstr "" - -#: ../builders/email_landing_page.rst:183 -msgid "Thanks and credits" -msgstr "" - -#: ../builders/email_landing_page.rst:187 -msgid "Thank you to everyone who contributed to this project. Special thanks to Adrian Schimpf from :xref:`Aivie` for all their hard work in leading the project, to :xref:`Webmecanik` for initializing this amazing new builder and to Joey from :xref:`Friendly Automate` for donating three Email Themes to the Community. Additional contributions: Alex Hammerschmied from :xref:`hartmut.io`, Dennis Ameling." -msgstr "" - -#: ../builders/email_landing_page.rst:191 -msgid "And of course a really big thank you to all the contributors who have helped to bring this project to this point." -msgstr "" diff --git a/docs/docs_translations/campaigns.pot b/docs/docs_translations/campaigns.pot deleted file mode 100644 index 81954afd..00000000 --- a/docs/docs_translations/campaigns.pot +++ /dev/null @@ -1,837 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../campaigns/campaign_builder.rst:4 -msgid "Using the Campaign Builder" -msgstr "" - -#: ../campaigns/campaign_builder.rst:8 -msgid "The Campaign Builder provides a blank canvas on which you can build your Campaign workflow. The Campaign Builder allows the use of conditions, decisions, and actions. It enables you to create a simple workflow by dragging and dropping various decisions, actions, and conditions onto a canvas." -msgstr "" - -#: ../campaigns/campaign_builder.rst:10 -msgid "To build your Campaign, perform the following steps:" -msgstr "" - -#: ../campaigns/campaign_builder.rst:12 -msgid "Click **Launch the Campaign Builder** on the New Campaigns wizard. The Contact Sources menu appears as shown in the following image." -msgstr "" - -#: ../campaigns/campaign_builder.rst:None -msgid "Screenshot of Campaign builder showing Contact sources" -msgstr "" - -#: ../campaigns/campaign_builder.rst:18 -msgid "In this step, you specify the Contacts to include in your Campaign. It's possible to trigger a Campaign when Contacts join a Segment, submit a Form, or a combination of the two." -msgstr "" - -#: ../campaigns/campaign_builder.rst:20 -msgid "Select where your Campaign pulls the Contacts from:" -msgstr "" - -#: ../campaigns/campaign_builder.rst:22 -msgid "**Contact Segments**: choose this option if you want to send your Campaign to a specific group of your Contacts that share certain attributes, for example, 'Located in the United States' or 'Visited Product A' and are in an existing Segment based on this criteria." -msgstr "" - -#: ../campaigns/campaign_builder.rst:24 -msgid "Note that the Segment selection shows public Segments only. If you create a Segment marked as private, that Segment won't be available for use in Campaigns." -msgstr "" - -#: ../campaigns/campaign_builder.rst:26 -msgid "**Contact Forms**: choose this option if you want to start the Campaign when the Contact completes a specified Form. Forms are the primary point of gathering information about a Contact. It's possible to take action in a Campaign based on the Form field values submitted." -msgstr "" - -#: ../campaigns/campaign_builder.rst:28 -msgid "You can select a mix of both types of Contact sources for your Campaign. To use both, click the grey selector button on either the left or right side of the **Contact source** box to add whichever source type you didn't originally select." -msgstr "" - -#: ../campaigns/campaign_builder.rst:0 -msgid "Screenshot of Campaign builder showing multiple sources selected." -msgstr "" - -#: ../campaigns/campaign_builder.rst:34 -msgid "After selecting one or more Contact sources, click the grey selector button to add at least one event to your Campaign. A Campaign event comprises of a combination of actions, decisions, and/or conditions as shown in the following image:" -msgstr "" - -#: ../campaigns/campaign_builder.rst:None -msgid "Screenshot of Campaign builder showing the available Campaign events." -msgstr "" - -#: ../campaigns/campaign_builder.rst:40 -msgid "For more information about Campaign Actions, Decisions, and Conditions, see the following topics." -msgstr "" - -#: ../campaigns/campaign_builder.rst:43 -msgid "Actions" -msgstr "" - -#: ../campaigns/campaign_builder.rst:44 -msgid "Campaign actions are events that you initiate on your Contacts or Contact records. These can represent sending communications to the Contact or may automate operational tasks to keep your marketing running. A single Campaign can include more than one action. When you create a Campaign, you select one of these actions to begin the workflow." -msgstr "" - -#: ../campaigns/campaign_builder.rst:46 -msgid "The actions that Mautic offers in a Campaign include:" -msgstr "" - -#: ../campaigns/campaign_builder.rst:48 -msgid "Campaign Actions in Mautic :header-rows: 1 :widths: 5, 95" -msgstr "" - -#: ../campaigns/campaign_builder.rst:52 -msgid "Action" -msgstr "" - -#: ../campaigns/campaign_builder.rst:53 -#: ../campaigns/campaign_builder.rst:150 -#: ../campaigns/campaign_builder.rst:172 -#: ../campaigns/campaign_builder.rst:195 -msgid "Description" -msgstr "" - -#: ../campaigns/campaign_builder.rst:54 -msgid "**Add Do Not Contact**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:55 -msgid "Adds the Contact to the Do Not Contact (DNC) list" -msgstr "" - -#: ../campaigns/campaign_builder.rst:56 -msgid "**Add to Company's score**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:57 -msgid "Adds or subtracts a designated number of Points to or from the score for all Companies associated with the Contact." -msgstr "" - -#: ../campaigns/campaign_builder.rst:58 -msgid "**Add Company action**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:59 -msgid "Associates a Contact with a Company and sets the Company as the primary Company for the Contact." -msgstr "" - -#: ../campaigns/campaign_builder.rst:60 -msgid "**Adjust Contact Points**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:61 -msgid "Adds or subtracts Points from the Contact’s Point total." -msgstr "" - -#: ../campaigns/campaign_builder.rst:62 -msgid "**Change Campaigns**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:63 -msgid "Removes a Contact from the existing Campaign, moves them into another Campaign, restarts the current Campaign or a combination of these. You must remove a Contact from a Campaign before restarting the Campaign." -msgstr "" - -#: ../campaigns/campaign_builder.rst:64 -msgid "**Change Contact's Stage**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:65 -msgid "Moves a Contact to the specified Stage." -msgstr "" - -#: ../campaigns/campaign_builder.rst:66 -msgid "**Delete Contact**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:67 -msgid "Permanently deletes the Contact record along with all the information about that Contact, including the Campaign event log record about that Contact. See the :doc:`Segment docs` about how to use this action to delete all Contacts in a Segment." -msgstr "" - -#: ../campaigns/campaign_builder.rst:68 -msgid "**Jump to Event**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:69 -msgid "Moves Contacts from one point in a Campaign to another without rebuilding events. Use this action to send the Contact to a different path in the Campaign." -msgstr "" - -#: ../campaigns/campaign_builder.rst:70 -msgid "**Modify Contact's Segments**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:71 -msgid "Adds or removes Contacts to/from Segments. When removing a Contact from a dynamic - filter-based - Segment via a Campaign action, they won't be re-added to the Segment based on meeting the filter criteria." -msgstr "" - -#: ../campaigns/campaign_builder.rst:72 -msgid "**Modify Contact's tags**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:73 -msgid "Overwrites or appends Tags on a Contact record. You can add or remove Tags, or do both, in the same action." -msgstr "" - -#: ../campaigns/campaign_builder.rst:74 -msgid "**Push Contact to Integration**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:75 -msgid "Sends the Contact record to the selected Integration, either creating a new Contact in the chosen Integration or updating the connected Contact record." -msgstr "" - -#: ../campaigns/campaign_builder.rst:76 -msgid "**Remove Do Not Contact**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:77 -msgid "Removes the Contact from the Do Not Contact (DNC) list." -msgstr "" - -#: ../campaigns/campaign_builder.rst:78 -msgid "**Send a Webhook**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:79 -msgid "Sends a Webhook to a defined URL, using the GET, POST, PUT, PATCH, or DELETE methods. Headers and data is customizable, and support the use of tokens, such as Contact fields and the Contact's IP address. For example, ``{contactfield=firstname}``" -msgstr "" - -#: ../campaigns/campaign_builder.rst:80 -msgid "**Send Email**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:81 -msgid "Sends a transaction or marketing Email to the selected Contact. You can send a transactional Email to the Contact multiple times. You can only send a marketing Email to the Contact once across multiple sources. If the Contact has already received this Email from another source or the current Campaign, they aren't sent the Email again and the Contact progresses through the Campaign." -msgstr "" - -#: ../campaigns/campaign_builder.rst:82 -msgid "**Send Email to User**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:83 -msgid "Sends an Email to an entity other than the Contact. This may be a Mautic User, the Contact's owner, or non-Users. Emails sent using this action don't generate any statistics for Contacts or Emails." -msgstr "" - -#: ../campaigns/campaign_builder.rst:84 -msgid "**Send Marketing Message**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:85 -msgid "Sends a message using the Contact's preferred Channel." -msgstr "" - -#: ../campaigns/campaign_builder.rst:86 -msgid "**Update Contact**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:87 -msgid "Updates the existing Contact's fields with the specified values." -msgstr "" - -#: ../campaigns/campaign_builder.rst:88 -msgid "**Update Contact's primary Company**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:89 -msgid "Updates the existing Contact's primary Company fields with the specified value. See :doc:`documentation on Companies `." -msgstr "" - -#: ../campaigns/campaign_builder.rst:90 -msgid "**Update Contact owner**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:91 -msgid "Updates the Contact's owner." -msgstr "" - -#: ../campaigns/campaign_builder.rst:96 -msgid "Notes on Campaign Actions" -msgstr "" - -#: ../campaigns/campaign_builder.rst:101 -msgid "As the first step of your Campaign, you typically send out an Email to your Segments. When you add an Email to a Campaign, you can select a potential **delay** for Email delivery as shown in the following image." -msgstr "" - -#: ../campaigns/campaign_builder.rst:None -msgid "Screenshot of Campaign builder showing the Email send delay options." -msgstr "" - -#: ../campaigns/campaign_builder.rst:107 -msgid "When attaching an Action to a decision's **non-action** initiated decision path, the delay becomes how long the Contact has to take action before the Campaign progresses down the non-action path. Image showing delayed actions on a non-action decision path in a Campaign." -msgstr "" - -#: ../campaigns/campaign_builder.rst:109 -msgid "The Delete Contact action also deletes the Campaign event log record about that Contact. Therefore, though this action might always display 0% progress on the Campaign detail overview, it could have deleted some Contacts." -msgstr "" - -#: ../campaigns/campaign_builder.rst:112 -msgid "The Delete Contact action doesn't allow connection with other Campaign events. Since the Contact won't exist after triggering this action, Campaign events can't exist after this point." -msgstr "" - -#: ../campaigns/campaign_builder.rst:114 -msgid "After adding an action, you can place a decision on the Campaign." -msgstr "" - -#: ../campaigns/campaign_builder.rst:117 -msgid "Decisions" -msgstr "" - -#: ../campaigns/campaign_builder.rst:119 -msgid "Campaign Decisions are actions that your Contacts initiate. Downloading an Asset, opening an Email, or visiting a Landing Page are examples of Decisions. These Decisions can be either directly initiated or implied based on non-action. The options for Decisions change based on the Campaign Actions that you select." -msgstr "" - -#: ../campaigns/campaign_builder.rst:121 -msgid "A decision usually has two paths denoted by the red and green icons on the decision tree." -msgstr "" - -#: ../campaigns/campaign_builder.rst:124 -msgid "Green paths" -msgstr "" - -#: ../campaigns/campaign_builder.rst:126 -msgid "Green paths indicate positive or affirmative actions." -msgstr "" - -#: ../campaigns/campaign_builder.rst:128 -msgid "A Contact takes this path if the Contact has made a direct action such as opening an Email or submitting a Form. Execution of Actions that follow the green paths happen immediately - or scheduled immediately in the case of a delay on the following action - at the time the Contact takes the action." -msgstr "" - -#: ../campaigns/campaign_builder.rst:131 -msgid "Red paths" -msgstr "" - -#: ../campaigns/campaign_builder.rst:133 -msgid "Red paths indicate non-action." -msgstr "" - -#: ../campaigns/campaign_builder.rst:135 -msgid "A Contact takes this path if a Contact hasn't taken the action. Use an action's delay settings to define at what point the Campaign should send the Contact to the following steps on this path." -msgstr "" - -#: ../campaigns/campaign_builder.rst:137 -msgid "Depending on meeting - or not meeting - the criteria for the decision, the Contact takes either the green or the red paths in the decision tree. For example, consider an instance where the decision is to visit a Landing Page. There can be two outcomes. If the Contact chooses to visit the Landing Page, then the green decision path connects to the next action in the Campaign workflow. If, however, the Contact doesn't visit the Landing Page, then the red decision path connects to a different action - for example a delay of 7 days then the marketer may send a follow up Email." -msgstr "" - -#: ../campaigns/campaign_builder.rst:None -msgid "Screenshot showing Campaign decisions available in Mautic" -msgstr "" - -#: ../campaigns/campaign_builder.rst:143 -msgid "Here are the decisions that Mautic offers in the Campaign Builder:" -msgstr "" - -#: ../campaigns/campaign_builder.rst:145 -msgid "Decision Actions in Mautic" -msgstr "" - -#: ../campaigns/campaign_builder.rst:149 -#: ../campaigns/campaign_builder.rst:171 -msgid "Decision" -msgstr "" - -#: ../campaigns/campaign_builder.rst:151 -msgid "**Device visit**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:152 -msgid "Set the options to track whether your Contact visits your resources from a specific device type, brand, or operating system." -msgstr "" - -#: ../campaigns/campaign_builder.rst:153 -msgid "**Downloads Asset**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:154 -msgid "Set the options to track whether your Contact downloads specified Asset/s." -msgstr "" - -#: ../campaigns/campaign_builder.rst:155 -msgid "**Request Dynamic Content**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:156 -msgid "Set options to push Campaign-based Dynamic Content if you have a webpage or Landing Page where you want to add Dynamic Content." -msgstr "" - -#: ../campaigns/campaign_builder.rst:157 -msgid "**Submits Form**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:158 -msgid "Set options to track whether the Contact has submitted any Mautic Forms. You can also limit this decision to track specific Forms." -msgstr "" - -#: ../campaigns/campaign_builder.rst:159 -msgid "**Visits a page**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:160 -msgid "Specify one or multiple pages you want the Contact to visit. Can be Mautic Landing Pages or pages on your website." -msgstr "" - -#: ../campaigns/campaign_builder.rst:161 -msgid "**Email-Related Decisions**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:162 -msgid "Some decisions in the Campaign Builder are available for use only if you select the Send Email Campaign action." -msgstr "" - -#: ../campaigns/campaign_builder.rst:165 -msgid "Here are the decisions that are Email-related:" -msgstr "" - -#: ../campaigns/campaign_builder.rst:167 -msgid "Email-related Decision Actions in Mautic" -msgstr "" - -#: ../campaigns/campaign_builder.rst:173 -msgid "**Opens Email**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:174 -msgid "Tracks whether the Contact opens the Email." -msgstr "" - -#: ../campaigns/campaign_builder.rst:175 -msgid "**Clicks Email**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:176 -msgid "Tracks whether the Contact clicks a link within the sent Email. This infers that the Contact opened the Email." -msgstr "" - -#: ../campaigns/campaign_builder.rst:177 -msgid "**Replies to Email**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:178 -msgid "Tracks if a Contact has replied to an Email that you sent. For more information, see Contact replies." -msgstr "" - -#: ../campaigns/campaign_builder.rst:182 -msgid "Conditions" -msgstr "" - -#: ../campaigns/campaign_builder.rst:184 -msgid "Campaign conditions execute different actions based on a Contact's data. For example, to execute an action if a Contact has a valid Email address or do something else if they don't." -msgstr "" - -#: ../campaigns/campaign_builder.rst:186 -msgid "A condition has two paths, denoted by red and green icons as explained in the previous section." -msgstr "" - -#: ../campaigns/campaign_builder.rst:188 -msgid "Here are the different conditions that Mautic offers in the Campaign Builder:" -msgstr "" - -#: ../campaigns/campaign_builder.rst:190 -msgid "Condition Actions in Mautic" -msgstr "" - -#: ../campaigns/campaign_builder.rst:194 -msgid "Condition" -msgstr "" - -#: ../campaigns/campaign_builder.rst:196 -msgid "**Contact Campaigns**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:197 -msgid "Checks if the Contact is a member of another Campaign." -msgstr "" - -#: ../campaigns/campaign_builder.rst:198 -msgid "**Contact device**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:199 -msgid "Checks if the Contact has interacted with your Campaign from a specific device type, brand, or OS." -msgstr "" - -#: ../campaigns/campaign_builder.rst:200 -msgid "**Contact field value**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:201 -msgid "Checks if the information matches the selected criteria on the Contact record, the Contact’s primary Company, or UTM tags." -msgstr "" - -#: ../campaigns/campaign_builder.rst:202 -msgid "**Contact owner**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:203 -msgid "Checks if the selected User is the Contact's owner." -msgstr "" - -#: ../campaigns/campaign_builder.rst:204 -msgid "**Contact Segments**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:205 -msgid "Checks if the Contact is a member of selected Segments." -msgstr "" - -#: ../campaigns/campaign_builder.rst:206 -msgid "**Contact Tags**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:207 -msgid "Checks if specified Tags are on the Contact record." -msgstr "" - -#: ../campaigns/campaign_builder.rst:208 -msgid "**Form field value**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:209 -msgid "Checks if values submitted for a selected field on a selected Form matches specified criteria." -msgstr "" - -#: ../campaigns/campaign_builder.rst:210 -msgid "**Has active notification**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:211 -msgid "Checks if the Contact has an active web notification." -msgstr "" - -#: ../campaigns/campaign_builder.rst:212 -msgid "**Has valid Email address**" -msgstr "" - -#: ../campaigns/campaign_builder.rst:213 -msgid "Checks if the Contact's Email address has a valid syntax, for example name@example.com without spaces, other invalid characters or formats." -msgstr "" - -#: ../campaigns/campaign_builder.rst:216 -msgid "Notes on delayed conditions and dates" -msgstr "" - -#: ../campaigns/campaign_builder.rst:217 -msgid "Mautic respects delays set on the condition itself before passing down to a delay on any connected action. For example, if you are coming from a negative path on 'Opens Email', you can set a condition of 'has active notification' with a relative date of 1 day, followed by 'Send Email' on the negative path with a relative date of 2 days. Mautic checks after 1 day if there is an active notification and if there isn't, schedules the Email for two days later." -msgstr "" - -#: ../campaigns/campaign_builder.rst:220 -msgid "Using a custom date field to trigger a Campaign" -msgstr "" - -#: ../campaigns/campaign_builder.rst:221 -msgid "In the condition based on a Contact field value, select the required date field. Then select date as the operator and select the required value from the drop-down list." -msgstr "" - -#: ../campaigns/campaign_builder.rst:223 -msgid "In the Anniversary option, you can only enter the day and month values." -msgstr "" - -#: ../campaigns/campaign_builder.rst:225 -msgid "Mautic evaluates Campaign conditions immediately, therefore if the date in the field matches the condition, Mautic executes then the positive action. If the date doesn't match, Mautic executes the negative action. The Contact doesn't wait for the condition to be TRUE." -msgstr "" - -#: ../campaigns/campaign_builder.rst:227 -msgid "In order to run Campaigns based on a particular date where a Contact may or may not be \"included\" today:" -msgstr "" - -#: ../campaigns/campaign_builder.rst:229 -msgid "create a Segment with a filter where the date field = ``TODAY``." -msgstr "" - -#: ../campaigns/campaign_builder.rst:230 -msgid "initiate the Campaign based on that Segment." -msgstr "" - -#: ../campaigns/campaign_builder.rst:231 -msgid "as Contacts move in and out of the Segment, the Campaign runs." -msgstr "" - -#: ../campaigns/campaign_builder.rst:232 -msgid "you can eliminate the condition since the Segment is changing daily." -msgstr "" - -#: ../campaigns/campaign_builder.rst:234 -msgid "This **doesn't work** for the Anniversary option." -msgstr "" - -#: ../campaigns/campaign_builder.rst:236 -msgid "If a Contact appears again at a later date in that Segment because the value of the date has changed, then the Contact passes through the Campaign only once, and hence isn't included in the Campaign again." -msgstr "" - -#: ../campaigns/campaign_builder.rst:241 -msgid "Triggering Campaign events" -msgstr "" - -#: ../campaigns/campaign_builder.rst:245 -msgid "Actions and Decisions in Mautic require a :doc:`cron job` which executes the following command at the desired interval:" -msgstr "" - -#: ../campaigns/campaign_builder.rst:251 -msgid "If you want to execute the command at different intervals for specific Campaigns, you can pass the ``--campaign-id=ID`` argument to the command." -msgstr "" - -#: ../campaigns/campaigns_overview.rst:2 -msgid "Campaigns overview" -msgstr "" - -#: ../campaigns/campaigns_overview.rst:4 -msgid "A Campaign is a marketing activity that aligns Components and the Channels through which you can publish your content in a coordinated, strategically timed approach to meet specific business objectives. After you add your Contacts and set up the required Channels, you can create Campaigns to build meaningful relationships with your Contacts." -msgstr "" - -#: ../campaigns/campaigns_overview.rst:6 -msgid "Campaigns are useful for Contact management, marketing operations, and sales workflows. A Campaign can send tailored messages to all Contacts in the Segment, or a subset of Contacts that you specify. You can set the Campaign schedule to send the message once or at a recurring interval, such as once a week." -msgstr "" - -#: ../campaigns/campaigns_overview.rst:8 -msgid "One of the main benefits of the Campaign workflow process is the ability to predefine these workflows and have them respond automatically to your Contacts and timelines. This automation minimizes the amount of time required for manual Contact activity and improves reliability of Contact nurturing." -msgstr "" - -#: ../campaigns/campaigns_overview.rst:11 -msgid "Campaign types" -msgstr "" - -#: ../campaigns/campaigns_overview.rst:13 -msgid "Campaigns can be broadly categorized into three types:" -msgstr "" - -#: ../campaigns/campaigns_overview.rst:18 -msgid "Time driven Campaigns" -msgstr "" - -#: ../campaigns/campaigns_overview.rst:22 -msgid "Time driven Campaigns are the type of Campaigns that center around specific timed events. These events can be anything, but are usually Emails. For instance, you can choose to trigger such Email events after a delay of a predefined number of days or on a specific date in the future." -msgstr "" - -#: ../campaigns/campaigns_overview.rst:27 -msgid "Contact driven Campaigns" -msgstr "" - -#: ../campaigns/campaigns_overview.rst:31 -msgid "Contact driven Campaigns can trigger events based on interactions with specific Contacts. These interactions can occur as a result of the Contact landing on a certain webpage or Landing Page, opening an Email, spending a specified amount of time on a website, or any other activities. Such Campaigns can respond to these actions typically by sending an Email to the Contact either immediately or at a specific time in future." -msgstr "" - -#: ../campaigns/campaigns_overview.rst:37 -msgid "Mixed Campaigns" -msgstr "" - -#: ../campaigns/campaigns_overview.rst:41 -msgid "Mautic allows you to create Campaigns which consist a mix of both time driven Campaigns as well as Contact driven actions. This powerful mixed Campaign strategy drives actions by both specific dates or after specific time frames, as well as actions taken by a Contact directly." -msgstr "" - -#: ../campaigns/campaigns_overview.rst:44 -msgid "Campaigns can trigger a variety of actions. Email actions mentioned in the preceding Campaign types are one example. The other actions that a Campaign can trigger include automatic assignment to a new Segment, assigning a new Point value, or pushing into an Integration, into a CRM or other systems." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:4 -msgid "Creating Campaigns" -msgstr "" - -#: ../campaigns/creating_campaigns.rst:8 -msgid "Creating Campaigns is a central part of the marketing automation process. When you create a new Campaign, you perform the basic administrative tasks such as choosing a name for the Campaign, creating a description, assigning a Category and defining publishing information for the Campaign." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:10 -msgid "At the heart of any marketing automation Campaign is the Campaign Builder. This allows you to specify how Contacts enter the Campaign, and what happens at every point after they enter the workflow." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:12 -msgid "After establishing the basics, the Campaign Builder handles the finer details of building a Campaign workflow using Conditions, Decisions, and Actions." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:15 -msgid "Prerequisites" -msgstr "" - -#: ../campaigns/creating_campaigns.rst:17 -msgid "Before you start creating Campaigns, you must ensure that you have the following set up:" -msgstr "" - -#: ../campaigns/creating_campaigns.rst:20 -msgid "Create a Contact Segment or a Form to initialize your Campaign. If you already have an existing Segment or Form to use, ensure that they're up-to-date." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:22 -msgid "Create any custom field that you need for your Contact profile." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:23 -msgid "Set up and configure any Integration that you intend to use in your Campaign." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:24 -msgid "Set up appropriate Channels such as Text Messages, Email, Focus items to communicate with your Contacts." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:25 -msgid "Create Assets, Landing pages, or other Components that you want to use for your Campaign. If using Assets, ensure that you upload them before creating your Campaign." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:27 -msgid "Although you can set up Channels and create Components during the process of creating the Campaign, it's ideal to have them ready beforehand as it makes the Campaign building process faster and more efficient." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:32 -msgid "Create your first Campaign" -msgstr "" - -#: ../campaigns/creating_campaigns.rst:36 -msgid "After you have the prerequisites in place, you are ready to create your first Campaign." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:39 -msgid "To begin creating Campaigns, perform the following steps:" -msgstr "" - -#: ../campaigns/creating_campaigns.rst:41 -msgid "Launch your Mautic instance." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:42 -msgid "Click **Campaigns** in the left navigation menu. The Campaigns page appears." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:43 -msgid "Click **New** on the Campaigns page. The New Campaign wizard appears as shown in the following image. Screenshot of the New Campaign screen" -msgstr "" - -#: ../campaigns/creating_campaigns.rst:None -msgid "Screenshot of the create a new Campaign interface" -msgstr "" - -#: ../campaigns/creating_campaigns.rst:49 -msgid "Enter a name and a brief description for your Campaign." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:50 -msgid "Optionally, you can set the following properties:" -msgstr "" - -#: ../campaigns/creating_campaigns.rst:52 -msgid "**Category** - Choose a Category to assign your Campaign to. Categories help you organize your Campaigns. To learn more about creating and managing Categories, see :doc:`/categories/categories-overview`." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:53 -msgid "**Allow Contacts to restart the Campaign** - Click the toggle switch to allow Contacts to restart the Campaign if you're building a Campaign for a recurring message - for example birthdays, subscriptions - or transactional operations - for example activity notifications, updating data. Enabling this option allows Contacts to go through the same Campaign multiple times." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:54 -msgid "**Published** - Click the toggle switch to publish or un-publish the Campaign. Ensure that you don't publish a Campaign until you're actually ready for it to go live. You can also schedule to publish or un-publish a Campaign at a future date by selecting a time and date." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:56 -msgid "Click **Launch Campaign Builder** to start building your Campaign, and add at least one event. For information about how to use the Campaign Builder, see :doc:`/campaigns/creating_campaigns`." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:59 -msgid "After adding events to your Campaign, close the Campaign Builder and click **Save & Close** to save your changes." -msgstr "" - -#: ../campaigns/creating_campaigns.rst:63 -msgid "Add or remove Contacts in batch" -msgstr "" - -#: ../campaigns/creating_campaigns.rst:65 -msgid "After creating your Campaign, you can add or remove Contacts in batch for Campaigns using the following command:" -msgstr "" - -#: ../campaigns/creating_campaigns.rst:72 -msgid "See documentation on :doc:`/configuration/cron_jobs` for further details." -msgstr "" - -#: ../campaigns/managing_campaigns.rst:4 -msgid "Managing Campaigns" -msgstr "" - -#: ../campaigns/managing_campaigns.rst:8 -msgid "You can manage your Campaigns from the Campaigns overview." -msgstr "" - -#: ../campaigns/managing_campaigns.rst:10 -msgid "Click any Campaign name on the Campaigns list to take you to the Campaign overview. Each tab displays details of your Campaign, including the number of Contacts added to the Campaign, the number of Emails sent, the number of page views resulting from the Campaign, and more." -msgstr "" - -#: ../campaigns/managing_campaigns.rst:12 -msgid "Additional information includes a quick overview of what decisions and actions are available in the Campaign, as well as a grid layout overview of all the Contacts in the Campaign." -msgstr "" - -#: ../campaigns/managing_campaigns.rst:14 -msgid "The following image shows a sample Campaign overview with its highlighted panels:" -msgstr "" - -#: ../campaigns/managing_campaigns.rst:None -msgid "Screenshot showing the Campaign overview" -msgstr "" - -#: ../campaigns/managing_campaigns.rst:20 -msgid "The **Details** drop-down menu gives a quick overview of the most important information about your Campaign. This information includes the name of the User who created the Campaign, Category of the Campaign, creation date and time, publishing date and time, Contact Segments in your Campaign and more." -msgstr "" - -#: ../campaigns/managing_campaigns.rst:22 -msgid "The **Campaign Statistics** panel shows the number of Contacts added to the Campaign over the specified period of time in graphical format. To specify the time period, use the From and To date selectors, and click Apply." -msgstr "" - -#: ../campaigns/managing_campaigns.rst:24 -msgid "The **Preview** tab displays a diagrammatic preview of your Campaign." -msgstr "" - -#: ../campaigns/managing_campaigns.rst:26 -msgid "The **Decisions** tab displays a tabular list of all the decisions that you have added to your Campaign." -msgstr "" - -#: ../campaigns/managing_campaigns.rst:28 -msgid "The **Actions** tab displays a tabular list of all the actions that you have added to your Campaign." -msgstr "" - -#: ../campaigns/managing_campaigns.rst:30 -msgid "The **Conditions** tab displays a tabular list of all he conditions that you have added to your Campaign." -msgstr "" - -#: ../campaigns/managing_campaigns.rst:32 -msgid "The **Contacts** tab displays a grid view of all the Contacts that you have added to your Campaign." -msgstr "" - -#: ../campaigns/managing_campaigns.rst:34 -msgid "The **Recent Activity** panel on the right displays the recent activities that have taken place in the Campaign." -msgstr "" - -#: ../campaigns/troubleshooting_campaigns.rst:4 -msgid "Troubleshooting Campaigns" -msgstr "" - -#: ../campaigns/troubleshooting_campaigns.rst:9 -msgid "Page visits aren't recognized" -msgstr "" - -#: ../campaigns/troubleshooting_campaigns.rst:11 -msgid "To workaround this issue, try one of the following options:" -msgstr "" - -#: ../campaigns/troubleshooting_campaigns.rst:13 -msgid "Make sure that you aren't testing the Page visit while logged into Mautic. Mautic ignores activity from Mautic Administrators. So, it's suggested that you use an anonymous session, an incognito window, another browser, or log out of Mautic." -msgstr "" - -#: ../campaigns/troubleshooting_campaigns.rst:15 -msgid "Ensure that the Contact getting tracked is in the Campaign. The easy way to test this is to review the timeline of the Contact for the page hit / inclusion into the Campaign." -msgstr "" - -#: ../campaigns/troubleshooting_campaigns.rst:17 -msgid "Mautic executes Campaigns sequentially and won't repeat per Contact. If the Contact has already visited the Page while part of the Campaign and triggered the Visits a Page decision, then the Contact's subsequent visits won't re-trigger the actions associated with the decision." -msgstr "" - -#: ../campaigns/troubleshooting_campaigns.rst:19 -msgid "Ensure that the URL in the Campaign action either matches exactly the URL visited, or use a wildcard. A URL can include the schema, host/domain, path, query parameters, and/or fragment. For example, if you have a URL of ``https://example.com`` and the page hit registers as ``https://example.com/index.php?foo=bar``, the Campaign decision won't trigger. However, if you use ``https://example.com*`` as the URL, it matches the rule and thus gets triggered." -msgstr "" - -#: ../campaigns/troubleshooting_campaigns.rst:21 -msgid "Another example is if you want to associate different page hits with specific Campaigns. For example, if you have Campaign A and Campaign B and you want to use the same base URL and path for both Campaigns but differentiate with a query parameter. For Campaign A, you can define a Visits a Page decision with ``https://example.com/my-page?utm_campaign=A*`` and for Campaign B, ``https://example.com/my-page?utm_campaign=B*``. A Contact only triggers the specific Campaign desired. If the goal is to trigger both Campaigns regardless of the query parameters, use ``https://example.com/my-page*``." -msgstr "" diff --git a/docs/docs_translations/categories.pot b/docs/docs_translations/categories.pot deleted file mode 100644 index 03035b15..00000000 --- a/docs/docs_translations/categories.pot +++ /dev/null @@ -1,65 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../categories/categories-overview.rst:4 -msgid "Categories" -msgstr "" - -#: ../categories/categories-overview.rst:8 -msgid "Categories are a way to organize Mautic elements. They're available for Assets, Campaigns, Emails, Focus Items, Forms, Pages, Points, Social Monitoring and Stages. There are two ways to use Categories:" -msgstr "" - -#: ../categories/categories-overview.rst:10 -msgid "Create element-specific Categories for example only for Assets, Emails or Forms." -msgstr "" - -#: ../categories/categories-overview.rst:11 -msgid "Create global Categories for all Mautic elements." -msgstr "" - -#: ../categories/categories-overview.rst:16 -msgid "Creating and managing Categories" -msgstr "" - -#: ../categories/categories-overview.rst:20 -msgid "To create new Categories, go to settings menu in the top right corner of Mautic. There choose Categories." -msgstr "" - -#: ../categories/categories-overview.rst:None -msgid "Screenshot of create new Category" -msgstr "" - -#: ../categories/categories-overview.rst:28 -msgid "When creating a new Category you can select type, title, description, alias, color and published status. The color will be helpful to quickly find Mautic elements by their appropriate Category when viewing things like the Calendar or other areas within Mautic." -msgstr "" - -#: ../categories/categories-overview.rst:31 -msgid "Using Categories for Contacts" -msgstr "" - -#: ../categories/categories-overview.rst:35 -msgid "In addition to organizing various Mautic elements Categories can be used to organize Contacts. In Contact details use the Preference menu to open Contact Preference Center." -msgstr "" - -#: ../categories/categories-overview.rst:None -msgid "Screenshot of assigning Category to Contact" -msgstr "" - -#: ../categories/categories-overview.rst:41 -msgid "Contact Categories can be used in Segment and dynamic content filters." -msgstr "" diff --git a/docs/docs_translations/channels.pot b/docs/docs_translations/channels.pot deleted file mode 100644 index 141e6042..00000000 --- a/docs/docs_translations/channels.pot +++ /dev/null @@ -1,1865 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../channels/emails.rst:2 -msgid "Emails" -msgstr "" - -#: ../channels/emails.rst:4 -msgid "Mautic enables marketers to automatically send Emails directly to a group of Contacts in a Segment by using a Campaign, or send Emails on a one-time basis. Emails provide a means for direct interaction with potential customers, clients, and Contacts." -msgstr "" - -#: ../channels/emails.rst:7 -msgid "Email types" -msgstr "" - -#: ../channels/emails.rst:None -msgid "Screenshot showing the types of Emails that are available in Mautic" -msgstr "" - -#: ../channels/emails.rst:13 -msgid "There are two types of Emails: template and Segment - broadcast - Emails." -msgstr "" - -#: ../channels/emails.rst:18 -msgid "Template Emails" -msgstr "" - -#: ../channels/emails.rst:22 -msgid "Template Emails are transactional by default. They're used in Campaigns, Form submit actions, Point triggers, etc. It's possible to send template Emails to the same Contact multiple times. You can't send template Emails to a Contact outside of another Mautic Component except when sending an Email directly to a Contact - in this case Mautic clones the content." -msgstr "" - -#: ../channels/emails.rst:25 -msgid "For this reason, template Emails sent directly to a Contact aren't associated with the template Email itself and thus stats aren't tracked against it." -msgstr "" - -#: ../channels/emails.rst:30 -msgid "Segment (Broadcast) Emails" -msgstr "" - -#: ../channels/emails.rst:34 -msgid "Segment Emails are marketing Emails by default. On creation the marketer assigns Segments to the Email. This determines which Contacts receive the communication. Note that each Contact can only receive the Email once - it's like a mailing list." -msgstr "" - -#: ../channels/emails.rst:None -msgid "Screenshot showing selecting Email Segments in Mautic" -msgstr "" - -#: ../channels/emails.rst:40 -msgid "This entry field is a multi-select which allows you to choose several Segments if necessary." -msgstr "" - -#: ../channels/emails.rst:42 -msgid "Mautic initiates the sending of these Emails with a :doc:`/configuration/cron_jobs` - see section on Send Scheduled Broadcasts - for example, Segment Emails - for more details on this." -msgstr "" - -#: ../channels/emails.rst:45 -msgid "Email formats" -msgstr "" - -#: ../channels/emails.rst:47 -msgid "In Mautic, it's possible to create Emails in both full HTML as well as basic text format - delivered as necessary to Contacts based on what their client supports. This is an important part of creating a strong relationship with Contacts by providing relevant information in the correct format." -msgstr "" - -#: ../channels/emails.rst:52 -msgid "Managing Emails" -msgstr "" - -#: ../channels/emails.rst:57 -msgid "Email overview" -msgstr "" - -#: ../channels/emails.rst:59 -msgid "The Email overview allows at-a-glance information regarding the success or failure of a particular Email. You can quickly see relevant information in regards to opens, bounces, successful click-throughs and other important statistics." -msgstr "" - -#: ../channels/emails.rst:62 -msgid "Translations" -msgstr "" - -#: ../channels/emails.rst:64 -msgid "When creating the Email, there is an option to assign a language and a translation parent. By selecting a translation parent, the current item is then considered to be a translation in the selected language of that parent item. If a Contact has a preferred language set, they receive the translated version in their preferred language if it exists. Otherwise, they receive the parent in the default language." -msgstr "" - -#: ../channels/emails.rst:66 -msgid "It's also possible to have translations of A/B test variants." -msgstr "" - -#: ../channels/emails.rst:69 -msgid "Base64 encoded images" -msgstr "" - -#: ../channels/emails.rst:71 -msgid "It's possible to encode all images in the Email text as base64. It attaches the image inside the Email body. It has several implications:" -msgstr "" - -#: ../channels/emails.rst:None -msgid "Screenshot showing Base64 settings for images in Emails" -msgstr "" - -#: ../channels/emails.rst:77 -msgid "The main idea with this option is that most of the Email clients display the images directly, without the need to allow images." -msgstr "" - -#: ../channels/emails.rst:78 -msgid "Some Email clients like GMail require the approval to display Base64 encoded images due to the tracking pixel being an image, and won't display the Base64 encoded images as a result. See the next paragraph for possible solution." -msgstr "" - -#: ../channels/emails.rst:79 -msgid "The Email body increases significantly if the Email contains many and/or large sized images. Some Email clients like GMail \"clip\" such messages and won't display it directly." -msgstr "" - -#: ../channels/emails.rst:82 -msgid "Tokens" -msgstr "" - -#: ../channels/emails.rst:84 -msgid "Mautic allows the use of tokens in Emails which gives the marketer the possibility to integrate a number of Contact fields in your Emails. These can be easily placed within your Emails and are automatically replaced with the appropriate text once sent." -msgstr "" - -#: ../channels/emails.rst:86 -msgid "Check the :doc:`/configuration/variables` documentation for a list of all the available default fields." -msgstr "" - -#: ../channels/emails.rst:89 -msgid "Default value" -msgstr "" - -#: ../channels/emails.rst:91 -msgid "A token can have a default value for cases when the Contact doesn't have the value known. You must specify the default value after a ``|`` character, for example:" -msgstr "" - -#: ../channels/emails.rst:97 -msgid "The ``|friend`` tells Mautic to use 'friend' if there is no first name present in the Contact field." -msgstr "" - -#: ../channels/emails.rst:100 -msgid "Encoded value" -msgstr "" - -#: ../channels/emails.rst:102 -msgid "It's possible to encode values used in a token using the following syntax:" -msgstr "" - -#: ../channels/emails.rst:108 -msgid "The ``|true`` tells Mautic to encode the value used, for example in URLs." -msgstr "" - -#: ../channels/emails.rst:111 -msgid "Date formats" -msgstr "" - -#: ../channels/emails.rst:113 -msgid "To use custom date fields in tokens, use the following format:" -msgstr "" - -#: ../channels/emails.rst:121 -msgid "The date outputs in a human-readable format, configured in the settings in your Global Configuration > System Settings under 'Default format for date only' and 'Default time only format'." -msgstr "" - -#: ../channels/emails.rst:124 -msgid "Contact replies" -msgstr "" - -#: ../channels/emails.rst:126 -msgid "To make use of monitoring replies from Contacts, you must have access to an IMAP server **other than Google or Yahoo** as they overwrite the return path, which prevents this feature from working." -msgstr "" - -#: ../channels/emails.rst:129 -msgid "To use the Monitored Email feature you must have the PHP IMAP extension enabled - most hosts already have this turned on." -msgstr "" - -#: ../channels/emails.rst:131 -msgid "Configure all Mautic sender/reply Email addresses to send a copy to one single inbox - most Email providers support this feature in their configuration panel." -msgstr "" - -#: ../channels/emails.rst:134 -msgid "It's best to create an Email address specifically for this purpose, as Mautic reads each message it finds in the given folder." -msgstr "" - -#: ../channels/emails.rst:136 -msgid "Go to the Mautic configuration and set up the inbox to monitor replies." -msgstr "" - -#: ../channels/emails.rst:None -#: ../channels/emails.rst:None -msgid "Screenshot showing IMAP mailbox setting for reply monitoring" -msgstr "" - -#: ../channels/emails.rst:142 -msgid "To fetch and process the replies, run the following cron command:" -msgstr "" - -#: ../channels/emails.rst:144 -msgid "``php path/to/mautic/bin/console mautic:email:fetch``" -msgstr "" - -#: ../channels/emails.rst:147 -msgid "Usage" -msgstr "" - -#: ../channels/emails.rst:148 -msgid "Contact replies within Campaigns function as decision after an Email Send action, to take further action based on whether the Contact has replied to the Email. Mautic tries to read the inbox, parse messages, and find replies from the specified Contact. The Contact, when matched with an incoming reply, proceeds down the positive path immediately after the reply detection." -msgstr "" - -#: ../channels/emails.rst:None -msgid "Screenshot showing Contact replies Campaign action" -msgstr "" - -#: ../channels/emails.rst:158 -msgid "Mailer as Owner" -msgstr "" - -#: ../channels/emails.rst:162 -msgid "This feature allows Mautic to automatically personalize Emails sent to a Contact who has an owner (Mautic User) assigned to them. This feature changes the from Email, from name and signature by changing the default setting to the Mautic Contact owner's User setting." -msgstr "" - -#: ../channels/emails.rst:167 -msgid "Sending from the Contact owner" -msgstr "" - -#: ../channels/emails.rst:171 -msgid "Open the Admin menu by clicking the cog icon in the top right corner." -msgstr "" - -#: ../channels/emails.rst:172 -msgid "Select the Configuration menu item." -msgstr "" - -#: ../channels/emails.rst:173 -msgid "Select the Email Settings tab." -msgstr "" - -#: ../channels/emails.rst:174 -msgid "Switch the Mailer is owner to Yes." -msgstr "" - -#: ../channels/emails.rst:175 -msgid "Save the configuration." -msgstr "" - -#: ../channels/emails.rst:178 -msgid "Overriding the mailer as owner setting" -msgstr "" - -#: ../channels/emails.rst:179 -msgid "It's possible to override the global setting on a per-Email basis." -msgstr "" - -#: ../channels/emails.rst:181 -msgid "There is a switch under the advanced settings of the Email, which allows you to decide whether to take the global mailer as owner setting, or the specified from address, into account." -msgstr "" - -#: ../channels/emails.rst:None -msgid "Screenshot showing mailer as owner switch" -msgstr "" - -#: ../channels/emails.rst:187 -msgid "If set to Yes, the global setting takes precedence." -msgstr "" - -#: ../channels/emails.rst:189 -msgid "If set to No, Mautic uses the address and name supplied in the Email 'From' fields." -msgstr "" - -#: ../channels/emails.rst:192 -msgid "Signatures" -msgstr "" - -#: ../channels/emails.rst:194 -msgid "Setting a signature happens in two places:" -msgstr "" - -#: ../channels/emails.rst:196 -msgid "The default signature is in the Configuration > Email Settings tab. The default text is" -msgstr "" - -#: ../channels/emails.rst:202 -msgid "Mautic replaces the ``|FROM_NAME|`` token with the name which is also defined in the Email Settings tab." -msgstr "" - -#: ../channels/emails.rst:204 -msgid "Mautic uses this signature by default if the Contact doesn't have an owner assigned." -msgstr "" - -#: ../channels/emails.rst:206 -msgid "Every Mautic User can configure their own signature in their account settings. Mautic uses this signature by default if the Contact has an owner assigned to them." -msgstr "" - -#: ../channels/emails.rst:209 -msgid "There are some exceptions where the Contact owner's signature isn't used, which is when a User sends an Email directly from a Contact's profile. In this case, Mautic uses the currently logged in User's signature, with the from name and Email specified in the Email send Form, and not the Contact owner. The values used are pre-filled with those of the currently logged in Mautic User." -msgstr "" - -#: ../channels/emails.rst:211 -msgid "It doesn't matter if the Contact has another owner assigned or if it doesn't have an owner at all." -msgstr "" - -#: ../channels/emails.rst:213 -msgid "Also, when sending a test Email this is also the case." -msgstr "" - -#: ../channels/emails.rst:219 -msgid "Using the Email signature" -msgstr "" - -#: ../channels/emails.rst:223 -msgid "Marketers can place the signature into an Email using the ``{signature}`` token." -msgstr "" - -#: ../channels/emails.rst:226 -msgid "Email delivery" -msgstr "" - -#: ../channels/emails.rst:228 -msgid "As Mautic uses the :xref:`Symfony Mailer` library since v5, it supports all Symfony Mailer core plugins out of the box. Transports for other Email services might be found on GitHub or Packagist." -msgstr "" - -#: ../channels/emails.rst:231 -msgid "SMTP transport" -msgstr "" - -#: ../channels/emails.rst:233 -msgid "The SMTP transport is the default transport used for sending Emails with Mautic. It's configured in the Mautic configuration under the Email Settings tab. The configuration is the same as in the :xref:`Symfony Mailer` documentation." -msgstr "" - -#: ../channels/emails.rst:235 -msgid "Mautic now uses a specific way of providing the connection details for Email transports to interpret, which is called a Data Source Name, or DSN. This is the example Data Source Name configuration mentioned in the :xref:`Symfony Mailer` documentation for SMTP:" -msgstr "" - -#: ../channels/emails.rst:241 -msgid "Mautic creates this automatically from the values entered in the Email configuration:" -msgstr "" - -#: ../channels/emails.rst:None -msgid "SMTP API DSN example" -msgstr "" - -#: ../channels/emails.rst:247 -msgid "Example DSN ``smtp://user:pass@smtp.example.com:port/path?option1=value1&option2=value2`` explained" -msgstr "" - -#: ../channels/emails.rst:252 -msgid "DSN part" -msgstr "" - -#: ../channels/emails.rst:253 -msgid "Example" -msgstr "" - -#: ../channels/emails.rst:254 -msgid "Explanation" -msgstr "" - -#: ../channels/emails.rst:255 -msgid "Scheme" -msgstr "" - -#: ../channels/emails.rst:256 -msgid "smtp" -msgstr "" - -#: ../channels/emails.rst:257 -msgid "Defines which email transport (plugin) will handle the email sending. It also defines which other DSN parts must be present." -msgstr "" - -#: ../channels/emails.rst:258 -msgid "User" -msgstr "" - -#: ../channels/emails.rst:259 -msgid "john" -msgstr "" - -#: ../channels/emails.rst:260 -msgid "Some transport wants username and password to authenticate the connection. Some public or private key. Some just API key." -msgstr "" - -#: ../channels/emails.rst:261 -msgid "Password" -msgstr "" - -#: ../channels/emails.rst:262 -msgid "pa$$word" -msgstr "" - -#: ../channels/emails.rst:263 -msgid "As mentioned above, read documentation for your particular transport and fill in the fields that are required. For SMPT this is for password." -msgstr "" - -#: ../channels/emails.rst:264 -msgid "Host" -msgstr "" - -#: ../channels/emails.rst:265 -msgid "smtp.mydomain.com" -msgstr "" - -#: ../channels/emails.rst:266 -msgid "For SMTP this is the domain name where your SMTP server is running. Other transports may have the domain handled inside it so many wants to put just ``default`` text here." -msgstr "" - -#: ../channels/emails.rst:267 -msgid "Path" -msgstr "" - -#: ../channels/emails.rst:268 -msgid "any/path" -msgstr "" - -#: ../channels/emails.rst:269 -msgid "This is usually empty. For SMTP this may be the path to the SMTP server. For other transports this may be the path to the API endpoint." -msgstr "" - -#: ../channels/emails.rst:270 -msgid "Port" -msgstr "" - -#: ../channels/emails.rst:271 -msgid "465" -msgstr "" - -#: ../channels/emails.rst:272 -msgid "Important for SMTP. The port value defines which encryption is used. This is usually 465 for SSL or 587 for TLS. Avoid using port 25 for security reasons. For other transports this may be the port to the API endpoint." -msgstr "" - -#: ../channels/emails.rst:273 -msgid "Options" -msgstr "" - -#: ../channels/emails.rst:274 -msgid "timeout=10" -msgstr "" - -#: ../channels/emails.rst:275 -msgid "This is optional. This may be the timeout for the connection or similar configuration. The config form will allow you to create multiple options." -msgstr "" - -#: ../channels/emails.rst:278 -msgid "Use the Mautic's global configuration to paste in the DSN information, especially the API keys and passwords. The values must be URL-encoded, and the configuration form does that for you. If you are pasting DSN settings directly into the config/local.php file, you must URL-encode the values yourself." -msgstr "" - -#: ../channels/emails.rst:283 -msgid "Example API transport installation" -msgstr "" - -#: ../channels/emails.rst:291 -msgid "If you want to use :xref:`Sendgrid` API instead of SMTP to send Emails, for example, you can install the official Symfony Sendgrid Transport by running the following command that is mentioned along others in the :xref:`Symfony Mailer` documentation." -msgstr "" - -#: ../channels/emails.rst:297 -msgid "After that, you can configure the transport in the Mautic configuration. The example DSN is again mentioned in the :xref:`Symfony Mailer` documentation along with other transports. In the example of using the Sendgrid API, the DSN looks like this:" -msgstr "" - -#: ../channels/emails.rst:303 -msgid "This is how it would be set up in Mautic's Email configuration:" -msgstr "" - -#: ../channels/emails.rst:0 -msgid "Sendgrid API DSN example" -msgstr "" - -#: ../channels/emails.rst:309 -msgid "To replace the Sendgrid API key, add it to the relevant field in the Email configuration and save. Mautic now uses the Sendgrid API to send Emails." -msgstr "" - -#: ../channels/emails.rst:312 -msgid "It's a nice perk that Mautic can use any transport provided by Symfony Mailer. However, be aware that such transports (from Symfony) don't support batch sending, even via API. They only send one email per request, as opposed to a thousand emails per request as is the case with some Mautic transports, which can make them slow at scale. They also don't support transport callback handling used for bounce management. If you plan to send larger volumes of Emails or need to use features which require callback handling, please consider using Email transports built specifically for such use. These plugins are available in the :doc:`Mautic Marketplace `." -msgstr "" - -#: ../channels/emails.rst:314 -msgid "The system can either send Emails immediately or queue them for processing in batches by a :doc:`cron job `." -msgstr "" - -#: ../channels/emails.rst:317 -msgid "Immediate delivery" -msgstr "" - -#: ../channels/emails.rst:319 -msgid "This is the default means of delivery. As soon as an action in Mautic triggers an Email to send, it's sent immediately. If you expect to send a large number of Emails, you should use the queue. Sending Email immediately may slow the response time of Mautic if using a remote mail service, since Mautic has to establish a connection with that service before sending the mail. Also attempting to send large batches of Emails at once may hit your server's resource limits or Email sending limits if on a shared host." -msgstr "" - -#: ../channels/emails.rst:322 -msgid "Queued delivery" -msgstr "" - -#: ../channels/emails.rst:324 -msgid "Mautic works most effectively with high send volumes if you use the queued delivery method. Mautic stores the Email in the configured spool directory until the execution of the command to process the queue. Set up a :doc:`cron job ` at the desired interval to run the command:" -msgstr "" - -#: ../channels/emails.rst:330 -msgid "Some hosts may have limits on the number of Emails sent during a specified time frame and/or limit the execution time of a script. If that's the case for you, or if you just want to moderate batch processing, you can configure batch numbers and time limits in Mautic's Configuration. See the :doc:`cron job documentation ` for more specifics." -msgstr "" - -#: ../channels/emails.rst:335 -msgid "Tracking Opened Emails" -msgstr "" - -#: ../channels/emails.rst:339 -msgid "Mautic automatically tags each Email with a tracking pixel image. This allows Mautic to track when a Contact opens the Email and execute actions accordingly. Note that there are limitations to this technology - the Contact's Email client supporting HTML and auto-loading of images, and not blocking the loading of pixels. If the Email client doesn't load the image, there's no way for Mautic to know the opened status of the Email." -msgstr "" - -#: ../channels/emails.rst:341 -msgid "By default, Mautic adds the tracking pixel image at the end of the message, just before the ```` tag. If needed, one could use the ``{tracking_pixel}`` variable within the body content token to have it placed elsewhere. Beware that you shouldn't insert this directly after the opening ```` because this prevents correct display of pre-header text on some Email clients." -msgstr "" - -#: ../channels/emails.rst:343 -msgid "It's possible to turn off the tracking pixel entirely if you don't need to use it, in the Global Settings." -msgstr "" - -#: ../channels/emails.rst:348 -msgid "Tracking links in Emails" -msgstr "" - -#: ../channels/emails.rst:352 -msgid "Mautic tracks clicks of each link in an Email, with the stats displayed at the bottom of each Email detail view under the Click Counts tab." -msgstr "" - -#: ../channels/emails.rst:355 -msgid "Unsubscribing" -msgstr "" - -#: ../channels/emails.rst:357 -msgid "Mautic has a built in means of allowing a Contact to unsubscribe from Email communication. You can insert the tokens ``{unsubscribe_text}`` or ``{unsubscribe_url}`` into your Email to have the text or the URL show at your desired location. The unsubscribe text token inserts a sentence with a link instructing the Contact to click to unsubscribe." -msgstr "" - -#: ../channels/emails.rst:359 -msgid "The unsubscribe URL token inserts the URL into your custom written instructions." -msgstr "" - -#: ../channels/emails.rst:361 -#: ../channels/emails.rst:374 -msgid "For example:" -msgstr "" - -#: ../channels/emails.rst:367 -msgid "You can find the configuration of the unsubscribe text in the global settings." -msgstr "" - -#: ../channels/emails.rst:370 -msgid "Online version" -msgstr "" - -#: ../channels/emails.rst:372 -msgid "Mautic also enables the hosting of an online version of the Email sent. To use that feature, simply add the following as URL on text to generate the online version link ``{webview_url}``." -msgstr "" - -#: ../channels/emails.rst:381 -msgid "Bounce management" -msgstr "" - -#: ../channels/emails.rst:383 -msgid "Mautic provides a feature which allows monitoring of IMAP accounts to detect bounced Emails and unsubscribe requests." -msgstr "" - -#: ../channels/emails.rst:385 -msgid "Note that Mautic makes use of \"append\" Email addresses. The return-path or the list-unsubscribe header uses something like ``youraddress+bounce_abc123@example.com``. The bounce or unsubscribe allows Mautic to determine what type of Email it's when it examines the inbox through IMAP. The ``abc123`` gives Mautic information about the Email itself, for example which Contact it was it sent to, what Mautic Email address it originated from, etc." -msgstr "" - -#: ../channels/emails.rst:387 -msgid "Some Email services overwrite the return-path header with that of the account's Email (GMail, Amazon SES). In these cases, IMAP bounce monitoring won't work." -msgstr "" - -#: ../channels/emails.rst:389 -msgid "Elastic Email, SparkPost, Mandrill, Mailjet, SendGrid and Amazon SES support Webhook callbacks for bounce management. See below for more details." -msgstr "" - -#: ../channels/emails.rst:394 -msgid "Monitored inbox configuration" -msgstr "" - -#: ../channels/emails.rst:398 -msgid "To use the Monitored Email feature you must have the PHP IMAP extension enabled (most shared hosts already have this turned on). Go to the Mautic configuration and fill in the account details for the inbox(es) you wish to monitor." -msgstr "" - -#: ../channels/emails.rst:404 -msgid "It's possible to use a single inbox, or to configure a unique inbox per monitor." -msgstr "" - -#: ../channels/emails.rst:406 -msgid "To fetch and process the messages, run the following command:" -msgstr "" - -#: ../channels/emails.rst:412 -msgid "Note that it's best to create an Email address specifically for this purpose, as Mautic reads each message it finds in the given folder." -msgstr "" - -#: ../channels/emails.rst:414 -msgid "If sending mail through GMail, the Return Path of the Email is automatically rewritten as the GMail address. It's best to use a sending method other than GMail, although Mautic can monitor a GMail account for bounces." -msgstr "" - -#: ../channels/emails.rst:416 -msgid "If you select an Unsubscribe folder, Mautic also appends the Email as part of the \"List-Unsubscribe\" header. It then parses messages it finds in that folder and automatically unsubscribe the Contact." -msgstr "" - -#: ../channels/emails.rst:419 -msgid "Webhook bounce management" -msgstr "" - -#: ../channels/emails.rst:421 -msgid "Since Mautic 5 all the Email transports use the same Webhook (sometimes called callback) URL: ``https://mautic.example.com/mailer/callback``. Please follow the documentation for the specific Email transport you've installed to get more information about the Webhook configuration." -msgstr "" - -#: ../channels/emails.rst:427 -msgid "Create a Segment with bounced Emails" -msgstr "" - -#: ../channels/emails.rst:431 -msgid "This isn't required, but if you want to be able to select the Contacts with bounced Emails easily - for example to delete all bounced Contacts - create a Segment with bounced Emails." -msgstr "" - -#: ../channels/emails.rst:433 -msgid "Go to Segments > New." -msgstr "" - -#: ../channels/emails.rst:434 -msgid "Type in the Segment name. For example Bounced Emails." -msgstr "" - -#: ../channels/emails.rst:435 -msgid "Select the Filters tab." -msgstr "" - -#: ../channels/emails.rst:436 -msgid "Create new Bounced Email equals Yes filter." -msgstr "" - -#: ../channels/emails.rst:437 -msgid "Wait for the ``bin/console mautic:segments:update`` command to be automatically triggered by a cron job or execute it manually." -msgstr "" - -#: ../channels/emails.rst:438 -msgid "All Contacts with bounced Emails should appear in this Segment." -msgstr "" - -#: ../channels/emails.rst:443 -msgid "Troubleshooting Emails" -msgstr "" - -#: ../channels/emails.rst:448 -msgid "Email open tracking" -msgstr "" - -#: ../channels/emails.rst:450 -msgid "Mautic tracks Email opens using a tracking pixel. This is a 1 pixel GIF image in the source code of Email messages sent by Mautic." -msgstr "" - -#: ../channels/emails.rst:452 -msgid "When a Contact opens an Email using an Email client like Outlook, Thunderbird, or GMail, the client tries to load the images in it. The image load request is what Mautic uses to track the Email open action." -msgstr "" - -#: ../channels/emails.rst:454 -msgid "Some Email clients have auto loading images turned off, and Contacts have to selectively \"Load Images\" inside an Email message. Some automatically open all images before delivering the Email to the Contact." -msgstr "" - -#: ../channels/emails.rst:456 -msgid "If the images aren't loaded for this reason or another, or if they're opened automatically before sending the Email on to the Contact, Mautic doesn't know about the open action. Therefore, Email open tracking isn't very accurate." -msgstr "" - -#: ../channels/emails.rst:459 -msgid "Email link tracking" -msgstr "" - -#: ../channels/emails.rst:461 -msgid "Before sending an Email, Mautic replaces all links in the Email with links back to Mautic including a unique key. If the Contact clicks on such a link, the link redirects the Contact to Mautic, which then tracks the click action and redirects the Contact to the original location. It's fast, so the Contact doesn't usually notice the additional redirect." -msgstr "" - -#: ../channels/emails.rst:463 -msgid "If the Email click doesn't get tracked, make sure that:" -msgstr "" - -#: ../channels/emails.rst:465 -msgid "Your Mautic server is on an accessible URL." -msgstr "" - -#: ../channels/emails.rst:466 -msgid "You sent it to an existing Contact via a Campaign or a Segment Email. Emails sent by the Send Example link, direct Email from the Contact profile, or Form submission preview Emails won't replace links with trackable links." -msgstr "" - -#: ../channels/emails.rst:467 -msgid "Make sure the URL in the href attribute is absolute and valid. It should start with ``http://`` or ideally ``https://``." -msgstr "" - -#: ../channels/emails.rst:468 -msgid "You've opened the link in a incognito browser (not in the same session where you're logged into Mautic)" -msgstr "" - -#: ../channels/emails.rst:469 -msgid "Check if Mautic replaced the link in the Email with a tracking link." -msgstr "" - -#: ../channels/emails.rst:472 -msgid "Unsubscribe link doesn't work" -msgstr "" - -#: ../channels/emails.rst:473 -msgid "The unsubscribe link **doesn't work in test Emails**." -msgstr "" - -#: ../channels/emails.rst:475 -msgid "This is because Mautic sends test Emails to a Mautic User and not to a Mautic Contact." -msgstr "" - -#: ../channels/emails.rst:477 -msgid "Mautic Users can't unsubscribe and therefore the unsubscribe link looks like this: ``https://mautic.example.com/|URL|``. However, the link **does** work correctly when you send the Email to a Contact." -msgstr "" - -#: ../channels/emails.rst:479 -msgid "Best practice is to create a Segment with a small number of Contacts to receive test Emails - for example, yourself - which ensures that you can fully test features such as unsubscribe behaviour." -msgstr "" - -#: ../channels/focus_items.rst:2 -msgid "Focus Items" -msgstr "" - -#: ../channels/focus_items.rst:4 -msgid "Focus items allow you to engage Users on your site through bars, modals, notifications, popups, and light boxes. It's possible to initiate Focus Items at different times and with different actions such as exit intent." -msgstr "" - -#: ../channels/focus_items.rst:6 -msgid "You can find Focus Items listed under the Channels menu." -msgstr "" - -#: ../channels/focus_items.rst:9 -msgid "Focus Item settings" -msgstr "" - -#: ../channels/focus_items.rst:10 -msgid "There are several different types of Focus Items, and many ways to configure them to deliver your strategic marketing goals." -msgstr "" - -#: ../channels/focus_items.rst:13 -msgid "Types of Focus Item" -msgstr "" - -#: ../channels/focus_items.rst:15 -msgid "There are three different types of Focus Item that you can create within Mautic. These allow you to achieve different marketing goals with your Focus Items. Select the appropriate option for your needs." -msgstr "" - -#: ../channels/focus_items.rst:0 -msgid "Screenshot showing the types of Focus Items." -msgstr "" - -#: ../channels/focus_items.rst:21 -msgid "**Collect Data** - This option presents a Form - which must already exist - within the Focus Item. This allows you to gather more information about your website visitors. Mautic considers a successful conversion on this type of Focus Item when there is a submission of this Form. This option is great for capturing simple information - for example a newsletter registration Form." -msgstr "" - -#: ../channels/focus_items.rst:22 -msgid "**Display a Notice** - This option presents a message to your visitors. There is no option for detecting a conversion with this type of Focus Item. This option is great for announcements and important messages." -msgstr "" - -#: ../channels/focus_items.rst:23 -msgid "**Emphasize a link** - This option allows you to drive visitors to a specific link which might be a resource on your website, a Mautic Landing Page, or any other web-based resource. Mautic considers a link click to be a successful conversion with this Focus Item. This option is great for Landing Pages to highlight a promotion or a sale - it displays a button to click which directs the visitor to a given link." -msgstr "" - -#: ../channels/focus_items.rst:26 -msgid "Engagement options" -msgstr "" - -#: ../channels/focus_items.rst:28 -msgid "For each type of Focus Item, there are settings to configure which control the triggering of the Focus Item, and how they interact with the visitor." -msgstr "" - -#: ../channels/focus_items.rst:0 -msgid "Screenshot showing the engagement settings for Focus Items." -msgstr "" - -#: ../channels/focus_items.rst:36 -msgid "**Animate** - When set to Yes, this applies a slide-in animation to the Focus Item. When set to No, the item appears without any kind of sliding motion." -msgstr "" - -#: ../channels/focus_items.rst:41 -msgid "**When to engage** - This setting controls the Focus Item shows. There are several options:" -msgstr "" - -#: ../channels/focus_items.rst:38 -msgid "**Upon arrival** - As soon as a visitor lands on the page" -msgstr "" - -#: ../channels/focus_items.rst:39 -msgid "**After slightly scrolling down** - Wait a little while until the visitor starts to scroll down the page" -msgstr "" - -#: ../channels/focus_items.rst:40 -msgid "**After scrolling to the middle** - Wait until the visitor scrolls to the middle of the page" -msgstr "" - -#: ../channels/focus_items.rst:41 -msgid "**After scrolling to the bottom** - Wait until the visitor scrolls right to the bottom of the page" -msgstr "" - -#: ../channels/focus_items.rst:42 -msgid "**Visitor intends to leave** - If the visitor's cursor moves over the address bar, or from the page to the tabs - for example to close the tab or open a new tab" -msgstr "" - -#: ../channels/focus_items.rst:43 -msgid "**Timeout before engage** - This option allows you to set the delay in seconds after reaching the option selected in **When to engage**. For example, if the setting is **Upon arrival** and **Timeout before engage** is 2 seconds, the Focus Item appears two seconds *after* the visitor lands on the page." -msgstr "" - -#: ../channels/focus_items.rst:49 -msgid "**How often to engage** - This option allows you to control how frequently the Focus Item displays to visitors. The options available include:" -msgstr "" - -#: ../channels/focus_items.rst:45 -msgid "**Every page** - Show on every page the visitors engages with on your website" -msgstr "" - -#: ../channels/focus_items.rst:46 -msgid "**Once per session** - Show once for each time that the visitor accesses your website" -msgstr "" - -#: ../channels/focus_items.rst:47 -msgid "**Every 2 minutes** - Show the Focus Item every two minutes that the visitor is on your website" -msgstr "" - -#: ../channels/focus_items.rst:48 -msgid "**Every 15 minutes** - Show the Focus Item every 15 minutes that the visitor is on your website" -msgstr "" - -#: ../channels/focus_items.rst:49 -msgid "**Once per hour** - Show the Focus Item once every hour that the visitor is on your website" -msgstr "" - -#: ../channels/focus_items.rst:50 -msgid "**Once per day** - Show the Focus Item once per day that the visitor is on your website" -msgstr "" - -#: ../channels/focus_items.rst:51 -msgid "**Stop engaging after a conversion** - This option is only available for the types which track a conversion (Collect Data and Emphasize a Link). If set to Yes, the Focus Item no longer displays if the visitor has either submitted the Form (Collect Data type) or clicked on the link (Emphasize a Link type)." -msgstr "" - -#: ../channels/focus_items.rst:56 -msgid "Styles" -msgstr "" - -#: ../channels/focus_items.rst:58 -msgid "There are four styles to choose from when creating a Focus Item. Each style has different configuration options relevant to the layout they provide." -msgstr "" - -#: ../channels/focus_items.rst:0 -msgid "Screenshot showing the styles for Focus Items." -msgstr "" - -#: ../channels/focus_items.rst:65 -msgid "Bar" -msgstr "" - -#: ../channels/focus_items.rst:66 -msgid "The Bar style creates a line across the top or bottom of the page, which includes the content of your Focus Item." -msgstr "" - -#: ../channels/focus_items.rst:68 -msgid "**Allow hide** - when set to Yes, website visitors have a small arrow to hide the bar. The arrow shows on the right hand side of the bar. Once clicked, the bar shrinks to hide the content but the arrow is still be visible in case they want to maximise it again with a single click. If set to No, the visitor can't hide the bar." -msgstr "" - -#: ../channels/focus_items.rst:69 -msgid "**Push page down** - This option allows the bar to push the page content up or down under the bar if set to Yes. If set to No, the bar covers the content at the top or bottom of the page depending on placement setting." -msgstr "" - -#: ../channels/focus_items.rst:70 -msgid "**Make sticky** - If set to Yes, the bar stays anchored in position even when the visitor scrolls the page. If set to No, the bar won't anchored and disappears as the visitor scrolls the page, and re-appears as they reverse the scroll." -msgstr "" - -#: ../channels/focus_items.rst:71 -msgid "**Placement** - This option allows you to display the bar at the top or the bottom of the page." -msgstr "" - -#: ../channels/focus_items.rst:74 -msgid "**Size** - This option allows you to specify the thickness of the bar, and the font size. The options include:" -msgstr "" - -#: ../channels/focus_items.rst:73 -msgid "**Large** - 50px height and 17pt font" -msgstr "" - -#: ../channels/focus_items.rst:74 -msgid "**Regular** - 30px height and 14pt font" -msgstr "" - -#: ../channels/focus_items.rst:77 -msgid "Modal" -msgstr "" - -#: ../channels/focus_items.rst:78 -msgid "The Modal style is probably the most popular style, and is often referred to as a pop-up or a light box." -msgstr "" - -#: ../channels/focus_items.rst:80 -msgid "Modals are small boxes which appear aligned horizontally centred on the page. The content behind the pop-up darkens when the Focus Item is active, which helps to draw attention - focus - to the pop-up." -msgstr "" - -#: ../channels/focus_items.rst:82 -msgid "**Placement** - This option allows you to select whether you would like the Modal to appear at the top, middle or bottom of the page." -msgstr "" - -#: ../channels/focus_items.rst:85 -msgid "Notification" -msgstr "" - -#: ../channels/focus_items.rst:87 -msgid "The Notification style is a small box which appears, sometimes referred to as a pop-up. Unlike with the Modal style, the pop-up shows in one of the four corners of the page, and the main content underneath the notification isn't darkened out behind the pop-up." -msgstr "" - -#: ../channels/focus_items.rst:89 -msgid "Visitors can choose to close this type of Focus Item with the *X* button in the top right corner of the notification." -msgstr "" - -#: ../channels/focus_items.rst:91 -msgid "**Placement** - This option allows you to select the corner to display the notification." -msgstr "" - -#: ../channels/focus_items.rst:94 -msgid "Full page" -msgstr "" - -#: ../channels/focus_items.rst:96 -msgid "The full page Focus Item completely takes over the whole page, hiding the rest of the page content until the visitor clicks the *X* button in the top right hand corner of the Focus Item." -msgstr "" - -#: ../channels/focus_items.rst:98 -msgid "There are no additional configuration options for this style of Focus Item." -msgstr "" - -#: ../channels/focus_items.rst:101 -msgid "Colors" -msgstr "" - -#: ../channels/focus_items.rst:103 -msgid "By default, Mautic determines the top colors extracted from the snapshot. Four colors are currently supported. You can customize colors by using the color picker or entering a hex code." -msgstr "" - -#: ../channels/focus_items.rst:105 -msgid "**Primary color** - For the Bar style, the primary color is the background color of the bar - For the Modal, Notification and full page styles, the primary color is the outline around the Focus Item with a thicker line on top than on the other three sides." -msgstr "" - -#: ../channels/focus_items.rst:108 -msgid "**Text color** - The color of the headline text entered in the Content section of the Focus Item editor" -msgstr "" - -#: ../channels/focus_items.rst:109 -msgid "**Button color** - The background color for the button on the Collect Data and Emphasize Link Focus Item types. This option isn't available for the Display a notice Focus Item type." -msgstr "" - -#: ../channels/focus_items.rst:110 -msgid "**Button text color** - The color for the button text on the Collect Data and Emphasize Link Focus Item types. This option isn't available for the Display Notice Focus Item type." -msgstr "" - -#: ../channels/focus_items.rst:113 -msgid "Content" -msgstr "" - -#: ../channels/focus_items.rst:114 -msgid "There are three editing modes to choose from when customizing Focus Items." -msgstr "" - -#: ../channels/focus_items.rst:0 -msgid "Screenshot showing the content options for creating Focus Items." -msgstr "" - -#: ../channels/focus_items.rst:121 -msgid "Basic" -msgstr "" - -#: ../channels/focus_items.rst:122 -msgid "This editor mode allows a simplified experience with a few fields - depending on the Focus Item type - with the content being automatically rendered on the Focus Item as it's created." -msgstr "" - -#: ../channels/focus_items.rst:124 -msgid "**Headline** - This is the main text used on the Focus Item. The aim is to capture the visitor's interest and attention." -msgstr "" - -#: ../channels/focus_items.rst:125 -msgid "**Tagline** - This option is only available for Emphasize a Link Focus Item types. It allows you to provide a second line of text to add more incentive for the visitor to click the link. This field is optional." -msgstr "" - -#: ../channels/focus_items.rst:126 -msgid "**Font** - This option allows you to select from available fonts used in the Focus Item. The font list isn't customizable." -msgstr "" - -#: ../channels/focus_items.rst:127 -msgid "**Select the Form to insert** - This option is only available for Collect Data Focus Item types. It allows you to select an existing Mautic Form to use with the Focus Item. For styling and formatting reasons, you may want to create a Form specifically for the Focus Item, adding styling attributes to the Attributes tab on the Form fields." -msgstr "" - -#: ../channels/focus_items.rst:128 -msgid "**Link text** - This option is only available for Emphasize a Link Focus Item types. It allows you to specify the text used on the Focus Item's button." -msgstr "" - -#: ../channels/focus_items.rst:129 -msgid "**Link URL** - This option is only available for Emphasize a Link Focus Item types. It allows you to specify the URL where you'd like to drive visitors with the Focus Item." -msgstr "" - -#: ../channels/focus_items.rst:130 -msgid "**Open in a new window** - This option is only available for Emphasize a Link Focus Item types. If set to Yes, this ensures that the link is opened in a new window. If set to No, the link opens in the current tab." -msgstr "" - -#: ../channels/focus_items.rst:133 -msgid "Editor" -msgstr "" - -#: ../channels/focus_items.rst:134 -msgid "This allows the User to edit the content with the global editor available in Mautic." -msgstr "" - -#: ../channels/focus_items.rst:137 -msgid "HTML" -msgstr "" - -#: ../channels/focus_items.rst:138 -msgid "This allows the User to enter HTML into a blank field for a fully customized Focus Item." -msgstr "" - -#: ../channels/focus_items.rst:141 -msgid "If you decide to switch editing styles, ensure that you clear the data from the previous style, otherwise Mautic may not display the final intended content." -msgstr "" - -#: ../channels/focus_items.rst:145 -msgid "Creating a Focus Item" -msgstr "" - -#: ../channels/focus_items.rst:147 -msgid "To create a new Focus Item, go to Channels > Focus Items and click the New button." -msgstr "" - -#: ../channels/focus_items.rst:150 -msgid "Some websites won't allow the preview to display. For the preview to work, the site must use an SSL certificate, and it must not block iframe previews with the ``x-frame-options: SAMEORIGIN`` header. An error will be displayed in the Focus Item builder if these conditions are not met." -msgstr "" - -#: ../channels/focus_items.rst:152 -msgid "When creating a new Focus Item, you can set the following fields:" -msgstr "" - -#: ../channels/focus_items.rst:154 -msgid "**Name** - A name used internally to identify the Focus Item" -msgstr "" - -#: ../channels/focus_items.rst:156 -msgid "**Website** - A website you would like to use to preview the Focus Item as you are building it - see preceding note, some websites won't allow this feature. If this is a problem, leave the URL field blank." -msgstr "" - -#: ../channels/focus_items.rst:158 -msgid "**Category** - Assign a Category to help you organize your Focus Items." -msgstr "" - -#: ../channels/focus_items.rst:160 -msgid "**Published** - Whether the Focus Item is available for use - published - or not available - unpublished" -msgstr "" - -#: ../channels/focus_items.rst:164 -#: ../channels/sms.rst:113 -msgid "**Publish at (date/time)** - This allows you to define the date and time at which this Text Message is available for sending to Contacts" -msgstr "" - -#: ../channels/focus_items.rst:166 -#: ../channels/sms.rst:115 -msgid "**Unpublish at (date/time)** - This allows you to define the date and time at which this Text Message ceases to be available for sending to Contacts." -msgstr "" - -#: ../channels/focus_items.rst:170 -msgid "**Google Analytics UTM tags** - Mautic supports UTM tagging in Emails, Focus Items, and Landing Pages. Any UTM tags with values populated are automatically appended to the end of any links used in the focus item. See :doc:`/channels/utm_tags` for more information." -msgstr "" - -#: ../channels/focus_items.rst:0 -msgid "Screenshot showing the creation of a Focus Item." -msgstr "" - -#: ../channels/focus_items.rst:179 -msgid "Using the Focus Item builder" -msgstr "" - -#: ../channels/focus_items.rst:183 -msgid "After you specify the general information for the Focus Item, click the builder option in the top right corner. If you've specified a URL in the Website field on the details page, the system displays a preview. If you don't see a preview, the website might block iframe previews. Hence, you may need to add the focus item to a development or staging environment without these security restrictions - if available - to see the preview." -msgstr "" - -#: ../channels/focus_items.rst:186 -msgid "The preview of the website doesn't appear until you select a style from the options on the Focus Item Builder." -msgstr "" - -#: ../channels/focus_items.rst:0 -msgid "Screenshot showing the Focus Item Builder" -msgstr "" - -#: ../channels/focus_items.rst:192 -msgid "You can use the menu on the sidebar to configure the Focus Item to your liking. The preview area on the left allows you to see how it appears on your website. You can also use the mobile phone icon at the top right to switch to a responsive view. This is important to ensure that you aren't blocking key elements of the User Experience on mobile devices." -msgstr "" - -#: ../channels/focus_items.rst:0 -msgid "Screenshot showing the Focus Item Builder in responsive mode." -msgstr "" - -#: ../channels/focus_items.rst:199 -msgid "Using Focus Items" -msgstr "" - -#: ../channels/focus_items.rst:201 -msgid "Once you have created your Focus Item, you're ready to publish it to your website. If you're not quite ready for the Focus Item to go live but you need to get it set up on your website, you can set the Focus Item to Unpublished." -msgstr "" - -#: ../channels/focus_items.rst:204 -msgid "Deploying to a website" -msgstr "" - -#: ../channels/focus_items.rst:206 -msgid "When you save the Focus Item, the code snippet required to display it on your website is shown in a green box on the Focus Item overview." -msgstr "" - -#: ../channels/focus_items.rst:0 -msgid "Screenshot showing the Focus Item code to be embedded within a website." -msgstr "" - -#: ../channels/focus_items.rst:213 -msgid "You may need assistance from your web development team to implement the Focus Item tracking code on your website." -msgstr "" - -#: ../channels/focus_items.rst:215 -msgid "You must also ensure that you have specified your website's domain where you expect to use the Focus Item in the CORS settings for your Mautic instance, otherwise it won't appear. To verify this, go to Settings > Configuration > System Settings > CORS Settings and set Restricted Domains to Yes. Ensure that you specify your domain in the relevant field. Alternatively (but not recommended, as this would allow other websites to display your Focus Items), set Restrict Domains to No and don't specify your domains." -msgstr "" - -#: ../channels/focus_items.rst:220 -msgid "Deploying through a Campaign" -msgstr "" - -#: ../channels/focus_items.rst:224 -msgid "It's possible to trigger a Focus Item to appear as part of a Campaign workflow. This doesn't require you to paste the Focus Item code onto your website as it's delivered through the existing Mautic Tracking Code." -msgstr "" - -#: ../channels/focus_items.rst:226 -msgid "Within the Campaign, add a decision for ``Visits a Page``, and then select the Action of ``Show Focus Item``. Note that you must precede it by ``Visits a Page`` to trigger the Focus Item." -msgstr "" - -#: ../channels/focus_items.rst:229 -msgid "Sometimes the Campaign Action can be unreliable and it's dependent on your Campaign steps, so it's recommended to use the direct embedding method in most cases." -msgstr "" - -#: ../channels/focus_items.rst:232 -msgid "Measuring success" -msgstr "" - -#: ../channels/focus_items.rst:234 -msgid "When using the Emphasize a Link type, Mautic displays the link on the Focus Item overview where you can view the number of unique clicks." -msgstr "" - -#: ../channels/focus_items.rst:236 -msgid "If you change the link in a Focus Item after deployment, all links are listed in the overview." -msgstr "" - -#: ../channels/focus_items.rst:238 -msgid "Additionally, Mautic applies UTM tags on Focus Items to both Form submissions and link clicks. If you are using a Focus Item to submit a Form, it's recommended that you have a Submit Action on the Form to record the UTM tags." -msgstr "" - -#: ../channels/marketing_messages.rst:2 -msgid "Marketing Messages" -msgstr "" - -#: ../channels/marketing_messages.rst:5 -msgid "What are Marketing Messages?" -msgstr "" - -#: ../channels/marketing_messages.rst:7 -msgid "Located under the Channels section in Mautic, Marketing Messages is one of the Channels available to you through which you can optimize and personalize communication with your customers." -msgstr "" - -#: ../channels/marketing_messages.rst:9 -msgid "Marketing messages allow you to empower the customer to decide how they prefer to receive the content you send, by setting the Channel they prefer." -msgstr "" - -#: ../channels/marketing_messages.rst:0 -msgid "Screenshot showing the Marketing Messages option in the main navigation menu of Mautic." -msgstr "" - -#: ../channels/marketing_messages.rst:15 -msgid "With Marketing Messages, you can create content and make it available through multiple Channels - Email, SMS, Browser Notification, Mobile Notification, Tweets, and any other Channel you decide to create using Mautic's extendable open architecture." -msgstr "" - -#: ../channels/marketing_messages.rst:17 -msgid "When using the 'Send Marketing Message' action in a Campaign, you can create the message in any or all of these Channels. If the Contact has a Channel preference set on their profile, Mautic sends the content on the preferred Channel. If they haven't specified a Channel, Mautic uses the default Channel - Email." -msgstr "" - -#: ../channels/marketing_messages.rst:19 -msgid "It's also possible for a Contact to specify their own frequency rules and pause communication all together on a Channel. When exceeding the defined limit and scheduling a Marketing Message, Mautic uses another Channel which has available frequency." -msgstr "" - -#: ../channels/marketing_messages.rst:24 -msgid "Creating a Marketing Message" -msgstr "" - -#: ../channels/marketing_messages.rst:28 -msgid "To create a new Marketing Message, navigate to the Channels section and click Marketing Messages. Click on New." -msgstr "" - -#: ../channels/marketing_messages.rst:30 -msgid "Provide a name and description for the Marketing Message, then choose the Channels you wish to use." -msgstr "" - -#: ../channels/marketing_messages.rst:33 -msgid "You must set up and configure the Channels before they become available - if you haven't set up Mobile Notifications or Text Messages, you won't see it as an option when creating a Marketing Message." -msgstr "" - -#: ../channels/marketing_messages.rst:0 -msgid "Screenshot showing the creation of a new Marketing Message in Mautic." -msgstr "" - -#: ../channels/marketing_messages.rst:39 -msgid "To enable a Channel, click Yes on the slider, and select - or create - the message." -msgstr "" - -#: ../channels/push_notifications.rst:2 -msgid "Mobile push notifications" -msgstr "" - -#: ../channels/push_notifications.rst:4 -msgid "Mobile notifications integrate your iOS and Android app with :xref:`OneSignal`. Using your own OneSignal account, you can now push a notification to your Contacts's mobile device - with their permission. Enable the Plugin in Mautic's Plugin manager to see Mobile Notifications listed under Channels in the menu." -msgstr "" - -#: ../channels/push_notifications.rst:6 -msgid "For more detailed information see the :xref:`OneSignal iOS` and :xref:`OneSignal Android` documentation." -msgstr "" - -#: ../channels/push_notifications.rst:9 -msgid "Setup" -msgstr "" - -#: ../channels/push_notifications.rst:14 -msgid "iOS code for OneSignal integration" -msgstr "" - -#: ../channels/push_notifications.rst:16 -msgid "To enable Push Notifications in your iOS app, add the following code - or a variant of it - inside your ``application`` func of ``AppDelegate``. The code examples below use Swift 3.1. Please modify them to your needs if you are using C#." -msgstr "" - -#: ../channels/push_notifications.rst:36 -msgid "For ease of use, we've created the following struct and func for sending user data to Mautic. Create this struct in your app, and import it where appropriate." -msgstr "" - -#: ../channels/push_notifications.rst:39 -msgid "UserData struct" -msgstr "" - -#: ../channels/push_notifications.rst:58 -msgid "pushUserDataToMautic func" -msgstr "" - -#: ../channels/push_notifications.rst:60 -msgid "This is a basic function for pushing the UserData struct to your Mautic installation. It will push the User data, and then display the response from Mautic as an app alert. Modify to meet the needs of your app." -msgstr "" - -#: ../channels/push_notifications.rst:94 -msgid "Notification statistics" -msgstr "" - -#: ../channels/push_notifications.rst:96 -msgid "In addition to the UserData that gets pushed to Mautic, you can push open / interaction stats to Mautic by sending the UserData struct, with an appended stat JSON key." -msgstr "" - -#: ../channels/sms.rst:2 -msgid "SMS Text messages" -msgstr "" - -#: ../channels/sms.rst:4 -msgid "With the SMS Channel it's possible to send text messages from Campaigns in Mautic." -msgstr "" - -#: ../channels/sms.rst:7 -msgid "To use this Channel you must first set up an SMS transport, such as :doc:`/plugins/twilio`." -msgstr "" - -#: ../channels/sms.rst:12 -msgid "Type of Text Messages" -msgstr "" - -#: ../channels/sms.rst:16 -msgid "Mautic allows you to create two types of Text Messages, in the same way as you can create different types of Emails." -msgstr "" - -#: ../channels/sms.rst:21 -msgid "Template Text Messages" -msgstr "" - -#: ../channels/sms.rst:25 -msgid "A template Text Message is automatically sent by Campaigns, Forms, Point triggers etc. You can edit Template Text Messages after creation, but they can't manually send them to a Contact list." -msgstr "" - -#: ../channels/sms.rst:30 -msgid "Segment Text Messages" -msgstr "" - -#: ../channels/sms.rst:34 -msgid "A Segment Text Message can be manually sent to Contact lists - Segments - in Mautic. Once sent, you can't edit the Text Message, however you can send it to new Contacts as they join the associated Segment." -msgstr "" - -#: ../channels/sms.rst:36 -msgid "Note that these are marketing Text Messages by default, and each Contact can only receive the Text Message once - it's the same principle as a mailing list." -msgstr "" - -#: ../channels/sms.rst:38 -msgid "You must initiate the send of Segment Text Messages with the ``Send Scheduled Broadcast`` cron job. See :doc:`cron jobs documentation ` for more information." -msgstr "" - -#: ../channels/sms.rst:43 -msgid "Creating a Text Message" -msgstr "" - -#: ../channels/sms.rst:47 -msgid "To create a Text Message, navigate to Channels > Text Messages and click the 'New' button." -msgstr "" - -#: ../channels/sms.rst:0 -msgid "Screenshot showing create new SMS button" -msgstr "" - -#: ../channels/sms.rst:53 -msgid "Select whether you wish to create a Template or Segment Text Message, which presents the required fields." -msgstr "" - -#: ../channels/sms.rst:58 -msgid "Template Text Message fields" -msgstr "" - -#: ../channels/sms.rst:62 -#: ../channels/sms.rst:89 -msgid "The following fields are available:" -msgstr "" - -#: ../channels/sms.rst:0 -msgid "Screenshot showing the fields required for a new Template Text Message" -msgstr "" - -#: ../channels/sms.rst:68 -msgid "**Internal name** - This is the internal name used within Mautic when referring to this Text Message. For example Mautic uses this in dropdown selection lists in the Campaign Builder." -msgstr "" - -#: ../channels/sms.rst:72 -msgid "**Text Message** - This is the actual content of the Text Message which is sent to the Contact. There is a character count below the field which helps you to identify the required number of messages to send the full text. You may use tokens, such as ``{contactfield=firstname}``. To find the appropriate token, go to Settings > Custom Fields and use the field alias with the token format: {contactfield=fieldalias}." -msgstr "" - -#: ../channels/sms.rst:76 -#: ../channels/sms.rst:103 -msgid "**Category** - This allows you to select a Category to help you with organizing your Text Messages." -msgstr "" - -#: ../channels/sms.rst:78 -#: ../channels/sms.rst:105 -msgid "**Language** - This allows you to set the language of this Text Message." -msgstr "" - -#: ../channels/sms.rst:80 -#: ../channels/sms.rst:107 -msgid "**Published** - This allows you to set the published status of the Text Message. Unpublished Text Messages aren't sent." -msgstr "" - -#: ../channels/sms.rst:85 -msgid "Segment Text Message fields" -msgstr "" - -#: ../channels/sms.rst:0 -msgid "Screenshot showing the fields required for a new Segment Text Message" -msgstr "" - -#: ../channels/sms.rst:95 -msgid "**Internal name** - This is the internal name used within Mautic when referring to this Text Message. For example, Mautic uses this in dropdown selection lists in the Campaign Builder." -msgstr "" - -#: ../channels/sms.rst:99 -msgid "**Text Message** - This is the actual content of the Text Message sent to the Contact. There is a character count below the field which helps you to identify the required number of messages to send the full text. You may use tokens, such as ``{contactfield=firstname}``. To find the appropriate token, go to Settings > Custom Fields and use the field alias with the token format: {contactfield=fieldalias}." -msgstr "" - -#: ../channels/sms.rst:109 -msgid "**Contact Segment** - This allows you to define the Segment/s who should receive the Text Message." -msgstr "" - -#: ../channels/sms.rst:118 -msgid "Creating Text Messages from Campaign Builder" -msgstr "" - -#: ../channels/sms.rst:122 -msgid "It's also possible to create a Text Message from within the Campaign Builder. To do this, select the Campaign Action of Send Text Message and press the New Text Message button rather than selecting an existing Text Message in the dropdown." -msgstr "" - -#: ../channels/sms.rst:0 -msgid "Screenshot showing the option to create an SMS from a Campaign" -msgstr "" - -#: ../channels/sms.rst:128 -msgid "As you plan to use this Text Message within a Campaign, it's by default created as a Template Text Message and show the relevant fields accordingly." -msgstr "" - -#: ../channels/sms.rst:133 -msgid "Sending Text Messages as a Marketing Messages" -msgstr "" - -#: ../channels/sms.rst:137 -msgid "Mautic allows you to create a single message - for example 'Red shoes on offer today!' - in multiple Channels, and have it delivered through the Channel which the Contact prefers. This means that they only receive the message once, and through their preferred Channel. You can create the messages under the :doc:`/channels/marketing_messages` section." -msgstr "" - -#: ../channels/sms.rst:139 -msgid "If a Contact's preferred Channel is Text Messages, Mautic delivers the message through the Text Message Channel when a Marketing Message includes a Text Message." -msgstr "" - -#: ../channels/sms.rst:0 -msgid "Screenshot showing the option to send a Text Message as a Marketing Message" -msgstr "" - -#: ../channels/sms.rst:146 -msgid "Managing unsubscribes" -msgstr "" - -#: ../channels/sms.rst:149 -msgid "In order for Mautic to process Text Message replies for unsubscribes and replies to messages, you must first configure the Webhook. For more information review the :doc:`/plugins/twilio` documentation." -msgstr "" - -#: ../channels/sms.rst:151 -msgid "Contacts can unsubscribe from your Text Messages by replying with the word ``STOP``, or any of the accepted phrases (``STOP``, ``STOPALL``, ``UNSUBSCRIBE``, ``CANCEL``, ``END``, and ``QUIT``), to your SMS. Once Mautic receives this SMS, Mautic flags the specific Contact as 'Do Not Contact' (DNC) for the SMS Channel, and won't allow messages again via this Channel unless the Contact manually re-subscribes at a later date." -msgstr "" - -#: ../channels/sms.rst:153 -msgid "You can also view SMS replies in the Contact timeline:" -msgstr "" - -#: ../channels/sms.rst:0 -msgid "Screenshot showing the reply from SMS" -msgstr "" - -#: ../channels/sms.rst:162 -msgid "Working with replies to Text Messages" -msgstr "" - -#: ../channels/sms.rst:166 -msgid "In a Mautic Campaign, where Mautic has an active Text Message provider, there is a Campaign Action called 'Sends a Text Message' which allows you to monitor incoming replies for specific patterns and take action accordingly." -msgstr "" - -#: ../channels/sms.rst:0 -msgid "Screenshot showing the Campaign action 'Sends a Text Message'" -msgstr "" - -#: ../channels/sms.rst:172 -msgid "This decision tracks replies to your messages and looks for specified patterns within a message. This isn't dependent on you first sending the Contact a message." -msgstr "" - -#: ../channels/sms.rst:174 -msgid "For example, you can specify 'red' in 'Pattern the reply should match'. If your message contains language, such as reply from the Contact using the word 'Red' to a question of their favourite shoe colour, Mautic looks for incoming Text Messages with that pattern. In this example, you may add an action on the decision's Yes path for adding a colour preference to the Contact's profile." -msgstr "" - -#: ../channels/sms.rst:177 -msgid "Important notes" -msgstr "" - -#: ../channels/sms.rst:179 -msgid "Contact phone numbers should be in the format +XXXXXXX including the + and with no spaces" -msgstr "" - -#: ../channels/sms.rst:180 -msgid "There must be a phone number in the Mobile Phone Contact field" -msgstr "" - -#: ../channels/sms.rst:181 -msgid "When configuring the Twilio Plugin, the sender number must be in the format +XXXXXXX and this number associated with the Twilio account" -msgstr "" - -#: ../channels/social_monitoring.rst:4 -msgid "Social Monitoring" -msgstr "" - -#: ../channels/social_monitoring.rst:8 -msgid "It's possible to add Contacts to Mautic through monitoring Twitter for mentions and hashtags." -msgstr "" - -#: ../channels/social_monitoring.rst:11 -msgid "Requirements" -msgstr "" - -#: ../channels/social_monitoring.rst:13 -msgid "The :doc:`/plugins/twitter` plugin must be configured" -msgstr "" - -#: ../channels/social_monitoring.rst:14 -msgid "You must trigger the Social Monitoring :doc:`cron job ` periodically." -msgstr "" - -#: ../channels/social_monitoring.rst:19 -msgid "Creating a Social Monitor" -msgstr "" - -#: ../channels/social_monitoring.rst:23 -msgid "To create a new Social Monitor, go to Channels > Social Monitoring and click New." -msgstr "" - -#: ../channels/social_monitoring.rst:25 -msgid "Mautic offers two options when creating a Social Monitor:" -msgstr "" - -#: ../channels/social_monitoring.rst:27 -msgid "**Twitter mention** - Any time someone mentions a specified username, Mautic creates them as a Contact" -msgstr "" - -#: ../channels/social_monitoring.rst:28 -msgid "**Twitter hashtag** - Any time someone uses a specified hashtag in a tweet, Mautic creates them as a Contact." -msgstr "" - -#: ../channels/social_monitoring.rst:0 -msgid "Screenshot showing the creation of a new Social Monitor." -msgstr "" - -#: ../channels/social_monitoring.rst:35 -msgid "Social mentions" -msgstr "" - -#: ../channels/social_monitoring.rst:37 -msgid "When selecting the Twitter Mention monitoring method, the following fields are available:" -msgstr "" - -#: ../channels/social_monitoring.rst:39 -msgid "**Twitter mention** - The Twitter handle you want to track mentions of. Don't include the @ symbol - for example ``mauticcommunity``." -msgstr "" - -#: ../channels/social_monitoring.rst:40 -#: ../channels/social_monitoring.rst:67 -msgid "**Description** - A description to use internally within Mautic to tell the marketer what the monitor is tracking." -msgstr "" - -#: ../channels/social_monitoring.rst:41 -#: ../channels/social_monitoring.rst:68 -msgid "**Match Contact names** - If set to Yes, Mautic tries to match the names of Contacts created from Twitter and associate the Twitter account with their existing Contact record. If set to No, this won't happen and you are likely to experience duplicated Contacts." -msgstr "" - -#: ../channels/social_monitoring.rst:43 -#: ../channels/social_monitoring.rst:70 -msgid "There are also the standard Mautic fields available:" -msgstr "" - -#: ../channels/social_monitoring.rst:45 -msgid "**Published** - This allows you to set the published status of the Social Monitor. Unpublished Social Monitors will not collect new Contacts." -msgstr "" - -#: ../channels/social_monitoring.rst:49 -msgid "**Publish at (date/time)** - This allows you to define the date and time at which this Social Monitor is monitoring for new Contacts. You might use this to coincide with an event, for example." -msgstr "" - -#: ../channels/social_monitoring.rst:51 -msgid "**Unpublish at (date/time)** - This allows you to define the date and time at which this Social Monitor is monitoring for new Contacts." -msgstr "" - -#: ../channels/social_monitoring.rst:55 -#: ../channels/social_monitoring.rst:82 -msgid "**Contact Segment** - This allows you to define the Segment/s in Mautic that the Contacts join if detected with this Social Monitor. This can be useful for identifying people who are talking about your brand, and directly add them to a Segment to take further action." -msgstr "" - -#: ../channels/social_monitoring.rst:0 -msgid "Screenshot showing the creation of a new Twitter Mentions Social Monitor." -msgstr "" - -#: ../channels/social_monitoring.rst:62 -msgid "Hashtags" -msgstr "" - -#: ../channels/social_monitoring.rst:64 -msgid "When selecting the Twitter Hashtags monitoring method, the following fields are available:" -msgstr "" - -#: ../channels/social_monitoring.rst:66 -msgid "**Twitter hashtag** - The Twitter hashtag mentions you want to track. Don't include the # symbol - for example ``mautic``." -msgstr "" - -#: ../channels/social_monitoring.rst:72 -msgid "**Published** - This allows you to set the published status of the Social Monitor. Unpublished Social Monitors won't collect new Contacts." -msgstr "" - -#: ../channels/social_monitoring.rst:76 -msgid "**Publish at (date/time)** - This allows you to define the date and time at which this Social Monitor is monitoring for new Contacts. This might be used to coincide with an event, for example." -msgstr "" - -#: ../channels/social_monitoring.rst:78 -msgid "**Unpublish at (date/time)** - This allows you to define the date and time at which this Social Monitor ceases to monitor for new Contacts." -msgstr "" - -#: ../channels/social_monitoring.rst:0 -msgid "Screenshot showing the creation of a new Twitter Hashtags Social Monitor." -msgstr "" - -#: ../channels/utm_tags.rst:2 -#: ../channels/utm_tags.rst:38 -msgid "UTM tags" -msgstr "" - -#: ../channels/utm_tags.rst:4 -msgid "UTM tags are also known as parameters or short text codes. When adding these tags to URLs or links, marketers can track performance, create customised audiences, and analyze on website traffic from various sources. Marketers can also use UTM tags with Google Analytics to clearly understand the effectiveness of their marketing content and return on investment for marketing projects." -msgstr "" - -#: ../channels/utm_tags.rst:7 -msgid "Key benefits of using UTM tags" -msgstr "" - -#: ../channels/utm_tags.rst:9 -msgid "With UTM tags, you can:" -msgstr "" - -#: ../channels/utm_tags.rst:11 -msgid "Track the value of marketing projects and measure return on investment" -msgstr "" - -#: ../channels/utm_tags.rst:12 -msgid "Get precise data about conversion and traffic sources" -msgstr "" - -#: ../channels/utm_tags.rst:13 -msgid "Test the effectiveness of marketing content through A/B testing" -msgstr "" - -#: ../channels/utm_tags.rst:16 -msgid "Using UTM tags in Mautic" -msgstr "" - -#: ../channels/utm_tags.rst:18 -msgid "To use UTM tags with Google Analytics where they appear in your Google Analytics Dashboard, you must install your Google Analytics tracking code on the resource you are linking to. This synchronizes with your Google Analytics Dashboard and records the UTM tags." -msgstr "" - -#: ../channels/utm_tags.rst:20 -msgid "If you use a Mautic landing page, you must go to Settings > Configuration > Tracking Settings, and add your Google Analytics ID." -msgstr "" - -#: ../channels/utm_tags.rst:0 -msgid "Screenshot showing the option to add Google Analytics code" -msgstr "" - -#: ../channels/utm_tags.rst:26 -msgid "If you use a non-Mautic Landing Page, you must manually embed the Google Analytics tracking script on the third-party Page." -msgstr "" - -#: ../channels/utm_tags.rst:28 -msgid "Mautic Users can automatically append UTM tags to all links in an Email or Focus Item. For other Channels, you can make the link trackable by including UTM values in the URL address. When a Contact clicks a link in an Email or Focus Item, Mautic records UTM tags and stores them in the Contact record. You can find the details on the Contact Event History overview. After recording the UTM tags, you can use them as filters in Segments." -msgstr "" - -#: ../channels/utm_tags.rst:30 -msgid "You can use UTM tags to track Contacts who convert from Dynamic Web Content slots in Emails, and determine the source in Google Analytics or Mautic Reports. You can also use them as columns in a Report by selecting UTM codes as the data source." -msgstr "" - -#: ../channels/utm_tags.rst:32 -msgid "The following table lists the Google Analytics UTM tags:" -msgstr "" - -#: ../channels/utm_tags.rst:34 -msgid "Title" -msgstr "" - -#: ../channels/utm_tags.rst:39 -msgid "Description" -msgstr "" - -#: ../channels/utm_tags.rst:40 -msgid "Campaign Source" -msgstr "" - -#: ../channels/utm_tags.rst:43 -msgid "The referring source of the web activity. It indicates the social network, search engine, newsletter name, or any other specific source driving the traffic." -msgstr "" - -#: ../channels/utm_tags.rst:42 -msgid "Examples: ``facebook``, ``twitter``, ``blog``, ``newsletters``" -msgstr "" - -#: ../channels/utm_tags.rst:43 -msgid "UTM code: utm_source" -msgstr "" - -#: ../channels/utm_tags.rst:44 -msgid "Sample code: ``utm_source=facebook``" -msgstr "" - -#: ../channels/utm_tags.rst:45 -msgid "Campaign Medium" -msgstr "" - -#: ../channels/utm_tags.rst:48 -msgid "UTM tags - Mautic Documentation" -msgstr "" - -#: ../channels/utm_tags.rst:47 -msgid "Examples: ``cpc``, ``organic_social``" -msgstr "" - -#: ../channels/utm_tags.rst:48 -msgid "UTM code: utm_medium" -msgstr "" - -#: ../channels/utm_tags.rst:49 -msgid "Sample code: utm_medium=paid_social" -msgstr "" - -#: ../channels/utm_tags.rst:50 -msgid "Campaign Name" -msgstr "" - -#: ../channels/utm_tags.rst:53 -msgid "The specific promotion or Campaign title that you want to track." -msgstr "" - -#: ../channels/utm_tags.rst:52 -msgid "Examples: summer_sale, free_trial" -msgstr "" - -#: ../channels/utm_tags.rst:53 -msgid "UTM code: utm_campaign" -msgstr "" - -#: ../channels/utm_tags.rst:54 -msgid "Sample code: utm_campaign=summer_sale" -msgstr "" - -#: ../channels/utm_tags.rst:55 -msgid "Campaign Content" -msgstr "" - -#: ../channels/utm_tags.rst:56 -msgid "The Assets within the messages. This non-configurable value auto-populates with the content Asset identifier associated with the specific Asset." -msgstr "" - -#: ../channels/utm_tags.rst:57 -msgid "Campaign Term" -msgstr "" - -#: ../channels/utm_tags.rst:58 -msgid "The keyword to search a Campaign. This non-configurable value auto-populates within the link text and tracks links within the messages." -msgstr "" - -#: ../channels/utm_tags.rst:61 -msgid "You don't need to fill all the options. You can use one, or a few, or all of them, as required." -msgstr "" - -#: ../channels/utm_tags.rst:66 -msgid "Using UTM tags in Emails" -msgstr "" - -#: ../channels/utm_tags.rst:70 -msgid "Mautic supports UTM tagging in Emails. Mautic can automatically append UTM tags to all links in an Email by entering the appropriate Campaign values in the fields provided." -msgstr "" - -#: ../channels/utm_tags.rst:72 -msgid "In Mautic, click Channels > Emails." -msgstr "" - -#: ../channels/utm_tags.rst:73 -msgid "Create a new Email or edit an existing Email. If you choose to edit an existing Email, click the Email and then click Edit." -msgstr "" - -#: ../channels/utm_tags.rst:74 -#: ../channels/utm_tags.rst:90 -msgid "Locate the Google Analytics UTM tags section on the bottom right." -msgstr "" - -#: ../channels/utm_tags.rst:75 -#: ../channels/utm_tags.rst:91 -msgid "Enter the appropriate information in the fields." -msgstr "" - -#: ../channels/utm_tags.rst:76 -#: ../channels/utm_tags.rst:92 -msgid "Click Apply." -msgstr "" - -#: ../channels/utm_tags.rst:79 -msgid "When adding links in Emails, use the edit link icon in the builder." -msgstr "" - -#: ../channels/utm_tags.rst:80 -msgid "When adding links in Code Mode, use the tag." -msgstr "" - -#: ../channels/utm_tags.rst:81 -msgid "All links must include a trailing slash. Otherwise, UTM codes aren't appended." -msgstr "" - -#: ../channels/utm_tags.rst:84 -msgid "Using UTM tags in Focus Items" -msgstr "" - -#: ../channels/utm_tags.rst:86 -msgid "Mautic supports UTM tagging in :doc:`/channels/focus_items`. Mautic can automatically append UTM tags to all links in a Focus Item by entering the appropriate values in the field provided." -msgstr "" - -#: ../channels/utm_tags.rst:88 -msgid "Click Channels > Focus Items" -msgstr "" - -#: ../channels/utm_tags.rst:89 -msgid "Create a new focus item or open an existing one." -msgstr "" - -#: ../channels/web_notifications.rst:2 -msgid "Web notifications" -msgstr "" - -#: ../channels/web_notifications.rst:4 -msgid "Web Notifications can be an extremely powerful tool for the marketer. Mautic integrated with :xref:`OneSignal` which allows you to push information to a Contact as they browse through web resources (Mautic Landing Pages, or with some configuration (see :xref:`OneSignal web push`), on your own website), giving you one more Channel that you can use to build a relationship with them." -msgstr "" - -#: ../channels/web_notifications.rst:6 -msgid "Web notifications in Mautic use OneSignal by default. Using your own OneSignal account, you can now push a notification to your Contacts's browser - with their permission. Enable the OneSignal Plugin in Mautic's Configuration to see Web Notifications listed under Channels in the menu." -msgstr "" - -#: ../channels/web_notifications.rst:8 -msgid "For more information see the OneSignal :xref:`OneSignal web push quickstart` documentation." -msgstr "" - -#: ../channels/web_notifications.rst:11 -msgid "Setup web notifications" -msgstr "" - -#: ../channels/web_notifications.rst:14 -msgid "Configuration" -msgstr "" - -#: ../channels/web_notifications.rst:16 -msgid "Create a OneSignal account and once logged in, create an App" -msgstr "" - -#: ../channels/web_notifications.rst:18 -msgid "Setup App Website Push Platforms in your OneSignal App" -msgstr "" - -#: ../channels/web_notifications.rst:0 -msgid "Screenshot showing creating push platforms on OneSignal." -msgstr "" - -#: ../channels/web_notifications.rst:24 -msgid "Select Typical Site and fill out the required fields." -msgstr "" - -#: ../channels/web_notifications.rst:28 -msgid "Download the SDK files from the next screen, and upload them to the root of your Mautic installation - this must be accessible at `https://mautic.example.com/OneSignalSDKWorker.js`." -msgstr "" - -#: ../channels/web_notifications.rst:32 -msgid "Get the keys from OneSignal under the Settings > Keys & IDs tab." -msgstr "" - -#: ../channels/web_notifications.rst:33 -msgid "Enable the features you wish to use - for example, whether to enable notifications on mobile apps, Landing Pages, tracked resources on your website, and whether to show a welcome notification after they subscribe. You can also specify a subdomain name, and if you're using iOS and Android notifications you can also enable these options - see :doc:`/channels/push_notifications`." -msgstr "" - -#: ../channels/web_notifications.rst:36 -msgid "Sending notifications" -msgstr "" - -#: ../channels/web_notifications.rst:37 -msgid "There are two ways to send website notifications to the Contact:" -msgstr "" - -#: ../channels/web_notifications.rst:39 -msgid "Send with a Campaign Action" -msgstr "" - -#: ../channels/web_notifications.rst:40 -msgid "Send via a :doc:`/channels/marketing_messages`" -msgstr "" diff --git a/docs/docs_translations/companies.pot b/docs/docs_translations/companies.pot deleted file mode 100644 index 3ae163d8..00000000 --- a/docs/docs_translations/companies.pot +++ /dev/null @@ -1,221 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../companies/companies_overview.rst:3 -msgid "Companies" -msgstr "" - -#: ../companies/companies_overview.rst:5 -msgid "Companies are a way to group Contacts based on association with organizations." -msgstr "" - -#: ../companies/companies_overview.rst:None -msgid "Mautic Company Overview" -msgstr "" - -#: ../companies/companies_overview.rst:12 -msgid "Engagements/Points chart" -msgstr "" - -#: ../companies/companies_overview.rst:14 -msgid "Engagements shown on the chart include any tracked action the Contacts made. Some examples might include page hits, Form submissions, Email opens and so on. The engagements line chart displays how active the Contacts of the Company were in the past 6 months. The chart displays also the sum of Points the Contacts received." -msgstr "" - -#: ../companies/companies_overview.rst:19 -msgid "List of Contacts assigned" -msgstr "" - -#: ../companies/companies_overview.rst:23 -msgid "You can find a table with the list of the assigned Contacts displaying the date of their last activity, preceding the information of the Company which includes the Company name, address, and all the custom Company fields, and the engagement chart. This is good way to have a view of the recent activity of the Contacts you know in this Company." -msgstr "" - -#: ../companies/companies_overview.rst:26 -msgid "Company duplicates" -msgstr "" - -#: ../companies/companies_overview.rst:27 -msgid "The Company name field is a unique identifier by default. You can choose any other Company field as unique identifier in the **custom fields** section." -msgstr "" - -#: ../companies/companies_overview.rst:29 -msgid "In *Configuration > Company Settings* you can choose the operator used when merging Companies with multiple identifiers - either **AND** or **OR**." -msgstr "" - -#: ../companies/companies_overview.rst:None -msgid "Setup operator for find duplications algorithm" -msgstr "" - -#: ../companies/companies_overview.rst:35 -msgid "These settings allow Mautic to find and merge duplicate Companies during the import, using the Integrations Framework and in other parts of Mautic." -msgstr "" - -#: ../companies/companies_overview.rst:38 -msgid "Company actions" -msgstr "" - -#: ../companies/companies_overview.rst:43 -msgid "Merging Companies" -msgstr "" - -#: ../companies/companies_overview.rst:47 -msgid "When editing a Company, you can merge this Company into another existing Company by using the **Merge** button." -msgstr "" - -#: ../companies/companies_overview.rst:49 -msgid "Search for the Company you wish to merge into, then click to start the merge. Contacts associated with the merged Companies now become associated with the remaining Company." -msgstr "" - -#: ../companies/companies_overview.rst:51 -msgid "After completion of the merge process, Mautic redirects you to the remaining Company, as the old Company no longer exists." -msgstr "" - -#: ../companies/companies_overview.rst:56 -msgid "Company Custom Fields" -msgstr "" - -#: ../companies/companies_overview.rst:60 -msgid "By default, a set of fields exist for Companies, but you can customize these fields to meet your needs." -msgstr "" - -#: ../companies/companies_overview.rst:62 -msgid "Go to **Custom Fields** and create a new field" -msgstr "" - -#: ../companies/companies_overview.rst:64 -msgid "Change the dropdown select box from Contact to Company objects" -msgstr "" - -#: ../companies/companies_overview.rst:66 -msgid "Save the custom field" -msgstr "" - -#: ../companies/companies_overview.rst:71 -msgid "Company Segments" -msgstr "" - -#: ../companies/companies_overview.rst:75 -msgid "You can create a Segment based on a Company record. Select any Company field to filter with and the matching criteria for it, and Mautic lists any Contacts that match the selected fields in the Segment." -msgstr "" - -#: ../companies/companies_overview.rst:80 -msgid "Identifying Companies" -msgstr "" - -#: ../companies/companies_overview.rst:84 -msgid "Mautic identifies Companies strictly through a matching criteria based on **Company Name**, **City**, **Country or State**. If a city or a country isn't delivered as an identifying fields to identify a Contact, the Company won't match." -msgstr "" - -#: ../companies/companies_overview.rst:89 -msgid "Company actions in Campaigns" -msgstr "" - -#: ../companies/companies_overview.rst:93 -msgid "It's possible to add a Contact to a new Company based on a Campaign action." -msgstr "" - -#: ../companies/companies_overview.rst:98 -msgid "Creating and managing Companies" -msgstr "" - -#: ../companies/companies_overview.rst:102 -msgid "To create or manage Companies, go to the Companies menu identified by the building icon in the left hand navigation. In this area you can create, edit, or delete Companies." -msgstr "" - -#: ../companies/companies_overview.rst:107 -msgid "Assigning Companies to Contacts" -msgstr "" - -#: ../companies/companies_overview.rst:111 -msgid "There are different ways to assign a Company to a Contact as explained below:" -msgstr "" - -#: ../companies/companies_overview.rst:114 -msgid "Contact profile" -msgstr "" - -#: ../companies/companies_overview.rst:116 -msgid "You can assign a Contact to Companies in the Contact's profile, while creating or editing an existing Contact. Mautic considers the latest Company assigned as the primary Company for the Contact." -msgstr "" - -#: ../companies/companies_overview.rst:119 -msgid "Contacts list view" -msgstr "" - -#: ../companies/companies_overview.rst:121 -msgid "You can batch assign Companies to selected Contacts in the Contact's list view." -msgstr "" - -#: ../companies/companies_overview.rst:126 -msgid "Via a Campaign" -msgstr "" - -#: ../companies/companies_overview.rst:130 -msgid "You can assign a Company to identify Contacts through a Campaign by selecting the **Assign Contact to Company** action." -msgstr "" - -#: ../companies/companies_overview.rst:135 -msgid "Through a Form" -msgstr "" - -#: ../companies/companies_overview.rst:139 -msgid "When identifying a Contact through a Form, you can also associate an existing Company or create a new one if:" -msgstr "" - -#: ../companies/companies_overview.rst:141 -msgid "The Form includes Company name as a Form field - mandatory for Company matching/creation," -msgstr "" - -#: ../companies/companies_overview.rst:142 -msgid "The Form includes City as a Form field - mandatory for Company matching/creation)," -msgstr "" - -#: ../companies/companies_overview.rst:143 -msgid "The Form includes Country as a form field - mandatory for Company matching/creation," -msgstr "" - -#: ../companies/companies_overview.rst:144 -msgid "The Form includes State as a form field - optional for Company matching/creation." -msgstr "" - -#: ../companies/companies_overview.rst:147 -msgid "Company scoring" -msgstr "" - -#: ../companies/companies_overview.rst:149 -msgid "It's possible to change the Company score through a Campaign action or a Form action. When using these actions, it's necessary to identify the Contact first, and then alter the score of the Companies assigned to that Contact." -msgstr "" - -#: ../companies/companies_overview.rst:151 -msgid "Select the **Change Company score** action in either a Form or a Campaign" -msgstr "" - -#: ../companies/companies_overview.rst:152 -msgid "Once submitted or triggered, Mautic identifies Companies in the Campaign or Form to change their score." -msgstr "" - -#: ../companies/companies_overview.rst:157 -msgid "Setting the primary Company" -msgstr "" - -#: ../companies/companies_overview.rst:161 -msgid "You can set the primary Company through the Contact details interface." -msgstr "" - -#: ../companies/companies_overview.rst:None -msgid "Screenshot showing setting the primary Company" -msgstr "" diff --git a/docs/docs_translations/components.pot b/docs/docs_translations/components.pot deleted file mode 100644 index 317eee33..00000000 --- a/docs/docs_translations/components.pot +++ /dev/null @@ -1,1313 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../components/assets.rst:2 -msgid "Assets" -msgstr "" - -#: ../components/assets.rst:4 -msgid "Assets are pieces of content you want to make available for your Contacts to access. You want to track and analyse who is viewing or downloading your Assets. You also may want to personalize the Contact's journey based on what Assets they interacted with. You may also do scoring based on interaction with Assets." -msgstr "" - -#: ../components/assets.rst:9 -msgid "Managing Assets" -msgstr "" - -#: ../components/assets.rst:12 -msgid "Asset Categories" -msgstr "" - -#: ../components/assets.rst:16 -msgid "Mautic allows you to organize Assets into Categories, which helps you easily locate resources. To create a new Category, review the :doc:`/categories/categories-overview` documentation." -msgstr "" - -#: ../components/assets.rst:21 -msgid "Working with Assets" -msgstr "" - -#: ../components/assets.rst:25 -msgid "Before creating an Asset, first establish and publish any Categories required. It's not possible to assign Assets to unpublished Categories. If you wish to use an Integration such as the Amazon S3 Plugin to host your files, set this up before creating an Asset." -msgstr "" - -#: ../components/assets.rst:30 -msgid "Creating a new Asset" -msgstr "" - -#: ../components/assets.rst:34 -msgid "Navigate to Components > Assets. Mautic lists any Assets you have previously created. Click New to begin creating an Asset." -msgstr "" - -#: ../components/assets.rst:36 -msgid "You create Assets by uploading local resources on your computer, or by locating the Asset from a remote storage host such as Amazon S3. There are limitations by size due to the settings of your server - any such restriction may display as a warning message in the file upload section." -msgstr "" - -#: ../components/assets.rst:39 -msgid "Add UTM to Asset" -msgstr "" - -#: ../components/assets.rst:40 -msgid "UTM parameters appended to the download link means that UTM data is available in the resource download Report." -msgstr "" - -#: ../components/assets.rst:44 -msgid "``/asset/{id}:{name}?utm_source=test&utm_medium=test&utm_campaign=test&utm_id=test&utm_term=test&utm_content=test``" -msgstr "" - -#: ../components/assets.rst:50 -msgid "Uploading an Asset" -msgstr "" - -#: ../components/assets.rst:54 -msgid "To upload an Asset, either drag the file into the box, or click in the box to open a file upload window. On selection of the file, it's automatically uploaded and appears in the boxed area." -msgstr "" - -#: ../components/assets.rst:56 -msgid "By default Mautic allows the following file types:" -msgstr "" - -#: ../components/assets.rst:62 -msgid "If you need to add extra file types, configure the maximum size of upload or the Assets directory, navigate to Configuration > Asset Settings." -msgstr "" - -#: ../components/assets.rst:None -msgid "Screenshot of Asset settings" -msgstr "" - -#: ../components/assets.rst:68 -#: ../components/dynamic_web_content.rst:112 -#: ../components/forms.rst:23 -msgid "The following fields are available:" -msgstr "" - -#: ../components/assets.rst:70 -msgid "**Title** - the title for the Asset" -msgstr "" - -#: ../components/assets.rst:71 -msgid "**Alias** - used to create the slug on the download URL. Created from the title automatically if not provided." -msgstr "" - -#: ../components/assets.rst:72 -msgid "**Description** - an internally used description to inform other Mautic Users what the Asset is and/or where it's used." -msgstr "" - -#: ../components/assets.rst:73 -msgid "**Category** - used to organize resources - see :doc:`/categories/categories-overview` for more information" -msgstr "" - -#: ../components/assets.rst:74 -msgid "**Language** - the language of this Asset - can be helpful in multilingual marketing Campaigns and for reporting purposes" -msgstr "" - -#: ../components/assets.rst:75 -msgid "**Published** - Whether the Asset is available for use - published - or not available - unpublished" -msgstr "" - -#: ../components/assets.rst:79 -msgid "**Publish at (date/time)** - This allows you to define the date and time at which this Asset is available" -msgstr "" - -#: ../components/assets.rst:81 -msgid "**Unpublish at (date/time)** - This allows you to define the date and time at which this Asset ceases to be available" -msgstr "" - -#: ../components/assets.rst:85 -msgid "**Block search engines from indexing this file** - If you don't want to index files like PDF, DOCx and so forth, setting this switch to Yes sends the X-Robots-Tag no-index http header. If set to No, the header isn't sent and your files could become indexed by search engines." -msgstr "" - -#: ../components/assets.rst:87 -msgid "Depending on the type of file uploaded, a preview may display after the upload completes." -msgstr "" - -#: ../components/assets.rst:None -msgid "Screenshot of create new Asset interface" -msgstr "" - -#: ../components/assets.rst:96 -msgid "Using remote Assets" -msgstr "" - -#: ../components/assets.rst:100 -msgid "Instead of uploading a file from your computer, you can either provide a link to a file on a cloud storage provider or browse your integrated cloud storage provider - for example an Amazon S3 bucket - by selecting the Remote tab, rather than Local." -msgstr "" - -#: ../components/assets.rst:105 -msgid "Viewing an Asset" -msgstr "" - -#: ../components/assets.rst:109 -msgid "Once you've uploaded an Asset, you'll want to make it available for your Contacts to access it. Using the Download URL from the Asset section in Mautic, you can track which Contacts are downloading or viewing the Assets." -msgstr "" - -#: ../components/assets.rst:111 -msgid "Copy and paste the link into your website, on a landing page, or as a link in an Email." -msgstr "" - -#: ../components/assets.rst:114 -msgid "In a Mautic Email or Landing Page, append ``?stream=1`` to the end of the URL to open the Asset in a new tab." -msgstr "" - -#: ../components/assets.rst:116 -msgid "Whether the Asset downloads or opens in a new tab depends on the Contact's browser settings. To gate an Asset by requiring them to submit some information before downloading, you may have a Form submit action to download an Asset." -msgstr "" - -#: ../components/assets.rst:118 -msgid "To ensure that Contacts are providing you with valid Email addresses for high-value Assets, attach the Asset to an Email and use the send Email Form submit action rather than instantly downloading the Asset." -msgstr "" - -#: ../components/assets.rst:123 -msgid "Editing an Asset" -msgstr "" - -#: ../components/assets.rst:127 -msgid "You can edit an Asset by clicking on the 'edit' button while viewing the Asset, or by selecting the arrow next to the checkbox for the Asset, and selecting 'edit'. The edit screens are the same as the view screens,with the saved content already populated in the fields." -msgstr "" - -#: ../components/assets.rst:132 -msgid "Deleting an Asset" -msgstr "" - -#: ../components/assets.rst:136 -msgid "It's possible to delete an Asset by clicking on the 'delete' button while viewing the Asset, or by selecting the arrow next to the checkbox for the Asset, and selecting 'delete'. Mautic displays a confirmation screen, prompting confirmation that you wish to delete the Asset." -msgstr "" - -#: ../components/assets.rst:139 -msgid "Once deleted, you can't retrieve an Asset, and statistics relating to the number of downloads for that Asset are no longer be available. Contact Points accumulated as a result of accessing the resource remain. It's recommended where possible to unpublish Assets which are no longer in use - in future there may be an archive feature." -msgstr "" - -#: ../components/dynamic_web_content.rst:4 -msgid "Dynamic Web Content" -msgstr "" - -#: ../components/dynamic_web_content.rst:8 -msgid "Dynamic Web Content is one of several methods Mautic uses to personalize the web experience for Contacts. Marketers can display different content to different people in specific areas of a webpage. Mautic Users may want to personalize content based on data collected about the website visitor. Even anonymous Contacts may see Dynamic Content, if you've collected any information about them - such as location data." -msgstr "" - -#: ../components/dynamic_web_content.rst:11 -msgid "Preparation" -msgstr "" - -#: ../components/dynamic_web_content.rst:13 -msgid "Before you consider using Dynamic Web Content, consider:" -msgstr "" - -#: ../components/dynamic_web_content.rst:15 -msgid "where on your website would you include personalized content?" -msgstr "" - -#: ../components/dynamic_web_content.rst:16 -msgid "What audience/s do you plan to personalize content for?" -msgstr "" - -#: ../components/dynamic_web_content.rst:17 -msgid "Do you collect the information required to accurately filter your Contacts in this way?" -msgstr "" - -#: ../components/dynamic_web_content.rst:21 -msgid "Website configuration" -msgstr "" - -#: ../components/dynamic_web_content.rst:23 -msgid "Once you've decided where on your website to display the content, you must create an area to add the content. Mautic is platform-agnostic - you can add slots into any website you have created. To do this, create an HTML slot to display the Dynamic Web Content." -msgstr "" - -#: ../components/dynamic_web_content.rst:25 -msgid "Change ``myslot`` in ``data-param-slot-name=\"myslot\"`` to the Requested Slot Name of your Dynamic Web Content item:" -msgstr "" - -#: ../components/dynamic_web_content.rst:33 -msgid "You can add your own default content between the ``
`` tags to ensure that content displays when the filters aren't matching - for example with new anonymous visitors or a Contact that doesn't match the criteria you have specified." -msgstr "" - -#: ../components/dynamic_web_content.rst:35 -msgid "Content Management System Plugins for Mautic also have specific ways to embed the content, for example:" -msgstr "" - -#: ../components/dynamic_web_content.rst:37 -msgid "**Joomla** - ``{mautic type=\"content\" slot=\"slotname\"} Insert default content {/mautic}``" -msgstr "" - -#: ../components/dynamic_web_content.rst:38 -msgid "**WordPress** - ``[mautic type=\"content\" slot=\"slotname\"] Insert default content [/mautic]``" -msgstr "" - -#: ../components/dynamic_web_content.rst:41 -msgid "Mautic configuration" -msgstr "" - -#: ../components/dynamic_web_content.rst:44 -msgid "It's important to ensure that you configure your CORS settings correctly when using Dynamic Web Content - if this isn't set up your content won't display. Read more in :ref:`CORS Settings`." -msgstr "" - -#: ../components/dynamic_web_content.rst:49 -msgid "Creating Dynamic Web Content slots" -msgstr "" - -#: ../components/dynamic_web_content.rst:53 -msgid "Mautic provides both Campaign-based and filter-based Dynamic Web Content. To create either type:" -msgstr "" - -#: ../components/dynamic_web_content.rst:55 -msgid "Navigate to the Components > Dynamic Content section" -msgstr "" - -#: ../components/dynamic_web_content.rst:56 -msgid "Click New to create a new slot" -msgstr "" - -#: ../components/dynamic_web_content.rst:None -msgid "Create a new Dynamic Web Content slot" -msgstr "" - -#: ../components/dynamic_web_content.rst:62 -msgid "The following values are available:" -msgstr "" - -#: ../components/dynamic_web_content.rst:64 -msgid "**Internal name** - This is how the slot displays in your list of Dynamic Web Content slots. You should include information on what you're personalizing - for example, country - and the content in the slot - for example, United States. If you're creating a personalized slot for people in the United States, you can name the slot Country - United States. If you plan to have more than one personalized content slot for the same audience across your website, include the page title or other identifying information for the particular slot." -msgstr "" - -#: ../components/dynamic_web_content.rst:68 -msgid "**Content** - Use the WYSIWYG editor to create the Dynamic Web Content slot. You may include images and videos. If you prefer HTML, click the `` Source`` icon in the toolbar to switch to the code view. Mautic's Dynamic Web Content supports tokens in the same way as Landing Pages or Emails. To add a token, start typing with the ``{`` character and available tokens are displayed. These include:" -msgstr "" - -#: ../components/dynamic_web_content.rst:70 -msgid "Contact field: {contactfield=fieldalias}" -msgstr "" - -#: ../components/dynamic_web_content.rst:71 -msgid "Landing page link: {pagelink=ID#}" -msgstr "" - -#: ../components/dynamic_web_content.rst:72 -msgid "Asset link: {assetlink=ID#}" -msgstr "" - -#: ../components/dynamic_web_content.rst:73 -msgid "Form: {form=ID#}" -msgstr "" - -#: ../components/dynamic_web_content.rst:74 -msgid "Focus item: {focus=ID#}" -msgstr "" - -#: ../components/dynamic_web_content.rst:78 -msgid "**Category** - Assign a Category to help you organize your Dynamic Web Content items. See :doc:`/categories/categories-overview` for more information." -msgstr "" - -#: ../components/dynamic_web_content.rst:80 -msgid "**Language** - the language of this Dynamic Web Content - can be helpful in multilingual marketing Campaigns and for reporting purposes" -msgstr "" - -#: ../components/dynamic_web_content.rst:82 -msgid "**Is a translation of** - If you're creating a slot in a second language translation - for example to use on a multilingual website - select the original base language Dynamic Web Content item which you're translating. The same slot displays the appropriate language based on the Campaign or filters set, but Mautic shows the translated content if a visitor is viewing the page in a different browser language." -msgstr "" - -#: ../components/dynamic_web_content.rst:84 -msgid "**Published** - Whether the Dynamic Web Content item is available for use - published - or not available - unpublished" -msgstr "" - -#: ../components/dynamic_web_content.rst:86 -msgid "**Is Campaign based** - if set to Yes, Mautic pushes this Dynamic Web Content to Contacts through a Campaign. When set to No, you can specify filters for visitors to see the content." -msgstr "" - -#: ../components/dynamic_web_content.rst:88 -msgid "**Requested slot name** - shown if using non-Campaign based Dynamic Web Content, this allows you to specify the slot name on your website in which the Contact sees the content." -msgstr "" - -#: ../components/dynamic_web_content.rst:92 -msgid "**Publish at (date/time)** - This allows you to define the date and time at which this Dynamic Web Content item is available for displaying to Contacts" -msgstr "" - -#: ../components/dynamic_web_content.rst:94 -msgid "**Unpublish at (date/time)** - This allows you to define the date and time at which this Dynamic Web Content item ceases to be available for displaying to Contacts." -msgstr "" - -#: ../components/dynamic_web_content.rst:98 -msgid "**UTM tags** - Mautic can append UTM tags to any links and Form submissions. See :doc:`/channels/utm_tags` for more information." -msgstr "" - -#: ../components/dynamic_web_content.rst:103 -msgid "Campaign-based Dynamic Web Content" -msgstr "" - -#: ../components/dynamic_web_content.rst:108 -msgid "Creating the request" -msgstr "" - -#: ../components/dynamic_web_content.rst:110 -msgid "Use a Campaign Decision for ``Request Dynamic Content`` to use Campaign-based dynamic content. The Campaign Decision checks if a Campaign member visits a page where a Dynamic Content slot is. Visitors to a page with a Dynamic Content slot receive the Dynamic Content." -msgstr "" - -#: ../components/dynamic_web_content.rst:114 -msgid "**Name** - the Campaign event. Start the name with something like Req-DWC: so when you're looking at Campaign Reports, you can see the event type." -msgstr "" - -#: ../components/dynamic_web_content.rst:116 -msgid "**Requested Slot Name** - Mautic checks for the slot name. You can see how many Contacts got to the Campaign event where you're checking if their visits request the slot." -msgstr "" - -#: ../components/dynamic_web_content.rst:118 -msgid "As an example, these two fields might look like: ``Req-DWC: Country-Header`` in the Contact history. The requested slot name is the slot Mautic looks for on the page. If it's on a 3rd-party page, it'll be in the code you use to add the Dynamic Content slot to your page. If it's on a Mautic Landing Page, define the slot name on the Landing Page." -msgstr "" - -#: ../components/dynamic_web_content.rst:120 -msgid "**Select Default Content** - choose the content which displays to visitors who don't meet the conditions set at the next step of the Campaign. Users may see the default content first, before Mautic pushes the Dynamic Content." -msgstr "" - -#: ../components/dynamic_web_content.rst:None -msgid "Create a new Dynamic Web Content request in a Mautic Campaign" -msgstr "" - -#: ../components/dynamic_web_content.rst:127 -msgid "Creating the filters" -msgstr "" - -#: ../components/dynamic_web_content.rst:129 -msgid "Once created, you can add filters on the affirmative path to determine which Contacts see the different variations. This happens with Conditions - read more in :doc:`/campaigns/creating_campaigns`." -msgstr "" - -#: ../components/dynamic_web_content.rst:131 -msgid "As an example, you might use the condition of ``Country = United States of America`` to filter only people located in the country." -msgstr "" - -#: ../components/dynamic_web_content.rst:134 -msgid "Pushing the Dynamic Web Content" -msgstr "" - -#: ../components/dynamic_web_content.rst:135 -msgid "Once the relevant filters are in place, you can add the Campaign action of 'Push Dynamic Content' which triggers Mautic to send the relevant content to the Contacts matching the filters." -msgstr "" - -#: ../components/dynamic_web_content.rst:None -msgid "Push Dynamic Web Content to Contact in a Mautic Campaign" -msgstr "" - -#: ../components/dynamic_web_content.rst:141 -msgid "With all this in place, it might look something like this:" -msgstr "" - -#: ../components/dynamic_web_content.rst:None -msgid "Dynamic Web Content to Contact in a Mautic Campaign" -msgstr "" - -#: ../components/dynamic_web_content.rst:147 -msgid "You may wish to decide on a naming convention for your Campaigns, for example prefixing with ``DWC:`` when you're pushing Dynamic Web Content." -msgstr "" - -#: ../components/dynamic_web_content.rst:152 -msgid "Filter-based Dynamic Web Content" -msgstr "" - -#: ../components/dynamic_web_content.rst:156 -msgid "Filters are often easier to work with and can be more reliable, as they don't rely on the triggering of a Campaign cron job." -msgstr "" - -#: ../components/dynamic_web_content.rst:159 -msgid "Creating filters" -msgstr "" - -#: ../components/dynamic_web_content.rst:161 -msgid "When creating the Dynamic Web Content item, select No for the 'Is Campaign based' switch which displays the filters tab." -msgstr "" - -#: ../components/dynamic_web_content.rst:163 -msgid "Use the filters to configure the criteria that Contacts must meet to see the Dynamic Web Content slot." -msgstr "" - -#: ../components/dynamic_web_content.rst:165 -msgid "Provide the content in the slot within the text editor area. Mautic displays this content when the filters match." -msgstr "" - -#: ../components/dynamic_web_content.rst:170 -msgid "Implementing Dynamic Web Content" -msgstr "" - -#: ../components/dynamic_web_content.rst:175 -msgid "Default content" -msgstr "" - -#: ../components/dynamic_web_content.rst:177 -msgid "Mautic displays the default content when the visitor doesn't match any of the filter criteria, or the visitor isn't a tracked/identified Contact. It's important to have something in the default content, rather than an empty space." -msgstr "" - -#: ../components/dynamic_web_content.rst:179 -msgid "For Campaign-based Dynamic Web Content, you specify the default content when you configure the Request Dynamic Content decision. In filter-based Dynamic Web Content, you create the default content on the page where you are inserting the slot, and Mautic replaces it with the Dynamic Content if the filter match." -msgstr "" - -#: ../components/dynamic_web_content.rst:182 -msgid "If you're using Focus Items as your Dynamic Web Content and only showing specific Focus Items to specific audiences, you don't need to have any default content, as Focus Items don't physically take up space on your page." -msgstr "" - -#: ../components/forms.rst:2 -msgid "Forms" -msgstr "" - -#: ../components/forms.rst:4 -msgid "Mautic subscribers use Forms for lead generation and data collection. With Mautic Forms, marketers can convert anonymous web visitors to known Contacts and build a Contact's profile with progressive profiling. The more data you can gather without appearing intrusive or annoying, the more effective your personalization strategy." -msgstr "" - -#: ../components/forms.rst:9 -msgid "Creating a new Form" -msgstr "" - -#: ../components/forms.rst:13 -msgid "To create a new Form:" -msgstr "" - -#: ../components/forms.rst:15 -msgid "Go to Components > Forms and click New" -msgstr "" - -#: ../components/forms.rst:18 -msgid "Select the type of Form you wish to create" -msgstr "" - -#: ../components/forms.rst:17 -msgid "**Campaign Form** - Mautic allows you to trigger a Campaign with the submission of this type of Form. Campaign Forms have less actions directly associated with the Form submit actions - which happen immediately after Form submission - as most actions trigger as part of a Campaign workflow." -msgstr "" - -#: ../components/forms.rst:18 -msgid "**Standalone Form** - A more commonly used Form, this allows the execution of many submit actions immediately at the point of Form submission." -msgstr "" - -#: ../components/forms.rst:21 -msgid "Forms with a lot of submit actions - particularly when submitting to third party systems such as a Customer Relationship Management system - can have an impact on the Form submission time. This is especially the case if there are a lot of fields. Consider using a Campaign Form if you can wait for the cron job to trigger the actions." -msgstr "" - -#: ../components/forms.rst:25 -msgid "**Category** - Assign a Category to help you organize your Forms." -msgstr "" - -#: ../components/forms.rst:27 -msgid "**Published** - Whether the Form is available for use - published - or not available - unpublished. Unpublished Forms won't be visible when you've added the Form using JavaScript. If you used the manual method to copy and paste the Form HTML, the Form remains visible but visitors **won't** be able to submit it - an error message prevents them from submitting if they try to submit an unpublished Form." -msgstr "" - -#: ../components/forms.rst:31 -msgid "**Publish at (date/time)** - This allows you to define the date and time at which this Form is available for submissions." -msgstr "" - -#: ../components/forms.rst:33 -msgid "**Unpublish at (date/time)** - This allows you to define the date and time at which this Form ceases to be available for submissions." -msgstr "" - -#: ../components/forms.rst:37 -msgid "**Disable search indexing** - If Yes, Mautic prevents search engines from finding and displaying the Form in search results by sending the ``noindex`` http header." -msgstr "" - -#: ../components/forms.rst:39 -msgid "**Kiosk mode** - If Yes, Mautic turns off tracking of Contacts created through the Form, so that the Form doesn't generate cookies or associate any IP address with the Contact record. Marketers may refer to this as 'data entry mode'. It's ideal for using at conferences or events where several Contacts may enter their information using the same device, as it prevents associating the activity on the device to Contacts." -msgstr "" - -#: ../components/forms.rst:41 -msgid "**Render style** - If Yes, the Form displays with the styling from either the selected Mautic Theme or the Attributes tab of the Form fields. When No, the Form adopts the styling of where it's embedded." -msgstr "" - -#: ../components/forms.rst:43 -msgid "**Theme** - Select a Mautic Theme which has styling for a Form. This dictates the styling of the Form when added to an external website or Application if 'Render style' is Yes." -msgstr "" - -#: ../components/forms.rst:46 -msgid "Not all Themes include Form styling. Check the Features column on your Themes listing in the Theme Manager to see which Themes include styling for Forms." -msgstr "" - -#: ../components/forms.rst:51 -msgid "Configuring Forms" -msgstr "" - -#: ../components/forms.rst:54 -msgid "Once you have selected the type of Form, you have some additional options to set." -msgstr "" - -#: ../components/forms.rst:57 -msgid "Details" -msgstr "" - -#: ../components/forms.rst:59 -msgid "The available details fields are:" -msgstr "" - -#: ../components/forms.rst:61 -msgid "**Name** - Title your Form, including any terms you may want to use to search for the Form." -msgstr "" - -#: ../components/forms.rst:62 -msgid "**Description** - Add a description, so other Mautic Users can see what the goal of the Form is. It may help to include information like any location where the Form appears." -msgstr "" - -#: ../components/forms.rst:65 -msgid "**Successful Submit Action** - Options include:" -msgstr "" - -#: ../components/forms.rst:64 -msgid "**Remain at Form** - nothing appears to happen, the Form remains as is" -msgstr "" - -#: ../components/forms.rst:65 -msgid "**Redirect URL** - directs the Contact to another location, such as a thank you Landing Page, after submission" -msgstr "" - -#: ../components/forms.rst:66 -msgid "**Display message** - shows a message over the Form once the Contact has submitted the Form." -msgstr "" - -#: ../components/forms.rst:67 -msgid "**Redirect URL/Message** - If you decide to use the Redirect URL successful submit action, paste the URL where you'd like to direct submitters. If you use Display message, enter the message to display." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing standalone Form" -msgstr "" - -#: ../components/forms.rst:74 -msgid "Fields" -msgstr "" - -#: ../components/forms.rst:76 -msgid "To control the maximum number of fields shown on a Form:" -msgstr "" - -#: ../components/forms.rst:78 -msgid "**Maximum fields displayed at a time** - This setting applies progressive profiling across multiple Forms. Select the maximum number of fields to display on a single Form." -msgstr "" - -#: ../components/forms.rst:80 -msgid "To add a new field to your Form:" -msgstr "" - -#: ../components/forms.rst:82 -msgid "Click the Add a new field dropdown and select the type of field you wish to use. Available fields include:" -msgstr "" - -#: ../components/forms.rst:84 -msgid "**CAPTCHA** - A basic tool for spam protection requiring the Form submitter to answer a question, or detecting when spambots try to submit data in a hidden CAPTCHA field - sometimes referred to as a honeypot. It's recommended to use some kind of CAPTCHA on every Form. It's also possible to support reCAPTCHA and other tools with third-party Plugins." -msgstr "" - -#: ../components/forms.rst:86 -msgid "**Checkbox Group** - This field allows a visitor to select one or more options from a list using checkboxes. This field type can also provide a single checkbox - for example to gain consent to use cookies and send marketing Emails or other messages to the Contact." -msgstr "" - -#: ../components/forms.rst:89 -msgid "You can associate checkbox group fields with *boolean* and *select - multiple* fields, but not *select* fields." -msgstr "" - -#: ../components/forms.rst:91 -msgid "**Date** - This field allows the visitor to select a date with a calendar picker. The formatting of the date applies the default setting in your Configuration." -msgstr "" - -#: ../components/forms.rst:93 -msgid "**Date/time** - Similar to the date field, this allows the visitor to select both the date and the time using a calendar picker." -msgstr "" - -#: ../components/forms.rst:95 -msgid "**Description** - A basic header field, most often used to provide a visual title for the Form. The header field acts as the field name or label. The description area - accessed under the Properties tab - is a free text WYSIWYG editor, where you can add a description of the Form. By default, the description shows immediately below the header field in paragraph text format." -msgstr "" - -#: ../components/forms.rst:97 -msgid "**Email** - This field requires the visitor to provide a valid Email address using the correct syntax expected from an Email address - ``name@domain.com``. It's recommended to have at least one Email field on your Form, as by default the Email field is the default identifier of a Contact in Mautic." -msgstr "" - -#: ../components/forms.rst:99 -msgid "**File** - This allows visitors to upload a file on the Form." -msgstr "" - -#: ../components/forms.rst:102 -msgid "When using the file upload field there is a limit of 1,000 submissions using the same filename. Note that you can attach the submitted files in the \"Send Form result\" action." -msgstr "" - -#: ../components/forms.rst:104 -msgid "**HTML area** - This field allows marketers to add custom HTML to their Form." -msgstr "" - -#: ../components/forms.rst:106 -msgid "**Hidden** - This field won't be visible on the Form, but include default values, saved along with the Form submission, for reporting or internal tagging purposes." -msgstr "" - -#: ../components/forms.rst:108 -msgid "**List - Country** - This populates Mautic's default, non-editable country list. To use a custom list you should make use of the Select field type and manually enter the countries you would like to include." -msgstr "" - -#: ../components/forms.rst:110 -msgid "**Page break** - This allows marketers to break up the Form into multiple parts or field groupings." -msgstr "" - -#: ../components/forms.rst:112 -msgid "**Number** - This field validates that the entered values are digits. The field allows decimals and negative numbers, but no other non-numerical values - including commas. On a mobile device, the keyboard changes to a number pad when a visitor clicks into this field." -msgstr "" - -#: ../components/forms.rst:114 -msgid "**Password** - This allows the visitor to create a password. Use this field if the Form creates an account and Mautic posts the results to another system/Form. You must not save the entered field value to the Contact profile for security reasons." -msgstr "" - -#: ../components/forms.rst:116 -msgid "**Phone** - This field maps by default to the Phone field, and validates numbers using the international format for phone numbers. The validation requires a country code - for example +1 for the United States of America or +44 for the United Kingdom)." -msgstr "" - -#: ../components/forms.rst:118 -msgid "**Radio group** - This field provides a group of single-select options with a radio button, sometimes referred to as an option button group." -msgstr "" - -#: ../components/forms.rst:120 -msgid "**Select** - This option shows a dropdown list where a visitor may choose one option. This field also allows multiple selections, which changes the display to a box with the options listed. On a mobile device, a single select box shows a dialog box with radio buttons, and with checkboxes for a multi-select field." -msgstr "" - -#: ../components/forms.rst:122 -msgid "**Social login** - This allows the visitor to connect their Twitter, Facebook or LinkedIn profiles with their Contact record. You must configure the Plugin for the social network before using this field." -msgstr "" - -#: ../components/forms.rst:124 -msgid "**Text** - This field shows a text box with 255 characters available. Common uses include specifying the visitor's first name, last name, city, and so forth." -msgstr "" - -#: ../components/forms.rst:126 -msgid "**Text area** - Similar to the text field, but without the 255 character limitation. The text area field has a character limit of 65,535 characters." -msgstr "" - -#: ../components/forms.rst:128 -msgid "**URL** - This field validates the entry as being in the expected format for a URL, including ``https://`` or ``http://``" -msgstr "" - -#: ../components/forms.rst:131 -msgid "Field options" -msgstr "" - -#: ../components/forms.rst:133 -msgid "Based on the field selected, Mautic displays various tabs in the fields editor interface. The available tabs are:" -msgstr "" - -#: ../components/forms.rst:135 -msgid ":ref:`General`" -msgstr "" - -#: ../components/forms.rst:136 -msgid ":ref:`Mapped field`" -msgstr "" - -#: ../components/forms.rst:137 -msgid ":ref:`Validation`" -msgstr "" - -#: ../components/forms.rst:138 -msgid ":ref:`Properties`" -msgstr "" - -#: ../components/forms.rst:139 -msgid ":ref:`Attributes`" -msgstr "" - -#: ../components/forms.rst:140 -msgid ":ref:`Behavior`" -msgstr "" - -#: ../components/forms.rst:143 -msgid "General" -msgstr "" - -#: ../components/forms.rst:145 -msgid "**Label** - This is the title of your field, telling the visitor what you'd like them to enter in the field. The label shows before the Form field by default." -msgstr "" - -#: ../components/forms.rst:147 -msgid "**Show label?** - When No, Mautic won't display the label on the Form." -msgstr "" - -#: ../components/forms.rst:149 -msgid "**Save result** - When No, Mautic won't save the data entered in the Form to the Form submissions table. When Yes, the submissions are accessible in the Form submission results. If mapped to a Contact field, Mautic still saves the data to that field." -msgstr "" - -#: ../components/forms.rst:151 -msgid "**Default value** - This allows the marketer to provide a default value for a field. The default value is useful when setting a value as a hidden field, or when you expect the visitor to enter a certain value. The Contact can change the default value when they complete the Form if the field is visible." -msgstr "" - -#: ../components/forms.rst:153 -msgid "**Help message** - This allows the marketer to add information for the visitor about what they should enter in the field, or why they should provide the information." -msgstr "" - -#: ../components/forms.rst:155 -msgid "**Input placeholder** - This allows the marketer to add text within the Form field, which gives the visitor an idea of what they should enter. The text disappears as soon as they click into the field, whereas default values don't. This can be particularly helpful in prompting the visitor if you require the data in a particular format, for example ``@Twitter`` for a Twitter account, including the ``@`` symbol." -msgstr "" - -#: ../components/forms.rst:158 -msgid "Mapped field" -msgstr "" - -#: ../components/forms.rst:160 -msgid "The mapped field tab allows the marketer to connect a field with an existing Contact or Company field in Mautic. This allows the data from the Form submission to automatically populate into the mapped field. Without the mapping, this information won't save in the Contact profile." -msgstr "" - -#: ../components/forms.rst:162 -msgid "The data type for the Form field should match the data type of the mapped field. For example, a date/time field should map to a Contact or Company field which uses the date/time field." -msgstr "" - -#: ../components/forms.rst:165 -msgid "Validation" -msgstr "" - -#: ../components/forms.rst:167 -msgid "The validation tab allows you to set whether the field is mandatory or not. If the field is mandatory and it's not completed by the visitor, the Form displays an error and the visitor sees a message informing them that they must complete the field before submitting the Form." -msgstr "" - -#: ../components/forms.rst:169 -msgid "Switch the slider to ``Yes`` to make the field mandatory." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing Form validation" -msgstr "" - -#: ../components/forms.rst:175 -msgid "It's also possible to add a validation message specific to this field, giving the visitor a prompt when they submit the Form and haven't included this field." -msgstr "" - -#: ../components/forms.rst:178 -msgid "Properties" -msgstr "" - -#: ../components/forms.rst:180 -msgid "The properties tab won't show on every field type. Different field types have different associated properties to configure." -msgstr "" - -#: ../components/forms.rst:183 -msgid "CAPTCHA" -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing CAPTCHA Form properties" -msgstr "" - -#: ../components/forms.rst:189 -msgid "With a CAPTCHA field, the answer field should be blank if you are using this as a honeypot to trap spam submissions. This hides the field, and spambots try to populate the field with data." -msgstr "" - -#: ../components/forms.rst:191 -msgid "Mautic recognizes if there's data in a honeypot CAPTCHA field and understands that it can't be a human submitting the Form." -msgstr "" - -#: ../components/forms.rst:193 -msgid "To have a human answer a basic question or statement - for example ``What's 2+2`` or ``Enter 'CAPTCHA' here`` - you would enter the expected input in the answer field, in this case, ``4`` or ``CAPTCHA``. The field's label should be the question, or you can use the label CAPTCHA and then have the question as the input placeholder." -msgstr "" - -#: ../components/forms.rst:195 -msgid "The custom error message allows you to display something which informs the human if they have entered the wrong information. The default message is ``The answer to \"{label}\" is incorrect. Please try again``." -msgstr "" - -#: ../components/forms.rst:198 -msgid "Checkbox group, radio group and select" -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing checkbox field values with a mapped custom field" -msgstr "" - -#: ../components/forms.rst:204 -msgid "With the checkbox, radio box and select fields, the properties tab allows you to choose what should be available for the visitor to select." -msgstr "" - -#: ../components/forms.rst:206 -msgid "If you have mapped the Form field to a Custom Field in Mautic, there is also the option to use the values provided in the Custom Field rather than listing them separately. This helps to prevent duplication and errors in the Form options." -msgstr "" - -#: ../components/forms.rst:208 -msgid "If you prefer to create your own field options, the ``Optionlist`` allows you to add options with a label and value pair." -msgstr "" - -#: ../components/forms.rst:210 -msgid "The label field controls the display of the field to the visitor completing the Form, and the value field controls the data saved to the database and stored against the Contact record. While they often match this might not always be the case. For example with a GDPR checkbox, the label might be ``Yes I accept that I may receive Email communications from this Company`` whereas the value stored to the database may be ``Yes`` or ``1``." -msgstr "" - -#: ../components/forms.rst:212 -msgid "In select fields, there are two additional settings to allow for setting the Empty Value - which serves the same purpose as the Input Placeholder and isn't saved to the database - and to determine whether to allow multiple values, which changes the field from ``Select`` to ``Select - Multiple``." -msgstr "" - -#: ../components/forms.rst:215 -msgid "Description area" -msgstr "" - -#: ../components/forms.rst:217 -msgid "Use the text entry field in the properties tab of the Description field to enter the information you would like to show with the Form - for example why the visitor should complete the Form. Often this information might display on the website, but you can also include it in the Form itself with this field." -msgstr "" - -#: ../components/forms.rst:220 -msgid "File" -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing file upload properties" -msgstr "" - -#: ../components/forms.rst:226 -msgid "When uploading a file within a Form there are several options under the properties tab:" -msgstr "" - -#: ../components/forms.rst:228 -msgid "Allowed file extensions: it's possible to set the file extensions permitted by providing a comma separated list." -msgstr "" - -#: ../components/forms.rst:229 -msgid "Maximum file size: the maximum size of attachment - also limited by server settings." -msgstr "" - -#: ../components/forms.rst:230 -msgid "Public accessible link to download: can you access the file via a public link?" -msgstr "" - -#: ../components/forms.rst:231 -msgid "Set as Contact profile image: set the image uploaded to be their Contact avatar" -msgstr "" - -#: ../components/forms.rst:234 -msgid "Attributes" -msgstr "" - -#: ../components/forms.rst:236 -msgid "Attributes are CSS tags which change the styling of a particular Form." -msgstr "" - -#: ../components/forms.rst:239 -msgid "Setting the Render Style to No on the Form means that Mautic ignores the styling in these fields." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the attributes for a checkbox group" -msgstr "" - -#: ../components/forms.rst:245 -msgid "**Field HTML name**: this is the machine name of the field, populated automatically from the label. You can customise this field if the label is long. You reference this field is when connecting Mautic Forms to other Forms, or when using the Manual Copy function to manually add the Form to your website or app." -msgstr "" - -#: ../components/forms.rst:246 -msgid "**Label attributes**: this field changes the way the label text appears. You should use the format ``style=\"attribute: descriptor\"`` to change the style. For example, to change the label to red, use ``style=\"color: red\"`` or ``style=\"color: #ff0000\"``." -msgstr "" - -#: ../components/forms.rst:247 -msgid "**Input attributes**: changes the way any text inside the Form field appears. This applies to the input placeholder text, text entered by the visitor submitting the Form, and the options for the select fields when Allow Multiple is Yes - including List - Country." -msgstr "" - -#: ../components/forms.rst:248 -msgid "**Field container attributes**: this changes the Form field. Use this to change the size of the box, fill color, rounded edges, or any other properties of the actual field." -msgstr "" - -#: ../components/forms.rst:249 -msgid "**Radio/Check box label attributes**: similar to input attributes, when available this field allows you to customize the way that radio buttons and checkboxes appear." -msgstr "" - -#: ../components/forms.rst:252 -msgid "Behavior" -msgstr "" - -#: ../components/forms.rst:255 -msgid "Text" -msgstr "" - -#: ../components/forms.rst:257 -msgid "The Behavior tab helps marketers to improve the experience for the visitor completing the Form. It also helps marketers implement progressive profiling, to gather more data from the Contact which helps in optimized personalization." -msgstr "" - -#: ../components/forms.rst:259 -msgid "**Show when value exists**: if Mautic knows the Contact and they're tracked, when a value exists for a field Mautic hides the field when this setting is No. This prevents the Contact answering the same question multiple times. You may want to display the field even if it's already known when you want to ensure you have the most up to date information about the Contact." -msgstr "" - -#: ../components/forms.rst:260 -msgid "**Show after X submissions**: this allows the marketer to show certain fields only when the Contact has submitted the Form a specified number of times. Enter a value between ``1`` and ``200``. When left undefined, the field shows every time the Contact views the Form. The goal is to minimize the number of fields shown to the Contact, so it's recommended to hide fields if it's not necessary to verify the values." -msgstr "" - -#: ../components/forms.rst:261 -msgid "**Auto-fill data**: this allows you to pre-populate Contact data with known Contacts where the information exists in the Contact profile. Auto-fill works with Mautic Landing Pages, and data won't pre-populate when placing the Form anywhere else. Even if you're hiding this field, you may wish to turn on auto-fill to ensure saving of the information with the Form submission." -msgstr "" - -#: ../components/forms.rst:264 -msgid "Field order" -msgstr "" - -#: ../components/forms.rst:266 -msgid "To change the order of fields on your Form:" -msgstr "" - -#: ../components/forms.rst:268 -msgid "Click the field you would like to move" -msgstr "" - -#: ../components/forms.rst:269 -msgid "Drag the field to a new location" -msgstr "" - -#: ../components/forms.rst:272 -msgid "Form actions" -msgstr "" - -#: ../components/forms.rst:274 -msgid "You may want to trigger certain actions to happen immediately after Form submission - this is what Form actions are for. This might include communications with the Contact, tracking, internal notifications, or other Contact management tasks." -msgstr "" - -#: ../components/forms.rst:277 -msgid "The Form actions available in Mautic are also available in Standalone Forms, which include more options as they're not associated with Campaigns. Campaigns tend to trigger most actions through Campaign actions so Forms associated with Campaigns only have a basic set of Form actions." -msgstr "" - -#: ../components/forms.rst:279 -msgid "**Add to Company's Score**: if a Contact associated with a Company record in Mautic has submitted the Form, you can add or subtract Points to the Company's overall score. Company scoring in Mautic doesn't aggregate Points for all its associated Contacts. Any actions that you want to contribute to a Company's score must be explicitly set. Negative numbers are valid if you want to subtract from a Company's score based on a Contact submitting a Form. If the Contact isn't tracked and the Form doesn't include a field mapped to Company or Company Name - on the Company object - the Company has no Points awarded." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the add to Company score Form action." -msgstr "" - -#: ../components/forms.rst:285 -msgid "**Adjust Contact's Points**: this action allows you to add, subtract, multiply or divide a Contact's score. Select the operator and the amount to change the Points by - for example: add 10, subtract 5, multiply by 3, divide by 2. If the Form is collecting information which doesn't identify the Contact, Mautic saves the Points to the anonymous Contact record. If that anonymous Contact record converts to or merges with a know Contact record based on some identifying event such as a Form submission, the Points stay with the Contact." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the adjust Contact score Form action." -msgstr "" - -#: ../components/forms.rst:291 -msgid "**Modify Contact's Segments**: this action allows you to change a Contact's Segment membership when they submit a Form. Type in the name of the Segment to add the Contact to or remove the Contact from. You can use both fields at the same time, and can include multiple Segments in either or both fields." -msgstr "" - -#: ../components/forms.rst:293 -msgid "Dynamic Segments based on filters update based on information in the Contact record automatically - you don't need add them to the Segment in a Form action." -msgstr "" - -#: ../components/forms.rst:295 -msgid "Typically you would use a Form action to populate static Segments - Segments which don't have any filters set. An example of when you might want to remove a Contact from a Segment in a Form action is for an event registration. You can build a filter-based Segment for the invitation Campaign, but once the Contact submits the registration Form you remove them from that Segment and added to a Segment for event attendees, so that they don't receive any more invitation Emails." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the modify Contact's Segments Form action." -msgstr "" - -#: ../components/forms.rst:301 -msgid "**Modify Contact's Tags**: if you use Tags in Mautic, you might want to add or remove Tags from a Contact following a Form submission. To add or remove a Tag you have used before, select the Tag from the list displayed when clicking into the field. To find a Tag, start to type the name in the box. To add a new Tag, type the full name and press Enter on your keyboard to save the Tag." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the modify Contact's Tags Form action." -msgstr "" - -#: ../components/forms.rst:307 -msgid "**Record UTM Tags**: if the Page your Form is on has UTM tags, whether it's a Mautic Landing Page or an external website, Mautic can record those UTM Tags and save them to the Contact record for reporting. This is useful if you want to run Reports on where your new Contacts and Form submissions are originating from." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the record UTM Tags Form action." -msgstr "" - -#: ../components/forms.rst:315 -msgid "**Remove Contact from Do Not Contact list**: this Form action allows you to remove a Contact from the Do Not Contact list when they submit a Form. Use this if a Contact has at some time unsubscribed from your Email list, and by filling out the Form, are giving you permission to Email them again." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the remove from Do Not Contact list Form action." -msgstr "" - -#: ../components/forms.rst:323 -msgid "**Download an Asset**: this option triggers an immediate download of the selected file when the Contact submits the Form. If you use Categories to organize your Assets, you can elect to have them download the most recently published Asset in a selected Category. If you prefer, you can link to a specific Asset." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the download an Asset Form action." -msgstr "" - -#: ../components/forms.rst:329 -msgid "**POST results to another Form**: use this option to connect your Mautic Form with some other Form. You may have Forms in other tools which you use for tracking and reporting, or back-end Forms triggering software instance creation." -msgstr "" - -#: ../components/forms.rst:331 -msgid "Enter the URL where the Form should post to, and Email address/s for anyone who should receive error notifications. If the Form you are posting to is behind a firewall, also enter the authorization header. If the field aliases - machine names - for any fields don't match, enter the alias the other Form uses for any fields on the Mautic Form." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the post to another Form action." -msgstr "" - -#: ../components/forms.rst:337 -msgid "**Push Contact to Integration**: once a Contact submits the Form, you may need to push them into another piece of software you are using for Contact management - such as a CRM. Ensure that the Plugin you want to use to push the Contacts is already configured and published, then select it in the dropdown field." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the push to Integration Form action." -msgstr "" - -#: ../components/forms.rst:343 -msgid "**Send Email to Contact**: to directly Email the Contact after they submit the Form, use this option. Select a Template Email from the list, or click New Email to build a new one. After selecting an Email, you can also make edits to the Email in a popup window and preview the Email." -msgstr "" - -#: ../components/forms.rst:None -#: ../components/forms.rst:None -msgid "Screenshot showing the send Email to User Form action." -msgstr "" - -#: ../components/forms.rst:349 -msgid "**Send Email to User**: to Email an internal User of Mautic after a Contact submits a Form. Select the Mautic User from the dropdown. Similar to the Send Email to Contact option, select the Template Email or create a new one. Mautic replaces any tokens in the display with the data from the Contact, not the User." -msgstr "" - -#: ../components/forms.rst:355 -msgid "**Send Form results**: this feature is commonly used for the purposes of a notification when a Contact submits a Form. It can also send a notification to the Contact of the data provided. Be sure to customize the subject line to state which Form the submission relates to. The Reply to Contact option sets the ``reply-to`` address to the Contact's address, so that if the notification is sent to your team, replying will go to the Contact automatically." -msgstr "" - -#: ../components/forms.rst:357 -msgid "If you have Contact Owners set in Mautic, you can also send the notification directly to the Contact's owner. It's also possible to send a copy of the Email to the Contact." -msgstr "" - -#: ../components/forms.rst:359 -msgid "You can style the message itself as you like, and you can click to insert the submitted values from the Form using tokens. You must add the fields to the Form before creating the action. If adding new fields after creating the Form action, edit the Form action and add the new tokens to the Email." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the send Form results action." -msgstr "" - -#: ../components/forms.rst:368 -msgid "Adding Forms to Pages" -msgstr "" - -#: ../components/forms.rst:372 -msgid "There are several ways to add your Mautic Forms to Landing Pages or Websites." -msgstr "" - -#: ../components/forms.rst:377 -msgid "Shortcodes" -msgstr "" - -#: ../components/forms.rst:381 -msgid "When working with Mautic Landing Pages or common Content Management Systems (CMS) including **Drupal**, **Joomla!** or **WordPress**, you can use a shortcode. In each case, replace ``ID#`` with the Mautic Form's ID number, found in the list of Forms or when viewing or editing a Form, the ID is at the end of the URL. This option uses JavaScript, which means that your embedded Form is always up to date with any changes made on your Mautic Form." -msgstr "" - -#: ../components/forms.rst:383 -msgid "**Mautic Landing Page**: ``{form= ID#}``" -msgstr "" - -#: ../components/forms.rst:384 -msgid "**Drupal 7.x**: ``{mauticform id =ID# width=300 px height=300 px}`` - be sure to change the width and height to the appropriate size for your website." -msgstr "" - -#: ../components/forms.rst:387 -msgid "This shortcode doesn't work for Drupal 8.x - it's recommended to use the Automatic Copy option instead." -msgstr "" - -#: ../components/forms.rst:389 -msgid "**Joomla!**: ``{mauticform ID#}``" -msgstr "" - -#: ../components/forms.rst:390 -msgid "**WordPress**: ``[mautic type=\"form\" id=ID#]``" -msgstr "" - -#: ../components/forms.rst:393 -msgid "Automatic copy" -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the options for embedding a Mautic Form." -msgstr "" - -#: ../components/forms.rst:399 -msgid "The Automatic option for embedding Mautic Forms uses JavaScript and ensures that the Forms on your website are always up to date with what you have set in Mautic. If you make changes to the Form in Mautic, you don't have to worry about re-copying the Form code everywhere you use the Form. Features including auto-fill and progressive profiling **only** works with the Automatic option." -msgstr "" - -#: ../components/forms.rst:402 -#: ../components/forms.rst:428 -msgid "Before copying the code to embed your Mautic Forms, ensure that you are on the correct domain name - not a staging area or internal reference for example - as the Form embed code references the URL." -msgstr "" - -#: ../components/forms.rst:405 -msgid "Via JavaScript" -msgstr "" - -#: ../components/forms.rst:407 -msgid "Other than using shortcodes with a CMS Plugin, this is the recommended method for embedding your Mautic Forms. Copy the line of code in the box and paste it into your website where you want the Form to display." -msgstr "" - -#: ../components/forms.rst:412 -msgid "Via IFrame" -msgstr "" - -#: ../components/forms.rst:416 -msgid "IFrames can be more difficult to use, and blocking by browsers is more likely, however there are sometimes where using an IFrame is preferable. Be sure to adjust the width and height for the space required to fit the Form. The visitor may need to scroll within the IFrame depending on the resolution of their browser. It's possible to display an error message in the event that the visitor's browser doesn't support IFrames, by editing the text between the ``

`` and ``

`` tags before copying the code and pasting it into your website." -msgstr "" - -#: ../components/forms.rst:419 -msgid "Manual copy" -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the options for manually embedding a Mautic Form." -msgstr "" - -#: ../components/forms.rst:425 -msgid "The manual copy option does provide more flexibility to extend Forms with JavaScript snippets and custom styling, however it's a manual process and any changes made within Mautic after copying the code won't be automatically reflected on your website unless you re-copy and paste the new HTML code." -msgstr "" - -#: ../components/forms.rst:430 -msgid "Copy the JavaScript code in the first box, and paste it into the head or body of your page. If you have multiple Mautic Forms on the same page, add this once only." -msgstr "" - -#: ../components/forms.rst:431 -msgid "Copy the HTML code in the second box, and paste it where you wish to display the Form." -msgstr "" - -#: ../components/forms.rst:432 -msgid "If you have Render Style set to Yes in the Form, the code includes the styling. If you have Render Style set to No, there is no styling included with the code, and the Form styling comes from the CSS from your website." -msgstr "" - -#: ../components/forms.rst:437 -msgid "Creating conditional Form fields" -msgstr "" - -#: ../components/forms.rst:441 -msgid "Mautic allows you to create conditional fields within Forms. This allows you to manage a set of dependencies between fields, so that the fields display only with certain conditions." -msgstr "" - -#: ../components/forms.rst:443 -msgid "To create conditional fields, you must first create any :doc:`/contacts/custom_fields` and use these fields within a Form." -msgstr "" - -#: ../components/forms.rst:448 -msgid "Creating Custom Fields" -msgstr "" - -#: ../components/forms.rst:452 -msgid "Using an example of wanting to show specific types of car based on the manufacturer, you would create the following custom fields:" -msgstr "" - -#: ../components/forms.rst:454 -msgid "**Car manufacturer**: this field should be of the Select data type. In this example, the options for this field are Ford, Nissan, Peugeot, and Fiat." -msgstr "" - -#: ../components/forms.rst:455 -msgid "**Ford cars**: this field should be of the Select - Multiple data type. In this example, the available options for this field are Focus, Mustang, Fiesta, and Galaxy." -msgstr "" - -#: ../components/forms.rst:458 -msgid "Adding conditional fields to a Mautic Form" -msgstr "" - -#: ../components/forms.rst:460 -msgid "Once you have created the required Custom Fields, add the parent field to the Form as detailed previously, and add the relevant information in the tabs." -msgstr "" - -#: ../components/forms.rst:463 -msgid "When using conditional fields, only ``Select``, ``Select - Multiple`` and ``Boolean`` field types are valid as the parent field." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the parent field for a conditional field on a Mautic Form" -msgstr "" - -#: ../components/forms.rst:469 -msgid "If you have defined the values in the Custom Field, turn the first switch to Yes to use those values. Otherwise, create the labels and values in the Properties tab. You can also associate the Form field with a Contact field where appropriate." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing the configuration of a parent field" -msgstr "" - -#: ../components/forms.rst:475 -msgid "Once saved, an option displays to add a conditional field." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing option to add a field based on the value of an existing field" -msgstr "" - -#: ../components/forms.rst:481 -msgid "In this example, select the ``Checkbox Group`` option, and under the Condition tab, choose ``including`` and ``Ford``." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing selection of parent field" -msgstr "" - -#: ../components/forms.rst:487 -msgid "This means that when the visitor selects Ford, the Form displays this field." -msgstr "" - -#: ../components/forms.rst:489 -msgid "There are two options:" -msgstr "" - -#: ../components/forms.rst:491 -msgid "**including**: if you want the child field to appear only if the selected value on the Form for the parent field **does match** the value/s specified" -msgstr "" - -#: ../components/forms.rst:492 -msgid "**excluding**: if you want the child field to appear only if the selected value on the Form for the parent field **doesn't match** the value/s specified" -msgstr "" - -#: ../components/forms.rst:494 -msgid "It's possible to set Any value to Yes, then the child field shows for any value of the parent field. This removes the filters to select an option." -msgstr "" - -#: ../components/forms.rst:496 -msgid "Map the field to a Contact field as appropriate, and under the Properties tab, either select to use the options in the Custom Field, or specify labels and options." -msgstr "" - -#: ../components/forms.rst:498 -msgid "Once saved, the Form displays the conditional field nested underneath the parent field." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing child field nested underneath the parent field" -msgstr "" - -#: ../components/forms.rst:505 -msgid "Blocking Form submissions from specified domains" -msgstr "" - -#: ../components/forms.rst:507 -msgid "Sometimes it's necessary to block certain domains from submitting Forms - for example to restrict access to proprietary content and reduce the volume of unqualified leads." -msgstr "" - -#: ../components/forms.rst:510 -msgid "Configuring blocked domains" -msgstr "" - -#: ../components/forms.rst:512 -msgid "To configure globally blocked domains - applying to all Forms in your Mautic instance - go to the Forms section in :doc:`/configuration/settings`." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing global domain blocking" -msgstr "" - -#: ../components/forms.rst:518 -msgid "Specify domains, one per line, using either full Email addresses or entire domains using an asterisk before the domain name, which acts as a wildcard. Ensure you save your changes." -msgstr "" - -#: ../components/forms.rst:522 -msgid "Applying domain name filtering to a Form" -msgstr "" - -#: ../components/forms.rst:524 -msgid "To apply domain name filtering on a Mautic Form, add an Email field to the Form - after setting up the domain exclusions in the previous step - and under the Validation tab, set the Domain name submission filter switch to Yes." -msgstr "" - -#: ../components/forms.rst:None -msgid "Screenshot showing domain blocking used in a Mautic Form" -msgstr "" - -#: ../components/forms.rst:530 -msgid "It's advised to provide a helpful message to display if the visitor tries to use an Email address from a blocked domain, to help them understand what the problem is." -msgstr "" - -#: ../components/landing_pages.rst:4 -msgid "Landing Pages" -msgstr "" - -#: ../components/landing_pages.rst:7 -msgid "Customizing the Preference Center" -msgstr "" diff --git a/docs/docs_translations/configuration.pot b/docs/docs_translations/configuration.pot deleted file mode 100644 index a569b9c8..00000000 --- a/docs/docs_translations/configuration.pot +++ /dev/null @@ -1,2197 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../configuration/command_line_interface.rst:4 -msgid "Command Line Interface (CLI) commands" -msgstr "" - -#: ../configuration/command_line_interface.rst:8 -msgid "Mautic may require you to use the command line (CLI). Listed below are the available CLI commands." -msgstr "" - -#: ../configuration/command_line_interface.rst:12 -msgid "You can find this list (and others - for example commands relating to Doctrine and other vendors) by running this command: ``bin/console``" -msgstr "" - -#: ../configuration/command_line_interface.rst:14 -msgid "You must be in the Mautic root directory to run the CLI commands." -msgstr "" - -#: ../configuration/command_line_interface.rst:16 -msgid "**Format**: command [options] [arguments]" -msgstr "" - -#: ../configuration/command_line_interface.rst:19 -#: ../configuration/command_line_interface.rst:27 -msgid "Options" -msgstr "" - -#: ../configuration/command_line_interface.rst:28 -#: ../configuration/command_line_interface.rst:187 -msgid "Description" -msgstr "" - -#: ../configuration/command_line_interface.rst:29 -msgid "-h, \\--help" -msgstr "" - -#: ../configuration/command_line_interface.rst:30 -msgid "Display this help message" -msgstr "" - -#: ../configuration/command_line_interface.rst:31 -msgid "-q, \\--quiet" -msgstr "" - -#: ../configuration/command_line_interface.rst:32 -msgid "Do not output any message" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "V, \\--version" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "\\--ansi" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "\\--no-ansi" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "Display this app version" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "Force ANSI output" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "Disable ANSI output" -msgstr "" - -#: ../configuration/command_line_interface.rst:39 -msgid "-n, \\--no-interaction" -msgstr "" - -#: ../configuration/command_line_interface.rst:40 -msgid "Do not ask any interactive question" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "-s, \\--shell" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "\\--process-isolation" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "Launch the shell." -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "Launch commands from shell as a separate process." -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "-e, \\--env=ENV" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "\\--no-debug" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "The Environment name. [default: \"prod\"]" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "Switches off debug mode." -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "-v" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "-vv" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "-vvv" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "\\--verbose" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "Increase the verbosity of messages:" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "1. for normal output," -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "2. for more verbose output and" -msgstr "" - -#: ../configuration/command_line_interface.rst:0 -msgid "3. for debug" -msgstr "" - -#: ../configuration/command_line_interface.rst:62 -msgid "Mautic commands" -msgstr "" - -#: ../configuration/command_line_interface.rst:63 -msgid "These are the commands you may need to use in relation to your Mautic instance. Add a ``bin/console`` before Mautic command." -msgstr "" - -#: ../configuration/command_line_interface.rst:65 -msgid "**Example**" -msgstr "" - -#: ../configuration/command_line_interface.rst:180 -msgid "Doctrine commands" -msgstr "" - -#: ../configuration/command_line_interface.rst:186 -msgid "Command" -msgstr "" - -#: ../configuration/command_line_interface.rst:188 -msgid "``doctrine:fixtures:load``" -msgstr "" - -#: ../configuration/command_line_interface.rst:189 -msgid "Installs Mautic sample data, overwriting existing data." -msgstr "" - -#: ../configuration/cron_jobs.rst:4 -msgid "Cron jobs" -msgstr "" - -#: ../configuration/cron_jobs.rst:10 -msgid "Mautic 3 introduced a new path for cron jobs ``bin/console`` - if you are using the legacy Mautic 2.x series you should replace this with the older version, ``app/console``" -msgstr "" - -#: ../configuration/cron_jobs.rst:12 -msgid "Mautic requires a few :xref:`cron jobs` to handle some maintenance tasks such as updating Contacts or Campaigns, executing Campaign Actions, sending Emails, and more. You must manually add the required cron jobs to your server. Most web hosts provide a means to add cron jobs either through SSH, cPanel, or another custom panel. Please consult your host's documentation/support if you are unsure on how to set up cron jobs." -msgstr "" - -#: ../configuration/cron_jobs.rst:17 -msgid "If you're new to Linux or Cron Jobs, then the Apache Foundation has :xref:`an excellent guide` which you should read before asking questions via the various support Channels." -msgstr "" - -#: ../configuration/cron_jobs.rst:19 -msgid "When setting up cron jobs, you must choose how often you want the cron jobs to run. Many shared hosts prefer that you run scripts every 15 or 30 minutes and may even override the scheduled times to meet these restrictions. Consult your host's documentation if they have such a restriction." -msgstr "" - -#: ../configuration/cron_jobs.rst:21 -msgid "**It's HIGHLY recommended that you stagger the following required jobs so as to not run the exact same minute.**" -msgstr "" - -#: ../configuration/cron_jobs.rst:23 -msgid "For instance:" -msgstr "" - -#: ../configuration/cron_jobs.rst:32 -msgid "Required" -msgstr "" - -#: ../configuration/cron_jobs.rst:34 -msgid "Mautic needs some mandatory cron jobs to run on a regular basis as follows:" -msgstr "" - -#: ../configuration/cron_jobs.rst:37 -msgid "Segment cron jobs" -msgstr "" - -#: ../configuration/cron_jobs.rst:39 -msgid "**To keep the Segments current:**" -msgstr "" - -#: ../configuration/cron_jobs.rst:45 -#: ../configuration/cron_jobs.rst:62 -msgid "By default, the script processes Contacts in batches of 300. If this is too many for your server's resources, use the option ``--batch-limit=X`` replacing X with the number of Contacts to process each batch." -msgstr "" - -#: ../configuration/cron_jobs.rst:47 -#: ../configuration/cron_jobs.rst:64 -msgid "You can also limit the number of Contacts to process per script execution using ``--max-contacts`` to further limit resources used." -msgstr "" - -#: ../configuration/cron_jobs.rst:52 -msgid "Campaign cron jobs" -msgstr "" - -#: ../configuration/cron_jobs.rst:56 -msgid "**To keep Campaigns updated with applicable Contacts:**" -msgstr "" - -#: ../configuration/cron_jobs.rst:66 -msgid "**To execute Campaigns events:**" -msgstr "" - -#: ../configuration/cron_jobs.rst:72 -msgid "By default, the script processes Contacts in batches of 100. If this is too many for your server's resources, use the option ``--batch-limit=X`` replacing X with the number of events to process each batch." -msgstr "" - -#: ../configuration/cron_jobs.rst:74 -msgid "You can also limit the number of Contacts to process per script execution using ``--max-events`` to further limit resources used." -msgstr "" - -#: ../configuration/cron_jobs.rst:78 -msgid "**To send frequency rules rescheduled marketing Campaign messages:** Messages marked as *Marketing Messages* - such as Emails as part of a marketing Campaign - get held in a message queue IF frequency rules are setup as either system wide or per Contact. To process this queue and reschedule sending these messages, add this cron job:" -msgstr "" - -#: ../configuration/cron_jobs.rst:82 -msgid "``mautic:messages:send``" -msgstr "" - -#: ../configuration/cron_jobs.rst:86 -msgid "that these messages are only added to the queue when frequency rules apply either system wide or per Contact." -msgstr "" - -#: ../configuration/cron_jobs.rst:89 -msgid "Optional" -msgstr "" - -#: ../configuration/cron_jobs.rst:91 -msgid "Depending on your server configuration, you can set up additional cron jobs that are optional for tasks such as sending Emails, importing Contacts, and more. The optional cron jobs are as follows:" -msgstr "" - -#: ../configuration/cron_jobs.rst:96 -msgid "Process Email queue cron job" -msgstr "" - -#: ../configuration/cron_jobs.rst:100 -msgid "If the system configuration is queueing Emails, a cron job processes them." -msgstr "" - -#: ../configuration/cron_jobs.rst:109 -msgid "Fetch and process Monitored Email cron job" -msgstr "" - -#: ../configuration/cron_jobs.rst:113 -msgid "If you are using Bounce Management, set up the following command to fetch and process messages:" -msgstr "" - -#: ../configuration/cron_jobs.rst:122 -msgid "Social Monitoring cron job" -msgstr "" - -#: ../configuration/cron_jobs.rst:126 -msgid "If you are using Social Monitoring, add the following command to your cron configuration:" -msgstr "" - -#: ../configuration/cron_jobs.rst:135 -msgid "Import Contacts cron job" -msgstr "" - -#: ../configuration/cron_jobs.rst:139 -msgid "To import an especially large number of Contacts or Companies in the background, use the following command:" -msgstr "" - -#: ../configuration/cron_jobs.rst:145 -msgid "The time taken for this command to execute depends on the number of Contacts in the CSV file. However, on successful completion of the import operation, a notification appears on the Mautic dashboard." -msgstr "" - -#: ../configuration/cron_jobs.rst:148 -msgid "Webhooks cron job" -msgstr "" - -#: ../configuration/cron_jobs.rst:150 -msgid "If the Mautic configuration settings include Webhook batch processing, use the following command to send the payloads:" -msgstr "" - -#: ../configuration/cron_jobs.rst:161 -msgid "Update MaxMind GeoLite2 IP database cron job" -msgstr "" - -#: ../configuration/cron_jobs.rst:165 -msgid "Mautic uses :xref:`MaxMind's` GeoLite2 IP database by default. The database license is :xref:`Creative Commons Attribution-ShareAlike 3.0 Unported License` and thus Mautic can't include it within the installation package. It's possible to download the database manually through Mautic's Configuration or automatically using the following script. MaxMind updates their database the first Tuesday of the month." -msgstr "" - -#: ../configuration/cron_jobs.rst:175 -msgid "Clean up old data cron job" -msgstr "" - -#: ../configuration/cron_jobs.rst:177 -msgid "Clean up a Mautic installation by purging old data. Note that you can't purge some types of data within Mautic. Currently supported are audit log entries, visitors - anonymous Contacts - and visitor Landing Page hits. Use ``--dry-run`` to view the number of records impacted before making any changes." -msgstr "" - -#: ../configuration/cron_jobs.rst:180 -msgid "Use the ``--gdpr`` flag to delete data to fulfill GDPR European regulation. This deletes Contacts that have been inactive for 3 years." -msgstr "" - -#: ../configuration/cron_jobs.rst:182 -msgid "**This permanently deletes data. Be sure to verify database backups before using as appropriate.**" -msgstr "" - -#: ../configuration/cron_jobs.rst:189 -msgid "MaxMind CCPA compliance cron job" -msgstr "" - -#: ../configuration/cron_jobs.rst:191 -msgid "MaxMind requires Users to keep a \"Do Not Sell\" list up to date, and remove all data relating to those IP addresses in the past from MaxMind." -msgstr "" - -#: ../configuration/cron_jobs.rst:193 -msgid "See more details in the official :xref:`MaxMind website`." -msgstr "" - -#: ../configuration/cron_jobs.rst:195 -msgid "It's recommended to run these two commands once per week, one after another." -msgstr "" - -#: ../configuration/cron_jobs.rst:201 -msgid "This command downloads the database of Do Not Sell IP addresses from MaxMind." -msgstr "" - -#: ../configuration/cron_jobs.rst:207 -msgid "This command finds data in the database loaded from MaxMind's Do Not Sell IP addresses and deletes the data." -msgstr "" - -#: ../configuration/cron_jobs.rst:212 -msgid "Send scheduled broadcasts (Segment Emails) cron job" -msgstr "" - -#: ../configuration/cron_jobs.rst:216 -msgid "Starting with Mautic 2.2.0, it's now possible to use cron to send scheduled broadcasts for Channel communications. The current only implementation of this is for Segment Emails. Instead of requiring a manual send and wait with the browser window open while AJAX batches over the send, it's possible to use a command to initiate the process." -msgstr "" - -#: ../configuration/cron_jobs.rst:218 -msgid "The caveat for this is that the Email must have a published up date and be currently published - this is to help prevent any unintentional Email broadcasts. Just as it was with the manual/AJAX process the message is only sent to Contacts who haven't already received the specific communication. This command sends messages to Contacts added to the source Segments later, so if you don't want this to happen, set an unpublish date." -msgstr "" - -#: ../configuration/cron_jobs.rst:225 -msgid "Command parameters:" -msgstr "" - -#: ../configuration/cron_jobs.rst:227 -msgid "``--channel=email`` what Channel to execute. Defaults to all Channels if none provided." -msgstr "" - -#: ../configuration/cron_jobs.rst:229 -msgid "``--id=X`` is what ID of Email, SMS or other entity to send." -msgstr "" - -#: ../configuration/cron_jobs.rst:231 -msgid "``--limit=X`` is how many Contacts to pull from the database for processing, set to 100 by default. Using this flag each time the cron fires, it processes X Contacts. The next time the cron job runs, it processes the following X Contacts, and so on." -msgstr "" - -#: ../configuration/cron_jobs.rst:233 -msgid "``--batch=X`` controls how many Emails processed in each batch. This can be different for every provider. For example, Mautic has API connection to SparkPost. Their API can send - at present - 1000 Emails per call. Therefore the batch should be 1000 for the fastest sending speed with this provider. Many SMTP providers can't handle 1000 emails in one batch, so this would need to be lower." -msgstr "" - -#: ../configuration/cron_jobs.rst:235 -msgid "``--min-contact-id`` and ``--max-contact-id`` allows the separation of Email sending by smaller chunks, by specifying contact ID ranges. If those ranges won't overlap, this allows you to run several broadcast commands in parallel." -msgstr "" - -#: ../configuration/cron_jobs.rst:240 -msgid "Send scheduled Reports cron job" -msgstr "" - -#: ../configuration/cron_jobs.rst:244 -msgid "Starting with Mautic 2.12.0, it's now possible to use cron to send scheduled Reports." -msgstr "" - -#: ../configuration/cron_jobs.rst:252 -msgid "for releases prior to 1.1.3, it's required to append ``--env=prod`` to the cron job command to ensure commands execute correctly." -msgstr "" - -#: ../configuration/cron_jobs.rst:257 -msgid "Configure Mautic Integration cron jobs" -msgstr "" - -#: ../configuration/cron_jobs.rst:261 -msgid "To perform synchronization of all Integrations and to manage Plugins, use the cron job commands in this section." -msgstr "" - -#: ../configuration/cron_jobs.rst:263 -msgid "**To fetch Contacts from the Integration:**" -msgstr "" - -#: ../configuration/cron_jobs.rst:269 -#: ../configuration/cron_jobs.rst:281 -msgid "or" -msgstr "" - -#: ../configuration/cron_jobs.rst:275 -msgid "**To push Contact activity to an Integration:**" -msgstr "" - -#: ../configuration/cron_jobs.rst:287 -msgid "These commands work with all available Plugins. To avoid performance issues when using multiple Integrations, you must specify the name of the Integration by adding the ``-integration`` suffix to the command. For instance, for integration of Mautic with HubSpot, use the following command:" -msgstr "" - -#: ../configuration/cron_jobs.rst:294 -msgid "**To install, update, turn on or turn off Plugins:**" -msgstr "" - -#: ../configuration/cron_jobs.rst:302 -msgid "you can replace ``mautic:plugins:reload`` with ``mautic:plugins:install`` or ``mautic:plugins:update``. They're the same commands with different alias." -msgstr "" - -#: ../configuration/cron_jobs.rst:306 -msgid "Tips & troubleshooting" -msgstr "" - -#: ../configuration/cron_jobs.rst:308 -msgid "If your environment provides a command-line specific build of PHP, often called ``php-cli``, you may want to use that instead of ``php`` as it has a cleaner output. On BlueHost and probably some other PHP hosts, the ``php`` command might be setup to discard the command-line parameters to ``console``, in which case you must use ``php-cli`` to make the cron jobs work." -msgstr "" - -#: ../configuration/cron_jobs.rst:310 -msgid "To assist in troubleshooting cron issues, you can pipe the output of each cron job to a specific file by adding something like ``>>/path/to/somefile.log 2>&1`` at the end of the cron job, then you can look at the contents of the file to see the output." -msgstr "" - -#: ../configuration/cron_jobs.rst:312 -msgid "If an error is occurring when running run the cron job this file provides some insight, otherwise the file is empty or has some basic stats. The modification time of the file informs you of the last time the cron job ran. You can thus use this to determine whether the cron job is running successfully and on schedule." -msgstr "" - -#: ../configuration/cron_jobs.rst:314 -msgid "In addition it's recommended to enable the non-interactive mode together with the no-ansi mode when you run your commands using cron. This way you ensure, that you have proper timestamps in your log and the output is more readable." -msgstr "" - -#: ../configuration/cron_jobs.rst:316 -msgid "Example output" -msgstr "" - -#: ../configuration/cron_jobs.rst:326 -msgid "If you have SSH access, try to run the command directly to Select for errors. If there is nothing printed from either in a SSH session or in the cron output, verify in the server's logs. If you see similar errors to ``'Warning: Invalid argument supplied for foreach()' in /vendor/symfony/console/Symfony/Component/Console/Input/ArgvInput.php:287``, you either need to use ``php-cli`` instead of ``php`` or try using ``php -d register_argc_argv=On``. `" -msgstr "" - -#: ../configuration/cron_jobs.rst:329 -msgid "Tracking script" -msgstr "" - -#: ../configuration/cron_jobs.rst:331 -msgid "After installation and setup of the :doc:`/configuration/cron_jobs` you're ready to begin tracking Contacts. You need to add a piece of JavaScript to the websites for each site you wish to track through Mautic." -msgstr "" - -#: ../configuration/cron_jobs.rst:333 -msgid "This is straightforward process, you can add this tracking script to your website template file, or install a Mautic Integration for the more common Content Management System platforms." -msgstr "" - -#: ../configuration/cron_jobs.rst:335 -msgid "Here is an example of the tracking JavaScript which you can access by clicking on **Tracking Settings** in the Global Configuration." -msgstr "" - -#: ../configuration/cron_jobs.rst:346 -msgid "You should replace the site URL, ``example.com/mautic`` with the URL to your Mautic instance in the example provided, but it's recommended to copy the whole code block from the tracking settings in your Mautic instance." -msgstr "" - -#: ../configuration/maxmind_license.rst:2 -msgid "MaxMind license" -msgstr "" - -#: ../configuration/maxmind_license.rst:4 -msgid "From the :xref:`2.16 release`, Mautic has supported using a license key to access the MaxMind IP lookup service." -msgstr "" - -#: ../configuration/maxmind_license.rst:8 -msgid "From the 3.2 release the format for the license key needs to be ``AccountID:Licensekey``. You can locate the Account ID directly preceding the license keys table." -msgstr "" - -#: ../configuration/maxmind_license.rst:10 -msgid "Follow these steps to configure your Mautic instance to use the license key." -msgstr "" - -#: ../configuration/maxmind_license.rst:12 -msgid "Create a MaxMind account by going to :xref:`MaxMind Signup`" -msgstr "" - -#: ../configuration/maxmind_license.rst:14 -msgid "After signing up, verify your Email and follow the steps to access your :xref:`MaxMind Account`." -msgstr "" - -#: ../configuration/maxmind_license.rst:16 -msgid "Click the Contact icon at the top right of the menu to login" -msgstr "" - -#: ../configuration/maxmind_license.rst:None -msgid "Screenshot of MaxMind Account" -msgstr "" - -#: ../configuration/maxmind_license.rst:22 -msgid "After logging in, under services click ``My License Key`` on the left hand side in the menu" -msgstr "" - -#: ../configuration/maxmind_license.rst:None -#: ../configuration/maxmind_license.rst:None -#: ../configuration/maxmind_license.rst:None -msgid "Screenshot of MaxMind license key" -msgstr "" - -#: ../configuration/maxmind_license.rst:28 -msgid "Then, Click ``Generate new License Key``" -msgstr "" - -#: ../configuration/maxmind_license.rst:None -msgid "Screenshot of MaxMind Generate key" -msgstr "" - -#: ../configuration/maxmind_license.rst:34 -msgid "Answer ``Will this key be used for GeoIP Update?`` with No and confirm" -msgstr "" - -#: ../configuration/maxmind_license.rst:None -msgid "Screenshot of MaxMind confirm key" -msgstr "" - -#: ../configuration/maxmind_license.rst:40 -msgid "Copy the license key that you see on the screen and note down the Account ID preceding the license key table" -msgstr "" - -#: ../configuration/maxmind_license.rst:46 -msgid "Go to Mautic > Settings > Configuration > System Settings > Miscellaneous Settings and enter the license key into the \"IP lookup service authentication\" **field in the format** ``AccountID:Licensekey``." -msgstr "" - -#: ../configuration/maxmind_license.rst:52 -msgid "Click ``Fetch IP Lookup Data Store``. This downloads the IP lookup database to your Mautic instance." -msgstr "" - -#: ../configuration/maxmind_license.rst:54 -msgid "Set up the :ref:`cron jobs` to periodically download a fresh copy." -msgstr "" - -#: ../configuration/settings.rst:2 -msgid "Mautic configuration settings" -msgstr "" - -#: ../configuration/settings.rst:4 -msgid "Proper configuration is important for branding, performance, and the User experience for your team as they do their jobs. These settings mostly don't need changing after initial configuration." -msgstr "" - -#: ../configuration/settings.rst:8 -msgid "System settings" -msgstr "" - -#: ../configuration/settings.rst:11 -msgid "General settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing General Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:17 -msgid "**Site URL** - This is where Mautic is physically installed. Set the URL for this site here. Cron jobs needs this to correctly determine absolute URLs when generating links for Emails, etc. It 's also called Mautic's 'base URL'." -msgstr "" - -#: ../configuration/settings.rst:19 -msgid "**Mautic’s root URL** - When a User signs in to their Mautic instance, they go to ``mautic.example.com``. However, that Landing Page is also accessible to the public. If a Contact visits that address, they see the Mautic login page for that instance." -msgstr "" - -#: ../configuration/settings.rst:21 -msgid "To brand that Landing Page, create a Mautic Landing Page that you’d want to greet any Contacts who visit your root ``URL``. Once you’ve done that, Users can sign in into Mautic by visiting ``mautic.example.com/s/login``." -msgstr "" - -#: ../configuration/settings.rst:23 -msgid "**404 page** - Select the Landing Page that you want to use as the 404 Landing Page. If you don’t want to use Mautic’s default 404 error page, create a custom Landing Page and select that page here. If you don’t select any page, Mautic uses the default error page." -msgstr "" - -#: ../configuration/settings.rst:26 -msgid "**Path to the cache, log, and images directory** - These are the file system paths where the cache, logs, and images are saved." -msgstr "" - -#: ../configuration/settings.rst:29 -msgid "System defaults" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing System defaults Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:35 -msgid "**Default item limit per page** - The number of Contacts, Campaigns, Emails, etc. which display on each page when you go to an item section. The default is ``10``." -msgstr "" - -#: ../configuration/settings.rst:37 -msgid "**Default timezone** - The User's default time zone, typically set to the time zone of the Company headquarters. Time zones are set for individual Users. The default is ``UTC``." -msgstr "" - -#: ../configuration/settings.rst:39 -msgid "For example: headquarters is in Boston and the default is set to ``US`` Eastern Time ``America/New York``. A User in San Francisco US Pacific Time may set ``America/Los Angeles`` to use Pacific Time in the User interface." -msgstr "" - -#: ../configuration/settings.rst:41 -msgid "**Default language** - The initial language assigned to Users. Individual Users may select their own settings. Mautic uses ``English - United States`` by default." -msgstr "" - -#: ../configuration/settings.rst:43 -msgid "**Cached data timeout (minutes)** - Mautic caches data to speed up page loads. Update this setting to change how long Mautic caches the data for. Mautic uses ``10 minutes`` as the default." -msgstr "" - -#: ../configuration/settings.rst:45 -msgid "**Date Range Filter Default** - Sets the default for how far back from the current date Mautic looks for data in Reports including Campaign and Email snapshots charts on the item page. This setting allows you to control the default for how far back from the current date Mautic looks for data. If you’ve changed the setting on a Report, Mautic uses what you’ve entered. Mautic’s default value is ``1 Month``." -msgstr "" - -#: ../configuration/settings.rst:47 -msgid "**Default format for full dates, date only, short dates, and time only** - The default setting uses the standard US time format. The letters in the boxes are PHP code. See the :xref:`PHP manual for date functions`." -msgstr "" - -#: ../configuration/settings.rst:50 -msgid "CORS settings" -msgstr "" - -#: ../configuration/settings.rst:52 -msgid "Cross-Origin Resource Sharing (CORS) enables data to pass between your website and Mautic." -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing CORS Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:58 -msgid "**Restrict Domains** - When set to No, any web page can pass information to Mautic. Select Yes to limit communication with your Mautic instance to websites listed in Valid Domains strongly recommended." -msgstr "" - -#: ../configuration/settings.rst:60 -msgid "**Valid Domains** - A list of domains allowed to communicate with your Mautic instance. In the text box, list the exact URL of the top level domain you want to allow, one per line. For example: ``http://www.example.com`` tracks any activity on non-secure example.com pages, but ``https://www.example.com`` won’t because this is only tracking on a secure (``https://``) website." -msgstr "" - -#: ../configuration/settings.rst:64 -msgid "In the Valid Domains field, don’t include a slash at the end. For example, use ``https://www.example.com`` instead of ``https://www.example.com/``." -msgstr "" - -#: ../configuration/settings.rst:67 -msgid "Miscellaneous settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Miscellaneous Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:73 -msgid "**Trusted hosts** - To explicitly allow the hosts that can send requests to Mautic. You can use regular expression and separate multiple hosts with a comma. i.e ``.*\\.?example.com$``. If left empty, Mautic will respond to all hosts." -msgstr "" - -#: ../configuration/settings.rst:75 -msgid "**Trusted proxies** - To configure the IP addresses that should be trusted as proxies. This setting is mandatory when using Mautic behind an SSL terminating proxy. Separate multiple IP addresses by a comma. i.e ``127.0.0.1, 10.0.0.0/8, fc00::/7``" -msgstr "" - -#: ../configuration/settings.rst:77 -msgid "**IP lookup service** - By default, Mautic uses :xref:`MaxMind's` database to identify the city of a website visitor, based on the location of the Internet Service Provider (ISP) for their IP address." -msgstr "" - -#: ../configuration/settings.rst:79 -msgid "**IP lookup service authentication** - To use any IP lookup service which requires authentication, enter your credentials." -msgstr "" - -#: ../configuration/settings.rst:81 -msgid "**List of IPs not to track Contacts with** - To turn off tracking for particular IP addresses, enter the addresses, one per line. Mautic doesn’t recommend adding your office IP address. If you list your internal IP address, Mautic won’t track clicks, page hits, etc., from that IP, **including when you are testing functionality**." -msgstr "" - -#: ../configuration/settings.rst:83 -msgid "**List of known Bots** - Mautic has the feature to identify and turn-off tracking for several known bots. To track activity from those bots, remove them from this list. To turn off tracking for other bots, add them here (one per line)." -msgstr "" - -#: ../configuration/settings.rst:85 -msgid "**URL Shortener** - If you use a URL shortening service like bit.ly for links in SMS messages, enter your access token here." -msgstr "" - -#: ../configuration/settings.rst:89 -msgid "For bit.ly, use the following URL structure: https://api-ssl.bitly.com/v3/shorten?access_token=[ACCESS_TOKEN]&format=txt&longUrl" -msgstr "" - -#: ../configuration/settings.rst:91 -msgid "**Item max lock time** - When a User edits a Campaign, Email, Landing Page, etc., Mautic locks the item to prevent simultaneous edits by other Users. When the initial User saves and closes or cancels out, the item may remain locked for this period of time. The default is ``0 seconds``." -msgstr "" - -#: ../configuration/settings.rst:93 -msgid "**Translate page titles** - To translate page titles in the Contact activity history from non-Latin (non-English) characters to Latin characters (English)." -msgstr "" - -#: ../configuration/settings.rst:97 -msgid "Update settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Update Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:103 -msgid "**Set the minimum stability level required for updates** - This allows you to receive notifications for early access releases. Always read the release notes before updating to an early access release. Set the minimum stability level required for updates." -msgstr "" - -#: ../configuration/settings.rst:105 -msgid "**Update Mautic through Composer [BETA]** - Set to 'Yes' if you update Mautic through Composer. This is a prerequisite if you want to install and update Plugins through the Marketplace. This becomes the default installation and update method in Mautic 5." -msgstr "" - -#: ../configuration/settings.rst:108 -msgid "Theme settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Theme Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:114 -msgid "**Default Theme** - Applies a Theme to any Form which doesn’t have a Theme already applied. If you don’t have a Landing Page for your Preference Center, but have preference settings turned on in Email settings, Mautic creates a default Preference Center page using the Form styling from the Theme selected here." -msgstr "" - -#: ../configuration/settings.rst:117 -msgid "API settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing API Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:123 -msgid "Full API documentation is available :xref:`Mautic developer API`." -msgstr "" - -#: ../configuration/settings.rst:125 -msgid "**API enabled** - Select Yes to pass data in and out of Mautic through the API." -msgstr "" - -#: ../configuration/settings.rst:127 -msgid "**Enable http basic auth?** - Enables basic authentication for Mautic’s API. It's recommended to only use this with secure sites (https)." -msgstr "" - -#: ../configuration/settings.rst:129 -msgid "**Access token lifetime** - When authorizing a new app or Integration, this setting limits how long the access token is valid (in minutes). The default is ``60`` minutes." -msgstr "" - -#: ../configuration/settings.rst:131 -msgid "For example - You add a new Integration to your SaaS platform. Enter 30 here to limit the access token validity to ``30`` minutes. If you haven’t completed the authentication in that period of time, you must revalidate." -msgstr "" - -#: ../configuration/settings.rst:133 -msgid "**Refresh token lifetime** - When using OAuth 2.0, the lifetime of the refresh token used to request a new access token once expired. Once the refresh token expires, you must reauthorize. The default is ``14`` days." -msgstr "" - -#: ../configuration/settings.rst:136 -msgid "Asset settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Assets Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:142 -msgid "**Path to the Asset directory** - Set the absolute path to the Assets upload folder. In order to prevent the public from accessing Assets, use a directory outside of the public web root." -msgstr "" - -#: ../configuration/settings.rst:144 -msgid "**Maximum size Megabytes** - Set the maximum size of uploaded Assets in Megabytes." -msgstr "" - -#: ../configuration/settings.rst:146 -msgid "**Allowed file extensions** - Extensions of files separated by commas. You can only upload files with the specified file extensions." -msgstr "" - -#: ../configuration/settings.rst:149 -msgid "Campaign settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Campaign Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:155 -msgid "**Wait time before retrying a failed action** - If for any reason a Campaign action doesn't execute, this is the length of time Mautic waits before trying again." -msgstr "" - -#: ../configuration/settings.rst:157 -msgid "**Use date range for all views** - When viewing a Campaign, the date range of actions, conditions, decisions, and Contacts displayed in the tabs is based on this setting." -msgstr "" - -#: ../configuration/settings.rst:159 -msgid "**Use summary statistics** - Improves performance when viewing a Campaign with thousands of events per day by using summarized data. When you first turn on this setting you will need to run a :ref:`cron job` to summarize existing data." -msgstr "" - -#: ../configuration/settings.rst:162 -msgid "Email settings" -msgstr "" - -#: ../configuration/settings.rst:165 -msgid "Mail send settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Mail Send Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:171 -msgid "**Name to send mail as** - The default name Emails come from. This is typically something like ``{YourCompany Marketing Team}`` or ``{YourCompany}``." -msgstr "" - -#: ../configuration/settings.rst:173 -msgid "**Email address to send mail from** - The Email address for the name you’re sending mail from. The address displays in the ``From:`` field when your Contacts receive your Emails." -msgstr "" - -#: ../configuration/settings.rst:177 -msgid "Ensure that you configure your sender domain, ``DKIM``, bounce, and click tracking domains. For more information, see the :ref:`Email` documentation." -msgstr "" - -#: ../configuration/settings.rst:179 -msgid "**Reply to address** - To have Contacts reply to a different address than the specified From address, add the desired address here. This is the default ``reply-to`` address where messages are sent from Mautic unless it is overridden in an individual Email. If this field is blank, the address specified in **Email address to send mail** from is used. The ``reply-to`` setting is useful if your configured sender domain - which you use in the from address - contains a subdomain that doesn't have MX records or is otherwise an address that can't receive Emails." -msgstr "" - -#: ../configuration/settings.rst:181 -msgid "**Custom return path (bounce) address** - Set a custom return path/bounce Email address for Emails sent from the system. Note that some mail transports, such as GMail, won't support this." -msgstr "" - -#: ../configuration/settings.rst:183 -msgid "**Mailer is owner** - If Contacts in Mautic have owners, select Yes to use the Contact owner as the sender of Emails to any Contacts they’re listed as the owner for." -msgstr "" - -#: ../configuration/settings.rst:187 -msgid "Mailer is owner overrides any other name or Email to send mail from, including the default and individual Emails. Every Contact owner’s domain must have ``SPF`` and ``DKIM`` records. You can see this configuration for individual Emails, rather than globally. For more information see :doc:`Mailer is owner`" -msgstr "" - -#: ../configuration/settings.rst:190 -msgid "**Service to send mail through** - Select the Email service provider you use, and enter your credentials." -msgstr "" - -#: ../configuration/settings.rst:193 -msgid "Default frequency rule" -msgstr "" - -#: ../configuration/settings.rst:195 -msgid "**Do not contact more than each ** - This limits the number of Marketing Messages a Contact receives in a certain period of time day, week, month. Transactional messages don’t count towards this limit. You can adjust this at the individual Contact level, either manually or by Preference Center setting." -msgstr "" - -#: ../configuration/settings.rst:199 -msgid "More information is available in the :doc:`Default Frequency Rule documentation`." -msgstr "" - -#: ../configuration/settings.rst:202 -msgid "Monitored inbox settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Monitored Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:208 -msgid "**Default Mailbox** - If your messages are going to bounce, this inbox is where you receive those bounce notifications." -msgstr "" - -#: ../configuration/settings.rst:210 -msgid "**Bounces** - A folder to monitor for new bounce messages or Emails." -msgstr "" - -#: ../configuration/settings.rst:212 -msgid "**Unsubscribe Requests** - A folder to monitor for new unsubscribe requests." -msgstr "" - -#: ../configuration/settings.rst:214 -msgid "**Contact Replies** - Similar to the monitored inbox for bounces, this is the inbox Mautic checks for Contact replies. Using :ref:`Replies to Email` decisions in any Campaign requires configuration. With ``Use custom connection settings?`` set to ``no``, Mautic checks the default mailbox. If set to ``yes``, you may track a different mailbox for replies." -msgstr "" - -#: ../configuration/settings.rst:217 -msgid "Message settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Message Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:223 -msgid "**Text for the** ``{webview_text``} **token** - The message indicating the reader can view the Email in their browser. The default is; ``Having trouble reading this Email? Click here``." -msgstr "" - -#: ../configuration/settings.rst:225 -msgid "To change the text, change the message between the ```` and ```` tags. Don't change the ``|URL|`` text, because that's a token, which creates a unique URL for each Contact." -msgstr "" - -#: ../configuration/settings.rst:227 -msgid "**Default Email signature** - The signature for your default Emails, which pairs with the name & Email address in the **Mail Send** settings." -msgstr "" - -#: ../configuration/settings.rst:229 -msgid "**Append tracking pixel into Email body?** - To track Email opens, select **Yes**. Select **No** to prevent tracking, reporting on, and using decisions based on Email opens." -msgstr "" - -#: ../configuration/settings.rst:231 -msgid "**Convert embed images to Base64** - Select **Yes** to display embedded images in Emails using embedded base64 code rather than as embedded images." -msgstr "" - -#: ../configuration/settings.rst:233 -msgid "**Disable trackable URLs** - Removes tracking from URLs in your Emails. Select Yes to prevent tracking, reporting on, and using decisions based on link clicks. Some Email service providers don’t like redirecting URLs. Using trackable URLs in your Emails may impact deliverability." -msgstr "" - -#: ../configuration/settings.rst:236 -msgid "Unsubscribe settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Unsubscribe Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:242 -msgid "**Text for the {unsubscribe_text} token** - Like the ``{webview_text}`` token, this allows you to customize the **Unsubscribe** link." -msgstr "" - -#: ../configuration/settings.rst:244 -msgid "For example - Edit between the ```` and ```` tags. Don’t change the URL as it's tokenized. If you add ``{unsubscribe_url}`` as a token in the Email, you won’t see this text." -msgstr "" - -#: ../configuration/settings.rst:246 -msgid "**Unsubscribed and resubscribed confirmation message** - If a Contact unsubscribes or resubscribes, this message displays on the page after the respective action. Don’t edit the ``|EMAIL|`` or the ``|URL|`` token in the ```` tag." -msgstr "" - -#: ../configuration/settings.rst:248 -msgid "**Show Contact preference settings** - Select **Yes** to direct the unsubscribe link to your configured Preference enter. If you haven’t created a Preference Center, Mautic creates a default page based on the next 5 settings. The created page uses the default Theme for styling." -msgstr "" - -#: ../configuration/settings.rst:250 -msgid "**Show Contact Segment preferences** - Select **Yes** to allow a Contact to change which Segments they’re part of on the Preference Center page. Segments won’t display on the Preference Center page if they aren’t published and public." -msgstr "" - -#: ../configuration/settings.rst:252 -msgid "**Show Contact frequency preferences** - Select **Yes** to allow an individual to limit the number of Marketing Messages they receive on each Channel from the Preference Center." -msgstr "" - -#: ../configuration/settings.rst:254 -msgid "**Show pause Contact preferences** - Select **Yes** to allow Contacts to turn-off messages from your Mautic account to their Email address for a specified date range. This action isn’t a full unsubscribe action, and at the end of the date range, In this case, it sends the message again after the date range ends, as this isn't a full unsubscribe action." -msgstr "" - -#: ../configuration/settings.rst:256 -msgid "**Show Contact’s Categories** - If you have Categories set for Contacts, Campaigns, Emails, etc., select Yes to allow the Contact to opt out of the Categories they choose from the Preference Center page." -msgstr "" - -#: ../configuration/settings.rst:258 -msgid "**Show Contact’s preferred Channel option** - If you have multiple Channels available within your Mautic instance. For example; Email, ``SMS``, mobile push, web notifications, etc., Contacts can choose their preferred Channel. This can be useful if you are using the Marketing Messages feature of Mautic. More information about the Preference Center is available :doc:`here`." -msgstr "" - -#: ../configuration/settings.rst:262 -msgid "Form settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Form Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:268 -msgid "**Do not accept submission from these domain names** - To block Contacts with specific Email domains from submitting your Forms, enter those domains in the dialog box. Select an option on each Form you want to apply this block to. You can restrict either specific Email aliases that belong to a domain or an entire domain. To block the entire domain, you can use wildcards (*)." -msgstr "" - -#: ../configuration/settings.rst:271 -msgid "Contact settings" -msgstr "" - -#: ../configuration/settings.rst:274 -msgid "Contact merge settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Contact Merge Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:280 -#: ../configuration/settings.rst:318 -msgid "**Merge by unique fields with operator** - You can determine which operator to use when merging fields if there is more than one unique identifier." -msgstr "" - -#: ../configuration/settings.rst:283 -msgid "Contact list settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Contact List Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:289 -msgid "**Columns** - Select from the left which fields appear on the Contact lists (when you go to Contacts in the Mautic and view the list)." -msgstr "" - -#: ../configuration/settings.rst:291 -msgid "To display the fields, select them from the left and move them to the right column, or remove from the right column if you don't want them to appear in the list." -msgstr "" - -#: ../configuration/settings.rst:294 -msgid "Import settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Import Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:300 -msgid "**Automatically import in the background if the CSV has more rows than defined** - If there are more than the specified number of rows in an import file, the CSV automatically sets to import in the background which requires a :ref:`cron job` to trigger. Set to 0 if you want to always import files in the background recommended for performance optimization." -msgstr "" - -#: ../configuration/settings.rst:303 -msgid "Segment settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Segment Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:309 -msgid "**Show warning if Segment hasn’t been rebuilt for X hours** - Every time a :ref:`cron jobs` runs, Segments are rebuilt. If there is an error that prevents a Segment from rebuilding, Mautic displays a warning message. This field allows you to configure the allowable length of time between rebuilds, after which the warning message appears." -msgstr "" - -#: ../configuration/settings.rst:312 -msgid "Company settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Company Merge Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:321 -msgid "Notification settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Campaign Notification Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Webhook Notification Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:331 -msgid "If a Campaign or Webhook is automatically unpublished because of a high volume of errors, Mautic sends a notification alerting Users." -msgstr "" - -#: ../configuration/settings.rst:333 -msgid "**Send notification to author** - Set this field to Yes to send an Email notification to the User who created the unpublished Campaign or Webhook. Deleted Users don't receive notifications." -msgstr "" - -#: ../configuration/settings.rst:336 -msgid "Landing page settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Landing Page Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:342 -msgid "**Show Category in page URL?** - If you use Categories, the Landing Page’s associated Category displays in the URL if you select Yes." -msgstr "" - -#: ../configuration/settings.rst:344 -msgid "**Analytics script** - To track Landing Page visits and activity in other platforms such as Google Analytics, add those tracking scripts here." -msgstr "" - -#: ../configuration/settings.rst:347 -msgid "Tracking settings" -msgstr "" - -#: ../configuration/settings.rst:350 -msgid "Mautic tracking settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Tracking Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:356 -msgid "**Tracking code** - Insert this code on any page you would like to have tracked in Mautic before the ending ```` tag." -msgstr "" - -#: ../configuration/settings.rst:360 -msgid "The default tracking code provided in a new instance updates and changes after you set up a new custom domain or when you make changes to an existing one. You must use the new tracking code that reflects the new or edited custom domain. If you are using the Plugin for WordPress, Drupal, or Joomla, re-enter your account information in the Plugin." -msgstr "" - -#: ../configuration/settings.rst:362 -msgid "**Identify visitor by tracking URL** - Select **Yes** to have Mautic begin tracking a Contact after the Contact clicks a link in an Email on a device where no cookie exists." -msgstr "" - -#: ../configuration/settings.rst:364 -msgid "**Anonymize IP** - Select **Yes** to not store full IP addresses for your visitors/Contacts. This setting aids customers in achieving General Data Protection Regulation compliance." -msgstr "" - -#: ../configuration/settings.rst:366 -msgid "**Identify visitors by IP** - Select **Yes** to use the IP address to identify Contacts. It's possible to track unidentified visitors with the same IP address as an existing Contact. This may result in undesirable outcomes with large Companies who use the same externally facing IP address." -msgstr "" - -#: ../configuration/settings.rst:368 -msgid "**Do Not Track 404 error for anonymous Contacts** - Select **Yes** to not track page hits on any 404 error page tracked by the tracking code. This option helps prevent filling your logs with hits from bots." -msgstr "" - -#: ../configuration/settings.rst:372 -msgid "The tracking code automatically detects the Preferred Timezone and Preferred Locale fields." -msgstr "" - -#: ../configuration/settings.rst:373 -msgid "Landing Pages including 4-byte UTF-8 characters, such as emojis and some Chinese or other non-Latin characters, in the Landing Page title or URL aren't tracked on a Contact’s activity history in Mautic. All Latin characters used in English and other western languages are of 1-byte and are tracked." -msgstr "" - -#: ../configuration/settings.rst:376 -msgid "Facebook pixel" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Facebook Pixel Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:382 -msgid "**Facebook Pixel ID** - Enter your Facebook Pixel ID and select the options you’d like to use the pixel for." -msgstr "" - -#: ../configuration/settings.rst:384 -msgid "**Enabled on your tracking landing page** - Select Yes to have Mautic append the Facebook Pixel to the Mautic tracking code to track Landing Pages where the tracking code exists." -msgstr "" - -#: ../configuration/settings.rst:386 -msgid "**Enabled on Mautic landing page** - Select Yes to have Mautic add the Facebook Pixel to Mautic landing pages." -msgstr "" - -#: ../configuration/settings.rst:390 -msgid "Google analytics" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Google Analytics Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:396 -msgid "**Google Analytics ID** - Enter your Google Analytics ID and select the options you’d like to use the pixel for." -msgstr "" - -#: ../configuration/settings.rst:398 -msgid "**Enabled on your tracking landing page** - Select Yes to have Mautic append the Google Analytics script to the Mautic tracking code to track Landing Pages where the tracking code exists." -msgstr "" - -#: ../configuration/settings.rst:400 -msgid "**Enabled on Mautic landing page** - Select Yes to have Mautic add the Google Analytics script to Mautic landing pages." -msgstr "" - -#: ../configuration/settings.rst:402 -msgid "**Enabled IP** ``Anonymization`` - For subscribers sensitive to General Data Protection Regulation or other data privacy laws and regulations, select Yes to anonymize the IP address of web visitors before sending it to Google Analytics.*" -msgstr "" - -#: ../configuration/settings.rst:405 -msgid "Report settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Report Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:411 -msgid "**Always quote data in CSV export** - Select Yes to wrap each Mautic field in double quotation marks when exported to a CSV file. For example: ``\"First Name\",”Last Name”,””, \"some text\"``." -msgstr "" - -#: ../configuration/settings.rst:414 -msgid "Text message settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Text Message Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:420 -msgid "**Select default transport to use** - If you have configured a delivery service for SMS messages, select the service here to send messages. You must configure a delivery service before selecting it here." -msgstr "" - -#: ../configuration/settings.rst:423 -msgid "User/Authentication settings" -msgstr "" - -#: ../configuration/settings.rst:426 -msgid "SAML/SSO settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing SAML/SSO Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:432 -msgid "**Identity provider metadata file** - Upload the metadata XML file from your Identity Provider (IDP) here." -msgstr "" - -#: ../configuration/settings.rst:434 -msgid "**Default Role for created Users** - You can select one of those Roles as the default for Users created using Single Sign-On by creating :doc:`User Roles` in the Roles section of the settings panel. If empty, Single Sign-On won't create any Mautic Users. See :doc:`Users and Roles`." -msgstr "" - -#: ../configuration/settings.rst:436 -msgid "Enter the names of the attributes the configured IDP uses for the Mautic User fields. Match the field name from your identity provider to the field name Mautic uses for User creation." -msgstr "" - -#: ../configuration/settings.rst:438 -msgid "**Email**" -msgstr "" - -#: ../configuration/settings.rst:439 -msgid "**First name**" -msgstr "" - -#: ../configuration/settings.rst:440 -msgid "**Last name**" -msgstr "" - -#: ../configuration/settings.rst:441 -msgid "**Username**" -msgstr "" - -#: ../configuration/settings.rst:443 -msgid "Use a custom X.509 certificate and private key to secure communication between Mautic and the IDP." -msgstr "" - -#: ../configuration/settings.rst:445 -msgid "Upload your:" -msgstr "" - -#: ../configuration/settings.rst:447 -msgid "**X.509 certificate**" -msgstr "" - -#: ../configuration/settings.rst:448 -msgid "**Private key file**" -msgstr "" - -#: ../configuration/settings.rst:450 -msgid "Enter your **Private key encryption password**" -msgstr "" - -#: ../configuration/settings.rst:453 -msgid "Webhook settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Webhook Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:459 -msgid "**Queue Mode** - Select how to process Webhook events. The process immediately executes the Webhook event as soon as it arrives. The queue mode improves performance by only adding the event to the queue and requires processing by a :ref:`cron command`." -msgstr "" - -#: ../configuration/settings.rst:461 -msgid "**Order of the queued events** - Process the events in chronological or reverse chronological order if a Webhook has a queue of multiple events." -msgstr "" - -#: ../configuration/settings.rst:464 -msgid "Social settings" -msgstr "" - -#: ../configuration/settings.rst:None -msgid "Screenshot showing Social Settings Configuration in Mautic" -msgstr "" - -#: ../configuration/settings.rst:470 -msgid "**Twitter Handle Field** - This field stores the Twitter username for Users added to Mautic through Social Monitoring." -msgstr "" - -#: ../configuration/variables.rst:2 -msgid "Variables" -msgstr "" - -#: ../configuration/variables.rst:5 -msgid "Default Value" -msgstr "" - -#: ../configuration/variables.rst:7 -msgid "The default value - sometimes called Fallback Text - is specified after the ``|`` character. Consider this Email salutation:" -msgstr "" - -#: ../configuration/variables.rst:9 -msgid "``Hi {contactfield=firstname|there},``" -msgstr "" - -#: ../configuration/variables.rst:12 -msgid "Contact fields" -msgstr "" - -#: ../configuration/variables.rst:14 -msgid "See :doc:`managing custom fields ` for more information." -msgstr "" - -#: ../configuration/variables.rst:20 -#: ../configuration/variables.rst:85 -#: ../configuration/variables.rst:107 -#: ../configuration/variables.rst:150 -#: ../configuration/variables.rst:171 -#: ../configuration/variables.rst:196 -#: ../configuration/variables.rst:219 -#: ../configuration/variables.rst:242 -#: ../configuration/variables.rst:257 -#: ../configuration/variables.rst:296 -msgid "Variable name" -msgstr "" - -#: ../configuration/variables.rst:21 -#: ../configuration/variables.rst:86 -#: ../configuration/variables.rst:108 -#: ../configuration/variables.rst:151 -#: ../configuration/variables.rst:172 -#: ../configuration/variables.rst:197 -#: ../configuration/variables.rst:220 -#: ../configuration/variables.rst:243 -#: ../configuration/variables.rst:258 -#: ../configuration/variables.rst:297 -msgid "Variable syntax" -msgstr "" - -#: ../configuration/variables.rst:22 -#: ../configuration/variables.rst:310 -msgid "Attribution" -msgstr "" - -#: ../configuration/variables.rst:23 -#: ../configuration/variables.rst:311 -msgid "``{contactfield=attribution}``" -msgstr "" - -#: ../configuration/variables.rst:24 -#: ../configuration/variables.rst:312 -msgid "Attribution Date" -msgstr "" - -#: ../configuration/variables.rst:25 -#: ../configuration/variables.rst:313 -msgid "``{contactfield=attribution_date}``" -msgstr "" - -#: ../configuration/variables.rst:26 -#: ../configuration/variables.rst:298 -msgid "Address Line 1" -msgstr "" - -#: ../configuration/variables.rst:27 -#: ../configuration/variables.rst:299 -#: ../configuration/variables.rst:301 -msgid "``{contactfield=address1}``" -msgstr "" - -#: ../configuration/variables.rst:28 -#: ../configuration/variables.rst:302 -msgid "Address Line 2" -msgstr "" - -#: ../configuration/variables.rst:29 -#: ../configuration/variables.rst:303 -msgid "``{contactfield=address2}``" -msgstr "" - -#: ../configuration/variables.rst:30 -#: ../configuration/variables.rst:322 -msgid "Country" -msgstr "" - -#: ../configuration/variables.rst:31 -#: ../configuration/variables.rst:323 -msgid "``{contactfield=country}``" -msgstr "" - -#: ../configuration/variables.rst:32 -#: ../configuration/variables.rst:318 -msgid "City" -msgstr "" - -#: ../configuration/variables.rst:33 -#: ../configuration/variables.rst:319 -msgid "``{contactfield=city}``" -msgstr "" - -#: ../configuration/variables.rst:34 -#: ../configuration/variables.rst:326 -msgid "Company" -msgstr "" - -#: ../configuration/variables.rst:35 -#: ../configuration/variables.rst:327 -msgid "``{contactfield=company}``" -msgstr "" - -#: ../configuration/variables.rst:36 -#: ../configuration/variables.rst:328 -msgid "Contact ID" -msgstr "" - -#: ../configuration/variables.rst:37 -#: ../configuration/variables.rst:329 -msgid "``{contactfield=id}``" -msgstr "" - -#: ../configuration/variables.rst:38 -#: ../configuration/variables.rst:91 -#: ../configuration/variables.rst:334 -msgid "Email" -msgstr "" - -#: ../configuration/variables.rst:39 -#: ../configuration/variables.rst:335 -msgid "``{contactfield=email}``" -msgstr "" - -#: ../configuration/variables.rst:40 -#: ../configuration/variables.rst:338 -msgid "Facebook" -msgstr "" - -#: ../configuration/variables.rst:41 -#: ../configuration/variables.rst:339 -msgid "``{contactfield=facebook}``" -msgstr "" - -#: ../configuration/variables.rst:42 -#: ../configuration/variables.rst:340 -msgid "Fax" -msgstr "" - -#: ../configuration/variables.rst:43 -#: ../configuration/variables.rst:341 -msgid "``{contactfield=fax}``" -msgstr "" - -#: ../configuration/variables.rst:44 -#: ../configuration/variables.rst:87 -#: ../configuration/variables.rst:348 -msgid "First Name" -msgstr "" - -#: ../configuration/variables.rst:45 -#: ../configuration/variables.rst:349 -msgid "``{contactfield=firstname}``" -msgstr "" - -#: ../configuration/variables.rst:46 -#: ../configuration/variables.rst:350 -msgid "Foursquare" -msgstr "" - -#: ../configuration/variables.rst:47 -#: ../configuration/variables.rst:351 -msgid "``{contactfield=foursquare}``" -msgstr "" - -#: ../configuration/variables.rst:48 -#: ../configuration/variables.rst:352 -msgid "Google+" -msgstr "" - -#: ../configuration/variables.rst:49 -#: ../configuration/variables.rst:353 -msgid "``{contactfield=googleplus}``" -msgstr "" - -#: ../configuration/variables.rst:50 -#: ../configuration/variables.rst:354 -msgid "Instagram" -msgstr "" - -#: ../configuration/variables.rst:51 -#: ../configuration/variables.rst:355 -msgid "``{contactfield=instagram}``" -msgstr "" - -#: ../configuration/variables.rst:52 -#: ../configuration/variables.rst:356 -msgid "IP Address" -msgstr "" - -#: ../configuration/variables.rst:53 -#: ../configuration/variables.rst:357 -msgid "``{contactfield=ipAddress}``" -msgstr "" - -#: ../configuration/variables.rst:54 -#: ../configuration/variables.rst:89 -#: ../configuration/variables.rst:362 -msgid "Last Name" -msgstr "" - -#: ../configuration/variables.rst:55 -#: ../configuration/variables.rst:363 -msgid "``{contactfield=lastname}``" -msgstr "" - -#: ../configuration/variables.rst:56 -#: ../configuration/variables.rst:366 -msgid "LinkedIn" -msgstr "" - -#: ../configuration/variables.rst:57 -#: ../configuration/variables.rst:367 -msgid "``{contactfield=linkedin}``" -msgstr "" - -#: ../configuration/variables.rst:58 -#: ../configuration/variables.rst:370 -msgid "Mobile Number" -msgstr "" - -#: ../configuration/variables.rst:59 -#: ../configuration/variables.rst:371 -msgid "``{contactfield=mobile}``" -msgstr "" - -#: ../configuration/variables.rst:60 -#: ../configuration/variables.rst:376 -msgid "Phone Number" -msgstr "" - -#: ../configuration/variables.rst:61 -#: ../configuration/variables.rst:377 -msgid "``{contactfield=phone}``" -msgstr "" - -#: ../configuration/variables.rst:62 -#: ../configuration/variables.rst:93 -#: ../configuration/variables.rst:380 -msgid "Position" -msgstr "" - -#: ../configuration/variables.rst:63 -#: ../configuration/variables.rst:381 -msgid "``{contactfield=position}``" -msgstr "" - -#: ../configuration/variables.rst:64 -#: ../configuration/variables.rst:388 -msgid "Skype" -msgstr "" - -#: ../configuration/variables.rst:65 -#: ../configuration/variables.rst:389 -msgid "``{contactfield=skype}``" -msgstr "" - -#: ../configuration/variables.rst:66 -#: ../configuration/variables.rst:390 -msgid "State" -msgstr "" - -#: ../configuration/variables.rst:67 -#: ../configuration/variables.rst:391 -msgid "``{contactfield=state}``" -msgstr "" - -#: ../configuration/variables.rst:68 -#: ../configuration/variables.rst:396 -msgid "Twitter" -msgstr "" - -#: ../configuration/variables.rst:69 -#: ../configuration/variables.rst:397 -msgid "``{contactfield=twitter}``" -msgstr "" - -#: ../configuration/variables.rst:70 -#: ../configuration/variables.rst:200 -#: ../configuration/variables.rst:261 -#: ../configuration/variables.rst:404 -msgid "Title" -msgstr "" - -#: ../configuration/variables.rst:71 -#: ../configuration/variables.rst:405 -msgid "``{contactfield=title}``" -msgstr "" - -#: ../configuration/variables.rst:72 -#: ../configuration/variables.rst:412 -msgid "Website" -msgstr "" - -#: ../configuration/variables.rst:73 -#: ../configuration/variables.rst:413 -msgid "``{contactfield=website}``" -msgstr "" - -#: ../configuration/variables.rst:74 -#: ../configuration/variables.rst:420 -msgid "Zip Code" -msgstr "" - -#: ../configuration/variables.rst:75 -#: ../configuration/variables.rst:421 -msgid "``{contactfield=zipcode}``" -msgstr "" - -#: ../configuration/variables.rst:78 -msgid "Contact Owner fields" -msgstr "" - -#: ../configuration/variables.rst:88 -msgid "``{ownerfield=firstname}``" -msgstr "" - -#: ../configuration/variables.rst:90 -msgid "``{ownerfield=lastname}``" -msgstr "" - -#: ../configuration/variables.rst:92 -msgid "``{ownerfield=email}``" -msgstr "" - -#: ../configuration/variables.rst:94 -msgid "``{ownerfield=position}``" -msgstr "" - -#: ../configuration/variables.rst:95 -#: ../configuration/variables.rst:173 -#: ../configuration/variables.rst:386 -msgid "Signature" -msgstr "" - -#: ../configuration/variables.rst:96 -msgid "``{ownerfield=signature}``" -msgstr "" - -#: ../configuration/variables.rst:99 -msgid "Company Contact fields" -msgstr "" - -#: ../configuration/variables.rst:101 -msgid "See :doc:`Companies` for more information." -msgstr "" - -#: ../configuration/variables.rst:109 -#: ../configuration/variables.rst:300 -msgid "Address Line 1 (Company)" -msgstr "" - -#: ../configuration/variables.rst:110 -msgid "``{contactfield=companyaddress1}``" -msgstr "" - -#: ../configuration/variables.rst:111 -#: ../configuration/variables.rst:304 -msgid "Address Line 2 (Company)" -msgstr "" - -#: ../configuration/variables.rst:112 -#: ../configuration/variables.rst:305 -msgid "``{contactfield=companyaddress2}``" -msgstr "" - -#: ../configuration/variables.rst:113 -#: ../configuration/variables.rst:306 -msgid "Annual Revenue (Company)" -msgstr "" - -#: ../configuration/variables.rst:114 -#: ../configuration/variables.rst:307 -msgid "``{contactfield=companyannual_revenue}``" -msgstr "" - -#: ../configuration/variables.rst:115 -#: ../configuration/variables.rst:320 -msgid "City (Company)" -msgstr "" - -#: ../configuration/variables.rst:116 -#: ../configuration/variables.rst:321 -msgid "``{contactfield=companycity}``" -msgstr "" - -#: ../configuration/variables.rst:117 -#: ../configuration/variables.rst:324 -msgid "Country (Company)" -msgstr "" - -#: ../configuration/variables.rst:118 -#: ../configuration/variables.rst:325 -msgid "``{contactfield=companycountry}``" -msgstr "" - -#: ../configuration/variables.rst:119 -#: ../configuration/variables.rst:330 -msgid "Description (Company)" -msgstr "" - -#: ../configuration/variables.rst:120 -#: ../configuration/variables.rst:331 -msgid "``{contactfield=companydescription}``" -msgstr "" - -#: ../configuration/variables.rst:121 -#: ../configuration/variables.rst:336 -msgid "Email (Company)" -msgstr "" - -#: ../configuration/variables.rst:122 -#: ../configuration/variables.rst:337 -msgid "``{contactfield=companyemail}``" -msgstr "" - -#: ../configuration/variables.rst:123 -#: ../configuration/variables.rst:346 -msgid "Fax (Company)" -msgstr "" - -#: ../configuration/variables.rst:124 -#: ../configuration/variables.rst:347 -msgid "``{contactfield=companyfax}``" -msgstr "" - -#: ../configuration/variables.rst:125 -msgid "Industry (Company)" -msgstr "" - -#: ../configuration/variables.rst:126 -msgid "``{contactfield=companyindustry}``" -msgstr "" - -#: ../configuration/variables.rst:127 -msgid "Name" -msgstr "" - -#: ../configuration/variables.rst:128 -#: ../configuration/variables.rst:373 -msgid "``{contactfield=companyname}``" -msgstr "" - -#: ../configuration/variables.rst:129 -#: ../configuration/variables.rst:374 -msgid "Number of Employees (Company)" -msgstr "" - -#: ../configuration/variables.rst:130 -#: ../configuration/variables.rst:375 -msgid "``{contactfield=companynumber_of_employees}``" -msgstr "" - -#: ../configuration/variables.rst:131 -#: ../configuration/variables.rst:378 -msgid "Phone Number (Company)" -msgstr "" - -#: ../configuration/variables.rst:132 -#: ../configuration/variables.rst:379 -msgid "``{contactfield=companyphone}``" -msgstr "" - -#: ../configuration/variables.rst:133 -#: ../configuration/variables.rst:392 -msgid "State (Company)" -msgstr "" - -#: ../configuration/variables.rst:134 -#: ../configuration/variables.rst:393 -msgid "``{contactfield=companystate}``" -msgstr "" - -#: ../configuration/variables.rst:135 -#: ../configuration/variables.rst:414 -msgid "Website (Company)" -msgstr "" - -#: ../configuration/variables.rst:136 -#: ../configuration/variables.rst:415 -msgid "``{contactfield=companywebsite}``" -msgstr "" - -#: ../configuration/variables.rst:137 -#: ../configuration/variables.rst:422 -msgid "Zip Code (Company)" -msgstr "" - -#: ../configuration/variables.rst:138 -#: ../configuration/variables.rst:423 -msgid "``{contactfield=companyzipcode}``" -msgstr "" - -#: ../configuration/variables.rst:141 -msgid "Mautic Component tokens" -msgstr "" - -#: ../configuration/variables.rst:143 -msgid "See :doc:`Components` and :doc:`Manage Pages` for more information." -msgstr "" - -#: ../configuration/variables.rst:152 -#: ../configuration/variables.rst:308 -msgid "Asset link for Asset id#" -msgstr "" - -#: ../configuration/variables.rst:153 -#: ../configuration/variables.rst:309 -msgid "``{assetlink=25}``" -msgstr "" - -#: ../configuration/variables.rst:154 -#: ../configuration/variables.rst:342 -msgid "Focus Item id#" -msgstr "" - -#: ../configuration/variables.rst:155 -#: ../configuration/variables.rst:343 -msgid "``{focus=4}``" -msgstr "" - -#: ../configuration/variables.rst:156 -#: ../configuration/variables.rst:344 -msgid "Form id#" -msgstr "" - -#: ../configuration/variables.rst:157 -#: ../configuration/variables.rst:345 -msgid "``{form=83}``" -msgstr "" - -#: ../configuration/variables.rst:158 -#: ../configuration/variables.rst:358 -msgid "Landing Page link for page id#" -msgstr "" - -#: ../configuration/variables.rst:159 -#: ../configuration/variables.rst:359 -msgid "``{pagelink=17}``" -msgstr "" - -#: ../configuration/variables.rst:162 -msgid "Email specific tokens" -msgstr "" - -#: ../configuration/variables.rst:164 -msgid "See :doc:`Manage Emails` for more information." -msgstr "" - -#: ../configuration/variables.rst:174 -#: ../configuration/variables.rst:387 -msgid "``{signature}``" -msgstr "" - -#: ../configuration/variables.rst:175 -#: ../configuration/variables.rst:394 -msgid "Subject" -msgstr "" - -#: ../configuration/variables.rst:176 -#: ../configuration/variables.rst:395 -msgid "``{subject}``" -msgstr "" - -#: ../configuration/variables.rst:177 -#: ../configuration/variables.rst:271 -msgid "Tracking pixel" -msgstr "" - -#: ../configuration/variables.rst:178 -#: ../configuration/variables.rst:272 -msgid "``{tracking_pixel}``" -msgstr "" - -#: ../configuration/variables.rst:179 -#: ../configuration/variables.rst:408 -msgid "Unsubscribe Text" -msgstr "" - -#: ../configuration/variables.rst:180 -#: ../configuration/variables.rst:409 -msgid "``{unsubscribe_text}``" -msgstr "" - -#: ../configuration/variables.rst:181 -#: ../configuration/variables.rst:416 -msgid "Web View Text" -msgstr "" - -#: ../configuration/variables.rst:182 -#: ../configuration/variables.rst:417 -msgid "``{webview_text}``" -msgstr "" - -#: ../configuration/variables.rst:183 -#: ../configuration/variables.rst:418 -msgid "Web View URL" -msgstr "" - -#: ../configuration/variables.rst:184 -msgid "``{webview_url}``" -msgstr "" - -#: ../configuration/variables.rst:187 -msgid "Landing Page tokens" -msgstr "" - -#: ../configuration/variables.rst:189 -msgid "See :doc:`/components/landing_pages` for more information." -msgstr "" - -#: ../configuration/variables.rst:198 -msgid "Meta Description" -msgstr "" - -#: ../configuration/variables.rst:199 -#: ../configuration/variables.rst:369 -msgid "``{pagemetadescription}``" -msgstr "" - -#: ../configuration/variables.rst:201 -#: ../configuration/variables.rst:407 -msgid "``{pagetitle}``" -msgstr "" - -#: ../configuration/variables.rst:202 -#: ../configuration/variables.rst:360 -msgid "Language bar" -msgstr "" - -#: ../configuration/variables.rst:203 -#: ../configuration/variables.rst:361 -msgid "``{langbar}``" -msgstr "" - -#: ../configuration/variables.rst:204 -#: ../configuration/variables.rst:400 -msgid "Share Buttons" -msgstr "" - -#: ../configuration/variables.rst:205 -#: ../configuration/variables.rst:401 -msgid "``{sharebuttons}``" -msgstr "" - -#: ../configuration/variables.rst:206 -#: ../configuration/variables.rst:402 -msgid "Success Message" -msgstr "" - -#: ../configuration/variables.rst:207 -#: ../configuration/variables.rst:403 -msgid "``{successmessage}``" -msgstr "" - -#: ../configuration/variables.rst:210 -msgid "Preference Center Landing Page tokens" -msgstr "" - -#: ../configuration/variables.rst:212 -msgid "See :doc:`customizing preference center` for more information." -msgstr "" - -#: ../configuration/variables.rst:221 -msgid "Lead Identifier" -msgstr "" - -#: ../configuration/variables.rst:222 -#: ../configuration/variables.rst:365 -msgid "``{leadidentifier}``" -msgstr "" - -#: ../configuration/variables.rst:223 -msgid "Category List" -msgstr "" - -#: ../configuration/variables.rst:224 -#: ../configuration/variables.rst:315 -msgid "``{categorylist}``" -msgstr "" - -#: ../configuration/variables.rst:225 -msgid "Segment List" -msgstr "" - -#: ../configuration/variables.rst:226 -#: ../configuration/variables.rst:385 -msgid "``{segmentlist}``" -msgstr "" - -#: ../configuration/variables.rst:227 -msgid "Preferred Channel" -msgstr "" - -#: ../configuration/variables.rst:228 -#: ../configuration/variables.rst:399 -msgid "``{preferredchannel}``" -msgstr "" - -#: ../configuration/variables.rst:229 -msgid "Channel Frequency" -msgstr "" - -#: ../configuration/variables.rst:230 -#: ../configuration/variables.rst:317 -msgid "``{channelfrequency}``" -msgstr "" - -#: ../configuration/variables.rst:231 -msgid "Save Preferences" -msgstr "" - -#: ../configuration/variables.rst:232 -#: ../configuration/variables.rst:383 -msgid "``{saveprefsbutton}``" -msgstr "" - -#: ../configuration/variables.rst:235 -msgid "Dynamic Web Content tokens" -msgstr "" - -#: ../configuration/variables.rst:244 -msgid "[Dynamic Content 1] | for example User-defined variable name" -msgstr "" - -#: ../configuration/variables.rst:245 -#: ../configuration/variables.rst:333 -msgid "``{dynamiccontent=\"Dynamic Content 1\"}``" -msgstr "" - -#: ../configuration/variables.rst:248 -msgid "Contact Monitoring" -msgstr "" - -#: ../configuration/variables.rst:250 -msgid "See :ref:`Contact Monitoring` for more information." -msgstr "" - -#: ../configuration/variables.rst:259 -msgid "Language" -msgstr "" - -#: ../configuration/variables.rst:260 -msgid "``{language}``" -msgstr "" - -#: ../configuration/variables.rst:262 -msgid "``{title}``" -msgstr "" - -#: ../configuration/variables.rst:263 -msgid "Landing Page Title" -msgstr "" - -#: ../configuration/variables.rst:264 -msgid "``{page_title}``" -msgstr "" - -#: ../configuration/variables.rst:265 -msgid "URL" -msgstr "" - -#: ../configuration/variables.rst:266 -msgid "``{url}``" -msgstr "" - -#: ../configuration/variables.rst:267 -msgid "Landing Page URL" -msgstr "" - -#: ../configuration/variables.rst:268 -msgid "``{page_url}``" -msgstr "" - -#: ../configuration/variables.rst:269 -msgid "Referrer" -msgstr "" - -#: ../configuration/variables.rst:270 -msgid "``{referrer}``" -msgstr "" - -#: ../configuration/variables.rst:273 -msgid "UTM Campaign" -msgstr "" - -#: ../configuration/variables.rst:274 -msgid "``{utm_campaign}``" -msgstr "" - -#: ../configuration/variables.rst:275 -msgid "UTM Content" -msgstr "" - -#: ../configuration/variables.rst:276 -msgid "``{utm_content}``" -msgstr "" - -#: ../configuration/variables.rst:277 -msgid "UTM Medium" -msgstr "" - -#: ../configuration/variables.rst:278 -msgid "``{utm_medium}``" -msgstr "" - -#: ../configuration/variables.rst:279 -msgid "UTM Source" -msgstr "" - -#: ../configuration/variables.rst:280 -msgid "``{utm_source}``" -msgstr "" - -#: ../configuration/variables.rst:281 -msgid "UTM Term" -msgstr "" - -#: ../configuration/variables.rst:282 -msgid "``{utm_term}``" -msgstr "" - -#: ../configuration/variables.rst:285 -msgid "Search filters" -msgstr "" - -#: ../configuration/variables.rst:287 -msgid "See the :ref:`Search` page for more information." -msgstr "" - -#: ../configuration/variables.rst:290 -msgid "Alphabetical list" -msgstr "" - -#: ../configuration/variables.rst:314 -msgid "Category List (Preference Center)" -msgstr "" - -#: ../configuration/variables.rst:316 -msgid "Channel Frequency (Preference Center)" -msgstr "" - -#: ../configuration/variables.rst:332 -msgid "[Dynamic Content 1]for example: user-defined variable name" -msgstr "" - -#: ../configuration/variables.rst:364 -msgid "Contact Identifier (Preference Center)" -msgstr "" - -#: ../configuration/variables.rst:368 -msgid "Meta Description (Landing Page)" -msgstr "" - -#: ../configuration/variables.rst:372 -msgid "Name (Company)" -msgstr "" - -#: ../configuration/variables.rst:382 -msgid "Save Preferences (Preference Center)" -msgstr "" - -#: ../configuration/variables.rst:384 -msgid "Segment List (Preference Center)" -msgstr "" - -#: ../configuration/variables.rst:398 -msgid "Preferred Channel (Preference Center)" -msgstr "" - -#: ../configuration/variables.rst:406 -msgid "Title (Landing Page)" -msgstr "" - -#: ../configuration/variables.rst:410 -msgid "Unsubscribe URL" -msgstr "" - -#: ../configuration/variables.rst:411 -msgid "``{unsubscribe_url}``" -msgstr "" - -#: ../configuration/variables.rst:419 -msgid "``{{webview_url}``" -msgstr "" diff --git a/docs/docs_translations/contacts.pot b/docs/docs_translations/contacts.pot deleted file mode 100644 index 567ed5ef..00000000 --- a/docs/docs_translations/contacts.pot +++ /dev/null @@ -1,45 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../contacts/custom_fields.rst:4 -msgid "Manage custom fields" -msgstr "" - -#: ../contacts/frequency_rules.rst:4 -msgid "Frequency rules" -msgstr "" - -#: ../contacts/import_contacts.rst:4 -msgid "Import Contacts" -msgstr "" - -#: ../contacts/manage_contacts.rst:4 -msgid "Managing Contacts" -msgstr "" - -#: ../contacts/manage_contacts.rst:9 -msgid "Contact tracking" -msgstr "" - -#: ../contacts/preference_center.rst:4 -msgid "Preference center" -msgstr "" - -#: ../contacts/preference_center.rst:8 -msgid "Customize preference center" -msgstr "" diff --git a/docs/docs_translations/dashboard.pot b/docs/docs_translations/dashboard.pot deleted file mode 100644 index c54e9ec0..00000000 --- a/docs/docs_translations/dashboard.pot +++ /dev/null @@ -1,205 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../dashboard/dashboard.rst:2 -msgid "Dashboard" -msgstr "" - -#: ../dashboard/dashboard.rst:4 -msgid "Mautic 1.4.0 introduced a customizable dashboard where each User can compose widgets with information they want to track. Mautic 2.0 brought a number of enhancements to the Dashboard." -msgstr "" - -#: ../dashboard/dashboard.rst:7 -msgid "Date range filter" -msgstr "" - -#: ../dashboard/dashboard.rst:9 -msgid "All the widgets will display data in the selected global date range filter at the top of the widget list. The default date range is set from 30 days ago to today." -msgstr "" - -#: ../dashboard/dashboard.rst:None -msgid "Screenshot of Dashboard date filter" -msgstr "" - -#: ../dashboard/dashboard.rst:15 -msgid "Line charts will change the time unit automatically depending on the day count selected in the date range filter like this:" -msgstr "" - -#: ../dashboard/dashboard.rst:17 -msgid "Date range is equal 1 day: data will be displayed in hours Date range is between 1 and 31 days: data will be displayed in days Date range is between 32 and 100 days: data will be displayed in weeks Date range is between 101 and 1000 days: data will be displayed in months Date range is greater than 1001 days: data will be displayed in years" -msgstr "" - -#: ../dashboard/dashboard.rst:19 -msgid "The only widget exceptions which display the same information independent on the date range are *Upcoming Emails* and *Recent activity*." -msgstr "" - -#: ../dashboard/dashboard.rst:22 -msgid "Widgets" -msgstr "" - -#: ../dashboard/dashboard.rst:26 -msgid "Don't create too many widgets. It can slow the dashboard Landing Page load down. If you have performance issues, decrease the amount of widgets." -msgstr "" - -#: ../dashboard/dashboard.rst:28 -msgid "A new widget can be added to your dashboard when you click the \"Add widget\" button. The \"Add widget\" Form which appears after each widget will let you define:" -msgstr "" - -#: ../dashboard/dashboard.rst:30 -msgid "**Name:** describe what the widget displays. If not filled, Mautic will call it the same as the widget type you select." -msgstr "" - -#: ../dashboard/dashboard.rst:32 -msgid "**Type:** select what information you want to display from the predefined widget types." -msgstr "" - -#: ../dashboard/dashboard.rst:34 -msgid "**Width:** select how wide the widget should be. The options are 25%, 50%, 75%, 100%. The default option is 100%. The optimal width for line charts is 100%, for tables 50%, for pie charts 25%." -msgstr "" - -#: ../dashboard/dashboard.rst:36 -msgid "**Height:** each widget can have different height. 5 heights are predefined. The dashboard will look best if you select a consistent height for each widget in the same row." -msgstr "" - -#: ../dashboard/dashboard.rst:38 -msgid "Some widgets have additional options:" -msgstr "" - -#: ../dashboard/dashboard.rst:40 -msgid "**Created Contacts over time**" -msgstr "" - -#: ../dashboard/dashboard.rst:42 -msgid "Show all Contacts: displays one line with all created Contacts." -msgstr "" - -#: ../dashboard/dashboard.rst:44 -msgid "Only identified: displays one line with only created and identified Contacts." -msgstr "" - -#: ../dashboard/dashboard.rst:46 -msgid "Only anonymous: displays one line with only anonymous visitors." -msgstr "" - -#: ../dashboard/dashboard.rst:48 -msgid "All identified vs anonymous: displays 2 lines with anonymous visitors and known Contacts." -msgstr "" - -#: ../dashboard/dashboard.rst:50 -msgid "Top Segments: displays up to 6 lines representing the number of Contacts added to the top 6 Segments. If no such Segment exists for the selected date range, the chart won't be displayed." -msgstr "" - -#: ../dashboard/dashboard.rst:52 -msgid "Top Segments with Identified vs Anonymous: displays up to 6 lines representing the top 3 Segments for the selected date range. Each Segment will show 2 lines with anonymous visitors and known Contacts." -msgstr "" - -#: ../dashboard/dashboard.rst:54 -msgid "**Emails in time**" -msgstr "" - -#: ../dashboard/dashboard.rst:56 -msgid "Only sent Emails: Displays 1 line with sent Emails." -msgstr "" - -#: ../dashboard/dashboard.rst:58 -msgid "Only opened Emails: Displays 1 line with opened Emails." -msgstr "" - -#: ../dashboard/dashboard.rst:60 -msgid "Only failed Emails: Displays 1 line with failed Emails." -msgstr "" - -#: ../dashboard/dashboard.rst:62 -msgid "Sent and opened Emails: Displays 2 lines with sent and opened Emails." -msgstr "" - -#: ../dashboard/dashboard.rst:64 -msgid "Sent, opened and failed Emails: Displays 3 lines with sent, opened and failed Emails." -msgstr "" - -#: ../dashboard/dashboard.rst:66 -msgid "**Landing Page visits in time**" -msgstr "" - -#: ../dashboard/dashboard.rst:68 -msgid "Total visits - Displays 1 line with all visits (Landing Page hits)." -msgstr "" - -#: ../dashboard/dashboard.rst:70 -msgid "Unique visits - Displays 1 line with unique visits (Contacts)." -msgstr "" - -#: ../dashboard/dashboard.rst:72 -msgid "Total and unique visits - Displays 2 lines with unique and all visits." -msgstr "" - -#: ../dashboard/dashboard.rst:75 -msgid "Widget ordering" -msgstr "" - -#: ../dashboard/dashboard.rst:77 -msgid "Each widget can be moved on the dashboard using the drag and drop interface. Click and hold on the name of the widget to move it to another position." -msgstr "" - -#: ../dashboard/dashboard.rst:80 -msgid "Dashboard export" -msgstr "" - -#: ../dashboard/dashboard.rst:82 -msgid "Each dashboard, once configured, can be exported to a single file and shared with others. You can make a backup, send it to a colleague or share it online. It exports only the widget configuration - the data which it pulls is not included in the exported file." -msgstr "" - -#: ../dashboard/dashboard.rst:85 -msgid "Dashboard import" -msgstr "" - -#: ../dashboard/dashboard.rst:87 -msgid "If you export a dashboard, you can then upload it and import it again in the Dashboard Import page." -msgstr "" - -#: ../dashboard/dashboard.rst:89 -msgid "Mautic installation come pre-loaded with 3 pre-defined dashboards. The one called default.json is imported automatically, when your dashboard doesn't contain any widgets. The other 2 predefined dashboards are provided as an example. You can export and import any other dashboards and switch between them. Pre-defined dashboards can be:" -msgstr "" - -#: ../dashboard/dashboard.rst:91 -msgid "Previewed - This will display the dashboard widgets for preview. The dashboard will be loaded using your existing Mautic data. Nothing is saved or changed. Applied - This sets the dashboard as your primary dashboard." -msgstr "" - -#: ../dashboard/dashboard.rst:95 -msgid "Your current widgets will be deleted by this action. Export the current dashboard if you want to go back to it later. Deleted - This will delete the predefined dashboard." -msgstr "" - -#: ../dashboard/dashboard.rst:99 -msgid "Widget cache" -msgstr "" - -#: ../dashboard/dashboard.rst:101 -msgid "The WidgetDetailEvent automatically caches the widget detail data for a period of time defined in the configuration. The default cache expiration period is 10 minutes." -msgstr "" - -#: ../dashboard/dashboard.rst:104 -msgid "Dashboard Permissions" -msgstr "" - -#: ../dashboard/dashboard.rst:106 -msgid "If a Mautic User doesn't have the 'see others' or 'see own' permissions for a bundle, they won't be able to create widgets for that bundle. However, the widget can still be visible on their dashboard. For example if a User creates the widgets and then the administrator removes the permission for that bundle, or if a User imports a dashboard which has widgets for bundles they're not permitted to access. In these cases, the widget is displayed on the dashboard, but with a message that the User doesn't have permission to see the data." -msgstr "" - -#: ../dashboard/dashboard.rst:110 -msgid "If a Mautic User has permission to see only their own data from a bundle, they will see only their own data in the Dashboard widgets. For example only Contacts which they own, Landing Page hits of the Landing Pages they created and so on." -msgstr "" diff --git a/docs/docs_translations/getting_started.pot b/docs/docs_translations/getting_started.pot deleted file mode 100644 index d77574a3..00000000 --- a/docs/docs_translations/getting_started.pot +++ /dev/null @@ -1,924 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../getting_started/how_to_install_mautic.rst:2 -msgid "Installation" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:4 -msgid "There are several ways to install Mautic, you should select the most appropriate method for your situation and technical knowledge." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:6 -msgid "Installing :ref:`using the production package`, with either the :ref:`web-based installer` or :ref:`from the command line`." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:8 -msgid "Installing locally by :ref:`cloning from GitHub` - for testing and local development," -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:10 -msgid ":ref:`Installing with Composer`" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:13 -msgid "Using the production package" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:15 -msgid "You can install the Mautic production package either by uploading the zipped installation package into the server location or using the command-line installation. The Mautic production package also requires access to a database server." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:17 -msgid "The Mautic installation is a three-step process:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:19 -msgid "Integrate the database server with the Mautic server." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:21 -msgid "Create an administrator account to access the Mautic server." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:23 -msgid "Set up the Email server for Email marketing automation." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:26 -msgid "Preparing for installation" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:28 -msgid "Before installing a package, ensure that:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:30 -msgid "Your server environment meets the minimum requirements for the version you are installing. Read more in :xref:`Mautic's Requirements`." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:32 -msgid "Your server directory is writable by the Mautic web server." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:34 -msgid "Your database meets the minimum requirements for the supported databases and valid User permissions to access to the database. Read more in :xref:`Mautic's Requirements`." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:36 -msgid "Your server has enough free disk space to run the installation. Consider the database size as well." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:38 -msgid "PHP's `max_execution_time` is at least 240 seconds." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:41 -msgid "Downloading a production package" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:43 -msgid "To get started :xref:`Download Mautic` to access the zip file of the latest stable release." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:45 -msgid "For more information about the available Mautic packages, visit the :xref:`Mautic Releases` Landing Page." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:48 -msgid "Uploading the production package" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:50 -msgid "After downloading a desired package, upload the package zip file to your web server, and unzip it in the directory where you plan to host the Mautic instance." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:52 -msgid "Your web server must have the permissions to access the unzipped files." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:55 -msgid "Using the web-based installer" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:57 -msgid "To access the Mautic server from your browser, enter the URL that corresponds to the Mautic instance (for example, `https://m.example.com`) in your web browser. It's recommended to secure your installation with an SSL certificate (https)." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:60 -msgid "Conducting environment checks" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:62 -msgid "After loading the package in the server, the Mautic installer validates if it can run successfully in your server environment." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:64 -msgid "You must resolve installation errors, displayed in red, before completing the Mautic package installation successfully. Warnings, displayed in orange, are often recommendations for a better Mautic experience." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:None -msgid "Screenshot showing Mautic pre-flight checks with warning about installing on a non-SSL connection" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:70 -msgid "If the environment checks are successful - displayed in green - click **Next Step** to begin the installation process." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:73 -msgid "Integrating the database" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:75 -msgid "Mautic assumes that the database is on the same server as Mautic." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:77 -msgid "For setting the database server on the **Mautic Installation-Database Setup** window:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:79 -msgid "Select **Database Driver**." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:81 -msgid "Enter **Database Host**." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:83 -msgid "Enter **Database Name**." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:85 -msgid "Enter **Database Username**." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:87 -msgid "If desired, you can also enter values for **Database Port**, **Database Table Prefix**, **Database Password**, and **Prefix for backup tables**." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:89 -msgid "**Backup existing tables?** is on by default, but you should turn it off for a new installation." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:None -msgid "Screenshot of database configuration screen" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:95 -#: ../getting_started/how_to_install_mautic.rst:106 -msgid "Click **Next Step**." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:98 -msgid "Creating the administrator account" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:100 -msgid "To create an Administrator account for your Mautic instance, enter values for the different fields on the **Mautic Installation - Administrative User** window." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:None -msgid "Screenshot showing the create User screen" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:111 -msgid "Configuring Email settings" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:115 -msgid "To configure your Email settings for your Mautic instance, enter details of your Email provider on the **Mautic Installation - Email Configuration** window. You can use a tool such as :xref:`Mailhog` to configure a local instance for testing." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:None -msgid "Screenshot showing the Email configuration screen" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:121 -msgid "For configuring your Email sender settings:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:123 -msgid "Enter the name and Email address to use with all outgoing Email communications by default. Verify that the provided Email address has been successfully authorized by your Email provider." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:125 -msgid "**Queue** Emails and send them through a cron job - to trigger the queue processing - instead of sending them immediately for larger instances of Email handling." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:127 -msgid "Select **Mailer transport**. If your provider isn't listed, select **Other SMTP Server** and provide the SMTP credentials. API-based sending is significantly faster than SMTP. Depending on the provider you select, additional fields appear to allow you to enter API keys and select regions." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:129 -msgid "Enter **Server** and **Port** for your Email provider." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:131 -msgid "Select **Encryption** and **Authentication mode** for your Email provider." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:133 -msgid "Click **Next Step** to log into the Mautic server." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:136 -msgid "Logging into Mautic" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:138 -msgid "On the Mautic login window, enter your Mautic administrator credentials to log into your Mautic instance." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:None -msgid "Screenshot of Mautic login screen" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:144 -msgid "Click **login** to continue working on your Mautic instance." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:147 -msgid "Installing with command line" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:149 -msgid "You can also install Mautic using the command line. You can either pass the settings parameters in the command, or create a local PHP file with your database settings. You can also define properties in this file using the syntax expected by the command-line options." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:151 -msgid "Use the command ``path/to/php bin/console mautic:install --help`` for the list of options and flags available." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:181 -msgid "Use the syntax below within a ``local.php`` file:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:210 -msgid "Installing with a local PHP file" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:212 -msgid "Run the following command after replacing the path to PHP bin and Mautic instance URL." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:214 -msgid "``path/to/php bin/console mautic:install https://m.example.com``" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:216 -msgid "If desired, you can also add parameters in the install command:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:226 -msgid "As the installation process begins, it flags up warnings and aborts if there are any critical errors." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:248 -msgid "You can now login to your Mautic instance with your Mautic Admin credentials." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:251 -msgid "Installing from GitHub" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:253 -msgid "It's essential to have all the files locally - including automated tests - from the GitHub repository when testing Mautic or contributing to it. Many of these files aren't included in the production build process." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:256 -msgid "Cloning Mautic from GitHub" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:258 -msgid "Install the :xref:`GitHub CLI` tool." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:260 -msgid "Click **Fork** at the top-right corner of the Mautic GitHub repository page to make a personal fork. You can also click to go directly to your fork if you already have one, if you don't then GitHub will offer to create one.." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:262 -msgid "After the fork is complete, click the green **Code** button to access the command for cloning the repository." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:264 -msgid "Switch to your terminal, and when in the directory where you wish to install Mautic, paste the command using the :xref:`GitHub CLI` tool this is in the format:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:272 -msgid "Please always choose to fork into a **personal account** rather than an organization. The latter prevents Mautic's maintainers from working with your Pull Request." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:275 -msgid "Install Mautic using DDEV" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:277 -msgid "You can use :xref:`DDEV` which is recommended for testing and development with Mautic. To get started:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:280 -msgid "Install :xref:`DDEV`." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:282 -msgid "Install and ensure you have :xref:`Docker` running on your system." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:284 -msgid "You can now change into the Mautic directory and kick off the DDEV quickstart using the command:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:292 -msgid "For troubleshooting see :xref:`DDEV Troubleshooting`." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:294 -msgid "See Mautic's :xref:`Handbook` for more detailed instructions." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:298 -msgid "This spins up a DDEV instance (which includes Mailhog, PHPMyAdmin, and Redis Commander) - by default at ``https://mautic.ddev.site`` - and also gives the option to set up Mautic ready for you to use. .. vale on" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:301 -msgid "This runs through the Composer install process, and installs Mautic at the command line with a default username of ``admin`` and password of ``mautic``." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:304 -msgid "Installing with Composer" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:306 -msgid "Since :xref:`Mautic 4` it's possible to install and manage Mautic using the full power of Composer. Mautic uses the latest version of :xref:`Composer`." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:308 -msgid "Mautic is in the process of decoupling Plugins and Themes from core, however at present while they have been technically mirrored out into separate repositories, the source files remain in the main :xref:`Mautic GitHub repository`." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:310 -msgid "When you clone from GitHub, running ``composer install`` installs all the dependencies, there are some other handy features which you can take advantage of when installing and managing Mautic." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:315 -msgid "Using the Recommended Project" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:319 -msgid "The Mautic :xref:`Recommended Project` is a template which provides a starter kit for managing your Mautic dependencies with Composer." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:322 -msgid "The instructions below refer to the global Composer installation. You might need to replace Composer with ``php composer.phar`` or something similar for your setup." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:324 -msgid "The basic command to use the Recommended Project is:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:330 -msgid "With Composer you can add new dependencies to install along with Mautic:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:337 -msgid "The Composer ``create-project`` command passes ownership of all files to the created project. You should create a new git repository, and commit all files not excluded by the .gitignore file." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:342 -msgid "What does the Recommended Project template actually do?" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:346 -msgid "When installing the given ``composer.json`` the following occurs:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:348 -msgid "Install Mautic in the ``docroot`` directory." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:349 -msgid "Autoloader uses the generated Composer autoloader in ``vendor/autoload.php``, instead of the one provided by Mautic in ``docroot/vendor/autoload.php``." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:350 -msgid "Plugins - packages of type ``mautic-plugin`` - are in ``docroot/plugins/``." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:351 -msgid "Themes - packages of type ``mautic-theme`` - are in ``docroot/themes/``." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:352 -msgid "Creates ``docroot/media`` directory." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:353 -msgid "Creates environment variables based on your ``.env`` file. See ``.env.example``." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:358 -msgid "Updating Mautic Core" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:362 -msgid "The Recommended Project attempts to keep all of your Mautic core files up-to-date." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:364 -msgid "The project ``mautic/core-composer-scaffold`` updates your scaffold files whenever there is an update to ``mautic/core-lib``." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:366 -msgid "If you customize any of the \"scaffolding\" files - commonly .htaccess - you may need to merge conflicts if new release of Mautic Core result in changes to your modified files." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:368 -msgid "Follow the steps below to update your core files." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:370 -msgid "1 Run ``composer update mautic/core-lib --with-dependencies`` to update Mautic core and its dependencies." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:372 -msgid "2 Run ``git diff`` to determine if any of the scaffolding files have changed. Review the files for any changes and restore any customizations to .htaccess or others." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:374 -msgid "3 Commit everything all together in a single commit, so the ``docroot`` remains in sync with the core when checking out branches or running git bisect." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:376 -msgid "4 In the event that there are non-trivial conflicts in step 2, you may wish to perform these steps on a branch, and use ``git merge`` to combine the updated core files with your customized files. This facilitates the use of a three-way merge tool such as :xref:`kdiff3`. This setup isn't necessary if your changes are simple - keeping all of your modifications at the beginning or end of the file is a good strategy to keep merges easy." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:378 -msgid "5 Run the following commands to update your database with any changes from the release:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:391 -msgid "Composer FAQs" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:396 -msgid "Should you commit downloaded third party Plugins?" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:398 -msgid "Composer says that the :xref:`Composer commit dependencies`. They provide arguments against but also workarounds if a project decides to do it anyway." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:401 -msgid "Should you commit the scaffolding files?" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:403 -msgid "The :xref:`Mautic Composer scaffold` Plugin can download the scaffold files - for example ``index.php``, ``.htaccess`` - to the ``docroot/`` directory of your project." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:406 -msgid "If you haven't customized those files you could choose to not commit them in your version control system - for example, git. If that's the case for your project it might be convenient to automatically run the Mautic Scaffold Plugin after every install or update of your project." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:410 -msgid "You can achieve that by registering ``@composer mautic:scaffold`` as post-install and post-update command in your composer.json:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:428 -msgid "How can you apply patches to downloaded Plugins?" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:430 -msgid "If you need to apply patches - depending on the Plugin, a pull request is often a better solution - you can do so with the ``composer-patches`` Plugin." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:432 -msgid "To add a patch to Mautic Plugin foobar insert the patches section in the extra section of ``composer.json``:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:448 -msgid "How can you specify a PHP version?" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:452 -msgid "This project supports PHP 7.4 as the minimum version currently - review :xref:`Mautic's Requirements` however, it's possible that a Composer update may upgrade some package that could then require PHP 7+ or 8+." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:454 -msgid "To prevent this you can add this code to specify the PHP version you want to use in the config section of ``composer.json``:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:467 -msgid "How can you use another folder than ``docroot`` as the root folder?" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:469 -msgid "By default the ``composer.json`` file places all Mautic core, Plugin and Theme files in the ``docroot`` folder. It's possible to change this folder to your own needs." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:472 -msgid "In following examples, ``docroot`` moves into ``public``." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:475 -msgid "New installations" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:477 -msgid "Run the create-project command without installing:" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:483 -msgid "Do a find and replace in the ``composer.json`` file to change ``docroot/`` into ``public/``" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:484 -#: ../getting_started/how_to_install_mautic.rst:497 -msgid "Review the changes in the ``composer.json`` file to ensure that there are no unintentional replacements" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:485 -msgid "Run ``composer install`` to install all dependencies in the correct location" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:488 -msgid "Existing installations" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:490 -msgid "Move the ``docroot/`` to ``public/``" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:496 -msgid "Do a find and replace in the ``composer.json`` file to change ``docroot/`` to ``public/``" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:498 -msgid "Run ``composer update --lock`` to ensure the autoloader is aware of the changed folder" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:503 -msgid "Setting up a local testing environment with DDEV" -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:507 -msgid "Often there is a need to have a local environment for testing Mautic - for example making a backup, testing new features or bug fixes." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:509 -msgid "In Mautic, DDEV is the tool of choice for this purpose. It's very easy to work with." -msgstr "" - -#: ../getting_started/how_to_install_mautic.rst:511 -msgid "To learn how to set up DDEV with Mautic, please review the documentation in the Contributors :xref:`Handbook`." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:4 -msgid "How to update Mautic" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:8 -msgid "There are two ways to update Mautic:" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:10 -msgid "Using the Command Line - recommended" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:11 -msgid "Through the User interface" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:13 -msgid "If your instance is in production, has a large number of Contacts and/or is on shared hosting, it's **strongly** recommended that you update at the command line." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:16 -msgid "Updating in the User interface requires a significant amount of resources, and can be error-prone if the server restricts resource allocation. A failed update or corrupted data can result from this. It's planned to remove this feature in Mautic 5.0, requiring updating at the command line." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:19 -msgid "Updating at the command line (non-Composer based installations)" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:21 -msgid "Before you commence updating Mautic, **please ensure that you have a tested backup of your Mautic instance**." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:23 -#: ../getting_started/how_to_update_mautic.rst:93 -msgid "This means that you have downloaded the files and database of your Mautic instance, and you have re-created it in a test environment somewhere and tested that everything is working as expected. This is your only recourse if there are any problems with the update. Never update without having a working, up-to-date backup." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:26 -msgid "Checking for updates at the command line" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:28 -msgid "Mautic can only be updated using Composer via the command line from version 5.0." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:30 -msgid "The update feature within the Mautic User interface (UI) has been deprecated from Mautic 4.2, but you will be alerted within the UI (see below figure) when a new version of the Mautic is available." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:None -msgid "Screenshot showing deprecated update feature warning" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:38 -msgid "Before starting to upgrade, it's highly recommended to take a backup of your instance. If updates are available, you will receive an update notification followed by step-by-step instructions in the command-line interface to complete the process." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:40 -msgid "Log in via the command line, and change directory to the Mautic directory using the command:" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:48 -msgid "The first step is to find out if there are any updates available using the following command:" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:54 -msgid "The output from this command tells you if there are any updates to apply. The notification links to an announcement post which explains what the release includes, and the recommended environment requirements if they are not being met (for example, a higher version of PHP must be installed or plugins that must be updated)." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:57 -msgid "It's a good idea to review the announcement link for information about the release. There may be important information or steps that you may need to take before updating." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:59 -msgid "After a system readiness check, you can apply the updates." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:62 -msgid "Installing updates at the command line" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:64 -msgid "If there are updates available, run the following command to apply them:" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:71 -msgid "This is followed by a prompt to run the command again with this additional argument:" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:79 -msgid "Updating in the browser" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:81 -msgid "When updating Mautic, there are several tasks which can take a long time to complete depending on the size of your Mautic instance." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:85 -msgid "If you have a lot of contacts and/or use shared hosting, you might run into problems when updating with the notification 'bell' icon in Mautic." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:87 -msgid "When updating within the browser, problems usually manifest as the update hanging part way through, or crashing with an error. They often arise as a result of resource limitation, particularly on shared hosting environments." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:89 -msgid "For this reason, it's always recommended that you :ref:`update at the command line` wherever possible. From Mautic 5.0 the ability to update in the browser will be completely removed, and you will have to update at the command line." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:91 -msgid "Before you commence updating, **please ensure that you have a tested backup of your Mautic instance**." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:96 -msgid "Checking for updates in the browser" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:98 -msgid "When Mautic makes a new release, a notification appears in your Mautic instance." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:100 -msgid "The notification links to an announcement post which explains what the release includes." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:103 -msgid "It's a good idea to read the announcement link for information about the release. There may be important information or steps that you may need to take before updating." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:105 -msgid "Once you have thoroughly read the release notes, and have tested your backup Mautic instance, you can click the notification to complete the update." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:107 -msgid "The update takes time to complete, and each step updates in the browser as it proceeds. Be patient and allow it to finish. On completion, a message confirms that the update has completed successfully." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:110 -msgid "The update wasn't successful" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:112 -msgid "If this has happened to you, head over to the Troubleshooting section for a step-by-step walk-through of how to complete the update. Maybe consider using the command line next time." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:115 -msgid "Stability levels" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:117 -msgid "By default, Mautic receives notifications both in the user interface and at the command line for stable releases only." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:119 -msgid "If you wish to help with testing early access releases in a development environment, do the following" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:121 -msgid "Edit your configuration and set the stability level to Alpha, Beta, or Release Candidate. This allows you to receive notifications for early access releases." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:122 -msgid "Always read the release notes before updating to an early access release." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:123 -msgid "Never enable early access releases for production instances." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:126 -msgid "What to do if you need help updating Mautic" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:128 -msgid "If you need help, you can ask for it in several places. You should remember that most members of the Community Forums, Slack, and GitHub are volunteers." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:130 -msgid "The :xref:`Mautic Community Forums` is the place where you can ask questions about your configuration if you think it is the cause of the problem. Please search before posting your question, since someone may have already answered it." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:132 -msgid "The live :xref:`Mautic Community Slack` is also available, but all support requests have to be posted on the forums. Create your request there first, then drop a link in Slack if you plan to discuss it there." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:134 -msgid "In all cases, it's important to provide details about the issue, as well as the steps you have taken to resolve it. At a minimum, include the following:" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:136 -msgid "Steps to reproduce your problem - a step-by-step walk-through of what you have done so far" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:137 -msgid "Your server's PHP version." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:138 -msgid "The version of Mautic you are on, and the version you are aiming to update to" -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:139 -msgid "The error messages you are seeing - if you don't see the error message directly, search for it in the var/logs folder within your Mautic directory and in the server logs. Server logs are in different places depending on your setup. Ubuntu servers generally have logs in ``/var/log/apache2/error.log``. Sometimes your hosting provider might offer a graphical interface to view logs in your Control Panel." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:141 -msgid "If you don't provide the information requested as a minimum, the person who might try to help you has to ask you for it, so please save them the trouble and provide the information upfront. Also, importantly, please be polite. Mautic is an open source project, and people are giving their free time to help you." -msgstr "" - -#: ../getting_started/how_to_update_mautic.rst:143 -msgid "If you are sure that you have discovered a bug and you want to report it to developers, you can :xref:`Mautic Github New Issue` on GitHub. GitHub is not the right place to request support or ask for help with configuration errors. Always post on the forums first if you aren't sure, if a bug report is appropriate this can link to the forum thread." -msgstr "" - -#: ../getting_started/switching_composer.rst:4 -msgid "How to switch to Composer" -msgstr "" - -#: ../getting_started/switching_composer.rst:8 -msgid "Until Mautic 4, you could download Mautic as a ZIP file and install it on any PHP server. However, many users were running into installation and update errors, many of which caused considerable frustration and in some cases, significant business disruption." -msgstr "" - -#: ../getting_started/switching_composer.rst:11 -msgid "In addition, Mautic recently introduced the :ref:`Mautic Marketplace` which isn't compatible with this installation method." -msgstr "" - -#: ../getting_started/switching_composer.rst:13 -msgid "As a result of the reasons mentioned above, Composer becomes the default method for installing and updating Mautic starting with the release of Mautic 5. Read more in the :xref:`composer blog post`." -msgstr "" - -#: ../getting_started/switching_composer.rst:16 -msgid "Switching to a Composer-based installation" -msgstr "" - -#: ../getting_started/switching_composer.rst:18 -msgid "Before starting, it's good to understand that there's two aspects to Mautic:" -msgstr "" - -#: ../getting_started/switching_composer.rst:20 -msgid "The database - This is where Mautic stores your Contact data." -msgstr "" - -#: ../getting_started/switching_composer.rst:22 -msgid "The codebase - This is where Mautic interacts with the database." -msgstr "" - -#: ../getting_started/switching_composer.rst:24 -msgid "When switching to a Composer-based installation, the **database** isn't touched, only the **codebase.**" -msgstr "" - -#: ../getting_started/switching_composer.rst:26 -msgid "In this tutorial, it's assumed that Mautic is currently installed in ``/var/www/html``." -msgstr "" - -#: ../getting_started/switching_composer.rst:28 -msgid "Here's the steps to follow to switch to a Composer-based installation:" -msgstr "" - -#: ../getting_started/switching_composer.rst:30 -msgid "Go to ``/var/www``" -msgstr "" - -#: ../getting_started/switching_composer.rst:32 -msgid "Run ``composer create-project mautic/recommended-project:^4 html-new --no-interaction``" -msgstr "" - -#: ../getting_started/switching_composer.rst:34 -msgid "Copy the following files and folders from ``/var/www/html`` to ``/var/www/html-new``:" -msgstr "" - -#: ../getting_started/switching_composer.rst:36 -msgid "Configuration files - in most cases, located at ``app/config/local.php`` - move to ``docroot/app/config/local.php``" -msgstr "" - -#: ../getting_started/switching_composer.rst:38 -msgid "The entire ``plugins`` directory - move to ``docroot/plugins``." -msgstr "" - -#: ../getting_started/switching_composer.rst:40 -msgid "Uploads - in most cases, located at ``app/media/files`` and ``app/media/images`` - move to ``docroot/app/media/files`` and ``docroot/app/media/images`` respectively." -msgstr "" - -#: ../getting_started/switching_composer.rst:42 -msgid "Custom dashboards from ``app/media/dashboards`` - move to ``docroot/app/media/dashboards``" -msgstr "" - -#: ../getting_started/switching_composer.rst:44 -msgid "Any custom Themes from ``themes`` - move to ``/docroot/themes``" -msgstr "" - -#: ../getting_started/switching_composer.rst:46 -msgid "Any translations from ``translations`` - move to ``/docroot/translations``" -msgstr "" - -#: ../getting_started/switching_composer.rst:48 -msgid "Rename ``/var/www/html`` to ``/var/www/html-old`` and ``/var/www/html-new`` to ``/var/www/html``" -msgstr "" - -#: ../getting_started/switching_composer.rst:50 -msgid "Update your web server configuration to point to ``/var/www/html/docroot`` instead of ``/var/www/html``" -msgstr "" - -#: ../getting_started/switching_composer.rst:52 -msgid "Log in to Mautic, and in your global settings enable the switch to fully manage Mautic with Composer - this will also enable you to work with the Mautic Marketplace." -msgstr "" - -#: ../getting_started/switching_composer.rst:None -msgid "Screenshot of switch enable Composer" -msgstr "" - -#: ../getting_started/switching_composer.rst:58 -msgid "You have successfully switched to a Composer-based installation. Test Mautic to see if it works as expected." -msgstr "" - -#: ../getting_started/switching_composer.rst:63 -msgid "Frequently Asked Questions (FAQs)" -msgstr "" - -#: ../getting_started/switching_composer.rst:65 -msgid "Q: Is existing data retained?" -msgstr "" - -#: ../getting_started/switching_composer.rst:67 -msgid "A: Yes, switching to the Composer-based installation only affects app files. It doesn't affect your data in any way." -msgstr "" - -#: ../getting_started/switching_composer.rst:69 -msgid "Q: What's the minimum Mautic version required to switch to the Composer-based installation?" -msgstr "" - -#: ../getting_started/switching_composer.rst:71 -msgid "A: It is necessary to have at least Mautic 4.0.0 in order to switch to a Composer-based installation." -msgstr "" diff --git a/docs/docs_translations/index.pot b/docs/docs_translations/index.pot deleted file mode 100644 index 55e16021..00000000 --- a/docs/docs_translations/index.pot +++ /dev/null @@ -1,145 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../index.rst:24 -msgid "Welcome to Mautic" -msgstr "" - -#: ../index.rst:31 -msgid "Getting Started with Mautic" -msgstr "" - -#: ../index.rst:40 -msgid "Configuration" -msgstr "" - -#: ../index.rst:51 -msgid "Authentication" -msgstr "" - -#: ../index.rst:58 -msgid "Contacts" -msgstr "" - -#: ../index.rst:69 -msgid "Segments" -msgstr "" - -#: ../index.rst:76 -msgid "Campaigns" -msgstr "" - -#: ../index.rst:87 -msgid "Categories" -msgstr "" - -#: ../index.rst:94 -msgid "Channels" -msgstr "" - -#: ../index.rst:108 -msgid "Companies" -msgstr "" - -#: ../index.rst:115 -msgid "Components" -msgstr "" - -#: ../index.rst:126 -msgid "Dashboard" -msgstr "" - -#: ../index.rst:133 -msgid "Email & Landing Page Builders" -msgstr "" - -#: ../index.rst:141 -msgid "Mautic Marketplace" -msgstr "" - -#: ../index.rst:148 -msgid "Plugins" -msgstr "" - -#: ../index.rst:176 -msgid "Points" -msgstr "" - -#: ../index.rst:184 -msgid "Queue" -msgstr "" - -#: ../index.rst:192 -msgid "Reports" -msgstr "" - -#: ../index.rst:199 -msgid "Search" -msgstr "" - -#: ../index.rst:206 -msgid "Stages" -msgstr "" - -#: ../index.rst:213 -msgid "Themes" -msgstr "" - -#: ../index.rst:224 -msgid "Translation" -msgstr "" - -#: ../index.rst:231 -msgid "User and Roles" -msgstr "" - -#: ../index.rst:2 -msgid "Welcome to the Mautic documentation" -msgstr "" - -#: ../index.rst:4 -msgid "**Mautic** is an open source marketing automation platform that provides you with the greatest level of audience intelligence, thus enabling you to make more meaningful customer connections." -msgstr "" - -#: ../index.rst:6 -msgid "To get started with Mautic, follow the :doc:`Getting started guide`. For next steps, you can learn :doc:`how to update Mautic`." -msgstr "" - -#: ../index.rst:9 -msgid "There are different types of documentation available to help you navigate your way through Mautic." -msgstr "" - -#: ../index.rst:11 -msgid ":xref:`End User Documentation` - Describes each aspect of Mautic in detail and explains how to use it.." -msgstr "" - -#: ../index.rst:13 -msgid ":xref:`Developer Documentation` - Describes details about the Mautic API, Webhooks, Themes and Plugin development." -msgstr "" - -#: ../index.rst:15 -msgid ":xref:`Knowledgebase` - Provides a database of tutorials, FAQs, and how-to articles." -msgstr "" - -#: ../index.rst:17 -msgid ":xref:`Community Handbook` - Describes how to get involved and contribute to Mautic's documentation development." -msgstr "" - -#: ../index.rst:21 -msgid "This documentation project is under active development." -msgstr "" diff --git a/docs/docs_translations/marketplace.pot b/docs/docs_translations/marketplace.pot deleted file mode 100644 index 38430bbc..00000000 --- a/docs/docs_translations/marketplace.pot +++ /dev/null @@ -1,222 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../marketplace/marketplace.rst:4 -msgid "Mautic Marketplace" -msgstr "" - -#: ../marketplace/marketplace.rst:10 -msgid "The current Marketplace version doesn't verify Mautic version compatibility of Plugins yet, as this requires a change in each existing Plugin." -msgstr "" - -#: ../marketplace/marketplace.rst:12 -msgid "Please don't blindly manually install Plugins you see in the Mautic Marketplace, as they may not work with your version of Mautic. Always verify if they support your Mautic version before installing. Developers can refer to the :xref:`Developer Documentation Marketplace` for how to make your Plugin compatible with the Mautic Marketplace." -msgstr "" - -#: ../marketplace/marketplace.rst:17 -msgid "Using the Mautic Marketplace" -msgstr "" - -#: ../marketplace/marketplace.rst:21 -msgid "From Mautic 4.2, a setting in the Mautic Configuration specifies that the instance uses Composer, which allows the installation, update, and removal of Plugins in the Mautic Marketplace. This is a requirement due to the technology which underpins the Mautic Marketplace." -msgstr "" - -#: ../marketplace/marketplace.rst:None -msgid "Screenshot of switch enable Composer" -msgstr "" - -#: ../marketplace/marketplace.rst:27 -msgid "Once configured, you can search the Marketplace using the filter, and install Plugins by selecting the option from the dropdown." -msgstr "" - -#: ../marketplace/marketplace.rst:None -#: ../marketplace/marketplace.rst:None -msgid "Screenshot of Composer enabled" -msgstr "" - -#: ../marketplace/marketplace.rst:33 -msgid "If you haven't correctly set the Composer setting, Mautic displays a warning that the Mautic Marketplace is available in read-only mode, with a link which explains how to transition to a :doc:`Composer-managed` installation." -msgstr "" - -#: ../marketplace/marketplace.rst:42 -msgid "List of Plugins" -msgstr "" - -#: ../marketplace/marketplace.rst:46 -msgid "The list of Plugins available in the Marketplace is accessible from your Mautic administration menu. Click the **cog icon** in the top right hand corner to display the menu." -msgstr "" - -#: ../marketplace/marketplace.rst:48 -msgid "The list view allows you to search for specific keywords. It displays quick stats including Plugin downloads and how many stars it has in :xref:`Packagist`. It also shows the vendor who has developed the Plugin. Sadly, the sorting by columns isn't available at the moment because it's not supported by the Packagist API. It's planned to add this in a future release." -msgstr "" - -#: ../marketplace/marketplace.rst:50 -msgid "Click a Plugin name to view details." -msgstr "" - -#: ../marketplace/marketplace.rst:None -msgid "Screenshot of marketplace list" -msgstr "" - -#: ../marketplace/marketplace.rst:57 -msgid "Plugin detail page" -msgstr "" - -#: ../marketplace/marketplace.rst:59 -msgid "The detail page gives you enough information together with links to additional resources to decide whether you want to install the Plugin or not." -msgstr "" - -#: ../marketplace/marketplace.rst:None -msgid "Screenshot of marketplace detail" -msgstr "" - -#: ../marketplace/marketplace.rst:67 -msgid "Latest stable version" -msgstr "" - -#: ../marketplace/marketplace.rst:69 -msgid "The first information you see is the latest stable version. *From Mautic 4.2, this includes the currently installed - if any - version and the ability to upgrade.*" -msgstr "" - -#: ../marketplace/marketplace.rst:71 -msgid "All Plugins should follow :xref:`semantic versioning` so you can see from the first glance whether it's a breaking change version, feature version or bug fix - patch - version. In short, it's more risky to install breaking change versions and less risky to install a bug fix version." -msgstr "" - -#: ../marketplace/marketplace.rst:73 -msgid "The license should be GPLv3 mostly as Mautic uses this license, and it's a viral license. This means anything using Mautic's code base should also use the same license." -msgstr "" - -#: ../marketplace/marketplace.rst:75 -msgid "Required packages are dependencies. The bigger is the list of dependencies, the bigger the size of the Plugin. More dependencies also means more security risks and incompatibility issues with future upgrades." -msgstr "" - -#: ../marketplace/marketplace.rst:78 -msgid "All versions" -msgstr "" - -#: ../marketplace/marketplace.rst:80 -msgid "The next table shows the list of all versions. *In the future versions of the Marketplace it should be possible to select which version you want to install or upgrade to*." -msgstr "" - -#: ../marketplace/marketplace.rst:82 -msgid "From the list you can see Plugin versions, and the release cadence. When you click a specific version, a new window opens where the Plugin maintainers should provide a changelog. This tells you what's added or bugs fixed in the specific version." -msgstr "" - -#: ../marketplace/marketplace.rst:85 -msgid "Maintainers" -msgstr "" - -#: ../marketplace/marketplace.rst:87 -msgid "In this section is a list of maintainers of the Plugin on Packagist. There may be more contributors in the GitHub repository. There is also a link to the maintainer's Packagist detail page where you can browse other PHP packages by the same maintainer." -msgstr "" - -#: ../marketplace/marketplace.rst:90 -msgid "GitHub information" -msgstr "" - -#: ../marketplace/marketplace.rst:92 -msgid ":xref:`github` is where many developers host their code. The majority of Mautic Plugins are available on GitHub. There are some stats available directly in this section, but you can find much more if you follow the link to the repository." -msgstr "" - -#: ../marketplace/marketplace.rst:95 -msgid "Packagist information" -msgstr "" - -#: ../marketplace/marketplace.rst:97 -msgid ":xref:`Packagist` is a PHP package repository. It's not related specifically to the Mautic Community, but to the PHP community." -msgstr "" - -#: ../marketplace/marketplace.rst:99 -msgid "All the PHP packages listed in Packagist are installable by Composer which is a tool for dependency management used under the hood when you install a Mautic Plugin. The Packagist section shows download stats of Plugin installations in different time frames." -msgstr "" - -#: ../marketplace/marketplace.rst:102 -msgid "Context menu" -msgstr "" - -#: ../marketplace/marketplace.rst:103 -msgid "The context menu shows actions you can take." -msgstr "" - -#: ../marketplace/marketplace.rst:105 -msgid "Close takes you to the List View" -msgstr "" - -#: ../marketplace/marketplace.rst:107 -msgid "Install installs the Plugin" -msgstr "" - -#: ../marketplace/marketplace.rst:109 -msgid "Issue tracker opens a new window with the issue tracker for the Plugin. It shows only if the Plugin has this information available. Use this option to search for issues with the Plugin and to report new issues to the maintainers." -msgstr "" - -#: ../marketplace/marketplace.rst:113 -msgid "Command line (CLI) command" -msgstr "" - -#: ../marketplace/marketplace.rst:115 -msgid "The Marketplace has commands for those who prefer using the command line to the user interface, or for automation of processes." -msgstr "" - -#: ../marketplace/marketplace.rst:120 -msgid "List Plugins" -msgstr "" - -#: ../marketplace/marketplace.rst:124 -msgid "``bin/console mautic:marketplace:list`` lists the first page of available Plugins like so:" -msgstr "" - -#: ../marketplace/marketplace.rst:163 -msgid "There are options allowing you to filter or go to next pages. To display the full list, add ``--help`` after the command, as used in other Mautic commands." -msgstr "" - -#: ../marketplace/marketplace.rst:172 -msgid "Example usage how to search for a ``Captcha`` Plugin: ``bin/console mautic:marketplace:list --filter=captcha``" -msgstr "" - -#: ../marketplace/marketplace.rst:175 -msgid "Planned features" -msgstr "" - -#: ../marketplace/marketplace.rst:177 -msgid "Watch out for more features in future releases including:" -msgstr "" - -#: ../marketplace/marketplace.rst:179 -msgid "Automatic Plugin updates - a configuration that allows you to set globally whether you want to automatically upgrade Plugins and also have the possibility of configuring this at the Plugin level. Automatic upgrades make sense only for bug fix releases. Other releases are too risky and manual updates required. :xref:`API reference`" -msgstr "" - -#: ../marketplace/marketplace.rst:181 -msgid "List security advisories :xref:`API reference`," -msgstr "" - -#: ../marketplace/marketplace.rst:183 -msgid "Notifications about new versions and security vulnerabilities that identified," -msgstr "" - -#: ../marketplace/marketplace.rst:185 -msgid "Support also Theme installations and updates." -msgstr "" - -#: ../marketplace/marketplace.rst:190 -msgid "How to get your Plugin listed on the Mautic Marketplace" -msgstr "" - -#: ../marketplace/marketplace.rst:194 -msgid "Please review the resources on the :xref:`Developer Documentation Marketplace` for more information." -msgstr "" diff --git a/docs/docs_translations/overview.pot b/docs/docs_translations/overview.pot deleted file mode 100644 index c2498b62..00000000 --- a/docs/docs_translations/overview.pot +++ /dev/null @@ -1,153 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../overview/overview.rst:2 -msgid "Mautic overview" -msgstr "" - -#: ../overview/overview.rst:4 -msgid "The Mautic platform helps you create a strong marketing strategy for your business. With Mautic, you can:" -msgstr "" - -#: ../overview/overview.rst:7 -msgid "Connect with your Contacts over Channels like Emails, Text Messages, Social Media, and Focus Items." -msgstr "" - -#: ../overview/overview.rst:9 -msgid "Segment your Contacts based on business requirements and personalize your marketing strategy for each Segment." -msgstr "" - -#: ../overview/overview.rst:10 -msgid "Create personalized Campaigns to engage with your Contacts." -msgstr "" - -#: ../overview/overview.rst:11 -msgid "Use performance metrics in Dashboards, Reports, Points, and Stages to measure the efficiency of your marketing strategy." -msgstr "" - -#: ../overview/overview.rst:14 -msgid "How it works" -msgstr "" - -#: ../overview/overview.rst:16 -msgid "To start, it helps to understand how the different pieces of Mautic fit together to give you a holistic marketing platform experience." -msgstr "" - -#: ../overview/overview.rst:None -msgid "Mautic Overview" -msgstr "" - -#: ../overview/overview.rst:24 -msgid "Contact management" -msgstr "" - -#: ../overview/overview.rst:26 -msgid "Build a rich and functional database of Contacts for your business, group them together based on your business needs or based on shared attributes." -msgstr "" - -#: ../overview/overview.rst:28 -msgid ":doc:`/contacts/manage_contacts` - Known or unknown individuals who have visited your websites or interacted with your business in some way. Contacts are the primary factor of a marketing automation platform." -msgstr "" - -#: ../overview/overview.rst:30 -msgid ":doc:`/segments/manage_segments` - A group of your Contacts that share certain attributes. For example, you may segment Contacts based on a Contact's location. This may help you easily send out location-based offers or promotions to this specific group of Contacts." -msgstr "" - -#: ../overview/overview.rst:32 -msgid ":doc:`/companies/companies_overview` - An assigned group of Contacts based on their Company or Companies." -msgstr "" - -#: ../overview/overview.rst:36 -msgid "Components" -msgstr "" - -#: ../overview/overview.rst:38 -msgid "Create and manage various types of content that you use for your marketing campaigns to engage your Contacts." -msgstr "" - -#: ../overview/overview.rst:40 -msgid ":doc:`/components/assets` - Valuable items that you provide to your Contacts upon completion of a Form. White papers, a downloadable app/file, documents or videos are some examples of Assets." -msgstr "" - -#: ../overview/overview.rst:42 -msgid ":doc:`/components/forms` - Forms are the primary point of customer engagement. They're used to collect contact information, often in exchange for providing access to an Asset such as a download, an event registration, or an Email newsletter." -msgstr "" - -#: ../overview/overview.rst:44 -msgid ":doc:`/components/landing_pages` - A powerful feature that not only allows you to promote content quickly and easily, but also allows you to rapidly create Landing Pages that are tightly tailored for a specific purpose, such as an advertising campaign." -msgstr "" - -#: ../overview/overview.rst:46 -msgid ":doc:`/components/dynamic_web_content` - A feature that you can use to personalize the web experience for your Contacts. Marketers can display different content to different people in specific areas of a webpage." -msgstr "" - -#: ../overview/overview.rst:49 -msgid "Campaigns" -msgstr "" - -#: ../overview/overview.rst:51 -msgid ":doc:`/campaigns/campaigns_overview` - With your Contact information and the Components in place, you can start to create customized marketing activities for your Contacts. You create these marketing activities primarily in Campaigns." -msgstr "" - -#: ../overview/overview.rst:54 -msgid "Channels" -msgstr "" - -#: ../overview/overview.rst:56 -msgid "Choose one or more Channels to deliver the content and messages to your Contacts." -msgstr "" - -#: ../overview/overview.rst:58 -msgid ":doc:`/channels/marketing_messages` - A way to personalize communication with your Contacts. With Marketing Messages, Contacts receive your content on a Channel they've set as their preference." -msgstr "" - -#: ../overview/overview.rst:60 -msgid ":doc:`/channels/emails` - Use built-in Email templates to send messages to a group of your Contacts, or send personalized messages to specific Contacts." -msgstr "" - -#: ../overview/overview.rst:62 -msgid ":doc:`/channels/focus_items` - A type of web personalization that enables marketers to embed on a webpage pop-up messages and Forms, bars and splash screens based on the Contact's behavior. By using Focus Items, you can easily convert visitors into known Contacts." -msgstr "" - -#: ../overview/overview.rst:64 -msgid ":doc:`/channels/social_monitoring` - Marketers can add Contacts to Mautic through Twitter mentions and hashtags." -msgstr "" - -#: ../overview/overview.rst:67 -msgid "Assess performance" -msgstr "" - -#: ../overview/overview.rst:69 -msgid "Analyze trends and assess the performance of your marketing strategy using various tools." -msgstr "" - -#: ../overview/overview.rst:71 -msgid ":doc:`/dashboard/dashboard` - A high-level representation of Contact data, Campaigns, and activities. You can create a highly personalized dashboard based on the information that you want to track." -msgstr "" - -#: ../overview/overview.rst:73 -msgid ":doc:`/reports/reports` - A tool to measure the effectiveness of your marketing Campaigns, Emails, Forms, or Landing Page hits. Reports also let you troubleshoot or workaround areas of improvement to enhance your marketing strategy." -msgstr "" - -#: ../overview/overview.rst:75 -msgid ":doc:`/points/points` - A score that's an indicator of progress for a Contact or customer. Points are a way for marketers to measure which of their Contacts are the most engaged based on their interactions and behavior." -msgstr "" - -#: ../overview/overview.rst:77 -msgid ":doc:`/stages/stages` - A customizable feature that enables you to keep a track of where your Contacts are in their marketing/sales journey." -msgstr "" diff --git a/docs/docs_translations/plugins.pot b/docs/docs_translations/plugins.pot deleted file mode 100644 index f5b28201..00000000 --- a/docs/docs_translations/plugins.pot +++ /dev/null @@ -1,213 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../plugins/amazon.rst:4 -msgid "Amazon S3" -msgstr "" - -#: ../plugins/citrix.rst:4 -msgid "Citrix" -msgstr "" - -#: ../plugins/clearbit.rst:4 -msgid "Clearbit" -msgstr "" - -#: ../plugins/connectwise.rst:4 -msgid "ConnectWise" -msgstr "" - -#: ../plugins/fullcontact.rst:4 -msgid "FullContact" -msgstr "" - -#: ../plugins/gmail.rst:4 -msgid "GMail" -msgstr "" - -#: ../plugins/hubspot.rst:4 -msgid "HubSpot" -msgstr "" - -#: ../plugins/icontact.rst:4 -msgid "iContact" -msgstr "" - -#: ../plugins/mailchimp.rst:4 -msgid "MailChimp" -msgstr "" - -#: ../plugins/microsoft_dynamics_crm.rst:4 -msgid "Microsoft Dynamics CRM" -msgstr "" - -#: ../plugins/microsoft_outlook.rst:4 -msgid "Microsoft Outlook" -msgstr "" - -#: ../plugins/pipedrive.rst:4 -msgid "Pipedrive" -msgstr "" - -#: ../plugins/plugin_resources.rst:4 -msgid "Plugin resources" -msgstr "" - -#: ../plugins/salesforce.rst:4 -msgid "Salesforce" -msgstr "" - -#: ../plugins/social_login.rst:4 -msgid "Social Login" -msgstr "" - -#: ../plugins/sugar_crm.rst:4 -msgid "Sugar CRM" -msgstr "" - -#: ../plugins/tag_manager.rst:4 -msgid "Tag Manager" -msgstr "" - -#: ../plugins/twilio.rst:4 -msgid "Twilio" -msgstr "" - -#: ../plugins/twilio.rst:7 -msgid "Mautic - Twilio Plugin" -msgstr "" - -#: ../plugins/twilio.rst:11 -msgid "Before you start to send text messages from your Mautic instance, it needs to connect to the service which can send them." -msgstr "" - -#: ../plugins/twilio.rst:13 -msgid "The first and default implemented service is :xref:`Twilio`." -msgstr "" - -#: ../plugins/twilio.rst:15 -msgid "In order to configure the text messages correctly, follow these steps:" -msgstr "" - -#: ../plugins/twilio.rst:17 -msgid "Create an account at :xref:`Twilio`." -msgstr "" - -#: ../plugins/twilio.rst:19 -msgid "In Mautic, go to *Settings* (cog icon) > *Plugins*." -msgstr "" - -#: ../plugins/twilio.rst:21 -msgid "Open *Twilio* Plugin and activate it." -msgstr "" - -#: ../plugins/twilio.rst:23 -msgid "Copy the *Account Sender ID* from Twilio account and paste it to *Account Sender ID* field in the Twilio Plugin configuration." -msgstr "" - -#: ../plugins/twilio.rst:25 -msgid "Unlock and copy the *Auth Token* and paste it to *Auth Token* field in the Twilio Plugin configuration." -msgstr "" - -#: ../plugins/twilio.rst:27 -msgid "Go to *Products* > *Phone Numbers* in Twilio, copy the number and paste it to the *Sending Phone Number* field in Mautic." -msgstr "" - -#: ../plugins/twilio.rst:29 -msgid "Select the *Text Message Enabled*? switch to *Yes* and save the Mautic configuration." -msgstr "" - -#: ../plugins/twilio.rst:34 -msgid "Alphanumeric Sender ID" -msgstr "" - -#: ../plugins/twilio.rst:38 -msgid "Alphanumeric Sender ID allows you to send Twilio Programmable SMS messages using a personalized sender name, in supported countries see :xref:`International Support for Alphanumeric Sender ID`." -msgstr "" - -#: ../plugins/twilio.rst:40 -msgid "Instead of using an E.164 formatted Twilio Phone number for the \"From\" value, you can use a custom string like your own business' branding." -msgstr "" - -#: ../plugins/twilio.rst:44 -msgid "You can't reply directly to messages sent out with an Alphanumeric Sender ID." -msgstr "" - -#: ../plugins/twilio.rst:49 -msgid "Alphanumeric Sender ID requirements" -msgstr "" - -#: ../plugins/twilio.rst:53 -msgid "Alphanumeric Sender ID is automatically supported on all new :xref:`upgraded (paid) Twilio accounts`. It's not supported for Free Trial accounts." -msgstr "" - -#: ../plugins/twilio.rst:55 -msgid "You can verify if your account has Alphanumeric Sender enabled by following these steps:" -msgstr "" - -#: ../plugins/twilio.rst:57 -msgid "Login to your account at :xref:`Twilio`." -msgstr "" - -#: ../plugins/twilio.rst:59 -msgid "From the left side navigation bar, click Programmable SMS." -msgstr "" - -#: ../plugins/twilio.rst:61 -msgid "Click Settings." -msgstr "" - -#: ../plugins/twilio.rst:63 -msgid "Verify that \"Alphanumeric Sender ID\" is set to Enabled." -msgstr "" - -#: ../plugins/twilio.rst:65 -msgid "Follow these steps to see if your account has Alphanumeric Sender enabled." -msgstr "" - -#: ../plugins/twilio.rst:70 -msgid "Send SMS Messages using an Alphanumeric Sender ID with Mautic" -msgstr "" - -#: ../plugins/twilio.rst:74 -msgid "Just setup your alias in plugin settings:" -msgstr "" - -#: ../plugins/twilio.rst:0 -msgid "Screenshot of alphanumeric-id" -msgstr "" - -#: ../plugins/twilio.rst:80 -msgid "Read more info about :xref:`Alphanumeric Sender ID` on Twillio site." -msgstr "" - -#: ../plugins/twitter.rst:4 -msgid "Twitter" -msgstr "" - -#: ../plugins/vtiger.rst:4 -msgid "Vtiger" -msgstr "" - -#: ../plugins/zapier.rst:4 -msgid "Zapier" -msgstr "" - -#: ../plugins/zoho_crm.rst:4 -msgid "Zoho CRM" -msgstr "" diff --git a/docs/docs_translations/points.pot b/docs/docs_translations/points.pot deleted file mode 100644 index d38ad797..00000000 --- a/docs/docs_translations/points.pot +++ /dev/null @@ -1,201 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../points/points.rst:4 -msgid "Points" -msgstr "" - -#: ../points/points.rst:8 -msgid "Points provide a way for properly weighing Contacts. These Points have both triggers and actions. The following section outlines all the relevant term definitions, and a thorough understanding of how Points function. This helps make your overall marketing automation process successful using Points" -msgstr "" - -#: ../points/points.rst:11 -msgid "Point actions" -msgstr "" - -#: ../points/points.rst:13 -msgid "Point actions are those times when a Contact receives a change in their Point total. These actions can be either positive or negative Point changes and occur based on a particular action as you determine." -msgstr "" - -#: ../points/points.rst:15 -msgid "To add a new action:" -msgstr "" - -#: ../points/points.rst:17 -msgid "Click **Points > Point Actions > + New** - located in the top right corner." -msgstr "" - -#: ../points/points.rst:None -msgid "Screenshot of Points action" -msgstr "" - -#: ../points/points.rst:22 -msgid "In the main panel, there are four boxes for key information. Enter the appropriate information." -msgstr "" - -#: ../points/points.rst:24 -msgid "**Name** - The name of your action. This is how the action displays in your list of actions, so choose an identifiable name." -msgstr "" - -#: ../points/points.rst:26 -msgid "**Description** - Add a description to help you find certain actions. There may be more actions which are similar or more in-depth." -msgstr "" - -#: ../points/points.rst:28 -msgid "**Change Points (+/-)** - The value change to set for the action. The ``+`` isn't necessary when adding Points. When subtracting Points, add the ``-`` symbol." -msgstr "" - -#: ../points/points.rst:30 -msgid "**When a Contact…** - This is the behavior or action the Contact must complete to trigger the action." -msgstr "" - -#: ../points/points.rst:32 -msgid "On the right side is more information:" -msgstr "" - -#: ../points/points.rst:34 -msgid "**Category** - Organize your Point actions based on their goals, Campaigns, etc. For more information, see :doc:`Categories`. All Points accumulate on a Contact record, regardless of Category. There is one Points score for each Contact." -msgstr "" - -#: ../points/points.rst:36 -msgid "**Published and Publish/Unpublish at date/time** - Once you have a Point action, Mautic awards Points when a Contact completes the action. Points aren't given for unpublished actions. If you have target behaviors that you want to award Points for within a certain time period, you can set the publish and unpublish dates" -msgstr "" - -#: ../points/points.rst:38 -msgid "**Is repeatable** - To award Points each time a Contact completes an action, select **Yes**. If you want to award Points **only** the first time someone completes the action, select **No** - this is the default." -msgstr "" - -#: ../points/points.rst:40 -msgid "Click **Save** or **Save & Close**." -msgstr "" - -#: ../points/points.rst:43 -msgid "Point triggers" -msgstr "" - -#: ../points/points.rst:45 -msgid "Once a Contact has accumulated a Point total, you may want to trigger an action with the Contact. You may create multiple triggers for different Point values." -msgstr "" - -#: ../points/points.rst:None -msgid "Screenshot of Points trigger" -msgstr "" - -#: ../points/points.rst:50 -msgid "Creating Point Triggers is like creating Point Actions. The **Name**, **Description**, **Category**, and **Publish** options are all the same. The trigger fires based on the minimum number of Points. Set a number and decide if you want to **Trigger for existing applicable Contacts upon saving - if published**." -msgstr "" - -#: ../points/points.rst:52 -msgid "Once you have decided and entered those options, go to the **Events** tab. Here, you can trigger one or more events once a Contact has reached your predetermined Point total. These Point triggers and associated events are also fully customizable." -msgstr "" - -#: ../points/points.rst:None -msgid "Screenshot of Points trigger events" -msgstr "" - -#: ../points/points.rst:58 -msgid "Campaign triggers" -msgstr "" - -#: ../points/points.rst:60 -msgid "**Modify Contact's Campaigns** - Add a Contact to or remove a Contact from any Campaigns you have published." -msgstr "" - -#: ../points/points.rst:63 -msgid "Contact triggers" -msgstr "" - -#: ../points/points.rst:65 -msgid "**Modify Contact's Segments** - Add a Contact to or remove a Contact from any Segments you have published." -msgstr "" - -#: ../points/points.rst:67 -msgid "**Modify Contact's tags** - Add or remove any Tags on the Contact record. If a Tag doesn't exist, you may create a new one in the edit window for this event." -msgstr "" - -#: ../points/points.rst:70 -msgid "Add-on triggers" -msgstr "" - -#: ../points/points.rst:72 -msgid "**Push Contact to Integration** - To only push Contacts to an Integration after hitting a minimum Point total, use this option. You must have the **Triggered action push Contacts to Integration** option selected in the Integration. After selecting this event, the system displays a dialog box where you can choose which Integration to push the Contact to. For example, if you base your definition of a Marketing Qualified Lead (MQL) on Point values, you may decide to only push Contacts who are MQLs to your CRM. Once a Contact meets the Points requirement to be an MQL, use this action to push the Contact to your CRM." -msgstr "" - -#: ../points/points.rst:76 -msgid "The Push Contact to Integration action isn't supported with the Salesforce Plugin." -msgstr "" - -#: ../points/points.rst:79 -msgid "Email triggers" -msgstr "" - -#: ../points/points.rst:81 -msgid "**Send an Email** - Send a template Email to the Contact based on their engagement. This may be some sort of special offer, congratulations, etc." -msgstr "" - -#: ../points/points.rst:None -msgid "Screenshot of Send an Email to User Email trigger" -msgstr "" - -#: ../points/points.rst:92 -msgid "**Send an Email to User** - Tell a team member that a Contact has reached a minimum number of Points. There is an option in this event to send the Email to the Contact's owner. You may either write a basic Email in the editor, or use a template Email." -msgstr "" - -#: ../points/points.rst:87 -msgid "Selecting a User and selecting the option of **send Email to Contact's owner** notifies both Contacts." -msgstr "" - -#: ../points/points.rst:89 -msgid "If User has no owner or if the owner is same as the Mautic User, this sends only one Email." -msgstr "" - -#: ../points/points.rst:91 -msgid "You can add more Emails to 'to', 'cc' and 'bcc' fields - separated by a comma. You can add space after each comma if needed." -msgstr "" - -#: ../points/points.rst:93 -msgid "Sends Notification to all address - User's Email, owner's Email, to, cc and bcc." -msgstr "" - -#: ../points/points_troubleshooting.rst:2 -msgid "Points troubleshooting" -msgstr "" - -#: ../points/points_troubleshooting.rst:5 -msgid "Page visits not recognized" -msgstr "" - -#: ../points/points_troubleshooting.rst:7 -msgid "To workaround this issue, try one of the following options:" -msgstr "" - -#: ../points/points_troubleshooting.rst:9 -msgid "Make sure that you aren't testing while logged into Mautic. Mautic ignores activity from Mautic Administrators. So, it's suggested that you use an anonymous session, an incognito window, another browser, or log out of Mautic." -msgstr "" - -#: ../points/points_troubleshooting.rst:11 -msgid "The tracking of Point actions is currently done once per Contact. This means that subsequent visits won't re-trigger the action if already triggered once." -msgstr "" - -#: ../points/points_troubleshooting.rst:13 -msgid "Ensure that the URL defined either matches exactly the URL visited or use a wildcard. A URL can include the schema, host/domain, path, query parameters, and/or fragment." -msgstr "" - -#: ../points/points_troubleshooting.rst:15 -msgid "For example, if you have a URL of ``https://example.com`` and the page hit registers as ``https://example.com/index.php?foo=bar``, the point action won't be recognized. However, if you use ``https://example.com*`` as the URL, it matches the rule and thus gets triggered." -msgstr "" diff --git a/docs/docs_translations/queue.pot b/docs/docs_translations/queue.pot deleted file mode 100644 index 9bc7e5e9..00000000 --- a/docs/docs_translations/queue.pot +++ /dev/null @@ -1,305 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../queue/message_queue.rst:4 -msgid "Message queue" -msgstr "" - -#: ../queue/message_queue.rst:8 -msgid "You can trigger a Campaign **marketing** Email, or send it as part of an Email broadcast - a Segment Email. When exceeding a frequency rule - whether defined at the Contact level or as a default set in Configuration, all Emails go to the Queue for processing later." -msgstr "" - -#: ../queue/message_queue.rst:11 -msgid "Priority and number of attempts" -msgstr "" - -#: ../queue/message_queue.rst:None -msgid "Screenshot showing marketing-Email" -msgstr "" - -#: ../queue/message_queue.rst:18 -msgid "You can select priority as **High** or **Normal**. When processing messages for a given date, Mautic places high priority messages at the top of the queue. Broadcasts are always treated as a normal priority." -msgstr "" - -#: ../queue/message_queue.rst:20 -msgid "On reaching the number of attempts specified, Mautic makes an attempt to send the Email again in the event of rescheduling. Even if the message is pending, exceeding the number of attempts means that Mautic won't send the message." -msgstr "" - -#: ../queue/message_queue.rst:23 -msgid "Processing a message queue" -msgstr "" - -#: ../queue/message_queue.rst:25 -msgid "This command processes all pending messages that haven't reached their maximum number of attempts and are in the pending queue." -msgstr "" - -#: ../queue/message_queue.rst:27 -msgid "Setup your :ref:`cron` as followed: ``php bin/console mautic:messages:send``" -msgstr "" - -#: ../queue/queue.rst:4 -msgid "Queue" -msgstr "" - -#: ../queue/queue.rst:8 -msgid "You can improved scalability by activating the queuing mechanism for Email and Page opens. Use this if you are getting too much traffic at once from people opening Pages or opening Emails." -msgstr "" - -#: ../queue/queue.rst:12 -msgid "Mautic 3.x Users who are implementing RabbitMQ or Beanstalkd need to configure the settings directly in their local configuration file. If you are using the legacy Mautic 2.x series the steps below remains the same." -msgstr "" - -#: ../queue/queue.rst:15 -msgid "Activating" -msgstr "" - -#: ../queue/queue.rst:17 -msgid "You can activate and configure the queuing mechanism by going to configuration:" -msgstr "" - -#: ../queue/queue.rst:19 -msgid "Open the administrator menu by clicking the cog icon in the top right corner." -msgstr "" - -#: ../queue/queue.rst:20 -msgid "Select the *Configuration* menu item." -msgstr "" - -#: ../queue/queue.rst:21 -msgid "Select the *Queue Settings* tab." -msgstr "" - -#: ../queue/queue.rst:22 -msgid "Switch the *Queue Protocol* to either *RabbitMQ* or *Beanstalkd*." -msgstr "" - -#: ../queue/queue.rst:23 -msgid "Save the configuration." -msgstr "" - -#: ../queue/queue.rst:28 -#: ../queue/queue.rst:36 -#: ../queue/queue.rst:86 -msgid "RabbitMQ" -msgstr "" - -#: ../queue/queue.rst:32 -msgid ":xref:`RabbitMQ` is one of the available queue protocols that Mautic supports. To use it, you must have a RabbitMQ server running. On :xref:`RabbitMQ`, you can obtain instructions on how to install RabbitMQ. For testing purposes, you can use :xref:`cloudamqp` which offers a RabbitMQ as a service." -msgstr "" - -#: ../queue/queue.rst:34 -msgid "Having set up a RabbitMQ server, you can configure Mautic to use it by setting the appropriate parameters ``mautic.rabbitmq_*`` in your installation's configuration file." -msgstr "" - -#: ../queue/queue.rst:40 -#: ../queue/queue.rst:90 -msgid "Parameter" -msgstr "" - -#: ../queue/queue.rst:41 -#: ../queue/queue.rst:91 -msgid "Default" -msgstr "" - -#: ../queue/queue.rst:42 -#: ../queue/queue.rst:92 -msgid "Description" -msgstr "" - -#: ../queue/queue.rst:43 -msgid "``rabbitmq_host``" -msgstr "" - -#: ../queue/queue.rst:44 -#: ../queue/queue.rst:94 -msgid "``'localhost'``" -msgstr "" - -#: ../queue/queue.rst:45 -msgid "The ``hostname`` of the RabbitMQ server" -msgstr "" - -#: ../queue/queue.rst:46 -msgid "``rabbitmq_port``" -msgstr "" - -#: ../queue/queue.rst:47 -msgid "``'5672'``" -msgstr "" - -#: ../queue/queue.rst:48 -msgid "The port that the RabbitMQ server is listening on" -msgstr "" - -#: ../queue/queue.rst:49 -msgid "``rabbitmq_vhost``" -msgstr "" - -#: ../queue/queue.rst:50 -msgid "``'/'``" -msgstr "" - -#: ../queue/queue.rst:51 -msgid "The virtual host to use for this RabbitMQ server" -msgstr "" - -#: ../queue/queue.rst:52 -msgid "``rabbitmq_user``" -msgstr "" - -#: ../queue/queue.rst:53 -#: ../queue/queue.rst:56 -msgid "``'guest'``" -msgstr "" - -#: ../queue/queue.rst:54 -msgid "The username for the RabbitMQ server" -msgstr "" - -#: ../queue/queue.rst:55 -msgid "``rabbitmq_password``" -msgstr "" - -#: ../queue/queue.rst:57 -msgid "The password for the RabbitMQ server" -msgstr "" - -#: ../queue/queue.rst:58 -msgid "``rabbitmq_idle_timeout``" -msgstr "" - -#: ../queue/queue.rst:59 -#: ../queue/queue.rst:62 -msgid "``0``" -msgstr "" - -#: ../queue/queue.rst:60 -msgid "The number of seconds after which the queue consumer should timeout when idle" -msgstr "" - -#: ../queue/queue.rst:61 -msgid "``rabbitmq_idle_timeout_exit_code``" -msgstr "" - -#: ../queue/queue.rst:63 -msgid "The exit code returned when the consumer exits due to idle timeout" -msgstr "" - -#: ../queue/queue.rst:65 -msgid "Example:" -msgstr "" - -#: ../queue/queue.rst:80 -msgid "Beanstalkd" -msgstr "" - -#: ../queue/queue.rst:82 -msgid ":xref:`Beanstalkd` is another available queue protocol that Mautic supports. To use it, you must have a Beanstalkd server running. On :xref:`Beanstalkd website`, you can obtain instructions on how to install Beanstalkd." -msgstr "" - -#: ../queue/queue.rst:84 -msgid "Once you have setup a Beanstalkd server, you can configure Mautic to use it by setting the appropriate parameters ``mautic.beanstalkd_*`` in your installation's configuration file." -msgstr "" - -#: ../queue/queue.rst:93 -msgid "``beanstalkd_host``" -msgstr "" - -#: ../queue/queue.rst:95 -msgid "The ``hostname`` of the Beanstalkd server" -msgstr "" - -#: ../queue/queue.rst:96 -msgid "``beanstalkd_port``" -msgstr "" - -#: ../queue/queue.rst:97 -msgid "``'11300'``" -msgstr "" - -#: ../queue/queue.rst:98 -msgid "The port that the Beanstalkd server is listening on" -msgstr "" - -#: ../queue/queue.rst:99 -msgid "``beanstalkd_timeout``" -msgstr "" - -#: ../queue/queue.rst:100 -msgid "``'60'``" -msgstr "" - -#: ../queue/queue.rst:101 -msgid "The default Time To Run - TTR - for Beanstalkd jobs" -msgstr "" - -#: ../queue/queue.rst:104 -msgid "Processing" -msgstr "" - -#: ../queue/queue.rst:106 -msgid "Activating the queuing mechanism queues up all Page hits and Email opens for later processing. You need to run some console commands on a regular basis to be able to process them." -msgstr "" - -#: ../queue/queue.rst:108 -msgid "To process the hits from a Page, use the following command:" -msgstr "" - -#: ../queue/queue.rst:110 -msgid "``php /path/to/mautic/bin/console mautic:queue:process --env=prod -i page_hit``" -msgstr "" - -#: ../queue/queue.rst:112 -msgid "To process the hits from an Email, use the following command:" -msgstr "" - -#: ../queue/queue.rst:114 -msgid "``php /path/to/mautic/bin/console mautic:queue:process --env=prod -i email_hit``" -msgstr "" - -#: ../queue/queue.rst:116 -msgid "When these commands run, they continue to run until you stop the program by using the keyboard combination ``Control + C``. If you want to run them to process only, say, 50 Page hits or Email hits, you can run the command like this instead:" -msgstr "" - -#: ../queue/queue.rst:118 -msgid "``php /path/to/mautic/bin/console mautic:queue:process --env=prod -i page_hit -m 50``" -msgstr "" - -#: ../queue/queue.rst:120 -msgid "or" -msgstr "" - -#: ../queue/queue.rst:122 -msgid "``php /path/to/mautic/bin/console mautic:queue:process --env=prod -i email_hit -m 50``" -msgstr "" - -#: ../queue/queue.rst:125 -msgid "Cron to push the jobs" -msgstr "" - -#: ../queue/queue.rst:127 -msgid "You need to run the following cron to keep pushing the jobs:" -msgstr "" - -#: ../queue/queue.rst:129 -msgid "``php /path/to/mautic/bin/console mautic:email:send``" -msgstr "" - -#: ../queue/queue.rst:131 -msgid "See the documentation on :ref:`cron jobs` for further information." -msgstr "" diff --git a/docs/docs_translations/reports.pot b/docs/docs_translations/reports.pot deleted file mode 100644 index ad99fd2e..00000000 --- a/docs/docs_translations/reports.pot +++ /dev/null @@ -1,430 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../reports/reports.rst:2 -msgid "Reports" -msgstr "" - -#: ../reports/reports.rst:4 -msgid "Mautic's Reports menu allows you to generate highly customizable Reports." -msgstr "" - -#: ../reports/reports.rst:6 -msgid "You can use the reporting tools to track marketing metrics, identify marketing activities that are effective or need improvement, and troubleshoot or investigate if you are curious about why something is happening." -msgstr "" - -#: ../reports/reports.rst:8 -msgid "To get to Reports, click the Reports link from the menu on the left side of your instance. To create a new Report, click the **+New** button in the top right corner." -msgstr "" - -#: ../reports/reports.rst:None -msgid "Screenshots of Mautic Report" -msgstr "" - -#: ../reports/reports.rst:17 -msgid "Data sources" -msgstr "" - -#: ../reports/reports.rst:19 -msgid "The **Details** tab on a Report contains the same options across all Reports and provides some general options for your Report." -msgstr "" - -#: ../reports/reports.rst:None -msgid "Screenshots of Mautic Report Details" -msgstr "" - -#: ../reports/reports.rst:25 -msgid "**Name** - Specify a Report name that makes it easy for you and other Users to identify the purpose of the Report." -msgstr "" - -#: ../reports/reports.rst:27 -msgid "**Data source** - Select the data source appropriate to the Report that you are building. Note that each data source has a different set of available columns, filters, and graphs. The available data sources are:" -msgstr "" - -#: ../reports/reports.rst:29 -msgid ":doc:`Assets`" -msgstr "" - -#: ../reports/reports.rst:31 -msgid "Assets" -msgstr "" - -#: ../reports/reports.rst:32 -msgid "Asset Downloads" -msgstr "" - -#: ../reports/reports.rst:34 -msgid ":doc:`Campaigns`" -msgstr "" - -#: ../reports/reports.rst:36 -msgid "Campaign Events" -msgstr "" - -#: ../reports/reports.rst:38 -msgid ":doc:`Channels Messages`" -msgstr "" - -#: ../reports/reports.rst:40 -msgid "Message Queue" -msgstr "" - -#: ../reports/reports.rst:42 -msgid ":doc:`Emails`" -msgstr "" - -#: ../reports/reports.rst:44 -msgid "Emails" -msgstr "" - -#: ../reports/reports.rst:45 -msgid "Emails Sent" -msgstr "" - -#: ../reports/reports.rst:47 -msgid ":doc:`Forms`" -msgstr "" - -#: ../reports/reports.rst:49 -msgid "Forms" -msgstr "" - -#: ../reports/reports.rst:50 -msgid "Form Submissions" -msgstr "" - -#: ../reports/reports.rst:52 -msgid ":doc:`Contacts`" -msgstr "" - -#: ../reports/reports.rst:54 -msgid "Contacts" -msgstr "" - -#: ../reports/reports.rst:55 -msgid "Multi Touch Attributions" -msgstr "" - -#: ../reports/reports.rst:56 -msgid "First Touch Attributions" -msgstr "" - -#: ../reports/reports.rst:57 -msgid "Last Touch Attributions" -msgstr "" - -#: ../reports/reports.rst:58 -msgid "Contact Point Log" -msgstr "" - -#: ../reports/reports.rst:59 -msgid "Frequency Rules" -msgstr "" - -#: ../reports/reports.rst:60 -msgid "Segment Membership" -msgstr "" - -#: ../reports/reports.rst:61 -msgid "Do Not Contact" -msgstr "" - -#: ../reports/reports.rst:62 -msgid "UTM Codes" -msgstr "" - -#: ../reports/reports.rst:64 -msgid ":doc:`Companies`" -msgstr "" - -#: ../reports/reports.rst:66 -msgid "Companies" -msgstr "" - -#: ../reports/reports.rst:68 -msgid ":doc:`Mobile Notifications`" -msgstr "" - -#: ../reports/reports.rst:70 -msgid "Mobile Notifications" -msgstr "" - -#: ../reports/reports.rst:71 -msgid "Mobile Notifications Sent" -msgstr "" - -#: ../reports/reports.rst:73 -msgid ":doc:`Pages`" -msgstr "" - -#: ../reports/reports.rst:75 -msgid "Landing Pages" -msgstr "" - -#: ../reports/reports.rst:76 -msgid "Page hits" -msgstr "" - -#: ../reports/reports.rst:78 -msgid "Videos" -msgstr "" - -#: ../reports/reports.rst:80 -msgid "Video hits" -msgstr "" - -#: ../reports/reports.rst:82 -msgid "As demonstrated, Mautic displays the data sources in the format: `` ``" -msgstr "" - -#: ../reports/reports.rst:84 -msgid "The parent data source provides a high-level summary of the data while the child data source provides a more granular view of Contact behavior that includes your Custom Fields and values." -msgstr "" - -#: ../reports/reports.rst:86 -msgid "**Description - optional** - Add detailed information about the Report, helping you and other Users better understand what the Report is for. You may want to include more information about filters, people, or departments." -msgstr "" - -#: ../reports/reports.rst:88 -msgid "**Published** - Select **Yes** to ensure that the Report is active, ready to send when scheduled in the Report options." -msgstr "" - -#: ../reports/reports.rst:90 -msgid "**System Report** - Select **Yes** so that all Users can access the Report. If set to No, only the owner of the Report and Users with permission to view others' Reports can see the Report." -msgstr "" - -#: ../reports/reports.rst:92 -msgid "**Owner** - Select the owner of the Report to determine who can see the Report if the System Report setting is No." -msgstr "" - -#: ../reports/reports.rst:94 -msgid "**Dynamic filters settings**" -msgstr "" - -#: ../reports/reports.rst:96 -msgid "Show opened by default - If you want to ensure that the date filters and filter options for any other Report filters are visible on a Report detail page without needing to open the filters drop-down, select Yes. For example, for an Emails Report, you might want to view dynamic filters for subject or sent date." -msgstr "" - -#: ../reports/reports.rst:97 -msgid "Hide date range - To hide the date range filter so that Users can’t change the dates that the Report displays data for, select to **Yes**." -msgstr "" - -#: ../reports/reports.rst:101 -msgid "Data" -msgstr "" - -#: ../reports/reports.rst:103 -msgid "You can customize each Report to include the columns of choice, filter data based on set criteria, and/or set a specific order for the data. In addition you can also group by specific fields, and select different function operators to calculate fields. Note that when you select functions operators, Mautic adds a totals row to the Report. Choosing to export a Report **won't** include this totals row." -msgstr "" - -#: ../reports/reports.rst:None -#: ../reports/reports.rst:None -msgid "Screenshots of Mautic Report Data" -msgstr "" - -#: ../reports/reports.rst:110 -msgid "**Columns** - Select the columns of data that you want to appear in the table of data in the Report. Click the column name in the left column to have it show in the Report. You can remove a column from the Report by clicking on its right column. The column returns to its original position on the left side. For example, if you select ID, it refers to the **ID** for the parent data source Category that you selected earlier Contact ID, Email ID, Asset ID, etc. It's recommended that you include **ID** in all Reports." -msgstr "" - -#: ../reports/reports.rst:111 -msgid "**Order** - For sorting the data in the Report, select data Points. The available sort options are **Ascending** and **Descending**. To add multiple columns, click **Add Order**. For fields that use text, an **Ascending** order lists values starting with B after values starting with A and so on. For number or date fields, the higher the number or later the date, the lower on the list the row is. Descending order is the opposite." -msgstr "" - -#: ../reports/reports.rst:115 -msgid "Adding multiple fields to order by uses the last one in the Order list first. Ordering by **First Name Ascending** and adding **Email Ascending**, for instance, sorts the Email column first and duplicate rows are then sorted by first name ascending." -msgstr "" - -#: ../reports/reports.rst:117 -msgid "**Filters** - Filter the data using conditions and values. This allows the generation of very granular Reports. This option helps you to narrow down the data included in the Report. The data Points used for filters don’t have to be columns that appear in the Report table. A commonly used filter for any Reports that include Contact record data is Email Not Empty, which displays only identified Contacts in the Report. Additional use cases can include Contacts or items that match a certain value, events happening within a certain date range, etc." -msgstr "" - -#: ../reports/reports.rst:121 -msgid "Setting the **Dynamic** option to **Yes** makes it easier for Users viewing the Report to change the data they see without actually editing the Report. Users can see the filter by opening the **Filters** drop-down from the top of the Report page." -msgstr "" - -#: ../reports/reports.rst:123 -msgid "**Group by** - Select the columns for which you want to group data. By default, Reports show all items individually. In many Reports, you may see the same Contact, Company, or item appear multiple times. To only see each record listed once, you can add a grouping based on some attribute for the record." -msgstr "" - -#: ../reports/reports.rst:125 -msgid "You can use Email or Contact ID to display a single row per Contact record. For example, you can group by **Contact ID** to view the unique number of Asset Downloads or Form Submissions for a single Form, instead of total Asset Downloads or Form Submissions, which could include duplicates." -msgstr "" - -#: ../reports/reports.rst:127 -msgid "**Calculated columns** - Select the function that you want to apply to individual columns. Calculated columns display count, average, sum, or the minimum or maximum values from a selected field. They're only available when using a grouping to show a calculation for that grouping. Continuing with the previous example of grouping by a Contact ID number or Email address, a COUNT calculation displays how many times that Contact record appears on the Report if not for the grouping." -msgstr "" - -#: ../reports/reports.rst:130 -msgid "Graphs" -msgstr "" - -#: ../reports/reports.rst:136 -msgid "Some Report types display graphs for visualization purposes. You can include such graphs in Reports and use them in Dashboard widgets." -msgstr "" - -#: ../reports/reports.rst:138 -msgid "To select an available graph and add it to the Report, click the name of the graph to move it from the left column to the right." -msgstr "" - -#: ../reports/reports.rst:139 -msgid "To remove a graph from a Report, click the name in the right column to move it to the left." -msgstr "" - -#: ../reports/reports.rst:141 -msgid "The availability and types of graphs vary by Report type." -msgstr "" - -#: ../reports/reports.rst:144 -msgid "Schedule" -msgstr "" - -#: ../reports/reports.rst:146 -msgid "Mautic allows scheduling Emails to send downloadable links containing the Report data in the ``.csv`` file format." -msgstr "" - -#: ../reports/reports.rst:148 -msgid "Use the toggle switch to turn on or off sending Reports via email." -msgstr "" - -#: ../reports/reports.rst:150 -msgid "Email Report - Select **Yes** to see additional options." -msgstr "" - -#: ../reports/reports.rst:152 -msgid "To - Specify the email addresses that should receive the Report. To send to multiple recipients, separate their email addresses with a comma. For example, ``example1@example.com``, ``example2@example.com``." -msgstr "" - -#: ../reports/reports.rst:154 -msgid "**Every** - Select the frequency with which you'd like to automatically send the Report:" -msgstr "" - -#: ../reports/reports.rst:156 -msgid "**now** - Sends the Report once, when it's saved." -msgstr "" - -#: ../reports/reports.rst:157 -msgid "**day** - Sends the Report every day at midnight in your time zone." -msgstr "" - -#: ../reports/reports.rst:158 -msgid "**week** - After selecting week, select the day of the week you'd like to send the Report. Mautic sends the Report at midnight in your time zone every week on the selected day." -msgstr "" - -#: ../reports/reports.rst:159 -msgid "**month** - After selecting month, select either the first or last and a day of the week. For example, set your Report to be automatically sent on the first Monday or last Friday of each month." -msgstr "" - -#: ../reports/reports.rst:161 -msgid "Alternatively, you can select Weekdays to send the Report on the first or last weekday of each month." -msgstr "" - -#: ../reports/reports.rst:163 -msgid "Once you've set all of the options you'd like in the **Details**, **Data**, **Graphs**, and **Schedule** tabs, click **Save & Close** to save the Report. Clicking **Apply** saves the progress you've made on building the Report and keeps you in the edit mode." -msgstr "" - -#: ../reports/reports.rst:168 -msgid "Cron job to schedule Reports" -msgstr "" - -#: ../reports/reports.rst:172 -msgid "Mautic requires the following cron command to be able to send scheduled Reports:" -msgstr "" - -#: ../reports/reports.rst:174 -msgid "``php /path/to/mautic/bin/console mautic:reports:scheduler [--report=ID]``" -msgstr "" - -#: ../reports/reports.rst:176 -msgid "The ``--report=ID`` argument allows you to specify a Report by ID if required. For more information, see :ref:`Cron jobs`." -msgstr "" - -#: ../reports/reports.rst:179 -msgid "Report options" -msgstr "" - -#: ../reports/reports.rst:181 -msgid "Once you've saved the Report, it's listed under the Reports section in Mautic." -msgstr "" - -#: ../reports/reports.rst:None -msgid "Screenshots of Mautic Report Options" -msgstr "" - -#: ../reports/reports.rst:187 -msgid "To view additional options for Report, click the drop-down menu next to the checkbox." -msgstr "" - -#: ../reports/reports.rst:189 -msgid "**Edit** takes you directly to the edit mode, rather than clicking on the view page and editing from there." -msgstr "" - -#: ../reports/reports.rst:191 -msgid "**Clone** copies the Report so that you can make small adjustments in a similar but new Report, while maintaining the original Report." -msgstr "" - -#: ../reports/reports.rst:193 -msgid "**Export & Send** sends a link containing the ``.csv`` file with the Report data to the email address on your User profile." -msgstr "" - -#: ../reports/reports.rst:195 -msgid "**Delete** deletes the Report immediately." -msgstr "" - -#: ../reports/reports.rst:200 -msgid "Exporting Reports" -msgstr "" - -#: ../reports/reports.rst:None -msgid "Screenshots of Mautic Exporting Report" -msgstr "" - -#: ../reports/reports.rst:208 -msgid "In addition to the **Schedule** and **Export & Send** features, Mautic supports exporting Reports in ``.csv,`` Excel, or HTML format. From the Reports list, click any Report. Open the drop-down menu in the top right corner and select the preferred export format." -msgstr "" - -#: ../reports/reports.rst:210 -msgid "To download the Report immediately:" -msgstr "" - -#: ../reports/reports.rst:212 -msgid "On the Schedule tab, do one of the following:" -msgstr "" - -#: ../reports/reports.rst:214 -msgid "Select **No**." -msgstr "" - -#: ../reports/reports.rst:215 -msgid "In the **Every** field, set the value to now." -msgstr "" - -#: ../reports/reports.rst:217 -msgid "Click **Save & Close**." -msgstr "" - -#: ../reports/reports.rst:219 -msgid "On the Report details page, click the dropdown on the top right and click **Export to CSV**." -msgstr "" - -#: ../reports/reports.rst:221 -msgid "Reset the schedule as needed." -msgstr "" - -#: ../reports/reports.rst:223 -msgid "Reporting data is also available to export by API. For more information, see the :xref:`Reports API documentation`." -msgstr "" diff --git a/docs/docs_translations/search.pot b/docs/docs_translations/search.pot deleted file mode 100644 index 89b1e104..00000000 --- a/docs/docs_translations/search.pot +++ /dev/null @@ -1,145 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../search/search_operators.rst:4 -msgid "Searching Mautic" -msgstr "" - -#: ../search/search_operators.rst:9 -msgid "Search operators and filters" -msgstr "" - -#: ../search/search_operators.rst:11 -msgid "Mautic offers a variety of search operators and filters for drilling down into relevant resources. You can find the available search filters and operators by clicking on the button with a question mark next to the search input." -msgstr "" - -#: ../search/search_operators.rst:13 -msgid "The search filters for that entity aren't available if such a button is missing." -msgstr "" - -#: ../search/search_operators.rst:None -msgid "Mautic Contact search" -msgstr "" - -#: ../search/search_operators.rst:21 -msgid "Mautic also has a 'global search' feature. In the top left-hand corner, click the magnifying glass icon next to the Mautic logo/notifications icon. This opens a search input where you can search across multiple different entities." -msgstr "" - -#: ../search/search_operators.rst:None -msgid "Mautic global search" -msgstr "" - -#: ../search/search_operators.rst:30 -msgid "Search operators" -msgstr "" - -#: ../search/search_operators.rst:32 -msgid "Here are some search operators you can use:" -msgstr "" - -#: ../search/search_operators.rst:34 -msgid "``+`` plus sign - Search for the exact string, for example, if you search for ``+admin``, then ``administrator`` won't match." -msgstr "" - -#: ../search/search_operators.rst:36 -msgid "``!`` exclamation mark - Not equals string" -msgstr "" - -#: ../search/search_operators.rst:38 -msgid "``\" \"`` double quotes - Search by phrase" -msgstr "" - -#: ../search/search_operators.rst:40 -msgid "``( )`` parentheses - Group expressions together." -msgstr "" - -#: ../search/search_operators.rst:42 -msgid "``OR`` - By default the expressions joins as ``AND`` statements. Use the OR operator to change that." -msgstr "" - -#: ../search/search_operators.rst:44 -msgid "``%`` - Use the % as a wildcard to search for specific names or values in a phrase for example, to find all Companies with the word ‘Technologies’ then type %technologies%" -msgstr "" - -#: ../search/search_operators.rst:47 -msgid "Search filters" -msgstr "" - -#: ../search/search_operators.rst:49 -msgid "Here are some search filters you can use:" -msgstr "" - -#: ../search/search_operators.rst:52 -msgid "Contacts search filters" -msgstr "" - -#: ../search/search_operators.rst:75 -msgid "Companies search filters" -msgstr "" - -#: ../search/search_operators.rst:87 -msgid "Segments search filters" -msgstr "" - -#: ../search/search_operators.rst:97 -msgid "Assets search filters" -msgstr "" - -#: ../search/search_operators.rst:110 -msgid "Forms search filters" -msgstr "" - -#: ../search/search_operators.rst:126 -msgid "Landing Pages search filters" -msgstr "" - -#: ../search/search_operators.rst:144 -msgid "Dynamic Content search filters" -msgstr "" - -#: ../search/search_operators.rst:160 -msgid "Emails search filters" -msgstr "" - -#: ../search/search_operators.rst:173 -msgid "Focus items search filters" -msgstr "" - -#: ../search/search_operators.rst:185 -msgid "Manage actions search filters" -msgstr "" - -#: ../search/search_operators.rst:197 -msgid "Manage triggers search filters" -msgstr "" - -#: ../search/search_operators.rst:209 -msgid "Stages search filters" -msgstr "" - -#: ../search/search_operators.rst:221 -msgid "Reports search filters" -msgstr "" - -#: ../search/search_operators.rst:233 -msgid "Users search filters" -msgstr "" - -#: ../search/search_operators.rst:252 -msgid "Webhooks search filters" -msgstr "" diff --git a/docs/docs_translations/segments.pot b/docs/docs_translations/segments.pot deleted file mode 100644 index 3464bd69..00000000 --- a/docs/docs_translations/segments.pot +++ /dev/null @@ -1,781 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../segments/manage_segments.rst:4 -msgid "Managing Segments" -msgstr "" - -#: ../segments/manage_segments.rst:8 -msgid "Segments in Mautic are lists or groups of Contacts. Use Segments to send Emails, trigger Campaigns, or for analysis. You can add and remove Contacts into *static* and *dynamic* Segment types." -msgstr "" - -#: ../segments/manage_segments.rst:10 -msgid "Segments provide ways to easily organize your Contacts. There are a variety of fields available for configuring these Segments." -msgstr "" - -#: ../segments/manage_segments.rst:12 -msgid "When viewing all Segments, the **# contacts** column on the right shows the number of Contacts included in that particular Segment." -msgstr "" - -#: ../segments/manage_segments.rst:None -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing Contacts matching that particular Segment." -msgstr "" - -#: ../segments/manage_segments.rst:19 -msgid "Mautic renamed lead lists to Segments in Mautic :xref:`1.4.0 release`." -msgstr "" - -#: ../segments/manage_segments.rst:24 -msgid "Creating a Segment" -msgstr "" - -#: ../segments/manage_segments.rst:28 -msgid "To create a new Segment, navigate to Segments in the menu, and click the **+New** button." -msgstr "" - -#: ../segments/manage_segments.rst:30 -#: ../segments/manage_segments.rst:269 -msgid "In the **Details** tab, add a **Name**, **Public name** and **Description** to your Segment." -msgstr "" - -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing creating a Segment." -msgstr "" - -#: ../segments/manage_segments.rst:36 -msgid "**Public Segment** - This option determines if the Segment is available for all Users to see and use, or only the User who created the Segment." -msgstr "" - -#: ../segments/manage_segments.rst:38 -msgid "**Available in Preference Center** - If set to **Yes**, Contacts can see and opt into or out of the Segment on a **Preference Center** page. The Segments display if the Preference Center has the **Segment List** slot type." -msgstr "" - -#: ../segments/manage_segments.rst:40 -msgid "**Published** - If set to **No**, the Segment won't be available for use in filters for other Segments, as a Contact source in Campaigns, modify Segment actions, etc. You'll still see the Segment in your **Segment list**, but it essentially won't exist anywhere else in Mautic." -msgstr "" - -#: ../segments/manage_segments.rst:42 -msgid "On the Details tab, static, and dynamic Segments also have the option to display a different public name for a Segment." -msgstr "" - -#: ../segments/manage_segments.rst:44 -msgid "**Public name** - Users can set a different name for the Segment, which is visible to Contacts in Preference Center options." -msgstr "" - -#: ../segments/manage_segments.rst:46 -msgid "Since :xref:`Mautic 3.2` it has been possible to provide a public name, in addition to an internal name, for a Segment." -msgstr "" - -#: ../segments/manage_segments.rst:51 -msgid "Viewing and exporting Contacts in a Segment" -msgstr "" - -#: ../segments/manage_segments.rst:55 -msgid "When viewing all Segments the **# contacts** column on the right shows the number of Contacts included in that particular Segment." -msgstr "" - -#: ../segments/manage_segments.rst:61 -msgid "To view Contacts in a specific Segment, click **View X Contacts** from your Segment list or in the Contacts section of Mautic, enter ``segment:segment-alias`` in the search bar." -msgstr "" - -#: ../segments/manage_segments.rst:66 -msgid "Static Segments" -msgstr "" - -#: ../segments/manage_segments.rst:70 -msgid "Static Segments aren't filter-based. Adding Contacts to a Segment in done in one of the following ways:" -msgstr "" - -#: ../segments/manage_segments.rst:75 -msgid "Manually moving Contacts" -msgstr "" - -#: ../segments/manage_segments.rst:79 -msgid "The two manual options to move a Contact into a static Segment are:" -msgstr "" - -#: ../segments/manage_segments.rst:84 -msgid "Batch updating Contacts" -msgstr "" - -#: ../segments/manage_segments.rst:87 -msgid "Use search filters in the Contacts section of Mautic to find the Contacts to change." -msgstr "" - -#: ../segments/manage_segments.rst:89 -#: ../segments/manage_segments.rst:467 -msgid "Select the checkboxes next to those Contacts." -msgstr "" - -#: ../segments/manage_segments.rst:91 -#: ../segments/manage_segments.rst:469 -msgid "Click the green arrow which appears at the top of the column." -msgstr "" - -#: ../segments/manage_segments.rst:93 -msgid "Select **Change Segments** from the list." -msgstr "" - -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing batch change Segment." -msgstr "" - -#: ../segments/manage_segments.rst:100 -msgid "Choose the **Segments** to add or remove Contacts from." -msgstr "" - -#: ../segments/manage_segments.rst:102 -#: ../segments/manage_segments.rst:130 -msgid "Click **Save**." -msgstr "" - -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing Change Segment." -msgstr "" - -#: ../segments/manage_segments.rst:111 -msgid "Adding individual Contacts" -msgstr "" - -#: ../segments/manage_segments.rst:115 -msgid "Navigate to the Contact record you want to change." -msgstr "" - -#: ../segments/manage_segments.rst:117 -msgid "Click the arrow in the top right, next to **Edit/Send Email/Close**." -msgstr "" - -#: ../segments/manage_segments.rst:119 -msgid "Select **Preference**." -msgstr "" - -#: ../segments/manage_segments.rst:None -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing individual change Segment." -msgstr "" - -#: ../segments/manage_segments.rst:126 -msgid "Click **Segments**." -msgstr "" - -#: ../segments/manage_segments.rst:128 -msgid "Choose the Segments you'd like to add the Contacts to or remove Contacts from." -msgstr "" - -#: ../segments/manage_segments.rst:139 -msgid "Campaign action" -msgstr "" - -#: ../segments/manage_segments.rst:143 -msgid "Inside a :ref:`Campaign`, you can add or remove Contacts from Segments using the **Modify Contact's Segment** action. To add Contacts to a Segment, you must have already created the Segment and set it to **Public Segment = Yes**." -msgstr "" - -#: ../segments/manage_segments.rst:145 -msgid "In the Campaign builder, click the bottom connector." -msgstr "" - -#: ../segments/manage_segments.rst:0 -msgid "Screenshot Campaign builder connector." -msgstr "" - -#: ../segments/manage_segments.rst:150 -msgid "Select **Action**." -msgstr "" - -#: ../segments/manage_segments.rst:152 -msgid "In the list of actions, select **Modify Contact's Segments**." -msgstr "" - -#: ../segments/manage_segments.rst:154 -msgid "Choose from the list of existing Segments you want to add or remove your Contact from." -msgstr "" - -#: ../segments/manage_segments.rst:0 -msgid "Screenshot showing list of existing Segments." -msgstr "" - -#: ../segments/manage_segments.rst:159 -msgid "Click Save and close." -msgstr "" - -#: ../segments/manage_segments.rst:164 -msgid "Form submit action" -msgstr "" - -#: ../segments/manage_segments.rst:168 -msgid "**Modify Contact's Segment** is available as a submit action on :ref:`Standalone Forms`. With a Campaign Form, create a Campaign with a **Modify Contact's Segment** action." -msgstr "" - -#: ../segments/manage_segments.rst:170 -msgid "Click **Actions**." -msgstr "" - -#: ../segments/manage_segments.rst:172 -msgid "From the **Add new submit action** menu, select **Modify Contact's Segments.**" -msgstr "" - -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing Form submit action." -msgstr "" - -#: ../segments/manage_segments.rst:177 -msgid "Add a Title for the submit action and add a **Description** - optional." -msgstr "" - -#: ../segments/manage_segments.rst:179 -msgid "Select the Segments you'd like to add the Contact to or remove the Contact from." -msgstr "" - -#: ../segments/manage_segments.rst:181 -#: ../segments/manage_segments.rst:219 -msgid "Click **Add**." -msgstr "" - -#: ../segments/manage_segments.rst:186 -msgid "Points trigger" -msgstr "" - -#: ../segments/manage_segments.rst:190 -msgid "Once a Contact has accrued an assigned number of Points, the system can add them to a Segment. This may be a Segment for your most engaged Contacts who become eligible for special offers, or a Segment your sales team reviews to find strong prospects." -msgstr "" - -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing Points trigger." -msgstr "" - -#: ../segments/manage_segments.rst:195 -msgid "In the **Points** section of the platform, select **Manage Triggers**." -msgstr "" - -#: ../segments/manage_segments.rst:197 -msgid "Click **+New**." -msgstr "" - -#: ../segments/manage_segments.rst:199 -msgid "Give your trigger a **Name** and **Description**." -msgstr "" - -#: ../segments/manage_segments.rst:201 -msgid "Enter the **Minimum number of Points** for adding a Contact to your Segment." -msgstr "" - -#: ../segments/manage_segments.rst:203 -msgid "Decide if you'd like to add all Contacts with at least that number of Points to the Segment:" -msgstr "" - -#: ../segments/manage_segments.rst:207 -msgid "If you only want to add new Contacts who reach the threshold to this Segment, select **No** - default." -msgstr "" - -#: ../segments/manage_segments.rst:209 -msgid "To add all existing Contacts with at least a certain number of Points to the Segment, toggle the switch to **Yes**." -msgstr "" - -#: ../segments/manage_segments.rst:211 -msgid "Click **Events**." -msgstr "" - -#: ../segments/manage_segments.rst:213 -msgid "Click the menu for **Add an event** and select **Modify Contact's Segments**." -msgstr "" - -#: ../segments/manage_segments.rst:215 -msgid "Add a **Title** for the event and a **Description** - optional." -msgstr "" - -#: ../segments/manage_segments.rst:217 -msgid "Select the Segments you'd like to add to or remove the Contact from." -msgstr "" - -#: ../segments/manage_segments.rst:221 -msgid "Click **Save & Close**." -msgstr "" - -#: ../segments/manage_segments.rst:223 -msgid "This accomplishes the same thing as creating a Dynamic Segment with a filter for Points, the operator ``greater than (or equal to)``, and the minimum number of Points. The difference is if you only want to add Contacts to a Segment who reach the point value after creating this trigger to a Segment, you can." -msgstr "" - -#: ../segments/manage_segments.rst:228 -msgid "CSV upload" -msgstr "" - -#: ../segments/manage_segments.rst:232 -msgid "If you have a list outside of Mautic, saved as a UTF-8 encoded CSV file, you can upload the list directly into a Mautic Segment." -msgstr "" - -#: ../segments/manage_segments.rst:234 -msgid "Click **Contact**." -msgstr "" - -#: ../segments/manage_segments.rst:236 -msgid "Click the menu in the upper-right hand corner and select **Import**." -msgstr "" - -#: ../segments/manage_segments.rst:238 -msgid "Ensure the file is in a UTF-8 CSV format. Select your file then click **Upload**." -msgstr "" - -#: ../segments/manage_segments.rst:240 -msgid "At the top of the next screen, select the Segment you want to add the Contacts to." -msgstr "" - -#: ../segments/manage_segments.rst:242 -msgid "Map the appropriate fields from the file. Remember to always map the unique identifier, so you don't create duplicates." -msgstr "" - -#: ../segments/manage_segments.rst:244 -msgid "Click **Import**." -msgstr "" - -#: ../segments/manage_segments.rst:246 -msgid "If your file is larger than 1,000 rows, the system changes screens and informs you once the file has uploaded. After the upload is complete, click the Segments section of the platform to see the added Contacts." -msgstr "" - -#: ../segments/manage_segments.rst:251 -msgid "Dynamic Segments" -msgstr "" - -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing Segment filters." -msgstr "" - -#: ../segments/manage_segments.rst:258 -msgid "Mautic moves Contacts into and out of dynamic Segments based on the filters applied to the Segment. As the data associated with the Contact updates, including Company associations and behaviors, Mautic updates Segment membership." -msgstr "" - -#: ../segments/manage_segments.rst:261 -msgid "Segment filters" -msgstr "" - -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing Segment Filters List." -msgstr "" - -#: ../segments/manage_segments.rst:267 -msgid "Create a new Segment by clicking the **+New** button." -msgstr "" - -#: ../segments/manage_segments.rst:271 -msgid "Click the **Filters** tab to add filters." -msgstr "" - -#: ../segments/manage_segments.rst:273 -msgid "Click the **Choose one**… menu and search for the field you'd like to Segment by." -msgstr "" - -#: ../segments/manage_segments.rst:277 -msgid "Listed below are three types of fields:" -msgstr "" - -#: ../segments/manage_segments.rst:279 -msgid "Contact fields" -msgstr "" - -#: ../segments/manage_segments.rst:281 -msgid "Set Fields to **Available for Segments = Yes** in your Custom Field manager to display here." -msgstr "" - -#: ../segments/manage_segments.rst:283 -msgid "Contact behavior and actions" -msgstr "" - -#: ../segments/manage_segments.rst:284 -msgid "Primary Company fields" -msgstr "" - -#: ../segments/manage_segments.rst:286 -msgid "Set Fields to **Available for Segments = Yes** in your Custom Field manager to appear here." -msgstr "" - -#: ../segments/manage_segments.rst:288 -msgid "Contacts associates with multiple Companies, but Mautic adds them to Segments based on fields for the primary Company." -msgstr "" - -#: ../segments/manage_segments.rst:290 -msgid "Add more filters, using the **And** and **Or** operators. An **Or** operator creates a new group of filters which can include And operators." -msgstr "" - -#: ../segments/manage_segments.rst:292 -msgid "Click **Save and close**." -msgstr "" - -#: ../segments/manage_segments.rst:296 -msgid "Segments are rebuilt according to how frequently you fire your :ref:`cron jobs`." -msgstr "" - -#: ../segments/manage_segments.rst:298 -msgid "If a Segment fails to rebuild for a predetermined length of time, Mautic displays a notification alerting you of an error. For information on defining this time period, see :ref:`Segment settings`" -msgstr "" - -#: ../segments/manage_segments.rst:299 -msgid "Mautic supports include/exclude operators with pipe-separated ``|`` values in the Text field types in Segment filters. You can paste the values from a spreadsheet." -msgstr "" - -#: ../segments/manage_segments.rst:304 -msgid "Using Date Filters" -msgstr "" - -#: ../segments/manage_segments.rst:308 -msgid "You can create dynamic Segments by using date filters." -msgstr "" - -#: ../segments/manage_segments.rst:312 -msgid "The date format for values stored in the database is ``YYYY-MM-DD``. For example, December 11, 2020 is stored as 2020-12-11 and November 12, 2020 is stored as 2020-11-12. To update the display format for dates, go to **Settings > Configuration > System Settings > System Defaults**. However, this doesn't alter the storage format in the database." -msgstr "" - -#: ../segments/manage_segments.rst:317 -msgid "Operators" -msgstr "" - -#: ../segments/manage_segments.rst:None -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing Operators." -msgstr "" - -#: ../segments/manage_segments.rst:324 -msgid "You must ensure that you use the correct operator and time frame to build an effective Segment." -msgstr "" - -#: ../segments/manage_segments.rst:326 -msgid "Once you've selected a date field as your filter, such as the default **Date last active** field or a custom **Birthday** field, you'll have a list of operators to choose from:" -msgstr "" - -#: ../segments/manage_segments.rst:328 -msgid "**Equals** - The value on the Contact record exactly matches the filter value." -msgstr "" - -#: ../segments/manage_segments.rst:330 -msgid "**Not Equal** - The value on the Contact record is any value that doesn't match the filter value." -msgstr "" - -#: ../segments/manage_segments.rst:332 -msgid "**Greater than** - The value on the Contact record is at a later date in time than X date. For example, ``Greater than`` today means anytime from tomorrow until the end of time." -msgstr "" - -#: ../segments/manage_segments.rst:334 -msgid "**Greater than or equal** - The value on the Contact record is either at a later date in time than or including X date. For example, ``Greater than or equal`` today means anytime from today until the end of time" -msgstr "" - -#: ../segments/manage_segments.rst:336 -msgid "**Less than** - The value on the Contact record is at an earlier date in time than X date. For example, ``Less than today`` means anytime from the beginning of time until yesterday." -msgstr "" - -#: ../segments/manage_segments.rst:338 -msgid "**Less than or equal** - The value on the Contact record is at an earlier date in time than X date. For example, ``Less than or equal today`` means anytime from the beginning of time until today." -msgstr "" - -#: ../segments/manage_segments.rst:340 -msgid "**Empty** - No value exists in the field on the Contact record." -msgstr "" - -#: ../segments/manage_segments.rst:342 -msgid "**Not empty** - A value exists in the field on the Contact record." -msgstr "" - -#: ../segments/manage_segments.rst:344 -msgid "**Like** - This operator isn't supported in date or date-time fields, don't use it." -msgstr "" - -#: ../segments/manage_segments.rst:346 -msgid "**Not like** - This operator isn't supported in date or date-time fields, don't use it." -msgstr "" - -#: ../segments/manage_segments.rst:348 -msgid "**Regexp** - Segment includes Contacts with values that match the specified regular expression pattern. If you aren't proficient with regular expression, don't use this operator." -msgstr "" - -#: ../segments/manage_segments.rst:350 -msgid "**Not regexp** - Segment includes Contacts with values that don't match the specified regular expression pattern. If you aren't proficient with regular expressions, don't use this operator." -msgstr "" - -#: ../segments/manage_segments.rst:352 -msgid "**Starts with** - Segment includes Contacts whose field values begin with the specified numbers. These filter values should generally reference years, or years and months." -msgstr "" - -#: ../segments/manage_segments.rst:354 -msgid "*For example, A value of 19 matches any Contacts whose field value has a year in the 1900^s. A value of 200 matches Contacts with a year value between 2000 and 2009 and a value of 2020-11 matches Contacts with a field value in November 2020.*" -msgstr "" - -#: ../segments/manage_segments.rst:356 -msgid "**Ends with** - Segment includes Contacts whose field values end with the specified numbers. These filter values should generally reference days, or months and days." -msgstr "" - -#: ../segments/manage_segments.rst:358 -msgid "*For example, A value of 1 matches anyone whose field value is on the 1^st, 21^st, or 31^st of any month but a value of 01 matches the 1 st of a month. A value of 01-01 finds Contacts whose value is for January 1 of any year.*" -msgstr "" - -#: ../segments/manage_segments.rst:360 -msgid "**Contains** - Segment includes Contacts with the specified filter value anywhere in the field value." -msgstr "" - -#: ../segments/manage_segments.rst:365 -msgid "Once you have selected the field you can then choose the type of operation to perform. These vary depending on the way you wish to filter your Contacts." -msgstr "" - -#: ../segments/manage_segments.rst:370 -msgid "Matching part of a string" -msgstr "" - -#: ../segments/manage_segments.rst:374 -msgid "There are 5 filters you can use for matching part of a string - ``starts with``, ``ends with``, ``contains``, ``like`` and ``regexp``. First three filters match strings as you enter it. ``like`` filter is for advanced Users - you can specify which type you want to use with ``%`` character:" -msgstr "" - -#: ../segments/manage_segments.rst:377 -msgid "``My string%`` is the same as ``starts with`` filter with ``My string`` value." -msgstr "" - -#: ../segments/manage_segments.rst:379 -msgid "``%My string`` is the same as ``ends with`` filter with ``My string`` value." -msgstr "" - -#: ../segments/manage_segments.rst:381 -msgid "``%My string%`` is the same as ``contains`` filter with ``My string`` value." -msgstr "" - -#: ../segments/manage_segments.rst:383 -msgid "``My string`` is the same as ``contains`` filter with ``My string`` value." -msgstr "" - -#: ../segments/manage_segments.rst:385 -msgid "A few notes for text filters:" -msgstr "" - -#: ../segments/manage_segments.rst:387 -msgid "You should use ``starts with``, ``ends with``, ``contains`` rather than ``like`` as they're more specific, and therefore can be more effective." -msgstr "" - -#: ../segments/manage_segments.rst:389 -msgid "A ``%`` character in the middle of the string has no special meaning. A ``contains`` filter with ``my % string`` searches for a string with ``%`` in the middle. The same is TRUE for a ``like`` filter with ``%my % string%`` value. There is no need to escape this character." -msgstr "" - -#: ../segments/manage_segments.rst:391 -msgid "Mautic searches for the ``%`` character in a value for the ``like`` filter, if finding at least one ``%`` Mautic doesn't perform any modification." -msgstr "" - -#: ../segments/manage_segments.rst:393 -msgid "You can use regular expressions in a ``regexp`` filter. Mautic recognises all common operators like ``|`` for OR - for example ``first string|second string``, character sets including ``[0-9]``, ``[a-z0-9]`` and so forth, repetitions (``+``, ``*``, ``?``) and more." -msgstr "" - -#: ../segments/manage_segments.rst:395 -msgid "You have to escape special characters with ``\\`` if you want to use them as matching character." -msgstr "" - -#: ../segments/manage_segments.rst:397 -msgid "Learn more about :xref:`Regex`." -msgstr "" - -#: ../segments/manage_segments.rst:401 -msgid "MySQL (and Mautic) uses POSIX regular expressions, which could behave differently from other types of regular expressions." -msgstr "" - -#: ../segments/manage_segments.rst:406 -msgid "Date options" -msgstr "" - -#: ../segments/manage_segments.rst:410 -msgid "Date filters allow you to choose a date via DatePicker:" -msgstr "" - -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing DatePicker." -msgstr "" - -#: ../segments/manage_segments.rst:415 -msgid "However, you can specify much more here. Mautic recognizes relative formats too - these string aren't translatable:" -msgstr "" - -#: ../segments/manage_segments.rst:417 -msgid "``+1 day`` - you can also use ``1 day``" -msgstr "" - -#: ../segments/manage_segments.rst:418 -msgid "``-2 days`` - you can also use ``2 days ago``" -msgstr "" - -#: ../segments/manage_segments.rst:419 -msgid "``+1 week`` / ``-2 weeks`` / ``3 weeks ago``" -msgstr "" - -#: ../segments/manage_segments.rst:420 -msgid "``+5 months`` / ``-6 months`` / ``7 months ago``" -msgstr "" - -#: ../segments/manage_segments.rst:421 -msgid "``+1 year`` / ``-2 years`` / ``3 years ago``" -msgstr "" - -#: ../segments/manage_segments.rst:423 -msgid "Example - Consider that today is ``2022-03-05``:" -msgstr "" - -#: ../segments/manage_segments.rst:425 -msgid "``Date identified equals -1 week`` returns all Contacts identified on 2022-02-26." -msgstr "" - -#: ../segments/manage_segments.rst:426 -msgid "``Date identified less than -1 week`` returns all Contacts identified before 2022-02-26." -msgstr "" - -#: ../segments/manage_segments.rst:427 -msgid "``Date identified equals -1 months`` returns all Contacts identified on 2022-02-05." -msgstr "" - -#: ../segments/manage_segments.rst:428 -msgid "``Date identified greater or equal -1`` year returns all Contacts identified 2021-03-05 and after." -msgstr "" - -#: ../segments/manage_segments.rst:429 -msgid "``Date identified greater than -1`` year returns all Contacts identified after 2021-03-05." -msgstr "" - -#: ../segments/manage_segments.rst:431 -msgid "Beside this you can specify your date with text. These formulas are **translatable**, so make sure you use them in correct format." -msgstr "" - -#: ../segments/manage_segments.rst:433 -msgid "``birthday`` / ``anniversary``" -msgstr "" - -#: ../segments/manage_segments.rst:434 -msgid "``birthday -7 days`` / ``anniversary -7 days``" -msgstr "" - -#: ../segments/manage_segments.rst:435 -msgid "``today`` / ``tomorrow`` / ``yesterday``" -msgstr "" - -#: ../segments/manage_segments.rst:436 -msgid "``this week`` / ``last week`` / ``next week``" -msgstr "" - -#: ../segments/manage_segments.rst:437 -msgid "``this month`` / ``last month`` / ``next month``" -msgstr "" - -#: ../segments/manage_segments.rst:438 -msgid "``this year`` / ``last year`` / ``next year``" -msgstr "" - -#: ../segments/manage_segments.rst:440 -msgid "Example (Consider that today is ``2022-03-05``):" -msgstr "" - -#: ../segments/manage_segments.rst:442 -msgid "``Date identified equals last week`` returns all Contacts identified in the specified date range, for example 2022-03-01 - 2022-03-07." -msgstr "" - -#: ../segments/manage_segments.rst:443 -msgid "``Date identified less than last week`` returns all Contacts identified before 2022-02-22." -msgstr "" - -#: ../segments/manage_segments.rst:444 -msgid "``Date identified equals last month`` returns all Contacts identified in the specified date range, for example 2022-02-01 - 2022-02-28." -msgstr "" - -#: ../segments/manage_segments.rst:445 -msgid "``Date identified greater or equal last year`` returns all Contacts identified 2021-01-01 and after." -msgstr "" - -#: ../segments/manage_segments.rst:446 -msgid "``Date identified greater than last year`` returns all Contacts identified after 2021-12-31." -msgstr "" - -#: ../segments/manage_segments.rst:447 -msgid "``Custom Contact date field equal birthday -1 day`` returns all Contacts identified every year on 03-04 (4th march)." -msgstr "" - -#: ../segments/manage_segments.rst:448 -msgid "``Custom Contact date field equal anniversary -1 month`` returns all Contacts identified every year on 02-04 (4th february)" -msgstr "" - -#: ../segments/manage_segments.rst:450 -msgid "Once you have created your Segment, any applicable Contact is automatically added through the execution of a :ref:`cron job`. This is the essence of Segments." -msgstr "" - -#: ../segments/manage_segments.rst:452 -msgid "To keep the Segments current, create a cron job that executes the :ref:`command` at the desired interval." -msgstr "" - -#: ../segments/manage_segments.rst:454 -msgid "Through the execution of that command, Mautic adds Contacts that match the filters and removes Contacts that no longer match. Any Contacts that were manually added remain part of the list regardless of filters." -msgstr "" - -#: ../segments/manage_segments.rst:459 -msgid "Delete all Contacts in a Segment" -msgstr "" - -#: ../segments/manage_segments.rst:463 -msgid "It's possible to delete all Contacts in a Segment manually rather than with a Campaign action. To do this, first create a Segment with filters that picks up all the Contacts you want to delete." -msgstr "" - -#: ../segments/manage_segments.rst:465 -msgid "This is a performance precaution since deleting more Contacts at one time could cause issues. You can, however, delete multiple batches of 100 Contacts to delete larger lists." -msgstr "" - -#: ../segments/manage_segments.rst:471 -msgid "Select **Delete Selected** from the list." -msgstr "" - -#: ../segments/manage_segments.rst:474 -msgid "Click **Delete**." -msgstr "" - -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing Deleting all Contacts in a Segment." -msgstr "" - -#: ../segments/manage_segments.rst:480 -msgid "Deleting thousands of Contacts this way in one Segment becomes a tedious task. Luckily, there is a trick how to let the background workers do the job for you." -msgstr "" - -#: ../segments/manage_segments.rst:482 -msgid "Create a Campaign which has the Segment as the source" -msgstr "" - -#: ../segments/manage_segments.rst:484 -msgid "Use the :ref:`Delete contact action`." -msgstr "" - -#: ../segments/manage_segments.rst:486 -msgid "This way the ``mautic:campaign:update`` and ``mautic:campaign:trigger`` commands delete all the Contacts in the Segment, and all the Contacts added to the Segment in the future. It's all done automatically in the background. It's necessary to configure the :ref:`cron jobs`." -msgstr "" - -#: ../segments/manage_segments.rst:492 -msgid "You can't recover deleted Contacts unless you restore your entire Mautic database backup. **Use with extreme caution**." -msgstr "" - -#: ../segments/manage_segments.rst:None -msgid "Screenshot showing deleting used Segment." -msgstr "" - -#: ../segments/manage_segments.rst:500 -msgid "Deleting or unpublishing a Segment" -msgstr "" - -#: ../segments/manage_segments.rst:504 -msgid "Since :xref:`Mautic 4` there is a step when deleting or unpublishing a Segment to ensure that it's not required as a filter by an existing Segment." -msgstr "" - -#: ../segments/manage_segments.rst:None -msgid "Screenshot deleting or unpublishing a Segment" -msgstr "" - -#: ../segments/manage_segments.rst:510 -msgid "If you attempt to delete or unpublish a Segment which is in use by a filter in another Segment, an alert prompts you to edit the other Segment, removing the dependency before you delete the Segment." -msgstr "" diff --git a/docs/docs_translations/stages.pot b/docs/docs_translations/stages.pot deleted file mode 100644 index 72c0d3f1..00000000 --- a/docs/docs_translations/stages.pot +++ /dev/null @@ -1,123 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../stages/stages.rst:2 -msgid "Stages" -msgstr "" - -#: ../stages/stages.rst:4 -msgid "Mautic Stages provide a means for Users to track and manage the progress of their Contacts through the various phases of the marketing lifecycle or funnel." -msgstr "" - -#: ../stages/stages.rst:6 -msgid "By categorizing Contacts into different Stages, you can better understand their engagement with the brand and tailor your marketing strategies accordingly." -msgstr "" - -#: ../stages/stages.rst:8 -msgid "Once you have created your Stages, you can easily move Contacts from one Stage to another based on their behavior or other criteria." -msgstr "" - -#: ../stages/stages.rst:13 -msgid "Creating Stages" -msgstr "" - -#: ../stages/stages.rst:17 -msgid "Navigate to the **Stages** section in the left side menu, and then click **+New**." -msgstr "" - -#: ../stages/stages.rst:None -msgid "Mautic Stages" -msgstr "" - -#: ../stages/stages.rst:25 -msgid "**Name** - While most Companies have similar Stage structures, each Company uses them differently. Come up with the Stages you want to track different parts of your marketing funnel with." -msgstr "" - -#: ../stages/stages.rst:27 -msgid "**Description** - To help you and other Users easily identify what qualifies a Contact for that Stage, it's recommended to add a description." -msgstr "" - -#: ../stages/stages.rst:29 -msgid "**Weight** - Used to decide the progression of your Stages. The greater the Stage weight number, the further along in the funnel a Contact is. Contacts can't move backwards to Stages with lower weights." -msgstr "" - -#: ../stages/stages.rst:31 -msgid "**Category** - Assign a Category to help you organize your Stages. For more information, see :ref:`categories`." -msgstr "" - -#: ../stages/stages.rst:33 -msgid "**Publish options** - The dashboard widget doesn't display data for an unpublished Stage. In addition, the Segment filters or Campaign conditions don't display the Stage. To avoid using the Stage while building it, set a future publish date and time. If you want the Stage to become unavailable after a certain time, set the date and time for unpublishing." -msgstr "" - -#: ../stages/stages.rst:38 -#: ../stages/stages.rst:None -msgid "Moving Contacts between Stages" -msgstr "" - -#: ../stages/stages.rst:42 -msgid "Moving Contacts between Stages requires a Campaign action." -msgstr "" - -#: ../stages/stages.rst:44 -msgid "Depending on how you define your Contact lifecycle and Stages, there may be different triggers for a Contact to move between Stages. Examples include behaviors within a Campaign, or moving between Segments which have criteria set up for each Stage." -msgstr "" - -#: ../stages/stages.rst:46 -msgid "In any Campaign where you want to have Contacts move between new Stages:" -msgstr "" - -#: ../stages/stages.rst:54 -msgid "Add a new **Action**." -msgstr "" - -#: ../stages/stages.rst:56 -msgid "Select **Change Contact's Stage** as the action type." -msgstr "" - -#: ../stages/stages.rst:58 -msgid "Select the Stage you want to move the Contacts to. You can base this on a prior event, or on a Segment that Contacts are in based on filters matching your requirements for a Stage." -msgstr "" - -#: ../stages/stages.rst:60 -msgid "For more information on setting up Campaigns, see :ref:`triggering campaign events`" -msgstr "" - -#: ../stages/stages.rst:64 -msgid "You can have multiple funnels with different Stages, and multiple Stages across those funnels with the same weight. A Contact can only ever be in one Stage at a time. It's not possible to move a Contact to a Stage which has a lesser weight than their current Stage. For example if they're currently in Stage B which has a weight of 50, you can't move them to Stage A which has a weight of 25." -msgstr "" - -#: ../stages/stages.rst:69 -#: ../stages/stages.rst:None -msgid "Visualizing Stage movement" -msgstr "" - -#: ../stages/stages.rst:73 -msgid "The Mautic dashboard features two widgets to help Users see how Contacts are moving between Stages." -msgstr "" - -#: ../stages/stages.rst:81 -msgid "The Stages in time widget shows how often Contacts change Stages. More change indicates more velocity through your funnel." -msgstr "" - -#: ../stages/stages.rst:84 -msgid "Lifecycle" -msgstr "" - -#: ../stages/stages.rst:86 -msgid "The lifecycle widget enables marketers to see the number of Contacts within a specified Segment in each Stage. You may include multiple Segments on the widget. It's possible to have more than one lifecycle widget to break down the information into separate graphs, but still display the data on the dashboard for multiple Segments." -msgstr "" diff --git a/docs/docs_translations/themes.pot b/docs/docs_translations/themes.pot deleted file mode 100644 index 1d4640a2..00000000 --- a/docs/docs_translations/themes.pot +++ /dev/null @@ -1,328 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../themes/code_mode.rst:4 -msgid "Code mode" -msgstr "" - -#: ../themes/code_mode.rst:8 -msgid "Code Mode is an option available in the Email and Landing Page edit Form. It allows you to create/insert/edit your content in HTML code. It's helpful for situations where you don't want to use a Mautic Theme and you want to use an HTML Theme copied from a third party Theme builder, or if you prefer editing HTML code directly." -msgstr "" - -#: ../themes/code_mode.rst:10 -msgid "The other option to edit Landing Page/Email content is to use the built-in drag-and-drop GrapesJS Builder. Read more in the :doc:`/builders/email_landing_page` section." -msgstr "" - -#: ../themes/code_mode.rst:13 -msgid "Select the Code mode" -msgstr "" - -#: ../themes/code_mode.rst:15 -msgid "If you want to work with existing HTML, select code mode from the Theme selector. To open the code mode Builder, click the advanced tab which appears." -msgstr "" - -#: ../themes/code_mode.rst:None -msgid "Screenshot of code mode builder" -msgstr "" - -#: ../themes/code_mode.rst:22 -msgid "Limitations" -msgstr "" - -#: ../themes/code_mode.rst:24 -msgid "If you use a Mautic Theme to create the Landing Page/Email and you subsequently want to edit the HTML code, you should think carefully about doing this." -msgstr "" - -#: ../themes/code_mode.rst:26 -msgid "Once you switch from a Theme to Code Mode, content becomes HTML and you can't switch back to the Theme again." -msgstr "" - -#: ../themes/code_mode.rst:28 -msgid "Selecting a Theme replaces the content with that of the default Theme, so you'll lose your modifications." -msgstr "" - -#: ../themes/code_mode.rst:30 -msgid "Instead, to make small code changes to an existing Theme, it's recommended to use the code mode built into the GrapesJS Builder." -msgstr "" - -#: ../themes/code_mode.rst:None -msgid "Screenshot of code mode" -msgstr "" - -#: ../themes/code_mode.rst:39 -msgid "Edit the HTML content in the code mode Builder" -msgstr "" - -#: ../themes/code_mode.rst:43 -msgid "In code mode, you can see the HTML content in the text area under the Advanced tab. There is no preview at this time." -msgstr "" - -#: ../themes/code_mode.rst:46 -msgid "Mautic tokens" -msgstr "" - -#: ../themes/code_mode.rst:48 -msgid "You can use the tokens in the code mode Builder by typing them directly into your code. For example when you type ``{contactfield=firstname}``." -msgstr "" - -#: ../themes/customizing_themes.rst:4 -msgid "Customizing Themes" -msgstr "" - -#: ../themes/customizing_themes.rst:8 -msgid "It's possible to customize Themes, or even to create your own from scratch, with Mautic. To do this go to the Theme Manager, open the drop down menu next to the pre-installed Theme you want to modify and download it." -msgstr "" - -#: ../themes/customizing_themes.rst:13 -msgid "Customizing an existing Theme" -msgstr "" - -#: ../themes/customizing_themes.rst:17 -msgid "To customize the downloaded Theme, review the :xref:`themes developer documentation` for detailed guidance." -msgstr "" - -#: ../themes/manage_themes.rst:4 -msgid "Manage Themes" -msgstr "" - -#: ../themes/manage_themes.rst:8 -msgid "Themes control the look and feel of the Mautic Landing Pages, Emails, Forms and Message screens." -msgstr "" - -#: ../themes/manage_themes.rst:10 -msgid "A basic Mautic installation comes pre-packaged with a number of Themes for you to use 'as-is' or adapt to suit specific projects." -msgstr "" - -#: ../themes/manage_themes.rst:12 -msgid "It's also possible to :xref:`create a Theme` for Mautic from scratch." -msgstr "" - -#: ../themes/manage_themes.rst:14 -msgid "Access the Theme Manager via the Admin Menu. Click the cog icon in the top right corner to open it and select the Theme menu item." -msgstr "" - -#: ../themes/manage_themes.rst:16 -msgid "The Themes section displays the list of Themes with the following details:" -msgstr "" - -#: ../themes/manage_themes.rst:18 -msgid "**Title** - The name or title of the Theme." -msgstr "" - -#: ../themes/manage_themes.rst:20 -msgid "**Author** - The name of the author or creator of the Theme." -msgstr "" - -#: ../themes/manage_themes.rst:22 -msgid "**Feature** - The list of features and Builders that the Theme supports." -msgstr "" - -#: ../themes/manage_themes.rst:None -msgid "Screenshot of Theme list" -msgstr "" - -#: ../themes/manage_themes.rst:28 -msgid "This list of Themes appears as selectable options in Forms, as this allows you to provide styling for Forms." -msgstr "" - -#: ../themes/manage_themes.rst:30 -msgid "Additionally, you can edit and customize Themes in the Email and Landing Page builders to meet your needs." -msgstr "" - -#: ../themes/manage_themes.rst:32 -msgid "With the Email and Landing Page builders, you can start from a template and build your own variations using the drag-and-drop Builder. For more information, see :doc:`Email builder` and :doc:`Landing Pages`." -msgstr "" - -#: ../themes/manage_themes.rst:37 -msgid "Installing a Theme" -msgstr "" - -#: ../themes/manage_themes.rst:41 -msgid "It's necessary to install a new or edited Theme as a zip package. The zip package must have the same structure as the preinstalled Themes and the config.json file must be present in the root folder of the zip package. The :xref:`themes developer documentation` contains more on that." -msgstr "" - -#: ../themes/manage_themes.rst:45 -msgid "You must select and zip all the files when creating the zip package. Ensure that you don't zip the files within a folder, otherwise the Theme won't install." -msgstr "" - -#: ../themes/manage_themes.rst:47 -msgid "You can build and install your own Forms Theme using Twig, and you can also install BeeFree templates as Themes." -msgstr "" - -#: ../themes/manage_themes.rst:49 -msgid "To install a Theme:" -msgstr "" - -#: ../themes/manage_themes.rst:51 -#: ../themes/manage_themes.rst:72 -#: ../themes/manage_themes.rst:93 -#: ../themes/manage_themes.rst:114 -#: ../themes/manage_themes.rst:156 -msgid "Log in to Mautic." -msgstr "" - -#: ../themes/manage_themes.rst:53 -#: ../themes/manage_themes.rst:74 -#: ../themes/manage_themes.rst:95 -#: ../themes/manage_themes.rst:116 -#: ../themes/manage_themes.rst:158 -msgid "Click the **Settings** icon." -msgstr "" - -#: ../themes/manage_themes.rst:55 -#: ../themes/manage_themes.rst:76 -#: ../themes/manage_themes.rst:97 -#: ../themes/manage_themes.rst:118 -msgid "Click **Themes**." -msgstr "" - -#: ../themes/manage_themes.rst:57 -msgid "On the Themes section, in the top-right corner, click **Choose file**." -msgstr "" - -#: ../themes/manage_themes.rst:59 -msgid "Browse and select the Theme." -msgstr "" - -#: ../themes/manage_themes.rst:61 -msgid "Click **Install**." -msgstr "" - -#: ../themes/manage_themes.rst:66 -msgid "Deleting a Theme" -msgstr "" - -#: ../themes/manage_themes.rst:70 -msgid "To delete a user-created Theme:" -msgstr "" - -#: ../themes/manage_themes.rst:78 -msgid "In the Themes section, locate the Theme that you want to delete." -msgstr "" - -#: ../themes/manage_themes.rst:80 -msgid "Select the drop-down before the Theme, and click **Delete**." -msgstr "" - -#: ../themes/manage_themes.rst:82 -msgid "In the confirmation dialog box, click **Delete**." -msgstr "" - -#: ../themes/manage_themes.rst:87 -msgid "Previewing a Theme" -msgstr "" - -#: ../themes/manage_themes.rst:91 -msgid "To preview a Theme:" -msgstr "" - -#: ../themes/manage_themes.rst:99 -msgid "In the Themes section, locate the Theme that you want to preview." -msgstr "" - -#: ../themes/manage_themes.rst:101 -msgid "Select the drop-down before the Theme, and click **Preview**." -msgstr "" - -#: ../themes/manage_themes.rst:103 -msgid "Mautic displays the preview of the Theme." -msgstr "" - -#: ../themes/manage_themes.rst:108 -msgid "Downloading a Theme" -msgstr "" - -#: ../themes/manage_themes.rst:112 -msgid "To download a Theme:" -msgstr "" - -#: ../themes/manage_themes.rst:120 -msgid "In the Themes section, locate the Theme that you want to download." -msgstr "" - -#: ../themes/manage_themes.rst:122 -msgid "Select the drop-down before the Theme, and click **Download**." -msgstr "" - -#: ../themes/manage_themes.rst:124 -msgid "Upon downloading a Theme on your local machine, you can modify it following the structure outlined in the :xref:`create a Theme` section of the Developer Documentation before reinstalling it for use in your instance." -msgstr "" - -#: ../themes/manage_themes.rst:129 -msgid "Update an old Theme" -msgstr "" - -#: ../themes/manage_themes.rst:133 -msgid "Mautic overwrites old Theme files when installing a Theme which already exists in Mautic. Therefore, the Theme updates can be also done by uploading the Theme with the new changes." -msgstr "" - -#: ../themes/manage_themes.rst:135 -msgid "Pre-installed Themes can't be overwritten, because the changes would return again after a Mautic update. If you want to change these Themes, download them and modify them to create a new, custom Theme, as outlined previously." -msgstr "" - -#: ../themes/manage_themes.rst:140 -msgid "Assigning a default Theme" -msgstr "" - -#: ../themes/manage_themes.rst:144 -msgid "You can assign your Mautic instance a default Theme for Landing Pages. Then use the Landing Page Builder to fill in the content for each new Landing Page you create." -msgstr "" - -#: ../themes/manage_themes.rst:None -msgid "Screenshot of Theme" -msgstr "" - -#: ../themes/manage_themes.rst:152 -msgid "Changing the Theme after building the Page may cause content to not display if the two Themes don't use the same placeholders." -msgstr "" - -#: ../themes/manage_themes.rst:154 -msgid "To assign a default Theme:" -msgstr "" - -#: ../themes/manage_themes.rst:160 -msgid "Click **Configuration**." -msgstr "" - -#: ../themes/manage_themes.rst:162 -msgid "Click Theme **Settings**." -msgstr "" - -#: ../themes/manage_themes.rst:164 -msgid "From the dropdown menu, select the Theme that you want to use as default." -msgstr "" - -#: ../themes/manage_themes.rst:166 -msgid "Click **Save & Close**." -msgstr "" - -#: ../themes/manage_themes.rst:168 -msgid "Themes are available to select for Emails and Landing Pages when creating them - this setting pre-selects the Theme chosen by default." -msgstr "" - -#: ../themes/manage_themes.rst:None -msgid "Screenshot of all Themes" -msgstr "" - -#: ../themes/theme_structure.rst:4 -msgid "Theme Structure" -msgstr "" - -#: ../themes/theme_structure.rst:8 -msgid "Visit the :xref:`themes developer documentation` about Themes for details about the Theme structure." -msgstr "" diff --git a/docs/docs_translations/translations.pot b/docs/docs_translations/translations.pot deleted file mode 100644 index 9d9017d0..00000000 --- a/docs/docs_translations/translations.pot +++ /dev/null @@ -1,21 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../translations/translations.rst:4 -msgid "Translation" -msgstr "" diff --git a/docs/docs_translations/users_roles.pot b/docs/docs_translations/users_roles.pot deleted file mode 100644 index 01adda33..00000000 --- a/docs/docs_translations/users_roles.pot +++ /dev/null @@ -1,250 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME \n" -"Language-Team: LANGUAGE \n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" - -#: ../users_roles/managing_roles.rst:4 -msgid "Roles" -msgstr "" - -#: ../users_roles/managing_roles.rst:8 -msgid "You can control access to Mautic instances by creating accounts for Users and associating them with a Role." -msgstr "" - -#: ../users_roles/managing_roles.rst:10 -msgid ":doc:`Users` are the accounts an individual uses to access Mautic, whereas :ref:`Roles` allow or deny access to various features within Mautic." -msgstr "" - -#: ../users_roles/managing_roles.rst:12 -msgid "Mautic uses Roles to control which resources and actions Users can access. When team members have different responsibilities, you may not want some team members working in certain parts of Mautic." -msgstr "" - -#: ../users_roles/managing_roles.rst:14 -msgid "By default, Mautic creates new Users with the Administrator Role with full system access. You can change that when manually creating a User, or select a different Role when importing a User by API." -msgstr "" - -#: ../users_roles/managing_roles.rst:19 -msgid "Creating a new Role" -msgstr "" - -#: ../users_roles/managing_roles.rst:24 -msgid "Full system access" -msgstr "" - -#: ../users_roles/managing_roles.rst:26 -msgid "If you select **Yes** on the **Full System Access** switch, you are creating an Administrator account which has the highest level of access to your Mautic instance." -msgstr "" - -#: ../users_roles/managing_roles.rst:None -#: ../users_roles/managing_roles.rst:None -msgid "Screenshot showing Mautic Roles" -msgstr "" - -#: ../users_roles/managing_roles.rst:31 -#: ../users_roles/managing_roles.rst:52 -msgid "Navigate to **Settings** > **Roles**." -msgstr "" - -#: ../users_roles/managing_roles.rst:33 -#: ../users_roles/managing_roles.rst:54 -#: ../users_roles/managing_users.rst:21 -msgid "Click **+New** in the top right corner." -msgstr "" - -#: ../users_roles/managing_roles.rst:35 -#: ../users_roles/managing_roles.rst:56 -msgid "In the **Details** tab, add a **Title** and **Description**." -msgstr "" - -#: ../users_roles/managing_roles.rst:37 -msgid "Select **Yes** on the **Full System Access** switch." -msgstr "" - -#: ../users_roles/managing_roles.rst:39 -msgid "Click **Save & Close**" -msgstr "" - -#: ../users_roles/managing_roles.rst:41 -msgid "Limit these accounts, and ensure that their credentials are secure." -msgstr "" - -#: ../users_roles/managing_roles.rst:43 -msgid "If you select this option, you won't be able to configure anything under **Permissions** because by default, this account has full access to everything." -msgstr "" - -#: ../users_roles/managing_roles.rst:46 -msgid "Setting granular permissions" -msgstr "" - -#: ../users_roles/managing_roles.rst:48 -msgid "Mautic allows you to create Roles with granular permissions for each bundle - or part - of Mautic." -msgstr "" - -#: ../users_roles/managing_roles.rst:50 -msgid "To configure a Role, leave the **Full System Access** switch at **No** and click the **Permissions** tab to start building the Role." -msgstr "" - -#: ../users_roles/managing_roles.rst:58 -msgid "Click the Permissions tab. The list of User permissions displays." -msgstr "" - -#: ../users_roles/managing_roles.rst:64 -msgid "Most permission Categories have options for **View**, **Edit**, **Create**, **Delete**, and **Publish**. Select checkboxes for the appropriate permissions for this Role. To select every checkbox and grant the User all permissions, select the **Full** option." -msgstr "" - -#: ../users_roles/managing_roles.rst:67 -msgid "Explaining the permission options" -msgstr "" - -#: ../users_roles/managing_roles.rst:69 -msgid "There are several options for selecting permissions:" -msgstr "" - -#: ../users_roles/managing_roles.rst:71 -msgid "**View** - this allows the Users with this Role to view this part of Mautic" -msgstr "" - -#: ../users_roles/managing_roles.rst:73 -msgid "**Edit** - this allows the Users with this Role to make changes to this part of Mautic" -msgstr "" - -#: ../users_roles/managing_roles.rst:75 -msgid "**Create** - this allows the Users with this Role to create new resources in this part of Mautic" -msgstr "" - -#: ../users_roles/managing_roles.rst:77 -msgid "**Delete** - this allows the Users with this Role to delete resources in this part of Mautic" -msgstr "" - -#: ../users_roles/managing_roles.rst:79 -msgid "**Publish** - this allows the Users with this Role to make resources in this part of Mautic available by publishing them" -msgstr "" - -#: ../users_roles/managing_roles.rst:81 -msgid "**Full** - this allows the Users with this Role all of the permissions." -msgstr "" - -#: ../users_roles/managing_roles.rst:83 -msgid "There are permission levels relating to resources the User has created themselves, and those created by others:" -msgstr "" - -#: ../users_roles/managing_roles.rst:85 -msgid "**Own** - this allows the Users with this Role to ``view/edit/delete/publish`` their own resources in this part of Mautic, but not those created by others" -msgstr "" - -#: ../users_roles/managing_roles.rst:87 -msgid "**Others** - this allows the Users with this Role to ``view/edit/delete/publish`` their own resources in this part of Mautic, and those created by others" -msgstr "" - -#: ../users_roles/managing_roles.rst:89 -msgid "There are permission levels relating to being able to manage resources:" -msgstr "" - -#: ../users_roles/managing_roles.rst:91 -msgid "**Manage** - this allows the Users with this Role to manage resources in this area of Mautic for example, managing custom fields or Plugins." -msgstr "" - -#: ../users_roles/managing_roles.rst:93 -msgid "There are permission levels relating to the editable fields in the Users section:" -msgstr "" - -#: ../users_roles/managing_roles.rst:95 -msgid "**Specified fields** - allow or deny the Users with this Role to edit specified fields in the Users section for example, Name, Username, Email, Position." -msgstr "" - -#: ../users_roles/managing_roles.rst:97 -msgid "**All** - this allows the Users with this Role to edit all fields relating to the Users section" -msgstr "" - -#: ../users_roles/managing_roles.rst:101 -msgid "User permissions restrict their view of dashboard widgets, resulting in them only seeing widgets for items or feature bundles they have permission to see." -msgstr "" - -#: ../users_roles/managing_roles.rst:103 -msgid "For example, if a User's Role doesn't have Asset permissions, they can't create or view widgets on the dashboard for Asset data." -msgstr "" - -#: ../users_roles/managing_roles.rst:105 -msgid "You can also :xref:`create Roles using the API`." -msgstr "" - -#: ../users_roles/managing_users.rst:4 -msgid "Managing Users" -msgstr "" - -#: ../users_roles/managing_users.rst:8 -msgid "An Administrator can manage Users with appropriate permissions in Mautic by accessing the settings cog wheel at the top right of the screen." -msgstr "" - -#: ../users_roles/managing_users.rst:10 -msgid "Create the User by completing all the mandatory fields, adding a signature if required, and assigning them a username and password. Always use a secure password for Users with access to your Mautic instance." -msgstr "" - -#: ../users_roles/managing_users.rst:None -msgid "Screenshot showing Mautic Users" -msgstr "" - -#: ../users_roles/managing_users.rst:15 -msgid "You can set up new Users in Mautic manually or through the API." -msgstr "" - -#: ../users_roles/managing_users.rst:17 -msgid "To set up a User manually:" -msgstr "" - -#: ../users_roles/managing_users.rst:19 -msgid "Navigate to **Settings** > **Users**." -msgstr "" - -#: ../users_roles/managing_users.rst:23 -msgid "Fill in the appropriate fields for your User:" -msgstr "" - -#: ../users_roles/managing_users.rst:25 -msgid "**First name** and **Last name** - Your User's first and last name." -msgstr "" - -#: ../users_roles/managing_users.rst:27 -msgid "**Roles** assigned based on permissions you grant." -msgstr "" - -#: ../users_roles/managing_users.rst:29 -msgid "**Signature** is only necessary if you're using the Mailer is owner feature in Mautic." -msgstr "" - -#: ../users_roles/managing_users.rst:31 -msgid "**Position - optional** - Your User's job title." -msgstr "" - -#: ../users_roles/managing_users.rst:33 -msgid "**Username, Email, Password** are the login credentials. If a User forgets their password, they can use the Forgot password link, but you can manually change their password here." -msgstr "" - -#: ../users_roles/managing_users.rst:37 -msgid "Passwords must be at least six characters in length. Ensure that you use a combination of upper and lower case alphabets, special characters, and numbers." -msgstr "" - -#: ../users_roles/managing_users.rst:39 -msgid "**Time zone** - Set the User's time zone, or use the default. Adding the User's time zone enables them to account for time zone differences for Email scheduling and other features." -msgstr "" - -#: ../users_roles/managing_users.rst:41 -msgid "**Language** - Select a language for each User, to improve their experience in Mautic." -msgstr "" - -#: ../users_roles/managing_users.rst:43 -msgid "When creating your Users, inform them of the credentials. Mautic doesn't send an Email notifying Users of their login information. Manually informing them is necessary." -msgstr "" diff --git a/docs/getting_started/how_to_install_mautic.rst b/docs/getting_started/how_to_install_mautic.rst index d5aef0c6..a69b82d6 100644 --- a/docs/getting_started/how_to_install_mautic.rst +++ b/docs/getting_started/how_to_install_mautic.rst @@ -146,7 +146,7 @@ Click **login** to continue working on your Mautic instance. Installing with command line ============================ -You can also install Mautic using the command line. You can either pass the settings parameters in the command, or create a local PHP file with your database settings. You can also define properties in this file using the syntax expected by the command-line options. +You can also install Mautic using the command line. You can either pass the settings parameters in the command, or create a local PHP file with your database settings. You can also define properties in this file using the syntax expected by the command-line options. Note that Mautic requires a complex password from version 5.1. Use the command ``path/to/php bin/console mautic:install --help`` for the list of options and flags available. @@ -195,7 +195,7 @@ Use the syntax below within a ``local.php`` file: 'db_backup_tables' => false, 'db_backup_prefix' => 'bak_', 'admin_email' => 'admin@example.com', - 'admin_password' => 'mautic', + 'admin_password' => 'Maut1cR0cks!', 'mailer_transport' => null, 'mailer_host' => null, 'mailer_port' => null, @@ -221,7 +221,7 @@ If desired, you can also add parameters in the install command: --mailer_from_name="Example From Name" --mailer_from_email="mautic@localhost" --mailer_transport="smtp" --mailer_host="localhost" --mailer_port="1025" --db_driver="pdo_mysql" --db_host="db" --db_port="3306" --db_name="db" --db_user="db" --db_password="db" - --db_backup_tables="false" --admin_email="admin@mautic.local" --admin_password="mautic" + --db_backup_tables="false" --admin_email="admin@mautic.local" --admin_password="Maut1cR0cks!" As the installation process begins, it flags up warnings and aborts if there are any critical errors. @@ -298,7 +298,7 @@ You can use :xref:`DDEV` which is recommended for testing and development with M This spins up a DDEV instance (which includes Mailhog, PHPMyAdmin, and Redis Commander) - by default at ``https://mautic.ddev.site`` - and also gives the option to set up Mautic ready for you to use. .. vale on -This runs through the Composer install process, and installs Mautic at the command line with a default username of ``admin`` and password of ``mautic``. +This runs through the Composer install process, and installs Mautic at the command line with a default username of ``admin`` and password of ``Maut1cR0cks!`` (note: pre Mautic 5.1 the password is just `mautic`. Installing with Composer ************************ @@ -508,4 +508,4 @@ Often there is a need to have a local environment for testing Mautic - for examp In Mautic, DDEV is the tool of choice for this purpose. It's very easy to work with. -To learn how to set up DDEV with Mautic, please review the documentation in the Contributors :xref:`Handbook`. \ No newline at end of file +To learn how to set up DDEV with Mautic, please review the documentation in the Contributors :xref:`Handbook`. diff --git a/docs/index.rst b/docs/index.rst index b58e9c24..2610e4e7 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -181,6 +181,7 @@ There are different types of documentation available to help you navigate your w points/points points/points_troubleshooting + points/point_groups .. toctree:: :maxdepth: 2 diff --git a/docs/links/queue_amazon_sqs.py b/docs/links/queue_amazon_sqs.py new file mode 100644 index 00000000..58a1f3a4 --- /dev/null +++ b/docs/links/queue_amazon_sqs.py @@ -0,0 +1,7 @@ +from . import link + +link_name = "queue-amazon-sqs" +link_text = "https://symfony.com/doc/5.4/messenger.html#amazon-sqs" +link_url = "https://symfony.com/doc/5.4/messenger.html#amazon-sqs" + +link.xref_links.update({link_name: (link_text, link_url)}) diff --git a/docs/links/queue_amqp_transport.py b/docs/links/queue_amqp_transport.py new file mode 100644 index 00000000..19678fc0 --- /dev/null +++ b/docs/links/queue_amqp_transport.py @@ -0,0 +1,7 @@ +from . import link + +link_name = "queue-amqp-transport" +link_text = "https://symfony.com/doc/5.4/messenger.html#amqp-transport" +link_url = "https://symfony.com/doc/5.4/messenger.html#amqp-transport" + +link.xref_links.update({link_name: (link_text, link_url)}) diff --git a/docs/links/queue_beanstalk_transport.py b/docs/links/queue_beanstalk_transport.py new file mode 100644 index 00000000..4b24408e --- /dev/null +++ b/docs/links/queue_beanstalk_transport.py @@ -0,0 +1,7 @@ +from . import link + +link_name = "queue-beanstalkd-transport" +link_text = "https://symfony.com/doc/5.4/messenger.html#beanstalkd-transport" +link_url = "https://symfony.com/doc/5.4/messenger.html#beanstalkd-transport" + +link.xref_links.update({link_name: (link_text, link_url)}) diff --git a/docs/links/queue_consuming_messages.py b/docs/links/queue_consuming_messages.py new file mode 100644 index 00000000..66c9b16d --- /dev/null +++ b/docs/links/queue_consuming_messages.py @@ -0,0 +1,7 @@ +from . import link + +link_name = "queue-consuming-messages" +link_text = "https://symfony.com/doc/5.4/messenger.html#consuming-messages-running-the-worker" +link_url = "https://symfony.com/doc/5.4/messenger.html#consuming-messages-running-the-worker" + +link.xref_links.update({link_name: (link_text, link_url)}) diff --git a/docs/links/queue_doctrine_transport.py b/docs/links/queue_doctrine_transport.py new file mode 100644 index 00000000..122c5a20 --- /dev/null +++ b/docs/links/queue_doctrine_transport.py @@ -0,0 +1,7 @@ +from . import link + +link_name = "queue-doctrine-transport" +link_text = "https://symfony.com/doc/5.4/messenger.html#doctrine-transport" +link_url = "https://symfony.com/doc/5.4/messenger.html#doctrine-transport" + +link.xref_links.update({link_name: (link_text, link_url)}) diff --git a/docs/links/queue_redis_transport.py b/docs/links/queue_redis_transport.py new file mode 100644 index 00000000..37adf0ce --- /dev/null +++ b/docs/links/queue_redis_transport.py @@ -0,0 +1,7 @@ +from . import link + +link_name = "queue-redis-transport" +link_text = "https://symfony.com/doc/5.4/messenger.html#redis-transport" +link_url = "https://symfony.com/doc/5.4/messenger.html#redis-transport" + +link.xref_links.update({link_name: (link_text, link_url)}) diff --git a/docs/links/queue_retries_failures.py b/docs/links/queue_retries_failures.py new file mode 100644 index 00000000..acaf3d80 --- /dev/null +++ b/docs/links/queue_retries_failures.py @@ -0,0 +1,7 @@ +from . import link + +link_name = "queue-retries-failures" +link_text = "https://symfony.com/doc/5.4/messenger.html#retries-failures" +link_url = "https://symfony.com/doc/5.4/messenger.html#retries-failures" + +link.xref_links.update({link_name: (link_text, link_url)}) diff --git a/docs/links/queue_saving_retrying_failed_messages.py b/docs/links/queue_saving_retrying_failed_messages.py new file mode 100644 index 00000000..e1494a21 --- /dev/null +++ b/docs/links/queue_saving_retrying_failed_messages.py @@ -0,0 +1,7 @@ +from . import link + +link_name = "queue-saving-retrying-failed-messages" +link_text = "https://symfony.com/doc/5.4/messenger.html#saving-retrying-failed-messages" +link_url = "https://symfony.com/doc/5.4/messenger.html#saving-retrying-failed-messages" + +link.xref_links.update({link_name: (link_text, link_url)}) diff --git a/docs/links/redis.py b/docs/links/redis.py new file mode 100644 index 00000000..f558ff97 --- /dev/null +++ b/docs/links/redis.py @@ -0,0 +1,7 @@ +from . import link + +link_name = "Redis" +link_text = "Redis" +link_url = "https://redis.io/" + +link.xref_links.update({link_name: (link_text, link_url)}) diff --git a/docs/locale/pt_BR/LC_MESSAGES/authentication.po b/docs/locale/pt_BR/LC_MESSAGES/authentication.po deleted file mode 100644 index ca622c6a..00000000 --- a/docs/locale/pt_BR/LC_MESSAGES/authentication.po +++ /dev/null @@ -1,217 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -# Translators: -# Ruth Cheesley , 2023 -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: 2023-07-21 15:27+0000\n" -"Last-Translator: Ruth Cheesley , 2023\n" -"Language-Team: Portuguese (Brazil) (https://app.transifex.com/mautic/teams/33223/pt_BR/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: pt_BR\n" -"Plural-Forms: nplurals=3; plural=(n == 0 || n == 1) ? 0 : n != 0 && n % 1000000 == 0 ? 1 : 2;\n" - -#: ../authentication/authentication.rst:2 -msgid "Authentication" -msgstr "Autenticação" - -#: ../authentication/authentication.rst:4 -msgid "" -"Mautic uses basic authentication for Users, however there is the ability to " -"integrate with a SAML SSO - Single Sign-On - provider." -msgstr "" -"O Mautic utiliza autenticação básica para Usuários, porém existe a " -"possibilidade de integração com um provedor SAML SSO - Single Sign-On." - -#: ../authentication/authentication.rst:9 -msgid "SAML Single Sign On" -msgstr "SAML Single Sign On" - -#: ../authentication/authentication.rst:13 -msgid "" -"SAML is a single sign on protocol that allows single sign on and User " -"creation in Mautic using a third party User source called an identity " -"provider (IDP)." -msgstr "" -"SAML é um protocolo de assinatura única que permite login único e criação de" -" Usuário no Mautic usando uma fonte terceira Origem do Usuário chamada " -"provedor de identidade (IDP)." - -#: ../authentication/authentication.rst:16 -msgid "Turning on SAML" -msgstr "Ativando o SAML" - -#: ../authentication/authentication.rst:17 -msgid "" -"To turn on SAML support in Mautic, you first need the IDP's metadata XML " -"which they provide. If it's a URL, browse to the URL then save the content " -"into an XML file." -msgstr "" -"Para ativar o suporte a SAML no Mautic, primeiro você precisa do XML de " -"metadados do IDP que eles fornecem. Se for uma URL, navegue até a URL e " -"salve o conteúdo em um arquivo XML." - -#: ../authentication/authentication.rst:19 -msgid "" -"Click the settings wheel in the top right corner to open the **Settings** " -"menu." -msgstr "" -"Clique no ícone de configurações no canto superior direito para abrir o menu" -" **Configurações**." - -#: ../authentication/authentication.rst:21 -msgid "Navigate to **Configuration** > **User/Authentication** Settings." -msgstr "" -"Navegue até **Configuração** > Configurações de **Usuário/Autenticação**." - -#: ../authentication/authentication.rstNone -msgid "Screenshot of SAML SSO Settings" -msgstr "Captura de tela das configurações de SAML SSO" - -#: ../authentication/authentication.rst:27 -msgid "Upload this file as the Identity Provider Metadata file." -msgstr "" -"Carregue este arquivo como o arquivo de Metadados do Provedor de Identidade." - -#: ../authentication/authentication.rst:29 -msgid "" -"It's recommended to create a non-Admin Role as the default Role for created " -"Users. Select this Role in the '**Default Role for created Users**' " -"dropdown. For more information, see :doc:`Users and " -"Roles`." -msgstr "" -"É recomendável criar uma função não administrativa como a Função padrão para" -" os Usuários criados. Selecione esta Função no menu suspenso '**Função " -"Padrão para Usuários criados**'. Para mais informações, veja :doc:`Usuários " -"e Funções1`." - -#: ../authentication/authentication.rstNone -msgid "Screenshot of the User Role Permission" -msgstr "Captura de tela da Permissão de Função do Usuário" - -#: ../authentication/authentication.rst:36 -msgid "Configuring the IDP" -msgstr "Configurando o IDP" - -#: ../authentication/authentication.rst:37 -msgid "The IDP may ask for the following settings:" -msgstr "O IDP pode solicitar as seguintes configurações:" - -#: ../authentication/authentication.rst:39 -msgid "" -"Entity ID - this is site URL, displayed at the top of User/Authentication " -"Settings. Copy this exactly 'as is' to the IDP." -msgstr "" -"ID da Entidade - este é o URL do site, exibido na parte superior das " -"configurações de usuário/autenticação. Copie isso exatamente 'como está' " -"para o IDP." - -#: ../authentication/authentication.rst:41 -msgid "" -"Service Provider Metadata - if the provider requires a URL, use " -"``https://example.com/saml/metadata.xml``. To use as a file rather than a " -"URL, browse to that URL and save the content as an XML file." -msgstr "" -"Metadados do Provedor de Serviços - se o provedor exigir uma URL, use " -"``https://exemplo.com.br/saml/metadata.xml``. Para usar como um arquivo em " -"vez de um URL, navegue até esse URL e salve o conteúdo como um arquivo XML." - -#: ../authentication/authentication.rst:43 -msgid "" -"Assertion Consumer Service - Use ``https://example.com/s/saml/login_check``." -msgstr "" -"Assertion Consumer Service - Use " -"``https://exemplo.com.br/s/saml/login_check``." - -#: ../authentication/authentication.rst:45 -msgid "" -"Issuer - this should come from the IDP but is often configurable. If it's a " -"URL, be sure that the scheme - ``http://`` and ``https://`` - aren't part of" -" it." -msgstr "" -"Emissor - deve vir do IDP, mas geralmente é configurável. Se for uma URL, " -"certifique-se de que o esquema - ``http://`` e ``https://`` - não faz parte " -"dela." - -#: ../authentication/authentication.rst:47 -msgid "" -"Verify request signatures or a SSL certificate - If the IDP supports " -"encrypting and validating request signatures from Mautic to the IDP, " -"generate a self signed SSL certificate. Upload the certificate and private " -"key through Mautic's Configuration > User/Authentication Settings under the " -"'Use a custom X.509 certificate and private key to secure communication " -"between Mautic and the IDP' section. Then upload the certificate to the IDP." -msgstr "" -"Verifique as assinaturas de solicitação ou um certificado SSL - Se o IDP " -"oferecer suporte à criptografia e validação de assinaturas de solicitação do" -" Mautic para o IDP, gere um certificado SSL auto assinado. Carregue o " -"certificado e a chave privada através de Configuração do Mautic > " -"Configurações de autenticação/usuário na seção 'Usar um certificado X.509 " -"personalizado e chave privada para proteger a comunicação entre o Mautic e o" -" IDP'. Em seguida, carregue o certificado no IDP." - -#: ../authentication/authentication.rst:49 -msgid "" -"Custom attributes - Mautic requires three custom attributes in the IDP " -"responses for the User Email, first name and last name. Username is also " -"supported but is optional. Configure the attribute names used by the IDP in " -"Mautic's Configuration > User/Authentication Settings under the 'Enter the " -"names of the attributes the configured IDP uses for the following Mautic " -"User fields' section." -msgstr "" -"Atributos personalizados - O Mautic requer três atributos personalizados nas" -" respostas IDP para o e-mail do usuário, nome e sobrenome. O nome de usuário" -" também é suportado, mas é opcional. Configure os nomes dos atributos usados" -" pelo IDP nas Configurações > Configurações de Usuário/Autenticação na seção" -" 'Entre com os nomes dos atributos de usos IDP configurados para seguir " -"campos de usuários Mautic'." - -#: ../authentication/authentication.rst:52 -msgid "Logging in" -msgstr "Fazendo login" - -#: ../authentication/authentication.rst:54 -msgid "" -"Once configured with the IDP and the IDP with Mautic, Mautic redirects all " -"logins to the IDP's login. ``/s/login`` is still available for direct logins" -" but you have to access it directly." -msgstr "" -"Uma vez configurado com o IDP e o IDP com Mautic, o Mautic redireciona todos" -" os logins para o login do IDP. ``/s/login`` ainda está disponível para " -"logins diretos, mas você deve acessá-lo diretamente." - -#: ../authentication/authentication.rst:56 -msgid "" -"Login to the IDP, which then redirects you back to Mautic. If the exchange " -"is successful Mautic creates a User if it doesn't already exist, and logs " -"the User into the system." -msgstr "" -"Faça login no IDP, que o redirecionará de volta ao Mautic. Se a troca for " -"bem-sucedida, o Mautic cria um usuário, caso ainda não exista, e registra o " -"usuário no sistema." - -#: ../authentication/authentication.rst:59 -msgid "Turning off SAML" -msgstr "Desativando o SAML" - -#: ../authentication/authentication.rst:61 -msgid "" -"To turn off SAML, click the Remove link to the right of the Identity " -"provider metadata file label." -msgstr "" -"Para desativar o SAML, clique no link Remover à direita do rótulo do arquivo" -" de metadados do provedor de identidade." - -#: ../authentication/authentication.rstNone -msgid "Screenshot of the authentication settings section" -msgstr "Captura de tela da seção de configurações de autenticação" diff --git a/docs/locale/pt_BR/LC_MESSAGES/categories.po b/docs/locale/pt_BR/LC_MESSAGES/categories.po deleted file mode 100644 index 246fb261..00000000 --- a/docs/locale/pt_BR/LC_MESSAGES/categories.po +++ /dev/null @@ -1,101 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) 2021, Mautic -# This file is distributed under the same license as the Mautic Documentation package. -# FIRST AUTHOR , YEAR. -# -# Translators: -# Ruth Cheesley , 2023 -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: Mautic Documentation 0.1.0\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2023-07-21 17:00+0200\n" -"PO-Revision-Date: 2023-07-21 15:27+0000\n" -"Last-Translator: Ruth Cheesley , 2023\n" -"Language-Team: Portuguese (Brazil) (https://app.transifex.com/mautic/teams/33223/pt_BR/)\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Language: pt_BR\n" -"Plural-Forms: nplurals=3; plural=(n == 0 || n == 1) ? 0 : n != 0 && n % 1000000 == 0 ? 1 : 2;\n" - -#: ../categories/categories-overview.rst:4 -msgid "Categories" -msgstr "Categorias" - -#: ../categories/categories-overview.rst:8 -msgid "" -"Categories are a way to organize Mautic elements. They're available for " -"Assets, Campaigns, Emails, Focus Items, Forms, Pages, Points, Social " -"Monitoring and Stages. There are two ways to use Categories:" -msgstr "" -"As categorias são uma forma de organizar os elementos do Mautic. Estão " -"disponíveis para Ativos, Campanhas, Emails, Itens de Focus, Formulários, " -"Landing Pages, Pontos, Monitoramento Social e Estágios. Há duas maneiras de " -"usar Categorias:" - -#: ../categories/categories-overview.rst:10 -msgid "" -"Create element-specific Categories for example only for Assets, Emails or " -"Forms." -msgstr "" -"Crie categorias específicas de elementos, por exemplo, apenas para Ativos, " -"E-mails ou Formulários." - -#: ../categories/categories-overview.rst:11 -msgid "Create global Categories for all Mautic elements." -msgstr "Crie categorias globais para todos os elementos do Mautic." - -#: ../categories/categories-overview.rst:16 -msgid "Creating and managing Categories" -msgstr "Criando e gerenciando Categorias" - -#: ../categories/categories-overview.rst:20 -msgid "" -"To create new Categories, go to settings menu in the top right corner of " -"Mautic. There choose Categories." -msgstr "" -"Para criar novas Categorias, vá para o menu de configurações no canto " -"superior direito do Mautic. Lá, selecione Categorias." - -#: ../categories/categories-overview.rstNone -msgid "Screenshot of create new Category" -msgstr "Captura de tela da criação de uma nova Categoria" - -#: ../categories/categories-overview.rst:28 -msgid "" -"When creating a new Category you can select type, title, description, alias," -" color and published status. The color will be helpful to quickly find " -"Mautic elements by their appropriate Category when viewing things like the " -"Calendar or other areas within Mautic." -msgstr "" -"Ao criar uma nova Categoria, você pode selecionar tipo, título, descrição, " -"pseudônimo, cor e status publicado (sim ou não). A cor será útil para " -"encontrar rapidamente os elementos do Mautic por sua Categoria apropriada ao" -" visualizar coisas como o Calendário ou outras áreas dentro do Mautic." - -#: ../categories/categories-overview.rst:31 -msgid "Using Categories for Contacts" -msgstr "Usando Categorias para Contatos" - -#: ../categories/categories-overview.rst:35 -msgid "" -"In addition to organizing various Mautic elements Categories can be used to " -"organize Contacts. In Contact details use the Preference menu to open " -"Contact Preference Center." -msgstr "" -"Além de organizar vários elementos do Mautic, as Categorias podem ser usadas" -" para organizar os Contatos. Em Detalhes do contato, use o menu Preferências" -" para abrir o Centro de Preferências do Contato." - -#: ../categories/categories-overview.rstNone -msgid "Screenshot of assigning Category to Contact" -msgstr "Captura de tela da atribuição de Categoria ao Contato" - -#: ../categories/categories-overview.rst:41 -msgid "Contact Categories can be used in Segment and dynamic content filters." -msgstr "" -"As Categorias de Contato podem ser usadas em filtros de conteúdo dinâmico e " -"de Segmento." diff --git a/docs/points/images/campaign-point-action-with-group.png b/docs/points/images/campaign-point-action-with-group.png new file mode 100644 index 00000000..4a8a6837 Binary files /dev/null and b/docs/points/images/campaign-point-action-with-group.png differ diff --git a/docs/points/images/campaign-point-condition-with-group.png b/docs/points/images/campaign-point-condition-with-group.png new file mode 100644 index 00000000..ab76c08d Binary files /dev/null and b/docs/points/images/campaign-point-condition-with-group.png differ diff --git a/docs/points/images/contact-group-points.png b/docs/points/images/contact-group-points.png new file mode 100644 index 00000000..ce3ffc43 Binary files /dev/null and b/docs/points/images/contact-group-points.png differ diff --git a/docs/points/images/form-action-with-point-group.png b/docs/points/images/form-action-with-point-group.png new file mode 100644 index 00000000..ece1bd7a Binary files /dev/null and b/docs/points/images/form-action-with-point-group.png differ diff --git a/docs/points/images/group-report.png b/docs/points/images/group-report.png new file mode 100644 index 00000000..66f28449 Binary files /dev/null and b/docs/points/images/group-report.png differ diff --git a/docs/points/images/new-group.png b/docs/points/images/new-group.png new file mode 100644 index 00000000..26a185fe Binary files /dev/null and b/docs/points/images/new-group.png differ diff --git a/docs/points/images/point-action-with-group.png b/docs/points/images/point-action-with-group.png new file mode 100644 index 00000000..c64c64f4 Binary files /dev/null and b/docs/points/images/point-action-with-group.png differ diff --git a/docs/points/images/point-trigger-with-group.png b/docs/points/images/point-trigger-with-group.png new file mode 100644 index 00000000..5edd0c14 Binary files /dev/null and b/docs/points/images/point-trigger-with-group.png differ diff --git a/docs/points/images/segment-group-filter-element.png b/docs/points/images/segment-group-filter-element.png new file mode 100644 index 00000000..7f59fa05 Binary files /dev/null and b/docs/points/images/segment-group-filter-element.png differ diff --git a/docs/points/images/segment-group-filter.png b/docs/points/images/segment-group-filter.png new file mode 100644 index 00000000..e3f38362 Binary files /dev/null and b/docs/points/images/segment-group-filter.png differ diff --git a/docs/points/point_groups.rst b/docs/points/point_groups.rst new file mode 100644 index 00000000..233606e5 --- /dev/null +++ b/docs/points/point_groups.rst @@ -0,0 +1,93 @@ +.. vale off + +Point Groups +############# + +.. vale on + +Point Groups is a feature that allows users to categorize the score of their Contacts. By setting up Point Groups, users can assign a specific number of Points to each action taken by a Contact, such as opening an Email, visiting a Landing page, or downloading an Asset. + +Managing Point Groups +====================== +To access the currently defined Point Groups in Mautic, navigate to the Points Menu and click the "Manage Groups" link. To create a new Group, simply click the "New" button. + +.. image:: images/new-group.png + :width: 600 + :alt: Screenshot of the create a new Group interface + +Enter a name and a description for the Group and click the "Save & Close" button to create the Group. + +Point Groups usage +=================== + +Point actions +------------- +You can change Contact's Points within a Points Group by using Points Actions. + +.. image:: images/point-action-with-group.png + :width: 600 + :alt: Screenshot of Points action with Group + +Point triggers +-------------- +You can use Point triggers based on Point Groups to automatically trigger specific events within the system. + +.. image:: images/point-trigger-with-group.png + :width: 600 + :alt: Screenshot of Points trigger with Group + +Campaign condition +------------------ +You can use a condition based on Group Contact score in a Campaign. + +.. image:: images/campaign-point-condition-with-group.png + :width: 600 + :alt: Screenshot of Points trigger with Group + +Campaign action +--------------- +You can use a Campaign action to increase or decrease the Group Contact score. + +.. image:: images/campaign-point-action-with-group.png + :width: 600 + :alt: Screenshot of Campaign Point action with Group + +Form action +--------------- +You can use a Form action to increase or decrease the Group Contact score. + +.. image:: images/form-action-with-point-group.png + :width: 600 + :alt: Screenshot of Form Adjust contact's points action with Group + +Segment filters +--------------- +Each Point Group adds a new filter that can be used to configurate the Segment. + +.. image:: images/segment-group-filter.png + :width: 600 + :alt: Screenshot of Segment Group filter + +.. image:: images/segment-group-filter-element.png + :width: 600 + :alt: Screenshot of Segment Group filter element + +Contact details +--------------- +You can display Point Groups in the Contact details. + +.. image:: images/contact-group-points.png + :width: 600 + :alt: Screenshot of Contact Details with Group Points + +Group Report +------------- +You can generate a Report that contains information about Contact Point Groups. + +.. image:: images/group-report.png + :width: 600 + :alt: Screenshot of Group Report + +Webhooks +-------- +Changing the Contact Group Points will not trigger the Contact Points Changed Event Webhook \ No newline at end of file diff --git a/docs/reports/reports.rst b/docs/reports/reports.rst index 8b984061..3e51bfae 100644 --- a/docs/reports/reports.rst +++ b/docs/reports/reports.rst @@ -60,6 +60,7 @@ The **Details** tab on a Report contains the same options across all Reports and * Segment Membership * Do Not Contact * UTM Codes + * Group score 7. :doc:`Companies`