14 Jan from 11:30pm to 12:23am
Mylo changed 34 translations in English, United Kingdom on NotificationAry. Hide changes
  1. <img src='../plugins/system/notificationary/images/logo.png' align='left' style='margin: 0; padding: 0; ' /> <p>NotificationAry sends e-mails to selected users, when a content item(Article, K2 item, DP Calendar events etc.) is added or modified.</p><div class='alert alert-message'>If you feel that something works wrong or illogical, please contact and describe the problem to let it be fixed. The plugin has a great number of conditional statements which are often combined and become very complicated. It's very hard to test all possible combinations after any code update.</div>
    <img src='../plugins/system/notificationary/images/logo.png' align='left' style='margin: 0; padding: 0; ' /> <p>NotificationAry sends e-mails to selected users, when a content item(Article, K2 item, DP Calendar events etc.) is added or modified.</p><div class='alert alert-message'>If you feel that something works wrong or illogical, please contact and describe the problem to let it be fixed. The plugin has a great number of conditional statements which are often combined and become very complicated. It's very hard to test all possible combinations after any code update.</div>

    <img src='../plugins/system/notificationary/images/logo.png' align='left' style='margin:  0; padding: 0; ' /> 
     
    <p>NotificationAry sends e-mails to selected users, when a content item(Article, K2 item, DP Calendar events etc.) is added or modified.</p><div class='alert alert-message'>If you feel that something works wrong or illogical, please contact and describe the problem to let it be fixed. The plugin has a great number of conditional statements which are often combined and become very complicated. It's very hard to test all possible combinations after any code update.</div>

    changed by Arygroup .
    Copy to clipboard
  2. <img src='../plugins/system/notificationary/images/logo.png' align='left' style='margin: 0; padding: 0; ' /> <p>NotificationAry sends e-mails to selected users, when a content item (Article, K2 item, DP Calendar events, etc.) is added or modified.</p><div class='alert alert-message'>If you feel that something doesn't work correctly or is illogical, please contact us and describe the problem so that it can be fixed. The plugin has a great number of conditional statements which are often combined and it can become very complicated. It's very hard to test all possible combinations after any code update.</div>
    <img src='../plugins/system/notificationary/images/logo.png' align='left' style='margin: 0; padding: 0; ' /> <p>NotificationAry sends e-mails to selected users, when a content item (Article, K2 item, DP Calendar events, etc.) is added or modified.</p><div class='alert alert-message'>If you feel that something doesn't work correctly or is illogical, please contact us and describe the problem so that it can be fixed. The plugin has a great number of conditional statements which are often combined and it can become very complicated. It's very hard to test all possible combinations after any code update.</div>

    <img src='../plugins/system/notificationary/images/logo.png' align='left' style='margin:  0; padding: 0; ' /> 
     
    <p>NotificationAry sends e-mails to selected users, when a content item (Article, K2 item, DP Calendar events, etc.) is added or modified.</p><div class='alert alert-message'>If you feel that something doesn't work correctly or is illogical, please contact us and describe the problem so that it can be fixed. The plugin has a great number of conditional statements which are often combined and it can become very complicated. It's very hard to test all possible combinations after any code update.</div>

    changed by Mylo .
    Copy to clipboard
  1. Enter the comma separated content item IDs. If you changed content type, make sure the IDs belong to the content type. E.g. you used content type Articles before and selected some article ids. Next you switched to content type K2. In this case you have to remove previous IDs and enter new ones.<br/><b>Please note!</b>If the '#~#JSELECT#~#' to the right is present, but works incorrectly, then enter IDs manually
    Enter the comma separated content item IDs. If you changed content type, make sure the IDs belong to the content type. E.g. you used content type Articles before and selected some article ids. Next you switched to content type K2. In this case you have to remove previous IDs and enter new ones.<br/><b>Please note!</b>If the '#~#JSELECT#~#' to the right is present, but works incorrectly, then enter IDs manually

    Enter the comma separated content item IDs. If you changed content type, make sure the IDs belong to the content type. E.g. you used content type Articles before and selected some article ids. Next you switched to content type K2. In this case you have to remove previous IDs and enter new ones.<br/><b>Please note!</b>If the '#~#JSELECT#~#' to the right is present, but works incorrectly, then enter IDs manually

    changed by Arygroup .
    Copy to clipboard
  2. Enter a comma-separated list of content item IDs. If you changed content type, make sure the IDs belong to the content type. E.g. you used content type Articles before and selected some article IDs. But then you switched to content type K2. In this case you have to remove previous IDs and enter new ones.<br/><b>Please note!</b>If the '#~#JSELECT#~#' to the right is present, but works incorrectly, then enter IDs manually.
    Enter a comma-separated list of content item IDs. If you changed content type, make sure the IDs belong to the content type. E.g. you used content type Articles before and selected some article IDs. But then you switched to content type K2. In this case you have to remove previous IDs and enter new ones.<br/><b>Please note!</b>If the '#~#JSELECT#~#' to the right is present, but works incorrectly, then enter IDs manually.

    Enter a comma-separated list of content item IDs. If you changed content type, make sure the IDs belong to the content type. E.g. you used content type Articles before and selected some article IDs. But then you switched to content type K2. In this case you have to remove previous IDs and enter new ones.<br/><b>Please note!</b>If the '#~#JSELECT#~#' to the right is present, but works incorrectly, then enter IDs manually.

    changed by Mylo .
    Copy to clipboard
  1. Attach diff info
    Attach diff info

    Attach diff info

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. Attach differing info
    Attach differing info

    Attach differing info

    changed by Mylo .
    Copy to clipboard
  1. For all users` changes?
    For all users` changes?

    For all users` changes?

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. For all users' changes?
    For all users' changes?

    For all users' changes?

    changed by Mylo .
    Copy to clipboard
  1. Include diff info
    Include diff info

    Include diff info

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. Include differing info
    Include differing info

    Include differing info

    changed by Mylo .
    Copy to clipboard
  1. Include fulltext into mail body
    Include fulltext into mail body

    Include fulltext into mail body

    changed by Arygroup .
    Copy to clipboard
  2. Include fulltext in email body
    Include fulltext in email body

    Include fulltext in email body

    changed by Mylo .
    Copy to clipboard
  1. Include introtext into mail body
    Include introtext into mail body

    Include introtext into mail body

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. Include introtext in email body
    Include introtext in email body

    Include introtext in email body

    changed by Mylo .
    Copy to clipboard
  1. If use hardcoded, then some options can be ignored for non-Article content type. I.e. most other extension don't have introtext field. Use of hardcoded mailbody mostly makes sence for Joomla articles. But you can give it a try with other content types
    If use hardcoded, then some options can be ignored for non-Article content type. I.e. most other extension don't have introtext field. Use of hardcoded mailbody mostly makes sence for Joomla articles. But you can give it a try with other content types

    If use hardcoded, then some options can be ignored for non-Article content type. I.e. most other extension don't have introtext field. Use of hardcoded mailbody mostly makes sence for Joomla articles. But you can give it a try with other content types

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. If hardcoded, some options can be ignored for non-Article content type. I.e. most other extension don't have introtext field. Use of hardcoded mailbody mostly makes sense for Joomla articles. But you can give it a try with other content types.
    If hardcoded, some options can be ignored for non-Article content type. I.e. most other extension don't have introtext field. Use of hardcoded mailbody mostly makes sense for Joomla articles. But you can give it a try with other content types.

    If hardcoded, some options can be ignored for non-Article content type. I.e. most other extension don't have introtext field. Use of hardcoded mailbody mostly makes sense for Joomla articles. But you can give it a try with other content types.

    changed by Mylo .
    Copy to clipboard
  1. Notify author only if one's content item is modified by a user allowed in `#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_WHERE_TO_SHOW_NOTIFICATION_SWITCH#~#` You may need to let the content author know about changes in his content performed by Editors, but not to let the author know about changes perfomed by Super Admins.
    Notify author only if one's content item is modified by a user allowed in `#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_WHERE_TO_SHOW_NOTIFICATION_SWITCH#~#` You may need to let the content author know about changes in his content performed by Editors, but not to let the author know about changes perfomed by Super Admins.

    Notify author only if one's content item is modified by a user allowed in `#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_WHERE_TO_SHOW_NOTIFICATION_SWITCH#~#` 
    You may need to let the content author know about changes in his content performed by Editors, but not to let the author know about changes perfomed by Super Admins.

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. Notify author only if their content item is modified by a user allowed in `#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_WHERE_TO_SHOW_NOTIFICATION_SWITCH#~#` You may need to let the content author know about changes in his content performed by Editors, but not to let the author know about changes performed by Super Users.
    Notify author only if their content item is modified by a user allowed in `#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_WHERE_TO_SHOW_NOTIFICATION_SWITCH#~#` You may need to let the content author know about changes in his content performed by Editors, but not to let the author know about changes performed by Super Users.

    Notify author only if their content item is modified by a user allowed in `#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_WHERE_TO_SHOW_NOTIFICATION_SWITCH#~#` 
    You may need to let the content author know about changes in his content performed by Editors, but not to let the author know about changes performed by Super Users.

    changed by Mylo .
    Copy to clipboard
  1. You may set to notify or not on changes performed by selected users. E.g. you don't want to notify other Super Admins when you update something. But you want superadmins to know about Editors' modifications.
    You may set to notify or not on changes performed by selected users. E.g. you don't want to notify other Super Admins when you update something. But you want superadmins to know about Editors' modifications.

    You may set to notify or not on changes performed by selected users. E.g. you don't want to notify other Super Admins when you update something. But you want superadmins to know about Editors' modifications.

    changed by Arygroup .
    Copy to clipboard
  2. You may set to notify or not on changes performed by selected users. E.g. you don't want to notify other Super Users when you update something. But you want Super Users to know about Editors' modifications.
    You may set to notify or not on changes performed by selected users. E.g. you don't want to notify other Super Users when you update something. But you want Super Users to know about Editors' modifications.

    You may set to notify or not on changes performed by selected users. E.g. you don't want to notify other Super Users when you update something. But you want Super Users to know about Editors' modifications.

    changed by Mylo .
    Copy to clipboard
  1. You may select whether to send notifications to users, which have no permission to view the content item. For example, you sell access to content and want to inform all users about a new content item. Or vice versa - you don't want the users who have no permissions to know about a new content item
    You may select whether to send notifications to users, which have no permission to view the content item. For example, you sell access to content and want to inform all users about a new content item. Or vice versa - you don't want the users who have no permissions to know about a new content item

    You may select whether to send notifications to users, which have no permission to view the content item. For example, you sell access to content and want to inform all users about a new content item. Or vice versa - you don't want the users who have no permissions to know about a new content item

    changed by Arygroup .
    Copy to clipboard
  2. You may select whether to send notifications to users that have no permission to view the content item. For example, you sell access to content and want to inform all users about a new content item. Or vice versa - you don't want to notify the users who don't have the permissions to view a new content item.
    You may select whether to send notifications to users that have no permission to view the content item. For example, you sell access to content and want to inform all users about a new content item. Or vice versa - you don't want to notify the users who don't have the permissions to view a new content item.

    You may select whether to send notifications to users that have no permission to view the content item. For example, you sell access to content and want to inform all users about a new content item. Or vice versa - you don't want to notify the users who don't have the permissions to view a new content item.

    changed by Mylo .
    Copy to clipboard
  1. Notify only if can view
    Notify only if can view

    Notify only if can view

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. Notify, if user can view
    Notify, if user can view

    Notify, if user can view

    changed by Mylo .
    Copy to clipboard
  1. When editing an content item a switch wether to notify is shown in the edit form.
    When editing an content item a switch wether to notify is shown in the edit form.

    When editing an content item a switch wether to notify is shown in the edit form.

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. When editing a content item, show a switch in the edit form for notifications.
    When editing a content item, show a switch in the edit form for notifications.

    When editing a content item, show a switch in the edit form for notifications.

    changed by Mylo .
    Copy to clipboard
  1. When editing a content item at Frontend, a switch wether to notify is shown in the edit form.
    When editing a content item at Frontend, a switch wether to notify is shown in the edit form.

    When editing a content item at Frontend, a switch wether to notify is shown in the edit form.

    changed by Arygroup .
    Copy to clipboard
  2. When editing a content item in the Frontend, show a switch in the edit form for notifications.
    When editing a content item in the Frontend, show a switch in the edit form for notifications.

    When editing a content item in the Frontend, show a switch in the edit form for notifications.

    changed by Mylo .
    Copy to clipboard
  1. Disable notification from the content item edit form. For example, you make minor changes and don't want users to be spammed.
    Disable notification from the content item edit form. For example, you make minor changes and don't want users to be spammed.

    Disable notification from the content item edit form. For example, you make minor changes and don't want users to be spammed.

    changed by Arygroup .
    Copy to clipboard
  2. Disable notification from the content item edit form. For example, you make minor changes and prefer not to send a notification.
    Disable notification from the content item edit form. For example, you make minor changes and prefer not to send a notification.

    Disable notification from the content item edit form. For example, you make minor changes and prefer not to send a notification.

    changed by Mylo .
    Copy to clipboard
  1. Only shown to those, who can login backend
    Only shown to those, who can login backend

    Only shown to those, who can login backend

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. Only shown to those who can login to backend
    Only shown to those who can login to backend

    Only shown to those who can login to backend

    changed by Mylo .
    Copy to clipboard
  1. If you want the plugin to fire on a third-party extension you must know at least the proper context and JTable class used by the component. This information is needed to properly fill in </b>#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS#~#</b> textarea found in your notification settings. To get the information enable this option save a content item (e.g. a K2 item) and watch the joomla message area at the page top. After done, disable the option. If you don't see a context message, then the plugin cannot handle that extension. Still there is a little chance it can. If you still need the component to work with NA, please contact the developer to try the little chance.
    If you want the plugin to fire on a third-party extension you must know at least the proper context and JTable class used by the component. This information is needed to properly fill in </b>#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS#~#</b> textarea found in your notification settings. To get the information enable this option save a content item (e.g. a K2 item) and watch the joomla message area at the page top. After done, disable the option. If you don't see a context message, then the plugin cannot handle that extension. Still there is a little chance it can. If you still need the component to work with NA, please contact the developer to try the little chance.

    If you want the plugin to fire on a third-party extension you must know at least the proper context and JTable class used by the component. This information is needed to properly fill in </b>#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS#~#</b> textarea found in your notification settings. To get the information enable this option save a content item (e.g. a K2 item) and watch the joomla message area at the page top. After done, disable the option. If you don't see a context message, then the plugin cannot handle that extension. Still there is a little chance it can. If you still need the component to work with NA, please contact the developer to try the little chance.

    changed by Arygroup .
    Copy to clipboard
  2. If you want the plugin to fire on a third-party extension you must know at least the proper context and JTable class used by the component. This information is needed to properly fill in </b>#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS#~#</b> textarea found in your notification settings. To get the information enable this option save a content item (e.g. a K2 item) and watch the joomla message area at the page top. When finished, disable the option. If you don't see a context message, then the plugin cannot handle that extension. Still there is still a chance it can. If you still need the component to work with NA, please contact the developer to try.
    If you want the plugin to fire on a third-party extension you must know at least the proper context and JTable class used by the component. This information is needed to properly fill in </b>#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS#~#</b> textarea found in your notification settings. To get the information enable this option save a content item (e.g. a K2 item) and watch the joomla message area at the page top. When finished, disable the option. If you don't see a context message, then the plugin cannot handle that extension. Still there is still a chance it can. If you still need the component to work with NA, please contact the developer to try.

    If you want the plugin to fire on a third-party extension you must know at least the proper context and JTable class used by the component. This information is needed to properly fill in </b>#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS#~#</b> textarea found in your notification settings. To get the information enable this option save a content item (e.g. a K2 item) and watch the joomla message area at the page top. When finished, disable the option. If you don't see a context message, then the plugin cannot handle that extension. Still there is still a chance it can. If you still need the component to work with NA, please contact the developer to try.

    changed by Mylo .
    Copy to clipboard
  1. Here you have 2 options. <ol> <li> You can select a registred to joomla component. This can be a core component, like Joomla articles com_content, but can also be a third-party, which fits Joomla compatibility conventions well enough, like DP Calendar. This will definitely work for Joomla core Articles and most of all will work for other extensions from the list. </li> <li>This option may be what you need in several cases: <ul> <li>You selected a joomla registred component under the first option, but it didn't work well. The plugin is not fired at all, gives a table error or sends wrong links to content items</li> <li>You want the plugin to work with a component not listed under the first option, for example K2 or HotSpots</li> </ul> </li> </ol>
    Here you have 2 options. <ol> <li> You can select a registred to joomla component. This can be a core component, like Joomla articles com_content, but can also be a third-party, which fits Joomla compatibility conventions well enough, like DP Calendar. This will definitely work for Joomla core Articles and most of all will work for other extensions from the list. </li> <li>This option may be what you need in several cases: <ul> <li>You selected a joomla registred component under the first option, but it didn't work well. The plugin is not fired at all, gives a table error or sends wrong links to content items</li> <li>You want the plugin to work with a component not listed under the first option, for example K2 or HotSpots</li> </ul> </li> </ol>

     
    Here you have 2 options. 
    <ol> 
    <li> You can select a registred to joomla component. This can be a core component, like Joomla articles com_content, but can also be a third-party, which fits Joomla compatibility conventions well enough, like DP Calendar. This will definitely work for Joomla core Articles and most of all will work for other extensions from the list. </li> 
    <li>This option may be what you need in several cases: 
    <ul> 
    <li>You selected a joomla registred component under the first option, but it didn't work well. The plugin is not fired at all, gives a table error or sends wrong links to content items</li> 
    <li>You want the plugin to work with a component not listed under the first option, for example K2 or HotSpots</li> 
    </ul> 
    </li> 
    </ol> 

    changed by Arygroup .
    Copy to clipboard
  2. Here you have 2 options. <ol> <li> You can select a registered Joomla component. This can be a core component, like Joomla articles com_content, but can also be a third-party, which fits Joomla compatibility conventions well enough, like DP Calendar. This will definitely work for Joomla core Articles and most of all will work for other extensions from the list. </li> <li>This option may be what you need in several cases: <ul> <li>You selected a Joomla registered component under the first option, but it didn't work well. The plugin is not fired at all, gives a table error, or sends wrong links to content items.</li> <li>You want the plugin to work with a component not listed under the first option... for example K2 or HotSpots.</li> </ul> </li> </ol>
    Here you have 2 options. <ol> <li> You can select a registered Joomla component. This can be a core component, like Joomla articles com_content, but can also be a third-party, which fits Joomla compatibility conventions well enough, like DP Calendar. This will definitely work for Joomla core Articles and most of all will work for other extensions from the list. </li> <li>This option may be what you need in several cases: <ul> <li>You selected a Joomla registered component under the first option, but it didn't work well. The plugin is not fired at all, gives a table error, or sends wrong links to content items.</li> <li>You want the plugin to work with a component not listed under the first option... for example K2 or HotSpots.</li> </ul> </li> </ol>

     
    Here you have 2 options. 
    <ol> 
    <li> You can select a registered Joomla component. This can be a core component, like Joomla articles com_content, but can also be a third-party, which fits Joomla compatibility conventions well enough, like DP Calendar. This will definitely work for Joomla core Articles and most of all will work for other extensions from the list. </li> 
    <li>This option may be what you need in several cases: 
    <ul> 
    <li>You selected a Joomla registered component under the first option, but it didn't work well. The plugin is not fired at all, gives a table error, or sends wrong links to content items.</li> 
    <li>You want the plugin to work with a component not listed under the first option... for example K2 or HotSpots.</li> 
    </ul> 
    </li> 
    </ol> 

    changed by Mylo .
    Copy to clipboard
  1. Absoulte
    Absoulte

    Absoulte

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. Absolute
    Absolute

    Absolute

    changed by Mylo .
    Copy to clipboard
  1. Images in HTML mostly have relative path. This is great for Joomla, but when you receive a notfication you cannot view such images. Use absolute path to have images viewable in your emails. This doesn't affect DIFF or any attachments, it only affects inline message images
    Images in HTML mostly have relative path. This is great for Joomla, but when you receive a notfication you cannot view such images. Use absolute path to have images viewable in your emails. This doesn't affect DIFF or any attachments, it only affects inline message images

    Images in HTML mostly have relative path. This is great for Joomla, but when you receive a notfication you cannot view such images. Use absolute path to have images viewable in your emails. This doesn't affect DIFF or any attachments, it only affects inline message images

    changed by Arygroup .
    Copy to clipboard
  2. Images in HTML mostly have a relative path. This is great for Joomla, but when you receive a notification you cannot view such images. Use an absolute path to have images viewable in your emails. This doesn't affect DIFF or any attachments, it only affects inline message images.
    Images in HTML mostly have a relative path. This is great for Joomla, but when you receive a notification you cannot view such images. Use an absolute path to have images viewable in your emails. This doesn't affect DIFF or any attachments, it only affects inline message images.

    Images in HTML mostly have a relative path. This is great for Joomla, but when you receive a notification you cannot view such images. Use an absolute path to have images viewable in your emails. This doesn't affect DIFF or any attachments, it only affects inline message images.

    changed by Mylo .
    Copy to clipboard
  1. Enable ajax when sending notifications. Can be useful, when you have a huge number of notification to be sent and meet timeouts or limit exceeds. Emails are sent slower and little by little in the ajax mode.
    Enable ajax when sending notifications. Can be useful, when you have a huge number of notification to be sent and meet timeouts or limit exceeds. Emails are sent slower and little by little in the ajax mode.

    Enable ajax when sending notifications. Can be useful, when you have a huge number of notification to be sent and meet timeouts or limit exceeds. Emails are sent slower and little by little in the ajax mode.

    changed by Arygroup .
    Copy to clipboard
  2. Enable Ajax when sending notifications. This can be useful when you have a huge number of notifications to be sent and get timeouts or exceed limits. Emails are sent slower and little by little in the Ajax mode.
    Enable Ajax when sending notifications. This can be useful when you have a huge number of notifications to be sent and get timeouts or exceed limits. Emails are sent slower and little by little in the Ajax mode.

    Enable Ajax when sending notifications. This can be useful when you have a huge number of notifications to be sent and get timeouts or exceed limits. Emails are sent slower and little by little in the Ajax mode.

    changed by Mylo .
    Copy to clipboard
  1. Delay in sec before sending start. Give you a chance to cancel.
    Delay in sec before sending start. Give you a chance to cancel.

    Delay in sec before sending start. Give you a chance to cancel.

    changed by Arygroup .
    Copy to clipboard
  2. Delay in seconds before notifications start sending. This will give you a chance to cancel.
    Delay in seconds before notifications start sending. This will give you a chance to cancel.

    Delay in seconds before notifications start sending. This will give you a chance to cancel.

    changed by Mylo .
    Copy to clipboard
  1. If you want to be able to cancel notification sending process, then you can give a user time to cancel before the sending starts.
    If you want to be able to cancel notification sending process, then you can give a user time to cancel before the sending starts.

    If you want to be able to cancel notification sending process, then you can give a user time to cancel before the sending starts.

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. If you want to be able to cancel the notification sending process, then you can give a user time to cancel before the sending starts.
    If you want to be able to cancel the notification sending process, then you can give a user time to cancel before the sending starts.

    If you want to be able to cancel the notification sending process, then you can give a user time to cancel before the sending starts.

    changed by Mylo .
    Copy to clipboard
  1. Who is allowed to cancel notification sending process? You may wish to allow superadmins to cancel the process, but not to Registred users
    Who is allowed to cancel notification sending process? You may wish to allow superadmins to cancel the process, but not to Registred users

    Who is allowed to cancel notification sending process? You may wish to allow superadmins to cancel the process, but not to Registred users

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. Who is allowed to cancel notification sending process? You may wish to allow Super Users to cancel the process, but not Registered users.
    Who is allowed to cancel notification sending process? You may wish to allow Super Users to cancel the process, but not Registered users.

    Who is allowed to cancel notification sending process? You may wish to allow Super Users to cancel the process, but not Registered users.

    changed by Mylo .
    Copy to clipboard
  1. For quick plugin settings access you may wish to add a menu item to backend component menu
    For quick plugin settings access you may wish to add a menu item to backend component menu

    For quick plugin settings access you may wish to add a menu item to backend component menu

    changed by Arygroup via a Batch Operation.
    Copy to clipboard
  2. For quick access to the plugin settings, you may wish to add a menu item to the backend component menu.
    For quick access to the plugin settings, you may wish to add a menu item to the backend component menu.

    For quick access to the plugin settings, you may wish to add a menu item to the backend component menu.

    changed by Mylo .
    Copy to clipboard
  1. <a class='showhidehelperinfo'>Click to show/hide help info how to fill in the template</a><div class='custom_context_help_info hide alert alert-info'> First of all you need to determine if the component you want to send notifications for uses Joomla plugin events. You may try a predefined template to get the idea what information is needed. To get the needed information: <ol> <li>Go to the general tab in the plugin settings and temporary enable internal information output( option at the bottom). Save the plugin. <br /> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR01#~# </li> <li>Save the item you want to send notification on. For example a K2 item or a HotSpot marker.</li> <li>Check the Joomla system message you get. <br/> n#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR02#~# <ul> <li> If you get no extended information there, then the system event <b>onContentAfterSave</b> is not fired by the component when saving an item. You may try to ask the component developers to add joomla event hooks, maybe they would like their extension to be compatible with regular joomla plugins. </li> <li> If you get the extended information, then continue. </li> </ul> </li> <li> Copy the <b>Сontext</b> and the <b>Item table class</b> to the textarea. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR03#~# </li> <li> Temporary disable SEF in Joomla global configuration to get non-SEF links. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR04#~# </li> <li> Frontent view link: View a content item in Frontend and copy-paste the link to the textarea. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR05#~# </li> <li> Frontend edit link: Login as a superadmin to frontend and copy-paste the link you click to edit an item. <br><b>Note!</b> Some components don't have a frontend edit option. In this case enter word <i>false</i> <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR06#~# </li> <li> Enable SEF back. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR07#~# </li> <li> Backend edit link: Go to the list of items, for example,list of K2 items, mouse over an item and copy-paste the link to the textarea. <br /> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR08#~# </li> <li> <i>Category table class</i> and <i>Category context</i> rows are optional and help to determine the content item category path. The plugin tries to determine it automatically. <br/>If you badly need the category path in your notification email and it doesn't work with the empty lines, then try to determine options by saving a category and getting the plugin helper system message.<br/> For example for K2 this approach wouldn't work, as K2 doesn't run onContentAfterSave event when saving a category. But this may work for another extensions.<br/> If you still cannot determine it, then you must have a look into the component code. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR09#~# </li> <li> Now remove parts preceding <b>index.php?...</b>(if not done automatically) in the links and replace the content ID number with the <b>##ID##</b> code. </li> <li> Rows beginning <b>onContent...</b> in most cases should not be touches, as only developers can understand what this means. This lines are used to set alias functions to the core joomla event functions. For example, HotSpots doesn't run joomla core onContentAfterSave at Frontend, but uses an own event which does the same named onAfterHotspotSave. </li> <li> For frontend links you can either remove or leave <b>Itemid=..</b> part. Removing it will force the plugin to try to find a proper Itemid (active menu item) when updating a content item. Leaving it will force the plugin to use the Itemid anyway. </li> <li> Don't forget hide internal information <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR10#~# </li> </ol> </div>
    <a class='showhidehelperinfo'>Click to show/hide help info how to fill in the template</a><div class='custom_context_help_info hide alert alert-info'> First of all you need to determine if the component you want to send notifications for uses Joomla plugin events. You may try a predefined template to get the idea what information is needed. To get the needed information: <ol> <li>Go to the general tab in the plugin settings and temporary enable internal information output( option at the bottom). Save the plugin. <br /> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR01#~# </li> <li>Save the item you want to send notification on. For example a K2 item or a HotSpot marker.</li> <li>Check the Joomla system message you get. <br/> n#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR02#~# <ul> <li> If you get no extended information there, then the system event <b>onContentAfterSave</b> is not fired by the component when saving an item. You may try to ask the component developers to add joomla event hooks, maybe they would like their extension to be compatible with regular joomla plugins. </li> <li> If you get the extended information, then continue. </li> </ul> </li> <li> Copy the <b>Сontext</b> and the <b>Item table class</b> to the textarea. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR03#~# </li> <li> Temporary disable SEF in Joomla global configuration to get non-SEF links. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR04#~# </li> <li> Frontent view link: View a content item in Frontend and copy-paste the link to the textarea. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR05#~# </li> <li> Frontend edit link: Login as a superadmin to frontend and copy-paste the link you click to edit an item. <br><b>Note!</b> Some components don't have a frontend edit option. In this case enter word <i>false</i> <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR06#~# </li> <li> Enable SEF back. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR07#~# </li> <li> Backend edit link: Go to the list of items, for example,list of K2 items, mouse over an item and copy-paste the link to the textarea. <br /> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR08#~# </li> <li> <i>Category table class</i> and <i>Category context</i> rows are optional and help to determine the content item category path. The plugin tries to determine it automatically. <br/>If you badly need the category path in your notification email and it doesn't work with the empty lines, then try to determine options by saving a category and getting the plugin helper system message.<br/> For example for K2 this approach wouldn't work, as K2 doesn't run onContentAfterSave event when saving a category. But this may work for another extensions.<br/> If you still cannot determine it, then you must have a look into the component code. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR09#~# </li> <li> Now remove parts preceding <b>index.php?...</b>(if not done automatically) in the links and replace the content ID number with the <b>##ID##</b> code. </li> <li> Rows beginning <b>onContent...</b> in most cases should not be touches, as only developers can understand what this means. This lines are used to set alias functions to the core joomla event functions. For example, HotSpots doesn't run joomla core onContentAfterSave at Frontend, but uses an own event which does the same named onAfterHotspotSave. </li> <li> For frontend links you can either remove or leave <b>Itemid=..</b> part. Removing it will force the plugin to try to find a proper Itemid (active menu item) when updating a content item. Leaving it will force the plugin to use the Itemid anyway. </li> <li> Don't forget hide internal information <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR10#~# </li> </ol> </div>

    <a class='showhidehelperinfo'>Click to show/hide help info how to fill in the template</a><div class='custom_context_help_info hide alert alert-info'> 
    First of all you need to determine if the component you want to send notifications for uses Joomla plugin events. 
    You may try a predefined template to get the idea what information is needed. To get the needed information: 
    <ol> 
    <li>Go to the general tab in the plugin settings and temporary enable internal information output( option at the bottom). Save the plugin. 
    <br /> 
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR01#~# 
     
     
    </li> 
    <li>Save the item you want to send notification on. For example a K2 item or a HotSpot marker.</li> 
    <li>Check the Joomla system message you get. 
    <br/> 
     
    n#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR02#~# 
     
     
    <ul> 
    <li> 
    If you get no extended information there, then the system event <b>onContentAfterSave</b> is not fired by the component when saving an item. You may try to ask the component developers to add joomla event hooks, maybe they would like their extension to be compatible with regular joomla plugins. 
    </li> 
    <li> 
    If you get the extended information, then continue. 
    </li> 
    </ul> 
    </li> 
    <li> 
    Copy the <b>Сontext</b> and the <b>Item table class</b> to the textarea. 
    <br/> 
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR03#~# 
     
     
     
    </li> 
    <li> 
    Temporary disable SEF in Joomla global configuration to get non-SEF links. 
    <br/> 
     
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR04#~# 
     
     
    </li> 
    <li> 
    Frontent view link: View a content item in Frontend and copy-paste the link to the textarea. 
    <br/> 
     
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR05#~# 
     
     
     
    </li> 
    <li> 
    Frontend edit link: Login as a superadmin to frontend and copy-paste the link you click to edit an item. <br><b>Note!</b> Some components don't have a frontend edit option. In this case enter word <i>false</i> 
    <br/> 
     
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR06#~# 
     
     
     
    </li> 
    <li> 
    Enable SEF back. 
    <br/> 
     
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR07#~# 
     
    </li> 
    <li> 
    Backend edit link: Go to the list of items, for example,list of K2 items,  mouse over an item and copy-paste the link to the textarea. 
    <br /> 
     
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR08#~# 
     
     
     
    </li> 
    <li> 
    <i>Category table class</i> and <i>Category context</i> rows are optional and help to determine the content item category path. The plugin tries to determine it automatically. <br/>If you badly need the category path in your notification email and it doesn't work with the empty lines, then try to determine options by saving a category and getting the plugin helper system message.<br/> 
    For example for K2 this approach  wouldn't work, as K2 doesn't run onContentAfterSave event when saving a category. But this may work for another extensions.<br/> 
    If you still cannot determine it, then you must have a look into the component code. 
    <br/> 
     
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR09#~# 
     
     
     
    </li> 
    <li> 
    Now remove parts preceding <b>index.php?...</b>(if not done automatically) in the links and replace the content ID number with the <b>##ID##</b> code. 
    </li> 
    <li> 
    Rows beginning <b>onContent...</b> in most cases should not be touches, as only developers can understand what this means. This lines are used to set alias functions to the core joomla event functions. For example, HotSpots doesn't run joomla core onContentAfterSave at Frontend, but uses an own event which does the same named onAfterHotspotSave. 
    </li> 
    <li> 
    For frontend links you can either remove or leave <b>Itemid=..</b> part. Removing it will force the plugin to try to find a proper Itemid (active menu item) when  updating a content item. Leaving it will force the plugin to use the Itemid anyway. 
    </li> 
     
    <li> 
    Don't forget hide internal information 
    <br/> 
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR10#~# 
     
    </li> 
    </ol> 
     
    </div> 

    changed by Arygroup .
    Copy to clipboard
  2. <a class='showhidehelperinfo'>Click to show/hide help info on how to fill in the template</a><div class='custom_context_help_info hide alert alert-info'> First, determine if the component you want to send notifications for uses Joomla plugin events. You may try a predefined template to get the idea what information is needed. To get the needed information: <ol> <li>Go to the general tab in the plugin settings and temporarily enable the internal information output at the bottom. Save the plugin. <br /> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR01#~# </li> <li>Save the item you want to send notifications on. For example, a K2 item or a HotSpot marker.</li> <li>Check the Joomla system message you get. <br/> n#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR02#~# <ul> <li> If you get no extended information there, then the system event <b>onContentAfterSave</b> is not fired by the component when saving an item. You may try to ask the component developers to add Joomla event hooks, maybe they would like their extension to be compatible with regular Joomla plugins. </li> <li> If you get the extended information, then continue. </li> </ul> </li> <li> Copy the <b>Сontext</b> and the <b>Item table class</b> to the textarea. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR03#~# </li> <li> Temporary disable SEF in Joomla global configuration to get non-SEF links. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR04#~# </li> <li> Frontent view link: View a content item in Frontend and copy-paste the link to the textarea. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR05#~# </li> <li> Frontend edit link: Login as a superadmin to frontend and copy-paste the link you click to edit an item. <br><b>Note!</b> Some components don't have a frontend edit option. In this case enter the word <i>false</i>. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR06#~# </li> <li> Enable SEF back. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR07#~# </li> <li> Backend edit link: Go to the list of items, mouse over an item, and copy-paste the link to the textarea. <br /> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR08#~# </li> <li> <i>Category table class</i> and <i>Category context</i> rows are optional and help to determine the content item category path. The plugin tries to determine it automatically. <br/>If you badly need the category path in your notification email and it doesn't work with the empty lines, then try to determine options by saving a category and getting the plugin helper system message.<br/> For example, this approach wouldn't work for K2 as K2 doesn't run onContentAfterSave event when saving a category. But this may work for other extensions.<br/> If you still cannot determine it, then you must have a look into the component code. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR09#~# </li> <li> Now remove parts preceding <b>index.php?...</b>(if not done automatically) in the links and replace the content ID number with the <b>##ID##</b> code. </li> <li> Rows beginning <b>onContent...</b> in most cases should not be touched, as only developers can understand what this means. These lines are used to set alias functions to the core Joomla event functions. For example, HotSpots doesn't run Joomla core onContentAfterSave at Frontend, but uses its own event which does the same - named onAfterHotspotSave. </li> <li> For frontend links you can either remove or leave <b>Itemid=..</b> part. Removing it will force the plugin to try to find a proper Itemid (active menu item) when updating a content item. Leaving it will force the plugin to use the Itemid anyway. </li> <li> Don't forget to hide internal information <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR10#~# </li> </ol> </div>
    <a class='showhidehelperinfo'>Click to show/hide help info on how to fill in the template</a><div class='custom_context_help_info hide alert alert-info'> First, determine if the component you want to send notifications for uses Joomla plugin events. You may try a predefined template to get the idea what information is needed. To get the needed information: <ol> <li>Go to the general tab in the plugin settings and temporarily enable the internal information output at the bottom. Save the plugin. <br /> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR01#~# </li> <li>Save the item you want to send notifications on. For example, a K2 item or a HotSpot marker.</li> <li>Check the Joomla system message you get. <br/> n#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR02#~# <ul> <li> If you get no extended information there, then the system event <b>onContentAfterSave</b> is not fired by the component when saving an item. You may try to ask the component developers to add Joomla event hooks, maybe they would like their extension to be compatible with regular Joomla plugins. </li> <li> If you get the extended information, then continue. </li> </ul> </li> <li> Copy the <b>Сontext</b> and the <b>Item table class</b> to the textarea. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR03#~# </li> <li> Temporary disable SEF in Joomla global configuration to get non-SEF links. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR04#~# </li> <li> Frontent view link: View a content item in Frontend and copy-paste the link to the textarea. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR05#~# </li> <li> Frontend edit link: Login as a superadmin to frontend and copy-paste the link you click to edit an item. <br><b>Note!</b> Some components don't have a frontend edit option. In this case enter the word <i>false</i>. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR06#~# </li> <li> Enable SEF back. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR07#~# </li> <li> Backend edit link: Go to the list of items, mouse over an item, and copy-paste the link to the textarea. <br /> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR08#~# </li> <li> <i>Category table class</i> and <i>Category context</i> rows are optional and help to determine the content item category path. The plugin tries to determine it automatically. <br/>If you badly need the category path in your notification email and it doesn't work with the empty lines, then try to determine options by saving a category and getting the plugin helper system message.<br/> For example, this approach wouldn't work for K2 as K2 doesn't run onContentAfterSave event when saving a category. But this may work for other extensions.<br/> If you still cannot determine it, then you must have a look into the component code. <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR09#~# </li> <li> Now remove parts preceding <b>index.php?...</b>(if not done automatically) in the links and replace the content ID number with the <b>##ID##</b> code. </li> <li> Rows beginning <b>onContent...</b> in most cases should not be touched, as only developers can understand what this means. These lines are used to set alias functions to the core Joomla event functions. For example, HotSpots doesn't run Joomla core onContentAfterSave at Frontend, but uses its own event which does the same - named onAfterHotspotSave. </li> <li> For frontend links you can either remove or leave <b>Itemid=..</b> part. Removing it will force the plugin to try to find a proper Itemid (active menu item) when updating a content item. Leaving it will force the plugin to use the Itemid anyway. </li> <li> Don't forget to hide internal information <br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR10#~# </li> </ol> </div>

    <a class='showhidehelperinfo'>Click to show/hide help info on how to fill in the template</a><div class='custom_context_help_info hide alert alert-info'> 
    First, determine if the component you want to send notifications for uses Joomla plugin events. 
    You may try a predefined template to get the idea what information is needed. To get the needed information: 
    <ol> 
    <li>Go to the general tab in the plugin settings and temporarily enable the internal information output at the bottom. Save the plugin. 
    <br /> 
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR01#~# 
     
     
    </li> 
    <li>Save the item you want to send notifications on. For example, a K2 item or a HotSpot marker.</li> 
    <li>Check the Joomla system message you get. 
    <br/> 
     
    n#~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR02#~# 
     
     
    <ul> 
    <li> 
    If you get no extended information there, then the system event <b>onContentAfterSave</b> is not fired by the component when saving an item. You may try to ask the component developers to add Joomla event hooks, maybe they would like their extension to be compatible with regular Joomla plugins. 
    </li> 
    <li> 
    If you get the extended information, then continue. 
    </li> 
    </ul> 
    </li> 
    <li> 
    Copy the <b>Сontext</b> and the <b>Item table class</b> to the textarea. 
    <br/> 
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR03#~# 
     
     
     
    </li> 
    <li> 
    Temporary disable SEF in Joomla global configuration to get non-SEF links. 
    <br/> 
     
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR04#~# 
     
     
    </li> 
    <li> 
    Frontent view link: View a content item in Frontend and copy-paste the link to the textarea. 
    <br/> 
     
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR05#~# 
     
     
     
    </li> 
    <li> 
    Frontend edit link: Login as a superadmin to frontend and copy-paste the link you click to edit an item. <br><b>Note!</b> Some components don't have a frontend edit option. In this case enter the word <i>false</i>. 
    <br/> 
     
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR06#~# 
     
     
     
    </li> 
    <li> 
    Enable SEF back. 
    <br/> 
     
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR07#~# 
     
    </li> 
    <li> 
    Backend edit link: Go to the list of items, mouse over an item, and copy-paste the link to the textarea. 
    <br /> 
     
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR08#~# 
     
     
     
    </li> 
    <li> 
    <i>Category table class</i> and <i>Category context</i> rows are optional and help to determine the content item category path. The plugin tries to determine it automatically. <br/>If you badly need the category path in your notification email and it doesn't work with the empty lines, then try to determine options by saving a category and getting the plugin helper system message.<br/> 
    For example, this approach wouldn't work for K2 as K2 doesn't run onContentAfterSave event when saving a category. But this may work for other extensions.<br/> 
    If you still cannot determine it, then you must have a look into the component code. 
    <br/> 
     
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR09#~# 
     
     
     
    </li> 
    <li> 
    Now remove parts preceding <b>index.php?...</b>(if not done automatically) in the links and replace the content ID number with the <b>##ID##</b> code. 
    </li> 
    <li> 
    Rows beginning <b>onContent...</b> in most cases should not be touched, as only developers can understand what this means. These lines are used to set alias functions to the core Joomla event functions. For example, HotSpots doesn't run Joomla core onContentAfterSave at Frontend, but uses its own event which does the same - named onAfterHotspotSave. 
    </li> 
    <li> 
    For frontend links you can either remove or leave <b>Itemid=..</b> part. Removing it will force the plugin to try to find a proper Itemid (active menu item) when updating a content item. Leaving it will force the plugin to use the Itemid anyway. 
    </li> 
     
    <li> 
    Don't forget to hide internal information 
    <br/> 
     
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANUAL_CONTEXTS_DESC_SCR10#~# 
     
    </li> 
    </ol> 
     
    </div> 

    changed by Mylo .
    Copy to clipboard
  1. This concerns only Frontend. At some templates notification switch make break the things. If you meet such a problem, try Simple option.
    This concerns only Frontend. At some templates notification switch make break the things. If you meet such a problem, try Simple option.

    This concerns only Frontend. At some templates notification switch make break the things. If you meet such a problem, try Simple option.

    changed by Arygroup .
    Copy to clipboard
  2. This concerns only Frontend. In some templates, the notification switch will break things. If you encounter such a problem, try the Simple option.
    This concerns only Frontend. In some templates, the notification switch will break things. If you encounter such a problem, try the Simple option.

    This concerns only Frontend. In some templates, the notification switch will break things. If you encounter such a problem, try the Simple option.

    changed by Mylo .
    Copy to clipboard
  1. You may wish to notify only when an item is published. Or only when something is changed in a published item. And so on.<br/> If you select only an action, then only status change will trigger a notification.<br/> For example, it you select <b>#~#JSTATUS#~#:#~#JPUBLISHED#~#</b>, then a notification is sent on changes in a published item or on publishing the item, as the final status is <b>#~#JPUBLISHED#~#</b>. <br/> If you select <b>#~#PLG_SYSTEM_NOTIFICATIONARY_ACTION#~#:#~#JTOOLBAR_PUBLISH#~#</b>, then a notification will be sent only when you change the content item status to <b>#~#JPUBLISHED#~#</b>, but not when editing an already published item.<br/> <br/> Be aware of possible meaningless conjunction of options here.<br/> <br/><b>NOTE!</b> For some third-party extensions status change cannot be determined.
    You may wish to notify only when an item is published. Or only when something is changed in a published item. And so on.<br/> If you select only an action, then only status change will trigger a notification.<br/> For example, it you select <b>#~#JSTATUS#~#:#~#JPUBLISHED#~#</b>, then a notification is sent on changes in a published item or on publishing the item, as the final status is <b>#~#JPUBLISHED#~#</b>. <br/> If you select <b>#~#PLG_SYSTEM_NOTIFICATIONARY_ACTION#~#:#~#JTOOLBAR_PUBLISH#~#</b>, then a notification will be sent only when you change the content item status to <b>#~#JPUBLISHED#~#</b>, but not when editing an already published item.<br/> <br/> Be aware of possible meaningless conjunction of options here.<br/> <br/><b>NOTE!</b> For some third-party extensions status change cannot be determined.

    You may wish to notify only when an item is published. 
    Or only when something is changed in a published item. And so on.<br/> 
    If you select only an action, then only status change will trigger a notification.<br/> 
    For example, it you select <b>#~#JSTATUS#~#:#~#JPUBLISHED#~#</b>, then a notification is sent on changes in a published item or on publishing the item, 
    as the final status is <b>#~#JPUBLISHED#~#</b>. <br/> 
    If you select <b>#~#PLG_SYSTEM_NOTIFICATIONARY_ACTION#~#:#~#JTOOLBAR_PUBLISH#~#</b>, then a notification will be sent only 
    when you change the content item status to <b>#~#JPUBLISHED#~#</b>, but not when editing an already published item.<br/> 
    <br/> 
    Be aware of possible meaningless conjunction of options here.<br/> 
    <br/><b>NOTE!</b> For some third-party extensions status change cannot be determined.

    changed by Arygroup .
    Copy to clipboard
  2. You may wish to notify only when an item is published or only when something is changed in a published item.<br/> If you select an action, then only the status change will trigger a notification.<br/> For example, it you select <b>#~#JSTATUS#~#:#~#JPUBLISHED#~#</b>, then a notification is sent on changes in a published item or upon publishing the item since the final status is <b>#~#JPUBLISHED#~#</b>. <br/> If you select <b>#~#PLG_SYSTEM_NOTIFICATIONARY_ACTION#~#:#~#JTOOLBAR_PUBLISH#~#</b>, then a notification will be sent only when you change the content item status to <b>#~#JPUBLISHED#~#</b>, but not when editing an already published item.<br/> <br/> Be aware of the possible meaningless conjunction of options here.<br/> <br/><b>NOTE!</b> For some third-party extensions status change cannot be determined.
    You may wish to notify only when an item is published or only when something is changed in a published item.<br/> If you select an action, then only the status change will trigger a notification.<br/> For example, it you select <b>#~#JSTATUS#~#:#~#JPUBLISHED#~#</b>, then a notification is sent on changes in a published item or upon publishing the item since the final status is <b>#~#JPUBLISHED#~#</b>. <br/> If you select <b>#~#PLG_SYSTEM_NOTIFICATIONARY_ACTION#~#:#~#JTOOLBAR_PUBLISH#~#</b>, then a notification will be sent only when you change the content item status to <b>#~#JPUBLISHED#~#</b>, but not when editing an already published item.<br/> <br/> Be aware of the possible meaningless conjunction of options here.<br/> <br/><b>NOTE!</b> For some third-party extensions status change cannot be determined.

    You may wish to notify only when an item is published or only when something is changed in a published item.<br/> 
    If you select an action, then only the status change will trigger a notification.<br/> 
    For example, it you select <b>#~#JSTATUS#~#:#~#JPUBLISHED#~#</b>, then a notification is sent on changes in a published item or upon publishing the item since the final status is <b>#~#JPUBLISHED#~#</b>. <br/> 
    If you select <b>#~#PLG_SYSTEM_NOTIFICATIONARY_ACTION#~#:#~#JTOOLBAR_PUBLISH#~#</b>, then a notification will be sent only 
    when you change the content item status to <b>#~#JPUBLISHED#~#</b>, but not when editing an already published item.<br/> 
    <br/> 
    Be aware of the possible meaningless conjunction of options here.<br/> 
    <br/><b>NOTE!</b> For some third-party extensions status change cannot be determined.

    changed by Mylo .
    Copy to clipboard
  1. <a class='showhidehelperinfo'><b>You may use PHP code in the custom mail subject and body, but be careful!</b> [show/hide]</a> <div class='custom_context_help_info hide '> <p>It can be needed if you use a custom placeholder and want it to be prepared using PHP. E.g. convert a timestamp to a human readable date format.</p> <p>For example, for JEvents you may wish to use a start event date, which placeholder is <b>##Content#data##DTSTART##</b>, but the value is stored in linux era format like <b>1469773800</b>. So to output it propely you cause smth. like <code>&lt;?php echo JHTML::_('date', "##Content#data##DTSTART##", 'Y-m-d H:i:s'); ?&gt;</code>.</p> <p>The security problem can come, when you run PHP code over a user input custom text like titles or descriptions. A hacker may add an article with content like <code>&lt;p&gt;Some HTML code&lt;/p&gt; &lt;?php ...run hacker code here.... ?&gt;</code> </p> <p>Normally Joomla is protected from such code injections at several levels, but it's better to be careful. This is the place, when under some conjunction of circumstances, if using wrongly, you can eval a user input code.</p> <p>So use PHP code here with care and over safe data, which cannot be directy changed by a user or contain hacker code. For example date format cannot contain anything except date. But text content like title, description, potentially contains everything.</p> </div>
    <a class='showhidehelperinfo'><b>You may use PHP code in the custom mail subject and body, but be careful!</b> [show/hide]</a> <div class='custom_context_help_info hide '> <p>It can be needed if you use a custom placeholder and want it to be prepared using PHP. E.g. convert a timestamp to a human readable date format.</p> <p>For example, for JEvents you may wish to use a start event date, which placeholder is <b>##Content#data##DTSTART##</b>, but the value is stored in linux era format like <b>1469773800</b>. So to output it propely you cause smth. like <code>&lt;?php echo JHTML::_('date', "##Content#data##DTSTART##", 'Y-m-d H:i:s'); ?&gt;</code>.</p> <p>The security problem can come, when you run PHP code over a user input custom text like titles or descriptions. A hacker may add an article with content like <code>&lt;p&gt;Some HTML code&lt;/p&gt; &lt;?php ...run hacker code here.... ?&gt;</code> </p> <p>Normally Joomla is protected from such code injections at several levels, but it's better to be careful. This is the place, when under some conjunction of circumstances, if using wrongly, you can eval a user input code.</p> <p>So use PHP code here with care and over safe data, which cannot be directy changed by a user or contain hacker code. For example date format cannot contain anything except date. But text content like title, description, potentially contains everything.</p> </div>

    <a class='showhidehelperinfo'><b>You may use PHP code in the custom mail subject and body, but be careful!</b> [show/hide]</a> 
    <div class='custom_context_help_info hide '> 
    <p>It can be needed if you use a custom placeholder and want it to be prepared using PHP. E.g. convert a timestamp to a human readable date format.</p> 
    <p>For example, for JEvents you may wish to use a start event date, which placeholder is <b>##Content#data##DTSTART##</b>, but the value is stored in linux era format like <b>1469773800</b>. So to output it propely you cause smth. like <code>&lt;?php echo JHTML::_('date',  "##Content#data##DTSTART##", 'Y-m-d H:i:s'); ?&gt;</code>.</p> 
    <p>The security problem can come, when you run PHP code over a user input custom text like titles or descriptions. A hacker may add an article with content like 
    <code>&lt;p&gt;Some HTML code&lt;/p&gt; &lt;?php ...run hacker code here.... ?&gt;</code> 
    </p> 
    <p>Normally Joomla is protected from such code injections at several levels, but it's better to be careful. This is the place, when under some conjunction of circumstances, if using wrongly, you can eval a user input code.</p> 
    <p>So use PHP code here with care and over safe data, which cannot be directy changed by a user or contain hacker code. For example date format cannot contain anything except date. But text content like title, description, potentially contains everything.</p> 
    </div> 

    changed by Arygroup .
    Copy to clipboard
  2. <a class='showhidehelperinfo'><b>You may use PHP code in the custom mail subject and body, but be careful!</b> [show/hide]</a> <div class='custom_context_help_info hide '> <p>It can be needed if you use a custom placeholder and want it to be prepared using PHP. E.g. convert a timestamp to a human readable date format.</p> <p>For example, for JEvents you may wish to use a start event date, whose placeholder is <b>##Content#data##DTSTART##</b>, but the value is stored in Linux format like <b>1469773800</b>. So to output it properly you code something like <code>&lt;?php echo JHTML::_('date', "##Content#data##DTSTART##", 'Y-m-d H:i:s'); ?&gt;</code>.</p> <p>The security problem can come, when you run PHP code over a user input custom text like titles or descriptions. A hacker may add an article with content like <code>&lt;p&gt;Some HTML code&lt;/p&gt; &lt;?php ...run hacker code here.... ?&gt;</code> </p> <p>Normally Joomla is protected from such code injections at several levels, but it's better to be careful. This is the place, when under some conjunction of circumstances, if used wrongly, you can eval user input code.</p> <p>So use PHP code here with care and over safe data, which cannot be directy changed by a user or contain hacker code. For example date format cannot contain anything except date. But text content, like title or description, potentially contains everything.</p> </div>
    <a class='showhidehelperinfo'><b>You may use PHP code in the custom mail subject and body, but be careful!</b> [show/hide]</a> <div class='custom_context_help_info hide '> <p>It can be needed if you use a custom placeholder and want it to be prepared using PHP. E.g. convert a timestamp to a human readable date format.</p> <p>For example, for JEvents you may wish to use a start event date, whose placeholder is <b>##Content#data##DTSTART##</b>, but the value is stored in Linux format like <b>1469773800</b>. So to output it properly you code something like <code>&lt;?php echo JHTML::_('date', "##Content#data##DTSTART##", 'Y-m-d H:i:s'); ?&gt;</code>.</p> <p>The security problem can come, when you run PHP code over a user input custom text like titles or descriptions. A hacker may add an article with content like <code>&lt;p&gt;Some HTML code&lt;/p&gt; &lt;?php ...run hacker code here.... ?&gt;</code> </p> <p>Normally Joomla is protected from such code injections at several levels, but it's better to be careful. This is the place, when under some conjunction of circumstances, if used wrongly, you can eval user input code.</p> <p>So use PHP code here with care and over safe data, which cannot be directy changed by a user or contain hacker code. For example date format cannot contain anything except date. But text content, like title or description, potentially contains everything.</p> </div>

    <a class='showhidehelperinfo'><b>You may use PHP code in the custom mail subject and body, but be careful!</b> [show/hide]</a> 
    <div class='custom_context_help_info hide '> 
    <p>It can be needed if you use a custom placeholder and want it to be prepared using PHP. E.g. convert a timestamp to a human readable date format.</p> 
    <p>For example, for JEvents you may wish to use a start event date, whose placeholder is <b>##Content#data##DTSTART##</b>, but the value is stored in Linux format like <b>1469773800</b>. So to output it properly you code something like <code>&lt;?php echo JHTML::_('date',  "##Content#data##DTSTART##", 'Y-m-d H:i:s'); ?&gt;</code>.</p> 
    <p>The security problem can come, when you run PHP code over a user input custom text like titles or descriptions. A hacker may add an article with content like 
    <code>&lt;p&gt;Some HTML code&lt;/p&gt; &lt;?php ...run hacker code here.... ?&gt;</code> 
    </p> 
    <p>Normally Joomla is protected from such code injections at several levels, but it's better to be careful. This is the place, when under some conjunction of circumstances, if used wrongly, you can eval user input code.</p> 
    <p>So use PHP code here with care and over safe data, which cannot be directy changed by a user or contain hacker code. For example date format cannot contain anything except date. But text content, like title or description, potentially contains everything.</p> 
    </div>

    changed by Mylo .
    Copy to clipboard
  1. Show a JavaScript confirmation window on saving a content item. <br/> Makes sense only when the switch is shown for tha item. <br/> Enable this option to have a last chance before sending mass mail.
    Show a JavaScript confirmation window on saving a content item. <br/> Makes sense only when the switch is shown for tha item. <br/> Enable this option to have a last chance before sending mass mail.

    Show a JavaScript confirmation window on saving a content item. <br/> Makes sense only when the switch is shown for tha item. <br/> Enable this option to have a last chance before sending mass mail.

    changed by Arygroup .
    Copy to clipboard
  2. Show a JavaScript confirmation window on saving a content item. <br/> It makes sense only when the switch is shown for the item. <br/> Enable this option to have one last chance before sending mass mail.
    Show a JavaScript confirmation window on saving a content item. <br/> It makes sense only when the switch is shown for the item. <br/> Enable this option to have one last chance before sending mass mail.

    Show a JavaScript confirmation window on saving a content item. <br/> It makes sense only when the switch is shown for the item. <br/> Enable this option to have one last chance before sending mass mail.

    changed by Mylo .
    Copy to clipboard
  1. Select whether to allow users to subscribe/unsubscribe to/from the whole rule or certain categories. In the settings above you can select which categories to send notification on. But if you want to allow users to subscribe/unsubscribe to/from the whole rule or some categories, you must enable this option. <br/> E.g. you setup your NotificationAry to send notification on new News, Jobs and Offers, but want your users to allow to select which categories to stay subscribed to.<br />
    Select whether to allow users to subscribe/unsubscribe to/from the whole rule or certain categories. In the settings above you can select which categories to send notification on. But if you want to allow users to subscribe/unsubscribe to/from the whole rule or some categories, you must enable this option. <br/> E.g. you setup your NotificationAry to send notification on new News, Jobs and Offers, but want your users to allow to select which categories to stay subscribed to.<br />

    Select whether to allow users to subscribe/unsubscribe to/from the whole rule or certain categories. In the settings above you can select which categories to send notification on. But if you want to allow users to subscribe/unsubscribe to/from the whole rule or some categories, you must enable this option. <br/> E.g. you setup your NotificationAry to send notification on new News, Jobs and Offers, but want your users to allow to select which categories to stay subscribed to.<br />

    changed by Arygroup .
    Copy to clipboard
  2. Select whether to allow users to subscribe/unsubscribe to/from the whole rule or certain categories. In the settings above you can select which categories to send notifications on. But if you want to allow users to subscribe/unsubscribe to/from the whole rule or some categories, you must enable this option. <br/> E.g. you setup your NotificationAry to send notification on new Articles, Jobs and Offers, but want to allow your users the option to select which categories to stay subscribed to.<br />
    Select whether to allow users to subscribe/unsubscribe to/from the whole rule or certain categories. In the settings above you can select which categories to send notifications on. But if you want to allow users to subscribe/unsubscribe to/from the whole rule or some categories, you must enable this option. <br/> E.g. you setup your NotificationAry to send notification on new Articles, Jobs and Offers, but want to allow your users the option to select which categories to stay subscribed to.<br />

    Select whether to allow users to subscribe/unsubscribe to/from the whole rule or certain categories. In the settings above you can select which categories to send notifications on. But if you want to allow users to subscribe/unsubscribe to/from the whole rule or some categories, you must enable this option. <br/> E.g. you setup your NotificationAry to send notification on new Articles, Jobs and Offers, but want to allow your users the option to select which categories to stay subscribed to.<br />

    changed by Mylo .
    Copy to clipboard
  1. If a user belongs to a user group subscribed to the categories selected above, set if the one is subscribed or unsubscribed to all the categories by default. E.g. you setup your NotificationAry to send notification on new News, Jobs and Offers for all Registered users. This option determines if a newly added user should be subscribed to all the categories or not (to later subscribe on the user's own)
    If a user belongs to a user group subscribed to the categories selected above, set if the one is subscribed or unsubscribed to all the categories by default. E.g. you setup your NotificationAry to send notification on new News, Jobs and Offers for all Registered users. This option determines if a newly added user should be subscribed to all the categories or not (to later subscribe on the user's own)

    If a user belongs to a user group subscribed to the categories selected above, set if the one is subscribed or unsubscribed to all the categories by default. E.g. you setup your NotificationAry to send notification on new News, Jobs and Offers for all Registered users. This option determines if a newly added user should be subscribed to all the categories or not (to later subscribe on the user's own)

    changed by Arygroup .
    Copy to clipboard
  2. If a user belongs to a user group subscribed to the categories selected above, set if the one is subscribed or unsubscribed to all the categories by default. E.g. you setup your NotificationAry to send notification on new Articles for all Registered users. This option determines if a newly added user should be subscribed to all the categories or not (User can subscribe later on their own)
    If a user belongs to a user group subscribed to the categories selected above, set if the one is subscribed or unsubscribed to all the categories by default. E.g. you setup your NotificationAry to send notification on new Articles for all Registered users. This option determines if a newly added user should be subscribed to all the categories or not (User can subscribe later on their own)

    If a user belongs to a user group subscribed to the categories selected above, set if the one is subscribed or unsubscribed to all the categories by default. E.g. you setup your NotificationAry to send notification on new Articles for all Registered users. This option determines if a newly added user should be subscribed to all the categories or not (User can subscribe later on their own)

    changed by Mylo .
    Copy to clipboard
  1. Wrong notificationary rule uniqid
    Wrong notificationary rule uniqid

    Wrong notificationary rule uniqid

    changed by Arygroup .
    Copy to clipboard
  2. Wrong NotificationAry rule uniqid
    Wrong NotificationAry rule uniqid

    Wrong NotificationAry rule uniqid

    changed by Mylo .
    Copy to clipboard
  1. <a class='showhidehelperinfo'>Click to show/hide subscription management help</a><div class='custom_context_help_info hide'> <div class='span9'>To allow users to use the subscribe feature you must create a page with the subscription form and include the link to it into the email body. <br/> This can be an article or a page with a custom HTML module (don't forget to <a href='http://static.xscreenshot.com/2017/02/07/17/screen_bdf9777330bcb3dc1359da05e0f52272' class='modal' rel='{size: {x: 800, y: 500}, handler:"_QQ_"iframe"_QQ_"}' >enable Prepare content option</a>). Just insert a plugin code like <code>{na subscribe <u>UniqID</u>}</code> where <b>UniqID</b> is the value found in the right corner above. E.g. <code>{na subscribe 5889f0565a762}</code><br/> One more important thing. Since only logged in users can manage subscription, you may wish to limit the page access to the Registred users to demand login. The plugin code for guestes is removed from the output.<br/> So <ul> <li>Create a page and place the plugin code.</li> <li>Set page access level to Registred or whatever you need (optional)</li> <li>Insert the link to the page into the email body template.</li> </ul> <br> To override the subscription form output copy the layout files from <b>plugins/system/notificationary/layouts/*</b> to <b>/templates/YOURTEMPLATE/html/layouts/*</b> preserving folder structure and edit them. </div><div class='span3'> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR01#~#<br/><br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR02#~# #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR03#~# #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR04#~# </div> </div>
    <a class='showhidehelperinfo'>Click to show/hide subscription management help</a><div class='custom_context_help_info hide'> <div class='span9'>To allow users to use the subscribe feature you must create a page with the subscription form and include the link to it into the email body. <br/> This can be an article or a page with a custom HTML module (don't forget to <a href='http://static.xscreenshot.com/2017/02/07/17/screen_bdf9777330bcb3dc1359da05e0f52272' class='modal' rel='{size: {x: 800, y: 500}, handler:"_QQ_"iframe"_QQ_"}' >enable Prepare content option</a>). Just insert a plugin code like <code>{na subscribe <u>UniqID</u>}</code> where <b>UniqID</b> is the value found in the right corner above. E.g. <code>{na subscribe 5889f0565a762}</code><br/> One more important thing. Since only logged in users can manage subscription, you may wish to limit the page access to the Registred users to demand login. The plugin code for guestes is removed from the output.<br/> So <ul> <li>Create a page and place the plugin code.</li> <li>Set page access level to Registred or whatever you need (optional)</li> <li>Insert the link to the page into the email body template.</li> </ul> <br> To override the subscription form output copy the layout files from <b>plugins/system/notificationary/layouts/*</b> to <b>/templates/YOURTEMPLATE/html/layouts/*</b> preserving folder structure and edit them. </div><div class='span3'> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR01#~#<br/><br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR02#~# #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR03#~# #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR04#~# </div> </div>

     
    <a class='showhidehelperinfo'>Click to show/hide subscription management help</a><div class='custom_context_help_info hide'> 
     
    <div class='span9'>To allow users to use the subscribe feature you must create a page with the subscription form and include the link to it into the email body. <br/> This can be an article or a page with a custom HTML module (don't forget to <a href='http://static.xscreenshot.com/2017/02/07/17/screen_bdf9777330bcb3dc1359da05e0f52272' class='modal' rel='{size: {x: 800, y: 500}, handler:"_QQ_"iframe"_QQ_"}' >enable Prepare content option</a>). Just insert a plugin code like <code>{na subscribe <u>UniqID</u>}</code> where <b>UniqID</b> is the value found in the right corner above. E.g. <code>{na subscribe 5889f0565a762}</code><br/> 
    One more important thing. Since only logged in users can manage subscription, you may wish to limit the page access to the Registred users to demand login. The plugin code for guestes is removed from the output.<br/> 
    So <ul> 
    <li>Create a page and place the plugin code.</li> 
    <li>Set page access level to Registred or whatever you need (optional)</li> 
    <li>Insert the link to the page into the email body template.</li> 
    </ul> 
    <br> 
    To override the subscription form output copy the layout files from <b>plugins/system/notificationary/layouts/*</b> to <b>/templates/YOURTEMPLATE/html/layouts/*</b> preserving folder structure and edit them. 
    </div><div class='span3'> 
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR01#~#<br/><br/> 
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR02#~# 
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR03#~# 
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR04#~# 
     
    </div> 
    </div> 
     

    changed by Arygroup .
    Copy to clipboard
  2. <a class='showhidehelperinfo'>Click to show/hide subscription management help</a><div class='custom_context_help_info hide'> <div class='span9'>To allow users to use the subscribe feature you must create a page with the subscription form and include the link to it into the email body. <br/> This can be an article or a page with a custom HTML module (don't forget to <a href='http://static.xscreenshot.com/2017/02/07/17/screen_bdf9777330bcb3dc1359da05e0f52272' class='modal' rel='{size: {x: 800, y: 500}, handler:"_QQ_"iframe"_QQ_"}' >enable Prepare content option</a>). Just insert a plugin code like <code>{na subscribe <u>UniqID</u>}</code> where <b>UniqID</b> is the value found in the right corner above. E.g. <code>{na subscribe 5889f0565a762}</code><br/> One more important thing. Since only logged in users can manage their subscriptions, you may wish to limit the page access to Registered users to force users to login. The plugin code for guests is removed from the output.<br/> So <ul> <li>Create a page and place the plugin code.</li> <li>Set page access level to Registred or whatever you need (optional)</li> <li>Insert the link to the page into the email body template.</li> </ul> <br> To override the subscription form output copy the layout files from <b>plugins/system/notificationary/layouts/*</b> to <b>/templates/YOURTEMPLATE/html/layouts/*</b> preserving folder structure and edit them. </div><div class='span3'> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR01#~#<br/><br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR02#~# #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR03#~# #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR04#~# </div> </div>
    <a class='showhidehelperinfo'>Click to show/hide subscription management help</a><div class='custom_context_help_info hide'> <div class='span9'>To allow users to use the subscribe feature you must create a page with the subscription form and include the link to it into the email body. <br/> This can be an article or a page with a custom HTML module (don't forget to <a href='http://static.xscreenshot.com/2017/02/07/17/screen_bdf9777330bcb3dc1359da05e0f52272' class='modal' rel='{size: {x: 800, y: 500}, handler:"_QQ_"iframe"_QQ_"}' >enable Prepare content option</a>). Just insert a plugin code like <code>{na subscribe <u>UniqID</u>}</code> where <b>UniqID</b> is the value found in the right corner above. E.g. <code>{na subscribe 5889f0565a762}</code><br/> One more important thing. Since only logged in users can manage their subscriptions, you may wish to limit the page access to Registered users to force users to login. The plugin code for guests is removed from the output.<br/> So <ul> <li>Create a page and place the plugin code.</li> <li>Set page access level to Registred or whatever you need (optional)</li> <li>Insert the link to the page into the email body template.</li> </ul> <br> To override the subscription form output copy the layout files from <b>plugins/system/notificationary/layouts/*</b> to <b>/templates/YOURTEMPLATE/html/layouts/*</b> preserving folder structure and edit them. </div><div class='span3'> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR01#~#<br/><br/> #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR02#~# #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR03#~# #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR04#~# </div> </div>

     
    <a class='showhidehelperinfo'>Click to show/hide subscription management help</a><div class='custom_context_help_info hide'> 
     
    <div class='span9'>To allow users to use the subscribe feature you must create a page with the subscription form and include the link to it into the email body. <br/> This can be an article or a page with a custom HTML module (don't forget to <a href='http://static.xscreenshot.com/2017/02/07/17/screen_bdf9777330bcb3dc1359da05e0f52272' class='modal' rel='{size: {x: 800, y: 500}, handler:"_QQ_"iframe"_QQ_"}' >enable Prepare content option</a>). Just insert a plugin code like <code>{na subscribe <u>UniqID</u>}</code> where <b>UniqID</b> is the value found in the right corner above. E.g. <code>{na subscribe 5889f0565a762}</code><br/> 
    One more important thing. Since only logged in users can manage their  subscriptions, you may wish to limit the page access to Registered users to force users to login. The plugin code for guests is removed from the output.<br/> 
    So <ul> 
    <li>Create a page and place the plugin code.</li> 
    <li>Set page access level to Registred or whatever you need (optional)</li> 
    <li>Insert the link to the page into the email body template.</li> 
    </ul> 
    <br> 
    To override the subscription form output copy the layout files from <b>plugins/system/notificationary/layouts/*</b> to <b>/templates/YOURTEMPLATE/html/layouts/*</b> preserving folder structure and edit them. 
    </div><div class='span3'> 
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR01#~#<br/><br/> 
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR02#~# 
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR03#~# 
    #~#PLG_SYSTEM_NOTIFICATIONARY_FIELD_MANAGE_SUBSCRIPTION_PAGE_NOTE_SCR04#~# 
     
    </div> 
    </div> 
     

    changed by Mylo .
    Copy to clipboard
14 Jan from 11:30pm to 12:23am