Forum Replies Created

Viewing 15 replies - 331 through 345 (of 1,410 total)
  • Plugin Contributor redsand

    (@redsand)

    Hi @fpmsummer,

    Just wanted to follow up. We’re going to release a fix soon.

    In the mean time there is a workaround that you will likely want to use anyway.

    The error messages you’re seeing could happen from any plugin/theme/core update, so the best practice is to log errors instead of having them displayed visually. If you make a tweak to your php.ini file, you can avoid similar issues in the future. It’s also recommended for security to not display errors.

    Add this to your php.ini:

    
    custom_error_logs_path = /your/secure/path/outside/web/root/
    error_reporting        = E_ALL
    display_errors         = Off
    display_startup_errors = Off
    log_errors             = On
    error_log              = ${custom_error_logs_path}/custom_error_log.log;
    
    

    php.ini can use variables, so replace “custom_error_logs_path” in both places with your custom variable name. Replace “/your/secure/path/outside/web/root/” with a secure folder outside the web root. Replace “custom_error_log.log” with whatever you like for the error log name. This way all your logs will be combined into one, and will be inaccessible to web traffic. You’ll need to grab it by FTP or by PHP script.

    Hopefully this will be useful info.

    – Scott

    • This reply was modified 9 years, 5 months ago by redsand.
    Plugin Contributor redsand

    (@redsand)

    Ron,

    We’ve had this exact discussion a few months ago on WP Tavern. I’m not going to re-hash it again. If you would like our help, that’s great, but you need to be civil. If you don’t want our help, or don’t want to use the plugin, that is your right as well. Take care.

    – Scott

    • This reply was modified 9 years, 5 months ago by redsand.
    • This reply was modified 9 years, 5 months ago by redsand.
    Plugin Contributor redsand

    (@redsand)

    @comfortking,

    Tech support isn’t about placing blame, it’s about fixing issues. If you would like help resolving issues, we are happy to provide it.

    I would say that we always do take full responsibility. If we cause an issue, we fix it as fast as humanly possible. I’m not sure what else you could ask for. It’s a free open source plugin. If you compare our response times to other plugin developers, we’re one of the fastest by far.

    If you ever have an issue with the plugin, all you need to do is submit a support request, and we will always help fix the issue quickly.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @lkraav and @killbill-sbor,

    Thanks for reporting this. We’ll look into it.

    Just a note, the forums here are not our main support venue, and when issues are reported here, it takes longer for us to fix issues. It would be most helpful if you could submit a support request at the WP-SpamShield Support Page. Thank you.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @wasanajones,

    Thanks for reporting this.

    Just a note, the forums here are not our main support venue, and when issues are reported here, it takes longer for us to fix issues. It would be most helpful if you could submit a support request at the WP-SpamShield Support Page. Thank you.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    @comfortking,

    First off, please be civil. Actually, you are incorrect. Plugin developers are not under any kind of requirement to provide support, nor are we obligated to use the forums as our support venue. However, we provide some of the best tech support of any plugin out there. Our support process is precise, and allows us to get to the bottom of issues quickly.

    Unfortunately lashing out at developers does not solve anything. All it does is stifle innovation. Whenever a plugin developer adds new features or classes to a plugin, there is a risk of something breaking, even with the best testing processes. Issues usually only affect a subset of sites. This issue does not affect everyone. We test on a variety of sites and setups before releasing a new version, with a number of debugging tools. No issues came up in pre-flight, so these were impossible to predict.

    What we can do, is fix issues as quickly as possible. We usually fix issues within an hour or two of receiving the initial report. Few plugin developers can say that.

    – Scott

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

    Hi @raoul1983,

    The errors you see today with “/wp-content/plugins/wp-spamshield/” are WP-SpamShield errors in our latest release. These are not WooCommerce errors. We are currently working on a fix.

    One recommendation to make your site fully available and not display the errors, but log them instead: Enable WP_DEBUG with logging, but not error display. Instructions are detailed here.

    Please report any WP-SpamShield issues at the WP-SpamShield Support Page so we can fix issues as quickly as possible. Thank you.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @johnymas,

    Glad to hear you figured out the issue. If you have any future issues, please submit a support request using the secure form at the WP-SpamShield Support page, our main support channel for the plugin, and we’ll be happy to help.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @starhorsepax2,

    This has already been fixed in version 1.9.9.8.3. We issued a fix after it was reported to us.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @fpmsummer,

    Thanks for reporting this. We’ll look into it.

    Just a note, the forums here are not our main support venue, and when issues are reported here, it takes longer for us to fix issues. It would be most helpful if you could submit a support request at the WP-SpamShield Support Page. Thank you.

    Yes, you have full control over auto-updates. This is discussed in FAQ 16.

    – Scott

    PS. One recommendation is to set your PHP configuration to log errors instead of displaying them visually.

    • This reply was modified 9 years, 5 months ago by redsand.
    Plugin Contributor redsand

    (@redsand)

    Hi @abigailm,

    I’m not sure how many ways there are to say this, but the WordPress support forums here are not the main support venue for the plugin. The support form has basic information that is necessary to help users fix their issues. It takes less time to fill out than to post here.

    We can help you fix the issues on your site. I believe that you are mis-attributing the source of your site issues. This is based on our team doing tech support on literally tens of thousands of sites.

    As mentioned, we’ll be happy to help you, but there is literally nothing we can do for you if you don’t follow our support process.

    Suggestions are great, but when there is already a solution, that doesn’t help as it’s just reinventing the wheel. We are all about solving problems, so if you would like us to help you solve the problem, then please submit a support request at the WP-SpamShield Support Page. Thank you.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi Adam,

    You’re very welcome. We’re always glad to help. πŸ™‚

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @consultant1027,

    It’s not unusual for discussion forums to be moderated and for user registration agreements to acknowledge that they are agreeing to not post any promotional or explicit material…

    Yes, we’re quite familiar with forums and how they work. πŸ™‚ Our team is actively involved in a number of forums, and is actively involved in anti-spam efforts on a number of influential sites. We’ve been involved in anti-spam for a long time now. Acceptable use policies vary greatly by website.

    …so the freedom of speech issue really isn’t relevant.

    Unfortunately that’s simply not true.

    Where the freedom of speech issue is relevant, is that each forum has a different purpose and may have differing views on what is appropriate, and what is not.

    Perhaps one forum does not want links to pornography websites, but another forum may be an adult forum, and it may be perfectly appropriate there. If we added a blanket block on adult websites, we would effectively be dictating policy for all forum websites, and that is not our place. Each forum has to make their own policy and acceptable use standards.

    Notice that this is not an anti-porn plugin, but an anti-spam plugin.

    That’s not to say that we don’t agree with you about the need for better policy enforcement features in BuddyPress and bbPress.

    Perhaps we can develop something like this, but that would need to be a separate plugin.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @consultant1027,

    We have to walk a fine line between protecting website owners from spam and restricting free speech.

    What you’re talking about is human spam.

    If we add something like that to the plugin, it’s a bit of a slippery slope because we don’t want to restrict free communication on a forum.

    Restricting user communication on a forum is something that has to be dealt with carefully.

    The best way to protect against profile spam and other types of BuddyPress spam, is to prevent the spam user from registering in the first place. Spammers typically make their intentions clear from the beginning, and follow predictable patterns. It’s best to just cut them off right away. Using this strategy eliminates the vast majority of spam issues.

    WP-SpamShield’s has powerful registration anti-spam that will stop 100% of bot signups, and the vast majority of human spam signups.

    Once a user has joined a BuddyPress site, if they engage in activity such as posting spam links, you can mark them as a spammer in the User admin. That’s already built into BuddyPress. You’re not likely to have many of those after you install WP-SpamShield.

    I hope this helps answer your question. Please see the plugin’s documentation for more information on features.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi @greenscotland,

    WP-SpamShield has been thoroughly tested with bbPress and BuddyPress, and works well with both.

    We have an FAQ and Troubleshooting step that addresses that exact issue and shows you how to fix it. It’s usually due to a installation problem, site configuration issue, plugin conflict, or JavaScript conflict.

    If that doesn’t solve the problem for you, we will be happy to help you. You will need to take the following steps:

    1. The Troubleshooting Guide and Frequently Asked Questions (FAQs) are the place to start.

      Please take a few minutes to work through these, as they solve over 90% of issues users have. (Please be sure to follow all the steps, not just read through them.) The issue might not be what you suspect.

      It is extremely rare for users to have a JavaScript and cookies error after they have worked through the Troubleshooting Guide and FAQs.

      Once you have gone through the Troubleshooting Guide and FAQs, if that doesn’t solve the issue, we’ll need a bit more info from you on the specifics, and we’ll need to email back and forth, so you should move on to the next step.

    2. Submit a support request using the secure form at the WP-SpamShield Support page, our main support channel for the plugin. We have an excellent diagnostic process.

    That will allow us to help you diagnose this, find out what the real issue is, and get things working right for you.

    – Scott

    Please note that the WP-SpamShield Support page is our main support venue, not the WordPress forums here, so that will always be the best way to get a quick response and resolve any tech support issues. Please direct any further support questions there.

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