shinerweb
Forum Replies Created
-
Forum: Plugins
In reply to: [AMP for WP - Accelerated Mobile Pages] Plugin stopped working after update@ercan GUNES,
You might be better off opening up a new ticket/thread rather than commenting on this one.Forum: Plugins
In reply to: [WP-Members Membership Plugin] Customise Registration Form@mpbaweb I think Chad means where was the ‘source’ of the “[See Installing the Plugin with Custom Registration Fields for information on how to add/subtract fields from the default installation.]” so that he can go correct that.
He’s a plugins creator, not a mind reader. (<– that’s sarcasm 😉 )
@expressionssg did you confirm you don’t have the limit submissions field set?
It sounds like recreating the form is resetting that field allowing a further X number of submissions before the form stops displaying.
Or, try setting it to enabled and a number, saving the settings. Then clearing the setting and saving again to see if that clears it.In theory, Post SMTP would have no knowledge of any new roles created by users so wouldn’t be able to assign access rights to a custom user type.
At the moment, I believe Post SMTP uses the level of Admin to control access to all settings. It doesn’t split up access control down to specific areas within Post SMTP (i.e. access to logs, sending of test email, import/export, troubleshooting, notifications).However, there are other plugins which let you manage and control access to WP/Plugin features and controls.
One plugin I use and recommend to clients is “User Role Editor”
https://wordpress.org/plugins/user-role-editor/That plugin will let you assign access to Post SMTP, but it will give them access to “Manage Post SMTP” (manage_postman_smtp) which will include I suspect making the settings available as well as the logs.
You can assign access via a specific username or groups of users (i.e. in your case “Shop Manager”).We could ask @yehudah very nicely if we could create a specific privilege requirement for the logs but that isn’t a quick fix.
Hope that helps.
The SendGrid link has changed after they’ve updated their site.
For anyone else interested, the correct link is:https://sendgrid.com/docs/ui/account-and-settings/how-to-set-up-link-branding/
Forum: Reviews
In reply to: [PHP Compatibility Checker] Can’t Get It To WorkIs this a development site, or one with low visitors?
It uses WP_CRON to ‘batch process’ calls so if you have low traffic or WP_CRON is disabled (and you don’t have a server CRON set running), it cannot complete (or even move to the next stage).Also, if you have a low PHP execution timeout value set on the server, this could cause it to fail.
I’ve run this on some pretty crappy low powered customer servers to do a quick and dirty check of something and it’s always managed to run. It’s most likely a server config setting on your VPS or a site related setting (like zero traffic or WP_CRON disabled).
Forum: Reviews
In reply to: [PHP Compatibility Checker] Can’t Get It To Workwhat type of server/host are you running it on?
What do the logs show?
When you view the transcript, find the lines where the attachment is being sent and check for any errors.
How big is the attachment you are trying to send? (What’s the file upload limit for your server etc or the mail attachment limit for the sending account you are using).
Is it a file type extension supported by the sending account?Have a check of the transcript logs and post any error lines here.
Check the error logs on your server for any error messages from CF7 too.
What I think you are saying is that your Form Plugin is sending the results of a form submission to address1@somedomain.tld
It is also sending a confirmation message to the form submitter (submitter1@users-domain.tld)
You are saying that the user is getting his confirmation before the actual data of the form has reached address1@somedomain.tldThat would be a feature or behaviour of whatever form App/Plugin you are using, not Post SMTP.
Post SMTP simply replaces the WordPress WP-Mail function with a much better mail method.
It has no knowledge of what is being sent or when to send it.
That is determined by WordPress Core or the WordPress Plugins.i.e.
Form Plugin Does Stuff
Form Plugin Does more Stuff
Form Plugin Does more Stuff
Form Plugin sends Form Submission Data
Form Plugin sends Confirmation Mail
Form Plugin finishesAt no point does the Form Plugin have any knowledge that Post SMTP is involved, and likewise, Post SMTP doesn’t know that a Form plugin sent a mail.
There are also many factors in the chain that could affect the times.
i.e. You are using the same SMTP account to send the email. Your Form Plugin is likely to send the emails one after the other so any delay here would be minimal.
Unless you control the mail server where your submissions are sent, you don’t know how long it takes your inbound submissions to transit through it’s system. And if say you are using Microsoft Outlook to receive your emails, and that is set to only receive emails once per hour, you might have to wait 59 mins for the ‘new mail’ to pop up on your screen. Even if you have your mail client set to notify you immediately when a new email arrives (IMAP method), you still have no control over how long it takes the email to transit through their mail servers before it gets to your inbox.One possibility if you are using a Form module like Gravity is that you can override the forms notification behaviour and introduce a delay such that the completed form is sent on submit, but the confirmation email is delayed (a finite period) before being sent rather than being automatic as it is at the moment. You could use the WP Cron to set up an event that occurs in the future to send the user confirmation. Or something along those lines.
But Post SMTP can’t help you with any of this. It merely sends what it is told (the mail) to where it is told (the recipient) using what method it is told (SMTP server/Gmail API /SendGrid).
Only thing Post SMTP can control is the method.
The what and when is up to WordPress / Plugins.Unfortunately, GoDaddy is waffling you.
It might be quicker to recreate your Google Cloud/Google API app connection.
You’ll need to visit https://www.google.com/accounts/Logout?continue=https://console.developers.google.com/start/api?id=gmail and follow those instructions again.This is the step that verifies the external App (Post SMTP in this case) is authorised to connect to the Gmail API.
Add a new App, get the new Google ID and Google Secret and make sure you paste them exactly as shown into the correct boxes in your Post SMTP settings.
This is the step that authorises your Post SMTP to be able to connect to the Google Mail API.
When copying and pasting the ID & Secret, paste into Notepad (or similar) first and make sure there are no extra spaces or any other control characters at the end. Sometimes, if you have different language or a different encoding to normal set on your PC/Mac/Device, when you copy something onto the clipboard, it adds extra characters. Check what you paste into Notepad matches that at Google, then copy from Notepad to the Post SMTP settings page).It can really only be a firewall blocking communication between your GoDaddy server and Google, or the ID/Secret is incorrect (or the Google API App set-up wasn’t completed).
The fact that your Post SMTP tried to connect but got an “App Not verified” error suggests that there is no firewall between you and Google. Therefore, it must be the App ID or Secret that has the issues.
I have seen ‘weirdness’ with Google API’s before and it’s often quicker to just create a new App/connection rather than trying to edit/fix the one that’s not working.
Once you do get it working, from within your Google control panel, delete the broken one.Hotmail uses different rules to determine spam scores than Gmail.
If you have access to the domain zone files you could double check your SPF records to make sure you’ve added sendgrid/mailgun to your domain.
Those settings should be available within your mailgun/sendgrid accounts.You could also add the address to your Hotmail whitelist which might allow it to bypass the spam filters at Hotmail.
Hotmail also has a setting that will reject emails from addresses not in your contacts. Create a contact or send an email from within Hotmail to that address being blocked and that may add it automatically to your contacts (double check this works as that’s another setting).
Check your domain reputation via any of the online RBL tools to make sure your domain isn’t listed for any other reason.
Hope that helps
@cag8f
Security updates support for PHP version 5.4.x ended towards the end of 2015 which is over 2 and half years back.
5.4.45 was released in September 2015 and support for it basically ended there and then.I can only suggest going back to through the versions (click Developer mode on the Plugin page in the right hand sidebar), and find the last version that wasn’t a security update. You couldn’t use a version prior to that or you’d risk exposing your site.
5.4.45 would have stopped being supported well before the current developer (@yehudah) took over the maintenance and ownership of the plugin. I’m afraid it might be a case of testing different versions until you find one that works.Forum: Plugins
In reply to: [Ninja Forms - The Contact Form Builder That Grows With You] ValidationOn the form Advanced settings tab, go to “Restrictions”.
The top property allows you to set a unique field.
If you set that to say the users email address, it will only allow that user to fill out the form ‘once’. You will have to select a property within your form that is unique between different users (i.e. email address or username).
You can change the default message that is displayed when a user tries to submit a 2nd entry.See the Ninja Documentation here: https://ninjaforms.com/docs/unique-field-validation/
Just incase @yehudah is busy, 5.4.45 is a very out of date version of PHP and you should definitely upgrade it.
If you can, I would upgrade to the latest version of 7.x that you can. (7.2 is the latest at the moment).
I believe PHP 5.6.x is supported, but it won’t be supported for very much longer. Support for 5.6.x by the PHP group is due to expire very soon.If you can go to 7.x your site should see quite a decent speed improvement so it’s well worth updating to 7.x for that alone.
Depending on which mobile and which provider, you may need to clear the cache on your mobile browser. You are probably looking at the cached version of the form before you enabled hiding of the labels.