jgoldbloom

I ended up writing my own sidebar widget which is then loaded as a shortcut via the No Cache Ajax Widgets plugin, works great including the post link and pagination. Works with Comet Cache plugin and my fully cached home page since it’s called AJAX.

The widget has options for title, number of posts and type (topics or posts) combined into one widget. I accounted for excluded forums.

See it in action at https://www.cancerdefiance.net right sidebar where I opted to name it “Recent Forum Activity” limited to 10 posts. Looks identical to the Asgaros widgets.

If any developer wants to try this, let me know and I’ll post code here.

But I still would like to see the Asgaros widgets post links work, this solution of mine was done as I’m launching before @asgaros is back, so had to be done.

Followup:

For now in the bottom of wp-config.php (also works in child theme functions.php) I added a simple domain check to set a constant which if defined dynamically handles plugin deactivation/activation following WP API standards:

if (defined('DEVELOPEMENT_SITE')) {
		
	deactivate_plugins(array(ABSPATH.'wp-content/plugins/wp-fastest-cache/wpFastestCache.php',ABSPATH.'wp-content/plugins/wp-fastest-cache-premium/wpFastestCachePremium.php'));
	  
}
else {
	
	activate_plugins(array(ABSPATH.'wp-content/plugins/wp-fastest-cache/wpFastestCache.php',ABSPATH.'wp-content/plugins/wp-fastest-cache-premium/wpFastestCachePremium.php'));

	
}

I won’t include the line that sets the constant as that’s proprietary but for anyone else the above gets it done as an interim solution. Note the array includes both free/premium versions so edit for your needs. Also, the WP function to activate won’t reactivate a plugin already activated.

I really wish this technique was not necessary – I firmly advocate agnostic domains and feel plugin authors should account for that and make it so developers need not be required from their customer base for basic/critical situations like dev/prod environments. My .02.

Disregard, solved.

FYI, the feed URL and W3C validation:

https://validator.w3.org/feed/check.cgi?url=https%3A//www.cancerdefiance.net/feed/forum

Okay, remember this is about the subject line not the body. The issue is when character encoding is UTF-8 in the headser the subject line must be ASCII.

Details on this including a work around: https://ncona.com/2011/06/using-utf-8-characters-on-an-e-mail-subject/

But might be just simple to entity decode the subject line and retain your header.

Below is an example of actual headers from a typical email which led me to this with the ***subject line*** modified by me for this support forum post:

[Cancer Defiance Support Network] New answer: jim ***& #039;***s test
To: [email protected]
Mime-Version: 1.0
Content-Type: text/html; charset=UTF-8
Envelope-To: [email protected]
X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer)
Return-Path: <[email protected]>
Return-Path: <[email protected]>
Delivery-Date: Wed, 22 Mar 2017 07:39:21 -0400
Message-Id: <[email protected]>
Received: from server.cancerdefiance.com by server.cancerdefiance.com (Dovecot) with LMTP id iJmIBmli0lihSQAAD4BhsQ for <[email protected]>; Wed, 22 Mar 2017 07:39:21 -0400
Received: from ip72-219-201-235.dc.dc.cox.net ([72.219.201.235]:60439 helo=local-cancerdefiance.net) by server.cancerdefiance.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <[email protected]>) id 1cqebp-0004tf-0X for [email protected]; Wed, 22 Mar 2017 07:39:21 -0400
Delivered-To: [email protected]

Nope and using standard Mac mail. I will look deeper on my end try different mail clients plus examine the headers.

This support forum decoded my example above even though I encased it in a code block — sigh. I’m referring to the apostrophy ‘ which became &amp… Etc

Ugh

Ah, got it, thank you for both.

I can’t tell ya how refreshing it is to see a notice to users like this as opposed to some plugin authors who just silently disappear for months or longer. Have a safe/happy trip and yes –> I’m brown nosing. Yeah, I said it! ??

Hide it via CSS:

.asgarosforum-widget .widget-avatar img {

    display: none;
}

If advise using your theme custom/additional CSS if present or setting up a child theme and overriding styles there so no need to re-apply stuff on plugin updates.

Now the upper case first/last setting for display name in the same UM options area does not work – I easily resolved this with CSS but just letting you know. I am moving on – thanks again.

I understand completely. No problemo!

Cheers and enjoy the time off.

??

Yep, Forums/Subs and topics – the latter is my wish list numero uno.

I agree on WP core needing maturity, but could be ages, so:

Just wanted to ensure this didn’t drop entirely off the radar, I did not expect immediate action when I said sooner. If not possible for 1.4.4 in even a basic format enjoy your upcoming hiatus and I’ll put my developer hat back on and do a custom implementation as I have a deadline for launch before your return.

On a side note syndication is as powerful as SEO (and beyond local subscription) to bring in external traffic and expose a site beyond it’s web presence. Plus feed aggregation and daily news/feeds reading is so easy these days for end users both in OS’s and other popular means. So this is an important feature in the long run, my .02 based on experience.

Cheers for the effort, no matter the recent outcome — truly appreciated. ?? ‘Nuff said on my part unless any followup needed.

I did not know that option existed, that resolves the issue, thank you.

Please niote, with all due respect, WP already has this option – I am perplexed UM was built with an override – seems over engineered in my opinion regarding this setting. And, your last response was much more targeted, far more sensible and better for time management for both of us than the SOP conflict test response. If this was a complex issue, that would be proper. This is not.

Sigh, but thanks.

Yep, thanks!