The article is here: https://www.cloudways.com/blog/gutenberg-wordpress-custom-post-type/

The fix is in the comment by John Laprairie who provides an extended list of array values for 'supports'.

In particular, at least the 'title' value is required or when a new CPT is added, there will be no 'Add Title' field in the Gutenberg editor and no way to add a title for the CPT.

It's easy to overlook the correct comment and simply use the code in the article with the expectation that it should work, without having to spend considerable time debugging. Maybe there has been an update to Gutenberg which requires the 'title' value, after this article was initially written 11 months ago.

The article was written February 11, 2019 , the comment with the correct code was written 5 months ago (August 2019). IMHO it's a pretty poor show that it is still not corrected in January 2020 and isn't on a par with other articles I have read on Cloudways.

BTW, this 'feedback' subdomain appears not to have a SSL certificate. Just sayin'.

Hello Guys,Hope everybody is doing great! The purpose of me to visit here is to clear out my confusion about where to hire the cheap yet best Crypto Fund Administrator. Actually, after researching a lot and asked many people have increased my confusion. Now I am not able to decide for which company I need to go with. That’s the reason I visit here and want an exact answer from you all. Please suggest me the name of the company that offers the ideal yet affordable fund administrator services. It is my request that tell me the name of the company along with your experience with that particular company. Apart from this, you can share the prices of their services. I would extremely be overwhelmed and grateful for your favor. Eagerly waiting for your answers!

Visit- https://ascentfundservices.com/switch-administrator/

Hi

I notice that recently you have put in place tools which force a strong username and password for staging sites. Previously the username and password could be anything at all.

I'd like to suggest that you should roll back this change. Although (of course!) I am wholly in agreement that passwords should be strong in almost all cases, I believe that staging sites should have an option for this not to be the case.

Why?

1. Mainly - because the most obvious use case here is for sharing with a client. Whereas we could previously have for instance "demo" and client name as u/p (easily memorable both for us and for clients) - now we have to create and constantly re-share passwords when the client can't remember how to get in




2. Password managers don't normally offer the option to save popup NTCR-style passwords like this so we have to resort to logging into the CloudWays interface to see what is set




3. The actual thing that is being passworded isn't very sensitive - and actually shouldn't be. A staging site is almost always just a copy of a live site where tech changes have been made. In our case, the only reason for passwording it in the first place is that we don't want Google and other bots spidering it - it isn't sensitive at all.




4. If you left this option so that you had a warning there about weak passwords - "Are you SURE you don't want a strong password for this?" then IT people like myself can make a call on whether to set it as strong or weak, depending on use case. Mandating it in the way you do is preaching to an already tech-savvy audience!

I don't know if it's just me, but the support quality and speed has been degraded fast lately..

When I just became customer @Cloudways (like a year ago) support was fast and helpful. They took time and really looked into my issues.

Now it's a whole different story. Today for example, I have been on the chat for OVER 2 HOURS. Literally. All this time waiting, following up what the status was, if they weredoing anything. Very little replies. After an hour the first real reply came in which totally missed the boat, wasn't even related to my question.

I pointed this out on the chat and I was transfered to another agent which took a little time for like 2 minutes and then stopped replying too. Also messages are only read half, I need to point out things multiple times which I already mentioned.

When I pointed out this on the chat I received: "actually i am dealing with multiple customers which is wy it got delayed in the response"

We pay a serious extra for the 'managed service and support'. I mean, the prices of DigitalOcean servers are more than doubled. Which is totally find, but please keep your support and service in check..!

More staff maybe?

Oh, and my issue isn't resolved yet. Has been transfered to a ticket, so after 2 hours chatting with really not that much helpful feedback, I now have to wait for a reply on the ticket.