Pádraig ó Beirn

You can use the Disable Gutenberg plugin until your issue is resolved.

https://www.ads-software.com/plugins/disable-gutenberg/

The Disable Gutenberg plugin may be a better option.

https://www.ads-software.com/plugins/disable-gutenberg/

@travelseewrite
You can revert to the Classic Editor here:
https://www.ads-software.com/plugins/classic-editor/

Hi @it40,

I’ve tested Gutenberg with each release and every time I test just two things – whether or not I can manipulate my text and handle images as easily as the Classic editor. The answer for me is still no (at the time if writing). Unfortunately a multi-paragraph text model was not chosen. I haven’t moved beyond this to extensively testing embeds.

I don’t consider myself a developer but I’ve been working with WordPress since 2006 and know my way around the code. I am always happy to help others if I can but this is not the forum for that. I haven’t used the Snax plugin before and suggest contacting Snax support. Likewise for DigitalOcean. Contact me on Slack if you think I can be of any further help – @padraigobeirn

Also, don’t forget that you can install the Classic Editor plugin which will block Gutenberg (no pun intended ??) for the next couple of years. https://www.ads-software.com/plugins/classic-editor/

Hi @it40,

I’m sure from what you’ve written that you didn’t mean to give 5 stars. You can change the number of stars any time if you wish.

I’ve implemented the native WordPress commenting system which can be styled really well and, most importantly, works great on ALL areas of my site – category pages, static home pages and posts.

Thanks Ronald,

I appreciate it you looking into it. It must be something peculiar to my setup. I’ll stick with gravatar and the mystery man for now.

All the best,

Pádraig

Hi @priatnasuardi,

I was having the same problem and resolved it by creating a new project in the Google Developer console, then enabling the Picker API and creating your id credentials from there. You also need to enable the Drive API for the project. It’s tricky to set up but well worth it after a little perseverance. If you get it working please consider amending your 1 star.

At the time of writing, the quickest and easiest way you can change the colour on the front-end buttons etc. is by going to wp-content/plugins/deeper-comments/views/css/deeper.min.css and replacing all references to #437df9 with your own colour.

Please note that this is just a temporary fix until colour styling or child comment themes are implemented in the back-end. Until then you will have to replace the colour again each time the plugin is updated. A better way is to override the colour settings for the buttons in your own stylesheet so that plugin updates won’t affect your colour styles but there are 38 references to #437df9 in deeper.min.css so I just used a search & replace on that file to change them all for now.

Personally, I don’t think ‘No Comment’ is necessary if there aren’t any comments. You can hide it by putting this in your theme stylesheet:

.dpr-discu-main-loop-wrap h3{
display: none;
}

Thanks for the prompt reply. ????

Do you think it’s something you might implement in the next 12 months? I would keep my existing comment system for a year if it was on your development list but if it’s impossible and will never be implemented I will use something else that works with categories.

Best wishes,

Pádraig

While Eleonora’s response certainly deserves a round of applause your own outline above, @jdembowski, is simply excellent. I know you probably don’t have enough time in the day to interact like that with everyone but it’s absolutely brilliant to see. I gleaned a lot from it. Better reviews might be forthcoming if there were a few guiding questions in the review response form (like there are on the github form to help people make a good bug report) e.g. What do you like about this plugin? What do you not like? What features would you like to see? etc. If it was possible it might help guide people to making better reviews and save Tammie having to ask those questions, at least for some. In any case, thanks to you and the team for all your work. ????

Hi Kathy,

As a mere WordPress user, not a developer, I agree that Gutenberg should be optional but it’s always helpful to say what you didn’t like about your experience with it. There is a Classic Editor plugin which will continue to let you edit your posts as before. Also, your 5-star rating doesn’t reflect your review and if you want to change that you can.

@clorith – I have huge respect for the way you help and educate people on the forums, including me. ?? However, it would be worrying, in my opinion, if one-line reviews were considered for removal. There are also lots of 5-star Gutenberg reviews with one-liners containing something such as “the future of WordPress” or “long overdue” etc. and they shouldn’t be removed either even though they are not truly reviews. Best of luck with 4.9.8 and the Gutenberg callout. Although I have grave reservations I appreciate the amount of work gone into it and hope I can eventually use it as easily as the Classic editor.

You might want to check out the Classic Editor Addon plugin which is targeted at anyone who doesn’t want Gutenberg.
https://www.ads-software.com/plugins/classic-editor-addon

I am also toying with another CMS (Joomla) while I wait to see how Gutenberg is merged into core but the above plugin gives great peace of mind for anyone who has tried Gutenberg and prefers the Classic Editor. The Gutenberg team are working very hard on each release but, so far, it simply gets in the way of my writing unlike the Classic Editor. Hopefully this will change by the time it’s merged into core. I wouldn’t say RIP WordPress just yet. ??

I discovered the problem. I always download the latest version and install it manually via ftp as I have an images folder that is overwritten if I do the automatic update. When I clicked on the ‘download latest version’ button it wasn’t linked to the latest 4.6.9 version but 4.8.6. I had to update automatically and restore my images folder from a backup. The shortcodes now work as expected. Thanks very much.

• This reply was modified 6 years, 6 months ago by Pádraig ó Beirn.
• This reply was modified 6 years, 6 months ago by Pádraig ó Beirn.