A few questions for the plugin and a suggestion

    1. If I have the cookies box checked in the plugin. This is on loclhost via Xampp – I don’t see a visible cookie field to mark (unless it is invisible to the user?).
    2. If the cookie field is selected (I don’t see the one from the plugin) – but I can see the ones from worpdress in the discussion settings. Perhaps it would be good if the subscription option was also in mind – that is, whether to subscribe, not subscribe, or subscribe to everything. So that this field also remembers your selection.
    3. Your plugin would be powerful, beautiful and very useful – if it had the option to also choose a regular notification about a new post on the site. A simple link to the new added post and a choice for users whether they want it. There is also a regular field for adding your email address in the widget for such notifications. No nweestlater needed, just a simple tool complete with what is currently available – it would be really something very useful.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author WPKube

    (@wpkube)

    Hi @danishsard

    1. It’s not a visible checkbox for the visitor. The option turns the cookies on/off for everyone. But since WP adds that “save my name email and website” cookie checkbox we could make it check if the visitor selected that and if not then we do not apply the cookie. I’ll add that to the to do list.
    2. Currently only used to remember the email address to automatically apply it to some areas of the plugin, such as the email input field on the “request management link” page and the “subscribe without commenting” page. Will add it to the to do list to also remember the type of subscription.
    3. I’ve thought about it quite a bit since you originally asked about it and the more I think about it the more complex it gets.

      There’s no way to make it work as part of the current system we have for the subscription process since that system is specifically made for comments.

      So the entire system would need to be drastically changed to allow for other types of subscriptions.

      Also a whole new set of options in the backend. For example the email notification message, by default that references info about a comment so a separate option is needed for comments and for posts. Same thing applies to most of the options.

      And this being a plugin specifically for comments subscription those options would add a whole lot of confusion for users.

      It’s really highly complex if it’s done properly.

      You are currently using a different plugin for that purpose, correct?
    Thread Starter Danishsard

    (@danishsard)

    Hello, currently I don’t use any plugin for notifications about new posts, because over time it becomes too many plugins.

    However, there may be a way around this – in the sense of creating something as a new point, new files that use the same database and page with addresses and managing them. However, the remaining fragments are activated – i.e. the use of common elements and the use of separate elements on a separate settings page.

    Or making a simple separate plugin for this. Simple, without any extensions – so that the content could be parsed into your own language (although I would also translate it into Polish for everyone).

    What you do is so cool, so pretty, that I would love to use your products. Few things are done as friendly as what you do.

    Perhaps this problem can be circumvented by using common features – and additional functionalities – or a separate plug-in as an addition.

    All this would make this add-on fully sufficient in notifications. I know that many people use several at a time (even 4-5 different ones) – but then it’s crazy.

    • This reply was modified 9 months, 4 weeks ago by Danishsard.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘A few questions for the plugin and a suggestion’ is closed to new replies.