awtx

Thanks for the response.
I didn’t know if you were still active so instead of waiting I exported the 300+ entries and then imported them directly into Greenrope.

I’ll keep the custom development option in mind if we need anything else. I’m glad to hear that option is available.

Post SMTP is not compatible with PHP8

For those who are confused. You can either follow @ngnly instructions to edit the plugin or just login to the server with your FTP account and delete the plugin.
/wp-content/plugins/post-smtp/

You can download an older version from GitHub while you wait for Yehuda to upload a fixed version.
Version 1.7.10 https://github.com/yehudah/Post-SMTP/archive/master.zip

I keep the last 3 versions of any plugin so it was easy to install the previous version. If you have the previous working version 1.8.3 plugin on multiple sites, copy the old version from one of your other sites.

post-smtp version 1.8.6

[24-Apr-2018 00:26:17 UTC] PHP Warning:  require_once(Postman-Mail/PostmanContactForm7.php): failed to open stream: No such file or directory in /wp-content/plugins/post-smtp/Postman/Postman.php on line 57
[24-Apr-2018 00:26:17 UTC] PHP Fatal error:  require_once(): Failed opening required 'Postman-Mail/PostmanContactForm7.php' in /wp-content/plugins/post-smtp/Postman/Postman.php on line 57

https://www.ads-software.com/support/topic/invalid-argument-supplied-for-foreach-102/

This obviously is not a site specific error.

Its time to release an update or at least post an accurate solution with clear instructions.

The function hugeit_lightbox_get_images_url() does not exist in v2.1.0.

The post from @kluver clearly states the function is get_images_url(). I’m puzzled as to how you can be confused about your own plugin.

Please keep in mind that you have WordPress users who require a clearly stated solution rather than a paraphrased code reference.

Run a full backup of your site, then try installing v4.10.2

Meanwhile, check your uploads directory for files named uploads.php and uploads2.php. If they exist, you were hacked through an exploit in the shortcodes-ultimate plugin.

The plugin has been vulnerable to Authenticated Directory Traversal since v4.9.9 and it still exists in v4.10.1. They recently released v4.10.2 but I haven’t bothered inspecting it yet. If a developer doesn’t think our website safety is his concern, I don’t feel the need to continue using any of his plugins.

I had 85 sites attacked with malicious files uploaded due to the exploits in this plugin. Fortunately, I block browser access to .php files in my uploads directory. This saved me and clients from a potential disaster.

Did you check to make sure the web address is correct for the off-site javascript?

Oops, Andrew must have been out of coffee and a little grumpy. With a little guidance the adding of javascript to all sites in a multisite installation does have to do with WordPress. Solving a non-WordPress javascript error for a third party form would indeed deserve that response.

I’m surprised someone didn’t remind him that he is using multi-site. Any change to the main “active” theme will affect every site using that theme. If each site uses a different theme, then he would be back to the same mass editing hassle. Most HTML editors have a search & replace function that will find all instances in files in directories so it really is just a 5-10 minute task.

He could also create a custom plugin with the enqueue code and place it in the plugins or mu_plugins (must use) directory. That would load it automatically and instantly for all 200 sites in his multi-site installation. Unlike a standard plugin, this would only have the header and enqueue code.
https://codex.www.ads-software.com/Must_Use_Plugins
https://developer.www.ads-software.com/plugins/the-basics/header-requirements/

It really is a good idea to only load the script on pages that use the form. If the form is on every page, then the conditional should be changed to exclude admin pages.

/wp-content/mu_plugins/enqueue-ebscoscript.php

<?php
/* 
plugin header
*/
function enqueue_ebscoform() {
  if ( is_page( 'ebsco-form-page-slug' ) ) {
     wp_register_script( 'ebscoform', '//support.ebsco.com/eit/scripts/ebscohostsearch.js', array( 'jquery' ), '1.0', true );
  } 
}
add_action( 'wp_enqueue_scripts', 'enqueue_ebscoform' );
?>

• This reply was modified 8 years ago by awtx. Reason: added mu_plugins directory reference

Remember, it is always helpful if you provide details about your server. Sometimes there is a well-known issue with the versions of the LAMP/WAMP bundle you are using.
Server: Linux/Windows & version
Apache version
PHP version and memory limit for WordPress
SQL database server (i.e. MariaDB, MySQL, MSSQL & version)
WordPress version.
jQuery version (Using WordPress installed jQuery or external/optional version)

Have you enabled WordPress debugging, attempted the lookup, then reviewed the debug log to see if there is a more detailed error message? You might have other surprises in the debug log, like conflicting plugins, that are associated with the error. Just remember to disable debugging before you start digging into the log.

Have you looked at your web server error log for additional information?

As for the production environment, you could always clone a copy to a development web server. Then you could test & experiment without causing disruptions.

Thanks, sent email.

@phbernard, you are missing the point.
Don’t force the plugin to hide errors, that is a tremendous mistake.
Hiding the error output doesn’t fix the problem. Your plugin should not be generating errors if it is functioning properly. Can you imagine what would happen to a busy site if all the plugins behaved like yours?

Let WordPress handle the daily update check. You should not be generating extra traffic or using additional resources. If your plugin is generating debug entries, then you have some coding to clean up.

We like the plugin, we are simply asking you to make it more resource friendly.

[19-Nov-2015 15:40:58 UTC] RFG - Check if manual update notice should be displayed
[19-Nov-2015 15:40:58 UTC] RFG - There is no pending manual update
[19-Nov-2015 15:40:58 UTC] RFG - Check if automatic update notice should be displayed
[19-Nov-2015 15:40:58 UTC] RFG - There was no automatic update

@lbasurto
You need to gather some data to help the publisher track down the problem.

Have you turned on WordPress debugging to check for error messages?
Do you have any errors in your web server logs?
Have you installed or updated any other plugins that might have a conflict?

@charmedlife your site is hosted at GoDaddy.
You have 2 choices to resolve this problem:
1) use Postman SMTP and the Gmail API
2) Remove any and all SMTP plugins since GoDaddy is going to prevent them from working properly.

GoDaddy has a proxy that automatically captures any email handled by PHP mail() and routes it through port 25 to its relay servers. You CANNOT bypass that security measure so disable the SMTP plugin.

If your site owner email address uses the same domain as the website, GoDaddy will send mail to recipients at mulhollandsecurity.com. However, the majority of that email is going to be flagged as spam.

Create a @gateslosangeles.com forwarder using the free pack GoDaddy put in your account. Forward that email address to [email protected]. Use the forwarder for your site owner email and contact form recipient and you’ll get every message.

You’ll need to add an SPF record for gateslosangeles.com that has the GoDaddy SPF include and an IP4 entry for the site’s IP address.

Example SPF for gateslosangeles.com with GoDaddy forwarders:
v=spf1 ip4:160.153.42.70 include:secureserver.net ~all

“GoDaddy hosted forwarder or email account” means exactly that, the email is hosted at GoDaddy.

Explore your GoDaddy Products tab so you are familiar with your account.

— This is regarding GoDaddy hosting only. The Postman SMTP plugin is brilliant and the Easy WP SMTP plugin with work with the majority of hosting companies.

Jason, NO, you didn’t really fix anything. You are simply making it look like you did by duplicating what is happening automatically on the hosting server. Your plugin (or any SMTP plugin on a GoDaddy site) is not actually doing anything in this particular case.

Using an SMTP plugin for GoDaddy WordPress hosting is a completely useless extra step. GoDaddy will automatically route all PHP mail() email through their proxy controlled relay servers no matter what you attempt to do with scripts or plugins. Email from a GoDaddy hosted site can only be delivered to GoDaddy hosted forwarders or email accounts.

Even in this particular case where it looks like the plugin is doing the job, the efforts of the plugin are completely ignored on the server.

Per GoDaddy server admin staff; their antispam measures are hardcoded into the servers so that wp_mail() will always use PHP mail() and PHP mail() will always send mail through their relay servers. Any email is automatically whitelisted when sent from any of their website hosting accounts to GoDaddy hosted email accounts. Don’t ignore the SPF record though, that should always be setup to ensure normal email delivery.

No need to argue, just try using the plugin to send email directly to a Gmail account or any mailbox not hosted by GoDaddy. It will fail.

THIS IS VERY SIMPLE.
You absolutely cannot get around GoDaddy’s antispam security measures. You don’t need to install anything if, like @andrethierry, your website & email are hosted by GoDaddy. Just make sure your WordPress site owner email address and your contact forms send mail TO a GoDaddy hosted forwarder or email account. Andre was just working too hard (just like many of us have) to solve a expected problem when GoDaddy already had a super simple solution hardcoded into the server.

Looking at your domain, you don’t have to do anything.
Your MX record is pointing to GoDaddy so your email is setup there.

Just make sure your contact forms send TO your andrethierry.com email address. Then check the site owner email address in WordPress General Settings to make sure it has a andrethierry.com email address.

Login to WordPress, click Settings on left side menu, click General.

If you want WordPress alerts/notifications to do to a different email address that is not hosted at GoDaddy, setup a GoDaddy forwarder for it.

To send from WordPress to [email protected] you would create a forwarder [email protected] in your GoDaddy account and add [email protected] as the destination. Then in WordPress you would use [email protected].