irishetcher
Forum Replies Created
-
Forum: Reviews
In reply to: [Gutenberg] Bad ExperienceYou need to install a plugin to disable Gutenberg. Either Classic Editor Plugin or Disable Gutenberg is a good choice. There are other methods if you want to research those too. Once you apply one of these you should be returned to what you had before so long as you haven’t modified anything drastically by using Gutenberg.
Bottom line. Gutenberg (new block editor) can be problematic with sites that have been built with older plugins and custom coding. The new block editor also follows a whole new way of working with different workflows that don’t match the way WordPress has mainly worked up until now.
How you deal with this will vary from user to user. Personally all work I do with WordPress will remain using the older editor. I will continue to asses how the new block editor progresses and if it matures into something more usable and less buggy, will consider using full time on new projects. This could take a year or two, depending on how involved the way you work is tied to the old editor and how easy it is to convert to a new way of working with the new editor. You probably also need to consider using themes that are compatible with the new editor.
Forum: Reviews
In reply to: [Gutenberg] UN ERRORE SUI POSTIf I am correct in translating the above, by making some simple adjustments in how the new block editor functions, on top of better usability, it would improve its acceptance. Many on these forums are making valid and obvious points on why Gutenberg just isn’t working for them. It’s a real shame that the team behind the new editor don’t recognise this and make some enhancements to address these concerns.
- This reply was modified 7 years, 4 months ago by irishetcher.
Forum: Reviews
In reply to: [Gutenberg] No. Dumb. Big mistake.While I think there is a place for some sort of UX in the back end, the more I use the new block editor the more that I see that the wrong path has been taken with it because it disregards the methodologies and workflows that have take years to perfect and replaced it with something that is so narrow that it makes WordPress less useable.
Yes there are aspects of Gutenberg that have merit and in fact are way overdue and should have been integrated years ago but there are many other things that have been neglected and are still not addressed. Many of the good things about the new editor could have been implemented in a non disruptive way so as not to cause issues with the classic editor and cause so many issues with sites.
The thing is though it looks that the next phase is going to be another radical departure and it looks like those behind this opinionated approach are not for turning.
So what if the TinyMCE/metabox interface looks a bit dated, it works! And exactly as you say PHP, HTML, CSS, and Javascript tightly as code.
He also mentions Digital Experience Platform (DXP), something vaguely defined at this stage to what it will actually do.
See I think that web users just see websites where others want to contrive new experiences for what they believe is staying relevant.
- This reply was modified 7 years, 4 months ago by Jan Dembowski.
- This reply was modified 7 years, 4 months ago by Andrew Nevins. Reason: Removed advertisement of article
Forum: Reviews
In reply to: [Gutenberg] Breaks my Divi page builderIf the issue is you are getting the new block editor (Gutenberg) loading where the old editor was in the back end, make sure you have the latest version of Divi installed. Then go to Divi > Theme Options > Builder > Advanced tab and enable the option for Classic editor. This will prevent the block editor from loading and you should have older editor with Divi presented.
Forum: Plugins
In reply to: [Advanced Editor Tools] Nice update but some issuesThanks for the clarifications.
Will watch out for updates and keep investigating workarounds. Agree, you can end up with too many checkboxes and settings.
Forum: Plugins
In reply to: [Advanced Editor Tools] Nice update but some issuesA number of things.
I notice that when I create a new post, a classic paragraph gets added automatically. Perhaps some settings to set what happens by default, Classic Block, Classic Paragraph or user defined ( none with option to add other types of blocks). I notice if you try to remove the initial classic paragraph, a new one is added again, straight away. And the + to the left stops working after deleting/re-appearance of the classic paragraph. Switching it to a classic block, doing a add a different block type, then delete the classic block, dance is the current workaround.
Generally when you add a Classic paragraph there is no + icons underneath
to add other types of blocks.Similarly when you add columns, a classic paragraph gets automatically added. Users might want to add a different type of block. There is a few workarounds like converting deleting but these are a bit cumbersome with the wack-a-mole nature of Gutenberg.
Not sure if the following is a feature but in the process of fiddling with blocks and what I think was a kadence block row with two columns, then viewing and going back to edit, fixing/resolving a breakage by converting to classic block, I ended up with that classic block with two paragraphs in two columns. Checking the html isee it wrapped in some classed divs
<div class=”wp-block-columns has-2-columns”>
<div class=”wp-block-column”>
<p data-tadv-p=”keep”>content</p>
</div>
<p data-tadv-p=”keep”></p>
<div class=”wp-block-column”>
<p data-tadv-p=”keep”>Content</p>
</div>
</div>It actually looks quite nice but I cannot reproduce this? The only thing I can think of is that it’s part of the new block editors resolve mechanism.
- This reply was modified 7 years, 4 months ago by irishetcher.
- This reply was modified 7 years, 4 months ago by irishetcher.
- This reply was modified 7 years, 4 months ago by irishetcher.
- This reply was modified 7 years, 4 months ago by irishetcher.
Forum: Plugins
In reply to: [Advanced Editor Tools] Nice update but some issuesThanks Andrew.
That sorted all the issues in my opening post, even putting the blocks into the various column options. Great work.
I like the way you can transform from classic block to classic paragraph to paragraph and back again and combine blocks back to one classic block again.
- This reply was modified 7 years, 4 months ago by irishetcher.
Forum: Reviews
In reply to: [Gutenberg] Ash Tray on A MotorbikeAnd TinyMCE Advanced. Great edition. Now has a setting to be the one and only thing on the block. If turn its content into blocks, update/reload, Voilà, every thing back in the one classic block.
I see some good in the new block editor, but, not a lot right about it either. I feel the pain of all those struggling with it.
Forum: Plugins
In reply to: [Advanced Editor Tools] Nice update but some issuesUPDATE:
Putting Classic Blocks into columns, kadence or the standard ones seems to be problematic. Best avoided.
Forum: Reviews
In reply to: [Advanced Editor Tools] Wow – now supporting WP5!I concur. When configured it will keep everything in one block. If you even turn it into blocks, for experimental reasons, reload the page/view and return to edit. it automatically puts everything into a block.
Some caveats. Depending on your theme you will get some unwanted results. Mixing in with other blocks and the block breaks. So as always, things are weakened by the precarious nature of the new block editor.
Forum: Reviews
In reply to: [Block Gallery - Photo Gallery Gutenberg Blocks] Nicely executedHave been on the bleeding edge with beta updater plugin. Waiting for themes to be updates and looking to see if the core team add much needed features that will bring the editor up to match what the current backend editor dashboard editor can do in terms of the workflows I use.
I’ll be straight up. I am not a complete fan of the new block editor at the moment and how it is being introduced in such a forceful manner. The approach of shoving out the current editor as if it needs to be a separate plugin when, in fact it is still in core, is particularly aggravating. Classic Editor plugin is just a sophisticated switch to disable/control the new editor.
But hey, I don’t want to detract from the genuine work block developers are doing. I keep some test sites with everything up to date so I can find out what all the new options are and become adept at using them once I am ready to go full tilt with the new editor.
Forum: Plugins
In reply to: [Block Gallery - Photo Gallery Gutenberg Blocks] Redundant WarningCheers
Forum: Reviews
In reply to: [Gutenberg] Looks nice, works fine, horrible to use.Couldn’t agree with you more. The whole project screams of missed opportunities in many places and its slowness and bugginess is the nail in the coffin. Not for the developers, mind you, but the users like you, me and third party developers sitting on the fence waiting to see what pans out and what the options and alternatives are.
Given the zeal that this is being pushed a lot of goodwill could have been invested by not making it default, keeping the current editor default with a simple switch in settings and indicating a far longer lead in time. But, alas, a big Ulster says No!!!
- This reply was modified 7 years, 5 months ago by irishetcher.
Forum: Reviews
In reply to: [Gutenberg] They intentionally crippled the text editorYep, it is very disappointing, considering the potential of Gutenberg and how much better it could be if it addressed some of the basics you listed above.
WordPress has been screaming for years for improvements in the area of the text editor, and the block editor is a missed opportunity. With all the comment tags mixed in for delineation of blocks it is more urgent that we have text editor that can highlight the structure of the code. The mind boggles when you consider that code mirror was only introduced recently in WordPress but only make an appearance in the HTML block. How bonkers is that? It needs to be developed further and pushed into other corners of WordPress. I like the fact that I can zoom in on one block and get to see the HTML. What I don’t like is looking at a jumble of unformatted black code on a white background.
As for blocks, on their own they are no bad thing but the project focused in at too granular a level with paragraphs while ignoring higher layout structures such as sections, rows and columns. The column block is a poor implementation. Also bonkers in that the block editor was supposed to be a unifying concept to rectify the issue of themes and builder using no compatible ways of bringing page layout to the CMS.
What I see now is several vendors with their own blocks and, in fairness to them, these do a decent job on the right theme (when they are not suffering from the breaking changes of the rapid development). But, I can foresee the same issues cropping up again regarding developers taking over sites and changing to a different theme and block plugins; the same amount work will be spent on re-doing content, leading on to the perpetuation of opinionated views on which piece of software is better than which.
On the notion that the block builder will make it easier to use than the current editor. You can bet your bottom dollar that a lack of WordPress experience will always lead to sites being messed up.
Yes, that update worked and now everything is rendered nicely on the front end. I am liking how all this is shaping up but I still am seeing the occasional resolve block which sometimes doesn’t resolve the issue a tall, just disappears the block.
Hopefully once WP gets the block editor out of its beta phase we will see things settle down so keep up the good work.
- This reply was modified 7 years, 5 months ago by irishetcher.