This plugin is not provided by the package BwPostman. It can be acquired by purchase.
With this plugin it is possible to send newsletters at a specified point of time. The sending is processed at background.
The plugin BwPostman TimeControl only works and only installs, if the module cURL for php is installed and activated at Your web server!
You can figure out, whether the module cURL is installed at the web server by search for curl at the back end at System → System Information → PHP-Information. Do You find it, You are able to use this plugin. If You can't find cURL, contact Your provider (or change the provider), to be able to use this plugin.
The plugin needs an user, with which the automated sending will be processed. It is advisable to create a new user for this plugin. Also see advanced information below.
This user has to be able to log in at back end and he must be able to send newsletters. The sample user group BwPostmanNewsletterPublisher is appropriate by default. The permissions for Create and Edit newsletters and the permission to View newsletter are indeed not needed. You also could create a new user group on basis of the user group BwPostmanNewsletterPublisher and withdraw the superfluous permissions.
It is highly recommended to use an active mail address for this user, because success and error messages are sent to this user by mail.
This user may not be used otherwise. You never should login into backend by this user, nor to create a scheduled newsletter! For this You use the users previously used.
Cron Interval sets the interval in minutes the cron server looks for newsletters which are due. The newsletter will be sent, if the scheduled time is reached or has overtaken. The newsletter to send is entered at the queue known by the component and will be processed there. Manual and automated sending will be processed separately.
Tab Update Options
Licence code is used to get updates for the plugin BwPostman TimeControl.
Tab Curl Settings
While establishing the connection curl checks the certificate of the peer. To get this work curl have to know about the certification authority of this certificate. If the website doesn't run with HTTPS but only HTTP, then there is no certificate. If You use a self-signed certificate, curl does not Know about the certification authority. Both cases actually should occur, if You use a local installation of Joomla. And at both cases it helps to switch the option Verify peer? to no.
This setting is only meant for testing purpose and should be switched to Yes at productive websites!
Normally the certificate and the certification authority are installed system wide. If You have Your own certification authority, which signed the certificate, and this certificate is not installed system wide, i.e. at a local installation, You can enter the path to the certificate of the certification authority at Certificate path. i.e. this could be /usr/local/share/ca-certificates/my-cert.pem for linux or C://certs/ca-certificates/my-cert.pem for windows.
This setting takes no effect, if Verify peer? Is set to no.