Forum Replies Created

Viewing 15 replies - 226 through 240 (of 1,410 total)
  • Perhaps I can help, as I’ve had a bit of experience in this area.

    You can extend/customize the functionality of the wp_mail() function using one of its 6 hooks:

    ‘wp_mail’
    ‘wp_mail_from’
    ‘wp_mail_from_name’
    ‘wp_mail_content_type’
    ‘wp_mail_charset’
    ‘phpmailer_init’

    These are located in the wp-includes/pluggable.php, and have a good amount of inline documentation.

    Using these, you should be able to make the necessary changes. Just a word of caution: Make sure that you only add filters/actions to a hook when your specific email function is firing (or make sure any hooked functions only fire exactly when needed), because when you hook into wp_mail() it affects everything in WordPress (core code, plugins, themes, etc) that sends mail. So just be aware of that.

    Hope that helps!

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi GreenScotland,

    Thanks for taking time to let us know you like the plugin! We appreciate the positive feedback! πŸ™‚

    Have a good one.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @kodacollider,

    I’ll be happy to answer your question.

    The two plugins are perfectly compatible. WP-SpamShield will block the spam first, and keep it out of the database, so Akismet would be redundant. (Akismet filters differently, and evaluates spam after it has already been entered in the database.) However, if you want to use Akismet as a backstop, you are welcome to do so.

    I hope that helps! πŸ™‚

    – Scott

    • This reply was modified 9 years, 3 months ago by redsand.

    @gallardooo,

    Outstanding news! πŸ™‚

    If you ever need help in the future, let us know.

    Have a good one!

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hey Mitch,

    Thanks for the great feedback!

    – Scott

    Plugin Contributor redsand

    (@redsand)

    @pothi,

    Thanks for sharing your thoughts. I agree wholeheartedly with what you said. I think you explained things quite well. Much appreciated. πŸ™‚

    @frankyw,

    Thanks for reconsidering, and for the updated rating. πŸ™‚

    Have a good one!

    Hi @gallardooo,

    I’m sorry to hear about the issue you’re having. WP-SpamShield is 100% compatible with the Edge browser, and 100% compatible with Contact Form 7. CF7 is one of our favorite plugins, so we take extra care to make sure it’s compatible. πŸ™‚

    If you’re having that type of error, and it’s consistent, then there is a specific conflict on your site. Please see FAQ #9 and Troubleshooting Step 9, as these directly addresses that issue, and will help you fix it. (Over 90% of user issues are solved with the Troubleshooting Guide and FAQs.) If that doesn’t fix the issue, please submit a support request at the WP-SpamShield support page, and we will be happy to help you debug and resolve the issue.

    – Scott

    • This reply was modified 9 years, 3 months ago by redsand.

    @lowest,

    I agree wholeheartedly about calling another developer stupid. That’s just unprofessional, and uncalled for.

    Thanks, I’m glad you feel I should be here. πŸ™‚

    Don’t you see why 5000+ WordPress installations have installed this plugin? Because all 5000+ of them are tired of your advertisements!

    100% true!

    @joostdevalk,

    Anyone can participate in a thread. That’s sort of what the whole “open source community” is about. We’re supposed to encourage dialog, and encourage each other to be creators…not to tear each other down.

    And, since the topic directly relates to your recent pattern of going after other plugin developers (including us), I will say that yes, I have business being here. (Even if I was just a spectator, since it is a forum, anyone can contribute, and it would still be appropriate.)

    I agree wholeheartedly with what Mitch said:

    One final word for you Joost, change your attitude.

    @gioni,

    You’re welcome! πŸ™‚ No worries…Keep up the good work.

    @lowest,

    Yes, if @joostdevalk finds that there is a plugin conflict between another plugin and one of his plugins, or he feels it damages his brand, or simply does not like it, he goes straight to giving a 1-star review instead of submitting a support request.

    He’s done this with at least three plugins lately (possibly more), and always insists that the issue is with the other developer’s code.

    Our RS Head Cleaner Plus plugin also removes this HTML comment and he recently gave it a bogus 1-star review as well, although he used a different pretext. We fixed the issue he reported within a day (conflict with AMP plugin), and then he found something else to give it a 1-star for. You might be interested to read this for more context.

    It’s an obnoxious tactic, and other plugin developers need to call him out on it, and not put up with it.

    – Scott

    • This reply was modified 9 years, 3 months ago by redsand.
    • This reply was modified 9 years, 3 months ago by redsand.
    • This reply was modified 9 years, 3 months ago by redsand.
    • This reply was modified 9 years, 3 months ago by redsand.

    @gioni and @rohitink,

    I think it possibly has to do with the fact that the plugin is using file_get_contents() PHP function to retrieve URLs instead of using the WordPress HTTP API.

    I just finished the support thread on this, so perhaps take a look. When that is fixed, it will likely resolve the reCaptcha issues.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @webmom,

    Thanks for the positive feedback! That is awesome to hear…That’s our goal! We’re glad to hear that you don’t have to worry about spam anymore. πŸ™‚

    Take care!

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @franklycurious,

    Thanks for the great review, and sharing your experience with WP-SpamShield!

    I’m glad to hear that we could help you keep your site protected from spam. πŸ™‚

    Have a good one.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @thanewest,

    Thanks for the great review and feedback! I’m glad you liked our rebuttals! LOL, I enjoyed reading your review as well. πŸ™‚

    Thank you…we try hard to provide great support.

    Hmm…Pinterest…that’s an interesting question. We’ve never had anyone mention that. I don’t think any code in the plugin right now would prevent pinning. Is that something you’re concerned about, or is it more like a feature you’re interested in?

    It could be added fairly easily as an opt-in feature. Details on how to prevent pinning are here in the Pinterest docs. There is a meta tag that can be added to the head of a site to prevent all pinning, and an attribute that can be added to single images to prevent pinning.

    Thanks again for being a gr8 dev!

    You’re very welcome. Awesome people like you are really why we got into plugin development, and make it worthwhile. πŸ™‚

    – Scott

    Thread Starter redsand

    (@redsand)

    This isn’t a coding “bug” — it’s an development issue.

    I didn’t realize we were posting awards. Thanks for the lecture. That will solve the issue.

    • This reply was modified 9 years, 4 months ago by redsand.
Viewing 15 replies - 226 through 240 (of 1,410 total)