daniellj
Forum Replies Created
-
A simpler request would perhaps be to implement a simple filter that will make mailpress not to syncronize wordpress users with role ‘pending’, thus syncing only the role ‘subscriber’ and other valid roles for registered and granted members.
Forum: Plugins
In reply to: Deleted wordpress users not synced with mailpressResolved duplicate. See http://wordpress.org/support/topic/deleted-wordpress-users-not-synced-with-mailpress-1
Forum: Plugins
In reply to: [MailPress] Deleted wordpress users not synced with mailpressExcellent! That worked! I made the changes above on line 135 in file: …/wp-content/plugins/mailpress/mp-content/add-ons/MailPress_sync_wordpress_user.php.
That should be simple enought to put as a optional feature in the plugin settings, so that I wouldn’t have to make this code-change on every update.
Many thanks!!
Ok, I’ll be waiting 🙂
Keep up the good work!
Many thanks,
Forum: Plugins
In reply to: [MailPress] Deleted wordpress users not synced with mailpressSo, the fact that mailpress users are not synchronously removed from mailing-lists when they are deleted from the wordpress system is apparently a feature. I still don’t see the purpose of it. One would somehow expect that a user being permanently removed from wordpress has no way of accessing disallowed information by any means, including receiving emails with blog content. Many sites are user access managed.
To make mailpress much more widely usable, I would strongly suggest to add an option to be able to sync wordpress unconditionally, meaning that mailpress will blindly syncronize with the wordpress user-list in a way that a mailpress user cannot exist without also existing as a wordpress user.
Many thanks,
PS. It is actually a tedious, not to say impossible, job to manually delete a user from mailpress guided only by a list of several hundred or thousands wordpress users with no clue of which user have been removed. At the very least, I’d suggest deleted users to be marked as ‘Deleted’ in the mailpress user list, at the same time removed from ‘Active’. There could then be an option whether emails should be going out to ‘Deleted’ mailpress users or only to ‘Active’.
This is still not resolved with WordPress 3.6 and Mailpress 5.4!
Forum: Plugins
In reply to: Member Access blocks MailPress?This problem persists after uppdating to WordPress 3.2.4, Member Access 1.1.6 and MailPress 5.3, and now also the fix using alternate wp_cron doesn’t work any longer! Please, anybody – Help!
When inactivating Member Access it is clear from the logs how MailPress works – using the category of the current post it performs a loop match against all available categories:
No match doesn’t do anything:
post_category_10 ! newsletter categories (in) : 10 ! post categories : 17 ! Post 1122 not in required categorieswhereas a successful match sends out an email:
post_category_17 ! query_posts : {"cat":[17],"p":1122} ! ** Process successful ** (recipients : 2)When Member Access is activated MailPress instead stalls for a minute as soon as it should do a successful match (due to membership/access denial of reading that post!?), and then it doesn’t log anything until the next (unsuccessful match) and no emails are ever sent.
Any ideas!?
Cheers,
Forum: Plugins
In reply to: Member Access blocks MailPress?It clearly has something to do with standard cron…
A short workaround is to add the following line in wp-config.php:
define(‘ALTERNATE_WP_CRON’, true);
Cheers,
Forum: Fixing WordPress
In reply to: Email selected WordPress usersThat’s a shame. All plugins for handling emails are far too complicated for the end user administrators that I am developing websites for – or they achieve next to nothing…
Well, at least I can hope for a simple plugin.
Forum: Fixing WordPress
In reply to: Email selected WordPress usersExactly that! I’ve been waiting for this feature long time. All these complicated plugins out there and none doing this simple thing. We want the ‘Email’ option added to ‘users.php’ page in next wordpress version. Why satisfy with the ‘Delete’ option only?
Hope you folks can fix that!