Forum Replies Created

Viewing 15 replies - 136 through 150 (of 213 total)
  • As Chad says, this couldn’t be a function of the WP Members plugin, but would need to be achieved at WP level itself.

    If you want to encrypt the database so that any manual access of the data stored within it would be protected, then one option is to use Amazon RDS as your database. This has the option of encrypting the data within the database (by a simple switch in the config settings for that database).
    Any application that connects to that database has no knowledge of the encryption, it simply works ‘as is’. The encryption is only within the database itself (on Amazons RDS).

    You can’t really have a plugin or adapt/override WP Core code to do the encryption and decryption of part or all of the main database. Given that you are trying to prevent anyone who gains access to your database, the ability to read the data within the database without a key, if they managed to gain access to your WP site (say with admin level), or your server, then they would have access to the key/hash which WordPress would need to access to database. i.e. if they have access to your WordPress install, then it doesn’t matter if the database is encrypted, they’d have the key.

    So ideally, you’d need to encrypt/decrypt at the database server level itself and have any apps that access it be transparent to that.
    Providing you use strong access controls between your server and the database, it would at least protect the data from being accessed externally. (key point being, accessed externally).

    Even with Amazon RDS encryption, if someone gained access to your WordPress install, they would still have access to the data on the Amazon RDS encrypted or not as they could use your WordPress install to access the data.

    It’s a big can of worms…

    That looks like a genuine “address does not exist” error.
    Double check the recipient address is correct. Gmail is reporting that one or more of the recipients addresses failed (given you’ve got 0 successes and 27 fails).

    Just to clarify, do you mean that you would like an additional notification/status message for any messages within the log file, that have been sent using the “resend” function within the log file?

    When you hit resend, a new log entry is created for that resend, so it already is kind of shown. Unless, do you mean a new status such as ‘sent – via resend’ so that you can identify which messages were sent normally (with a status of ‘sent’) and a new status message to show they were sent or failed (via a resend)?

    One thing to check is that your host doesn’t have throttling enabled on your mail server. i.e. your server might be trying to send emails too quickly. Some hosts throttle the number of emails that can be sent per sec/min/hour.

    Or, it could be the number of connections being made from your server to the mail server, i.e. if your server is opening up too many concurrent connections (sending multiple emails in quick succession).

    With GSuite, I’m not 100% certain on the limits, but I have seen issues in the past whereby a clients App was attempting to connect and login way too quickly which was causing the connections to be rejected. After a period of time, he could connect again. There was a difference between different level of GSuite accounts. I’ll see if I can dig out any references to this.

    Are you able to see the actual error code returned by GSuite in your logs?
    Failing that, if you log into GSuite, you should be able to see connection requests and possibly any errors (again I can’t remember where that is in GSuite off the top of my head but if you have no joy locating it, I’ll try to find the reference).

    The PHPMailer issue you link to (stackoverflow) would be a hard error rather than intermittent.

    Just a few ideas…

    As WP Polls doesn’t support this, try Gravity Forms. It even has a Polls addon which means even less work, but you could achieve what you’re after with the main Gravity Forms (which supports conditional logic). Whilst not actually saved to the users profile, completed surveys can be linked to the users profile.
    If you really wanted to go down the route of saving the data to the users table, under the users profile, you could however easily do that with a few lines of code within your own functions.php

    Install a plugin called POST SMTP and use that to check the logs it creates to verify a mail is being sent. It will show you the communication between your site and the mail server. This will help you rule out whether a mail is being sent and not being received, or if the WP Members plugin is not sending an email at all.

    It’s CF7 that is displaying the Google reCAPTCHA flyout on every page, where it should (IMHO) only show that on pages that use a CF7 form, not every page of your site.
    I’m going to submit a request of my own, but wanted to add my ‘support’ to your comment.

    I’ve also noticed that it does seem to be using V3 too well either. You can usually test it’s effectiveness by using an icognito browsing session in which you are almost always asked for reCAPTCHA verification. CF7 forms aren’t doing that it appears.

    You can also login to your cpanel,launch file manager and simply delete those plugin folder.

    Take a backup of the file system first, then:

    navigate to /plugins/ and delete the mojo-marketplace-wp-plugin folder.

    Then navigate to /mu-plugins/ and delete the endurance-page-cache.php file.

    That should get your site up and running again until you can investigate what caused those plugins to die.

    Rather than use a plugin, if you have access to .htaccess, this is a much faster method of redirecting.

    On my phone ATM, but if you Google “htaccess redirect non SSL request” will show you a number of solutions that will work.

    That’s my preferred option rather than using a plugin.

    It’s also worth performing a check of your database for any non HTTPS looks to avoid any mixed content errors. For this, look for a global search and replace plugin. Most will let you do a dry run before making any changes permanently. Of course, make sure you take a backup of everything before you do anything!! Then take another backup just to be sure. Remove any global search and replace plugin after you’ve finished with it.

    Hi Cahebe,
    The point the previous reply was making is that the error is down to a broken theme, not a bug in WordPress. So you are unlikely to get help here, you’ll need to contact who ever supplied the original theme (ThemeForest or the actual theme developer).

    In saying that, if you are not seeing that error on the old server and only on this new server, one thing to check is the PHP versions on both server. Make sure the new server PHP version matches the old server.

    Do you have another plugin installed, something along the lines of a ‘subscription’ type plugin that sends notifications of replies to users that have already made comments?

    If you do, rather than replying via the Admin interface, try replying directly to the comment and seeing if you receive an email that way.

    I suspect that if you have a subscription type plugin installed, by using the WordPress Admin panel to reply directly, it’s bypassing your subscription plugin and not sending an email.

    I’ve just tested the latest version of POST SMTP on a couple of sites and had no issues replying via the wp-admin/edit-comments.php page.

    Also worth double checking that you don’t have ‘approve ALL comments/replies’ enabled and it’s not just the case that your own replies are being held in the moderation queue.

    Another possibility is if you have Akismet enabled (or another type service), your own domain could be blacklisted and the email is being blocked – but I’d put this one at the back of the queue when checking.

    The fact that you say you are not seeing anything in the POST SMTP logs suggests that the WP-MAIL function isn’t being called. That’s what leads me to think you have another plugin in between the REPLY function and POST SMTP.

    Hi @reinispro,
    Yup, you can do that by setting the Unique field to the email address of the form submitter (or another field that is specific to each of your users – which is usually the email address).

    Instructions here: https://ninjaforms.com/docs/unique-field-validation/

    A couple of possibilities…

    Although it uses the word Spam, the “OutboundSpamException” can also mean, that the connection to the Outlook server or the machine that tried to connect to the Outlook server appeared to show “spam like behaviour”

    Are you trying to send it with a “free” Outlook/Hotmail address account, or an Office365 type account?

    Have you authenticated the account that you are trying to use so that it has permission to use Post SMTP to send mail?

    Those are my first two guesses, but there is also the chance that the following is valid:

    It could be the Outlook server basically refusing to send your message because it thinks it is spam, so that returns a mail failure to Post SMTP.
    What was the contents of the message? (Did it contain bad HTML or a lot spammy words likely to trip up filters).
    Have your checked that the IP address of your connecting machine was not on any RBL’s?
    Did you run the content of the email through a spam assessment tool?

    Go to your form settings, click on restrictions, set the “Limit Submissions” field.

    See the Docs at: https://ninjaforms.com/docs/form-settings/

Viewing 15 replies - 136 through 150 (of 213 total)