lowertownmedia

I was able to solve the issue as I learned the script needs to specify the JSON value to pass to the target variable:

function update_user_status_to_pending_from_api (\WP_REST_Request $request){
$parameters = $request->get_json_params();
$userID = $parameters[“id”];
wp_set_object_terms( $userID, array( ‘pending’ ), ‘user_status’, false );
clean_object_term_cache( $userID, ‘user_status’ );
}

Thanks, this is helpful. I modified my function to this:

function update_user_status_to_pending_from_api ( $request){
$userID = get_json_params();
wp_set_object_terms( $userID, array( ‘pending’ ), ‘user_status’, false );
clean_object_term_cache( $userID, ‘user_status’ );
}

The function fires when I call it via my make.com RestAPI module and I have userID in the JSON body, but the script does not consume the value. Even if I append ?=UserID=3 to the URL the script ignores the value.

Your continued help is greatly appreciated!

Ian

As a next step I disabled all plugins except the essentials on my production sites and was unsuccessful.

I was also not able to reproduce this issue on my single site WordPress instance on a test server running Nginx. The php.ini and nginx settings as they relate to cache are the same so the only difference I’m noticing is my production instance is running a WP multi-site implementation which one wouldn’t think would make a difference in caching.

Any help is appreciated. I cannot productionize my sites until this is resolved.

Ian D. Campbell
Lowertown Media Company

Hi. I’ve made certain the Nginx caching is disabled and that I have no cache plugin installed. I’ve also made an implicit insert into wp-config.php of “define(‘WP_CACHE’,false);”

Thanks,

Ian D. Campbell
Lowertown Media Company

Hello @zahardoc and @keleigh824,

I was finally able to confirm the issue was with my SSL configuration by using several validation tools. Finally, using an openssl command (openssl s_client -connect lowertownmedia.com:443) I received an error that openssl could not retrieve the first certificate in the chain. It was suggested on an SSL forum to update my virtual host file to replace the reference to the cert.pem with fullchain.pem. Apple iTunes picked up the episodes immediately! I’m still dealing with errors from the other services but will post a separate forum entry if needed. Thanks again all!

Hi @zahardoc

You will see the current episodes in the RSS feed here

Episode 1 and Episode 2 URLs are enclosed.

It should also be noted that, Amazon, iHeart Radio and castvalidator reject the updated RSS feed with error “FATAL: SSL certificate problem: unable to get local issuer certificate. Failed to download feed from https://lowertownmedia.com/feed/podcast/cullenandfriends/”. Bear in mind that the letsencrypt cert has been the same since the server build and the publishing of the previously deleted (and what is currently showing on all platforms) episode.

I really, really like the Seriously Simple plugin and it appears to be the best plugin to support multiple podcasts. I would only consider an alternative if I can’t get this resolved.

Thank you again for your continual support.

Ian D. Campbell
Lowertown Media Company

@zahardoc you were correct that the second episode was not uploaded by me until this morning. My main concern is that the other episode has yet to propagate to any service. The Apple Podcasters website says the last RSS crawl was 8/22 which was a day after I uploaded the first episode. The current episodes are published with a current date or date in the past, all mp3s and all belong to the proper podcast record. Also bear in mind that all of the Podcast platforms to which I post are retaining an old episode that I deleted at least a month ago. Any additional assistance is greatly appreciated, thank you!

Ian D. Campbell
Lowertown Media Company

• This reply was modified 2 years, 3 months ago by lowertownmedia.

Thanks @zahardoc!

I’m using the Podcast Feed URL provided by Simply Podcasting which indeed is an html page. I’m not sure if there is a setting to make it XML? Something has had to have changed in settings, because the first promo episode propagated to all services correctly back in July. I’ve since removed that episode and added another two which are still not propagating to any services.

I took your recommendation and removed any WP caching plugins, which with Nginx caching shouldn’t be necessary. I am concerned though that you mentioned the providers could be relying on a cached page. I’d prefer not to disable caching at the web server level, but I’ll try anything at this point to get the podcast to properly propagate.

I also noticed that both iHeart as well as castfeedvalidator.com is complaining about my SSL cert: “FATAL: SSL certificate problem: unable to get local issuer certificate. Failed to download feed from https://lowertownmedia.com/?feed=podcast&podcast_series=cullenandfriends” I’m using a letsencrypt cert which is valid.

Thanks and your help is appreciated!

• This reply was modified 2 years, 3 months ago by lowertownmedia.

Thanks, @keleigh824!

Here is what I’ve tried based on your feedback:

It’s interesting that castfeedvalidator always times out at 2513 milliseconds but running a validation test via podba.se returns in .2 seconds. I’ve also ran the plain RSS URL through an international html tester and the page loads between .61 (Denver) and 1.17 (Bogota) seconds. I have both php caching and html caching (via Nginx) enabled on the server.

As far as my reading page settings in WP, the default values of 10 are set.

I am still suspicious it’s a performance or plugin issue, especially since ALL of my podcast platforms (iHeart, iTunes, Amazon, Google) aren’t receiving RSS updates. The platforms currently display an episode which I deleted weeks ago and do not display the newest episode I uploaded a few days ago.

Any additional troubleshooting steps would be greatly appreciated!

Ian D. Campbell
Lowertown Media Company