Hi, can you send a reference to your unanswered requests?
Thank you, Stefano.
I notice you are much more reactive here than by the support ticket system you provide…
Here are the tickets, all unresolved or unanswered :
#121371, from September 20, 2018 10:50 am
#121198, from September 19, 2018 3:11 pm
#121159, from September 19, 2018 1:30 pm
Thank you.
-
This reply was modified 7 years, 8 months ago by
Adage Group.
Hi, thank you for reporting the tickets, I’ve just reviewed them.
About your specific need to set the number of email per minute, this is not possible. The core cannot be changed (or it would require a lot of effort) to support that kind of configuration. More, even if added, it would be incompatible with many installation and hosting providers limits. That means we should keep two options, the current one and the mail per minute for you creating a lot of confusion.
Those specific delivery limits could be better addressed at the SMTP level or using an external provider.
About the message “missing shortcode in the dedicated page”, that’s a problem of the visual composer which does not stores the page content in the regular WP content field for posts and so we cannot detect it. Since that warning is really important to our users to avoid misconfigurations, we can only add an option to forcibly disable message, for example with a “define” on wp-config.php. I’ve already added that on the new development list.
About the subscription form on Newsletter dedicated page, that is a default behavior. That page can be hidden from menus, deindexed for search engines, and you can create a subscription page with contact form 7 as per your needs. Direct access to the dedicated page will always show the form. It is a coded behavior.
You can try to write the code as [newsletter form=”1″] and leave the form 1 code in the forms panel empty. Probably, but cannot grant it right now, no form will be shown.
Thank you, Stefano.
ps: as you can understand all the above are not (blocking) bugs but specific working modes you need and that could require a change in the plugin core. Except for the warning message which is triggered by a visual composer which changes the WP normal behavior which we’ll try to address.