tf5_bassist

Thanks for the quick response! Yeah, I’m not seeing any of that. Here’s a screen recording of what settings are saved, and what happens when I either bulk or single regenerate:

https://1drv.ms/v/s!At3BYw_MFTvp2WoinE2zWRb20QCu?e=ACevha

Thanks for the update!

Yeah, there’s nothing crazy going on with post types, and I’m only getting the spam comments on regular posts, which is really all that the site has.

I’ll look into running Akismet, and may end up pulling the trigger on the wpDiscuz bundle, depending on a few things.

Yay!

Looks like the WP Staging page shows an error stating that the current version isn’t compatible with WP 5.3.2. The plugin page does show tested with 5.3.2, however. Which one’s right? ????

Yeah, I recall that one, it was a different plugin that they offloaded to some other devs. It was just the plain ol’ free captcha plugin, whereas the current reCaptcha plugin uses the Google reCaptcha methods.

There’s been zero communication about this anywhere. Not on the blog, not on Twitter, not here. And it’s not even the first time this has happened to this plugin lmao.

Yeah, I didn’t see anything in the feature lists for customizable tracking, so figured it wasn’t there.

I did shoot a support ticket to their Lite support page, and Chris got back to me, so we’ll see if there’s anything they have for it.

Yeah, I had a feeling it would come down to getting Monster Insights to somehow not track the TA links. I don’t know if this option is hidden somewhere in the MI Pro feature set since I just use the free version, I wouldn’t be surprised that if they added the feature it would live there.

I’ll keep poking around and see what my options are there, and probably submit a ticket to the MI site if I can’t find any options.

At least it’s not just me, though, and I didn’t miss anything stupidly simple haha. Thanks for the quick reply!

…. only TLS 1.3? That’s not even really supported by a majority of browsers… lol. That’s pretty dumb haha.

https://caniuse.com/#feat=tls1-3

Found the issue. Runcloud performed a system-wide application rebuild process affecting all the deployed apps for all customers. This involved disabling TLS 1.0. For some odd reason, my AWS CF distribution origin was set to SSLv3/TLS 1.0, with TLS 1.1 and 1.2 disabled. wtf. Enabling TLS 1.1 and 1.2, killing 1.0 and SSLv3 on the origin settings resolved the issue.

Runcloud not only didn’t tell anyone the rebuild was disabling TLS 1.0, they didn’t tell anyone the rebuild was happening. So, that’s that. Hooray for excellent communication with customers. :/

Oh wow haha. Thanks for the quick response guys, and thanks for the video. Makes sense as to why it’s being done. In theory, it shouldn’t be too much impact on sites that use Amazon affiliates decloaked, but I’ll turn it on and give it a whirl.

Hey Josh, thanks for the quick response! Noted, future bugs/requests will go via the support ticket system, thanks!

Re the first bug, I understand that it does the decloaking on the front end, which works for text links. It’s only the Insert Image function that doesn’t decloak the link. You can see this in action here: https://www.creatorbeat.com/video/how-to-pick-the-best-teleprompter-for-more-professional-videos/

I’ll try to get some screenshots or screen recordings of the post edit screen and spacing issues with the inserted images soon, hopefully it will come across accurately.

Thanks again!

I was under the impression that comments did allow shortcodes. I mean, why would the shortcodes be in the edit comments reply page if they didn’t, right? lol. Well, guess not.

Disabled my fix, disabled wpDiscuz, and no-go on the shortcodes working.

For those who are wondering, you can allow shortcodes by dropping these in your functions.php code:

add_filter( ‘comment_text’, ‘shortcode_unautop’);
add_filter( ‘comment_text’, ‘do_shortcode’ );

So, I think I found out what may have happened. I’ve set up the ACM SSL certificate so that should be good, but the distribution/origin in W3TC is pointing to “www.creatorbeat.com” as the distribution name.

But the origin name in Cloudfront shows the name as “creatorbeat.com”. I think that when going through and migrating everything over to be a uniform URL of “https://www.creatorbeat.com”, I think I may have somehow changed the distribution name in the database. But I can’t find where (if any) the distribution is stored in the WP DB. Nor can I find any config files where it would have been written. Does anyone know where this actually is located?