otaku42

Hi,

thanks for your fast response. After reading it, I am still wondering:

In order to send e-mails to the “audience” defined by the admin – single users, all users with a given role, and so on – the plugin ultimately has to query the database to determine the actual e-mail addresses it should send the notification e-mail to. Wouldn’t it be possible to get like the full user profile at that point, and make profile content available through merge tags within the e-mail template?

Sure that wouldn’t work for any recipient specified via recipient type “email / merge tag”. But I’d expect it should be working for recipient types “user” and “role”, shouldn’t it?

Bye, Mike

Hi @alessandrotesoro,

I’ve did just updat and test the new version, it works like a charm. Thumbs up, thanks a lot for implementing this feature!

Bye, Mike

Hi @alessandrotesoro,

thanks for your response and taking the feature into consideration for a future version. For the time being I have found a acceptable solution that works around my issue:

The Members plugin provides a filter named members_is_private_page that allows other plugins to override the “private blog” setting on their discretion. I wrote a dead-simple plugin that makes use of this filter to make the registration page public (on a non-obvious path that I’ve set as slug for the page containing the [wpum_register] shortcode). It’s an ugly-ish hack, but works for me. Maybe it also helps someone else.

Bye, Mike

Thanks to Denis for mentioning, and thanks to Firas for allowing relicensing his work.

Just to mention it: they might argue that they used a trackback to send in the comment. So you should also mention your “150$ per unsolicited advertisement” also right beside the trackback links.

@anonymous: Well, well, hiding behind anonymity makes it easy to word up like this, right? People cheering for the elite-ness of a tool by talking about “stupid little teenyboppers with no coding knowledge” seem to forget that they once also were exactly that. Oh, yes, sure… you’ve been born with all the knowledge you have now.
WordPress is very far from being an elite tool. It’s an excellent tool, not only because it’s usable also for not-so-experienced users, but also for it’s standard compliance. That’s something that seems to have become very unpopular nowadays. But these features make WordPress being different from “yet-another-blogging-solution”.
Personally I appreciate very much the work that is being done for WordPress. There are many things that would be nice to have in WordPress, and some things that need improvement. And I try to contribute to that where possible.
If you are willing to help in a useful way I’m sure you’ll soon recognize that WordPress has a great community with people helping each other (no matter if experienced or not). But if you decide to keep trolling the way you did up to now, I suggest you should consider to silently move away and stop wasting our time.
Just my 0.02$.

IIRC, IIS 4.0 dates back into WinNT 4 times? So it’s kinda stone-aged, I guess…

If possible, please submit a patch for this issue to the sf.net patch tracker for the cafelog-project. Then we could take a look at it and possibly include it in CVS.

@”allow from this person”: currently there is no safe way to distinct people (or prevent others from faking their identity). This will last until there is a “register before posting a comment” function available, which I personally would dislike a lot. But the base idea (disabling links until comment gets approved) would be a nice feature. I put that on the “To Do list” ??

@other suggestions: comment moderation is already available, and automated comment moderation will be available soon. Things that are planned are blacklisting and bayesian filters.
Disallowing hyperlinks is (in my eyes) a bad idea. This will not just break the spam, but also other usefull links. Respectively, it won’t just break the spammers google ranking, but also other (wanted) site’s rank. And as Phil Ringnalda wrote in a comment to this blog post:

Something to consider, while looking for a way out of the spam nightmare we are in right now: anything (including not linking legit commenter’s URLs) which makes you have less impact on Google is a win for them.

By the way: you might be interested in joining the BlaM project (https://blam.sf.net), even if it is very silent currently. I’m aiming to get some things done as soon as I’m finished with the stuff I’m working on at my business job (hopefully by the end of this month).
Bye, Mike

The problem is that there currently is no adequate “infrastructure” for easily supporting localizations. This is definetly something on the developer’s wishlist, but not scheduled yet (as far as I know). If you guys had any ideas on how to (efficiently) add localization support to WP, write down your thinking to this thread. Thanks.
Bye, Mike

I’d vote to have something for WP that is similar to linuxcounter:
https://counter.li.org/

@sushubh: No one actually uses Opera… uhm, wait… there’s a mob ringing at the door, be right ba… *NO CARRIER*
??

LL described it correctly, but accidently changed “manual” and “automatic”.
So, let’s sum it up again:
“Manual” means, that you decide yourself about approval of newly posted comments. Currently “automatic” has the same meaning. But in the near future “automatic” will be the first step to allow WP to “automatically” approve comments by using things like “blacklist matching” or “bayesian filtering”.

@giles: The most recent one now is v1.0 ??