JohnNadeau

You’re welcome.

Too bad regarding #2.

What about #1 ?

Thanks

… oops… also meant to end with:

Once we changed our Outgoing SMTP settings from within Postman SMTP… all is good !

Just a quick Thank You to Jeremy @jeherve!

I’ve been going around/and/around with our WebHost (SiteGround). We have two WordPress sites on the same server that have been sending emails from our JetPack Contact Form flawlessly for over a year. Nothing has changed on our end. Then recently, email notifications of submissions stopped on both sites. I’m convinced that something had changed on SiteGround’s end, but they couldn’t figure it out. At Jeremy’s recommendation above, we installed Postman SMTP. It could not send a test email without changing all of the Outgoing SMTP settings. Once we changed our Outgoing SMTP settings from within Postman SMTP… all is good !

Just a quick Thank You to Jeremy @jeherve!

I’ve been going around/and/around with our WebHost (SiteGround). We have two WordPress sites on the same server that have been sending emails from our JetPack Contact Form flawlessly for over a year. Nothing has changed on our end. Then recently, email notifications of submissions stopped on both sites. I’m convinced that something had changed on SiteGround’s end, but they couldn’t figure it out. At Jeremy’s recommendation above, we installed Postman SMTP. It could not send a test email without changing all of the Outgoing SMTP settings.

Was this fixed in the latest version of your plugin 0.5.5 ?

We generally update our plugins within a week or two, so perhaps I’ve never seen a plugin flagged in the Plugin Screen when it is “substantially old”.

Having the “Updated X Days Ago” would be a good inline reminder as Plugin Updates are getting more mature.

By-the-way… I made the changes (outlined in the link first post) and it passed the SiteGround PHP Test. I upgraded to PHP 7.0.17 and it’s been running fine on two sites. So now, it’s just a matter of someone making the changes to the plugin for the next update ??

Hey @lindzconnell

Any word on using this plugin on an SSL/HTTPS website?

About 3 months ago, you said “very soon”.

Diverse Solutions has really dropped the ball on this! Google has been advising Web Masters of the direction of HTTPS/SSL for quite some time now.

Do we need to start shopping for another provider?

Thanks,

John

Hey @researcher

Did you run an A/B tests to isolate the high CPU usage to this plugin?

Test A: Plugin enabled = high CPU usage

Test B: Plugin disabled = low CPU usage

I ran SiteGround’s PHP Config tool (found within their SG Optimizer Plogin) to check PHP 7.0 Compatibility.

It reported back the following for your plugin:

Shortcodes Ultimate. See Errors:
FILE: /wp-content/plugins/shortcodes-ultimate/inc/core/tools.php
————————————–
FOUND 1 ERROR AFFECTING 1 LINE
————————————–
681 | ERROR | Using ‘break’ outside of a loop or switch structure is invalid and will throw a fatal error since PHP 7.0

Are you planning on making the changes for PHP7 compatibility ?

Hi Chris,

I ran SiteGround’s PHP Config tool (found within their SG Optimizer Plogin) to check PHP 7.0 Compatibility.

It reported back the following for your plugin:

Check Email See Errors:
FILE: /wp-content/plugins/check-email/plugin-register.class.php
——————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
——————————————–
35 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.

Are you planning on making the changes for PHP7 compatibility ?

Hey @carcarg

I sure would like to know if 4.7.3 solves your problem.

Thanks,

John

@ivanatanasov Thank you. I’ll check in with you at the Support Ticket.

@jeherve Thank you. THAT resolved it!

I was able to add “/wp-json/wp/v2/posts/” to the “Exclude URLs From Dynamic Caching” in the SG SuperCacher Plugin Dashboard at LeLac’s site.

I tried it with the full https://domain, but it didn’t work until I truncated it to the “path” only.

See screenshot here: https://snag.gy/wKMo6k.jpg

Thanks again for all of your help and insight!!!!!

John

Hi Jeremy,

Yes, I think you identified the issue!

We use SG SuperCache v2.3.2 on both sites.

I A/B tested it:
Loaded LakePath.com page in browser
Waited 5 minutes
Shift/Refreshed Webage in browser
A=No change in displayed posts.
Purged the SG SuperCache at LeLacAppelle.com
Shift/Refreshed Webage in browser
B=New set of posts were displayed.

Note: SG SuperCache was renamed to SG Optimizer v3.05. As of last night, they were having problems with it causing high CPU usage, so I rolled back and did testing above under v.2.3.2.

Are there any changes I can make in the code snippet we’re using to force it to bypass the cache, or should I reach out to SiteGround?

Thanks,

John

Hi Jeremy,

Sorry for my absence ??

I was finally able to update both sites to 4.7.2, all plugins, including your’s, and make the code snippets changes on both sites as well.

Result: it does pull the posts in randomly, but it does not appear to refresh them… even after 30 minutes.

These are the code snippets I currently have in Child Functions.php on both sites. Do you have any thoughts/suggestions?:

/* JRN Note Changes default cache of 10 minutes to refresh posts */
function jeherve_custom_api_embeds_caching() {
	return 1 * MINUTE_IN_SECONDS;
}
add_filter( 'jeherve_post_embed_posts_cache', 'jeherve_custom_api_embeds_caching' );

/* JRN Note Jeremy had me add to fix rand sort */

add_filter( 'rest_post_collection_params', 'my_prefix_add_rest_orderby_params', 10, 1 );

function my_prefix_add_rest_orderby_params( $params ) {
    $params['orderby']['enum'][] = 'rand';

    return $params;
}