[Hugh]

On your account page, copy the 2.2.5 link, change it to 2.3.1, download. Worked for me anyways.

[Hugh]

i saw Pippin's general email discussing it. This looks like the opportunity for him get out of WP so he can focus on the brewery. I've wondered for a while what his exit strategy may be - appears we now know.

(Reminded me i still need to get in touch with him for lunch. ... text sent.)

Cheers!

[Hugh]

What I did on most of my sites was to just update to the latest Disable Gutenberg. Jeff Starr added a setting to disable said Widget Block editor thingy (or whatever they're calling it).

[Hugh]

MXroute looks interesting. Hadn't seen it before. Thanks for the share.

[Hugh]

Here's another one to upvote: https://feedback.zionbuilder.io/roadmap/repeater-random-option

As I mention, easy peasy fix/addition.

[Hugh]

I saw your email. Looks like you spent a little bit of time with it. I concur with your assessment of their coding structure and such. I managed to find the options list for the Order By dropdown in the Query builder settings, then added rand to it. Works like a charm! Just need to get a pull request to them.

Speaking of which, BB, have you been on Github lately?

[Hugh]

As Full As Possible List of EIG Companies and Brands With Details (Beware EIG Hosting!)

Bookmark ^^^ that page if you haven't. Good resource to keep up with EIG hosting companies. Also has info on the Yoast acquisition, etc.

[Hugh]

Exciting news: Yoast joins Newfold Digital

https://hostingdiscussion.com/threads/newfold-digital-the-place-that-bough-eig-aquires-yoast-seo.78745/

I've never been a big fan of Yoast. Have a client site that is using them right now. We'll see how it goes from here.

And I didn't know EIG got bought by Newfold Digital. I don't have an opinion on that right now.

Thought this was good: https://onlinemediamasters.com/yoast-seo-premium-review/ (over a year old). And: https://onlinemediamasters.com/rank-math-vs-yoast/ (newer).

[Hugh]

Options:
1) Off: No encryption applied
2) Flexible: Encrypts traffic between the browser and Cloudflare
3) Full: Encrypts end-to-end, using a self signed certificate on the server
4) Full (strict): Encrypts end-to-end, but requires a trusted CA or Cloudflare Origin CA certificate on the server

Full vs Strict has to do with what type of certificate you have on your server. If it's not self signed, and an actual CA issued certificate, then you can use strict. Either way, the important thing is to have an actual CA certificate on your site (i.e. via Let's Encrypt), which it sounds like you do. After that, shouldn't really matter Full or Strict at Cloudflare.

If it is an upsell attempt, I've never seen it as being in your face about it.

[Hugh]

Sent first pull request. Simple one to help with me getting my workflows sorted out. We should probably have a short call (Zoom, or otherwise) to hammer out any details - and for me to have a "show and tell". Next week?

[Hugh]

I've been using (and liking) SourceTree for a while. Unless you have a better tool, I'm going with that. 🙂

[Hugh]

Perfect! I'm in.

I'll get things setup on my end as soon as possible to work with those repos.

[Hugh]

I concur with Paul, this would be a great series!

[Hugh]

It was like that last Friday. Anyway...

Thanks BB!

(We still need to talk some code. 🙂 )

[Hugh]

Ah, that explains it. 🙂

[Author]

Posts