azitlies
Forum Replies Created
-
Forum: Plugins
In reply to: [Classic Editor] After last update the html editor doesnt provide word wrap@vipini ???
You should look at the html (in the ‘text’ tab) of any page / post that isn’t acting as it should?
Look for any wordpress construct (wp-table, wp-paragraph, etc etc etc), that has the word ‘Block’ in it (IE wp-block-table). Then remove the word ‘block’.
I”m *guessing* that’s the problem. I had something just like it and that’s what was causing it. But if you don’t find anything as I’ve described, the problem is almost certainly caused by the CSS behind your html, **however** it’s being invoked.
Forum: Plugins
In reply to: [Classic Editor] After last update the html editor doesnt provide word wrapHad something similar happen before. I found that in the text mode, some of the html had been changed to their corresponding ‘block’ versions, iirc, it was like wp-table got changed to wp-block-table.
That means different css is going to be used, provided by your theme, so odd behavior is possible.
Double check that you have no ‘wp-block etc’ in the text.
Forum: Reviews
In reply to: [Classic Editor] Fixes Major Problem the WordPress Team CreatedHear! Hear!
Well said. Folks, do a search for ‘how to disable gutenberg’ and you’ll find many good ways to accomplish that (my favorite is a simple entry in functions.php).
But to the original point – having to jump through hoops (which may or may not exist in the future) to have the editor / environment that made WP so popular to begin with is… well… nonsensical and flabbergasting.
An (essentially) knife edge cut over like this is a huge bet, which may, due to the technical environment / limitations, turn out to be simply a fad.
Gutenberg absolutely should have been the plugin.
Forum: Plugins
In reply to: [Classic Editor] Issues with Classic editorHere’s something some of you may want to try; I’m using this method as it fits my needs (I have no need for gutenberg or any settings for it).
I think this will also help to eliminate the classic plugin as being the cause.
“Place the following code in your functions.php file:
add_filter(‘use_block_editor_for_post’, ‘__return_false’);”
(from blog aid dot net article by MaAnna Stephenson)
This should ideally be in a child theme’s functions.php, so the parent theme can be updated without affecting anything. But for testing purposes it can probably be placed in the parent (current) theme.
Deactivate the classic plugin after above. If you **still** have the same problems, I don’t see how it could be the classic plugins fault.
Forum: Plugins
In reply to: [Classic Editor] Can’t copy & paste in classic editorI just tested this, after a fresh wp 5.1 install and disable gutenberg plugin (among a few other quite basic plugins).
No problem copy and pasting into the visual tab and having it show up. One test was a copy and paste of some flat html from another site, another test was from a msft word document – specifically created with various fonts, sizes, colors. All worked fine.
I’d suggest you may have a plugin causing issues?
Forum: Plugins
In reply to: [Classic Editor] Copy-paste and keep formattingYes, and the only document type I’m aware of that allows this IS a word doc. Paste it into the ‘view’ tab, not the ‘text’ tab.
Forum: Plugins
In reply to: [Classic Editor] Editor Issues – I Think Caused by the Block EditorI found that same problem on many of my pages after the wp5 and block editor. Even installing the classic editor plugin didn’t get everything back to normal.
The editor is a critical aspect to wp. Amazingly so. I’ve tried cutting and pasting pdf files and it didn’t understand the formatting. But it does seem to understand the formatting of msft word files…
Anyway, in your case, just add <br /> at the end of ea line, that will cause the next line to start on a new line.
cheers
Forum: Plugins
In reply to: [Classic Editor] Deregister gutenberg scripts & stylesThis has been talked about a little so far. As far as I know, even after choosing Classic editor, at least 2 ‘block’ type css scripts are loaded with every page. They may have fixed that already… maybe not.
Forum: Plugins
In reply to: [Classic Editor] Thanks for Keeping the Classic EditorA site I manage uses at least 4 or 5 different tables. Only the classic editor is installed and they (the tables) adjust dynamically for the various devices (phones, tablets, etc) that access it.
It’s the theme. The theme has html and css (not all themes, but some), to allow for dynamic adjustments.
You don’t necessarily need a plugin to do it.
Forum: Plugins
In reply to: [Classic Editor] Remove Gutenberg CSSI’ve been able to dequeue those scripts using a child theme, their names are wp-block-library and wp-block-library-theme. I used wp_dequeue_style().
Totally agree that if one is using the Classic editor, they should not be loaded as they shouldn’t be used.
Cheers
Forum: Plugins
In reply to: [Classic Editor] version 1.2 creating wp-block-embedOkay, this is what i think happened;
Updating from wp 4.x.x to 5 (it’s now 5.1), made some changes by itself. I’m guessing because the default (only? there was no classic plugin installed) was the block editor, it modified some classes in the html;
A perfect example would be wp-table, I think became wp-block-table. I just finished changing all mine back to wp-table, now, the new twentysixteen theme looks as it should (word wrap, borders, etc), but it didn’t after the update because it was using (new) blocks.css and editor-blocks.css (in the new version of the theme).
I originally thought the classic plugin was the issue but it might have just been going to wp 5.x caused it. It *might* be wise to tell people to install the classic editor plugin prior to going to wp 5? If that’s even possible, as that editor is in core in 4.x.x?
It’s really not clear what changed it, and I’ve no way to test it now. So it’s updated and all working, alas.
I’d suggest one last thing, don’t say people are “afraid” to use the block editor… Me, I’ve used vi, dreamweaver, c++ and Java editors, programmed in assembler… etc etc etc
It’s not fear, it’s a matter of spending hours and hours and hours, to do what? Make your website look exactly as it does already?
That’s not fear, that’s avoiding wasting time. That’s why people resent it, if it’s not broke, don’t fix it.
Cheers
Forum: Reviews
In reply to: [Classic Editor] It’s called ‘Classic’ for a reasonMy understanding is that the powers at wp believe they will get more people to use wp if they have an editor that ‘non technical’ people are more likely to use…
imho, they are taking the wrong route for this goal. 1st, there’s no guarantee of reaching the goal, so why make the new editor the default? What if it fails?
Additionally, all the problems it’s causing existing customers. To many of us, this is kindof a nightmare. To have our website(s) we maintain become discombobulated and require hours and hours of time to figure out what’s wrong.
There’s an old saying ‘Don’t fix it if it ain’t broken’, apropos.
I’m sure they think that eventually everyone will move to the new editor and everything will be okay. It’s possible though that many core users will move to a different platform, and the ‘new people because of the easier editor’ simply won’t happen. People who don’t know what they’re doing lose interest fast.
The whole situation is causing quite a dilemma for many users.
Forum: Plugins
In reply to: [Classic Editor] version 1.2 creating wp-block-embedBut it happened simply by updating this plugin from ver 1.1 to 1.2?
I didn’t change anything, I didn’t use the block editor, I just updated the plugin and Voila! It changed by itself…