 | Lars Fosdal on Security alarm provider Woonve… |
 | Thomas Mueller on Question got closed in May 202… |
 | Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
Posted by jpluimers on 2025/08/29
Reminder to self: check if the WordPress.com classic editor is still alive and still supports adding Crowdsignal (formerly Polldaddy) polls (Crowdsignal is part of Automattic, the WordPress.com parent company).
From [Wayback/Archive] Crowdsignal Dashboard – Polls, Surveys & more plugin for WordPress (I made the areas that are important to me in bold):
Posted in Classic editor, Development, Gutenberg editor, Power User, SocialMedia, Software Development, Web Development, WordPress, WordPress | Leave a Comment »
Posted by jpluimers on 2024/07/11
Quoting in full from [Wayback/Archive] Nelson’s Weblog: tech / zero-width-space to demonstrate a zero-width-space problem with WordPress too.
Posted in Bookmarklet, Classic editor, Development, Gutenberg editor, JavaScript/ECMAScript, Power User, Scripting, SocialMedia, Software Development, Twitter, Web Browsers, Web Development, WordPress | Leave a Comment »
Posted by jpluimers on 2023/10/25
When you use the WordPress classic editor (which for me still works far better than the Gutenberg one), avoid at all cost the use of the [Wayback/Archive] SyntaxHighlighter Code Block – Page 2 – WordPress.com Support.
Each time you switch between from Text View back to Visual, some characters are html-encoded, like:
& becomes &> becomes >Switching twice makes & into &>.
Switching three times makes & into &&&gt.
I already explained why to avoid the Gutenberg editor in Bookmarklet to force WordPress classic-editor.
Via:
–jeroen
Posted in Classic editor, Development, Gutenberg editor, SocialMedia, Software Development, Web Development, WordPress, WordPress | Leave a Comment »
Posted by jpluimers on 2023/09/19
Boy, two extra modifier keys: [Wayback/Archive] How to Strip Formatting When You Copy and Paste Text: 5 Ways
To paste as plain text on a Mac, you can use the somewhat cumbersome shortcut
Option+Cmd+Shift+Vto paste without formatting. This is a system-wide shortcut, so unlike Windows, it should work everywhere. Technically, the shortcuts pastes and matches the formatting, but this has the same effect of removing the original formatting.
Via [Wayback/Archive] macos word microsoft office paste without formatting – Google Search.
Paste without formatting is an issue on Windows as well. The default should be “paste without formatting” instead of the current “paste with source formatting”. See for instance these tweets:
Posted in Apple, Classic editor, Development, Gutenberg editor, Mac OS X / OS X / MacOS, Office, Office 2011 for Mac, Power User, Software Development, Web Development, WordPress | Leave a Comment »
Posted by jpluimers on 2023/07/20
Maintaining a blog takes considerable time, so I wrote a bit of JavaScript for the browser console and bookmarklets to help me navigate faster, especially from my published posts on wiert.me back to the WordPress editing environment.
I wrote this because a query like [Wayback/Archive] wordpress get id from post html – Google Search top hits only contain results that work within the WordPress environment itself, like for instance [Wayback/Archive] 14 Ways to Get Post ID in WordPress.
This blog post is long and contains a lot of information, so I have split it in quite a few sections.
Let’s get started:
Posted in Bookmarklet, Classic editor, Development, Gutenberg editor, JavaScript/ECMAScript, Power User, Scripting, Software Development, Web Browsers, Web Development | Leave a Comment »
Posted by jpluimers on 2022/03/29
A while ago, WordPress.com heavily started to de-emphasise the Classic Editor in order to boost the Gutenberg editor which is bloaty (in both browser DOM usage (heavily slowing down editing) and content (lots of meta tags that are added to blog source) and is missing essential features (especially nesting of blocks often breaks things).
With 7000+ blog posts in the Classic Editor format (a few in still supported markdown format: that experiment failed horribly!) that still require editing (especially because of link rot)
So here is the Bookmarklet code to switch back an editing URL that you can use for as long as the Classic Editor is there:
javascript:location.href=document.location.href+'&classic-editor';
Yup, it is that simple: it appends &classic-editor to the URL.
Posted in Bookmarklet, Classic editor, Development, Gutenberg editor, Internet, link rot, Power User, Software Development, Web Browsers, Web Development, WordPress, WWW - the World Wide Web of information | Leave a Comment »
Posted by jpluimers on 2022/03/18
For my link list as WordPress.com is actively hiding them:
?classic-editor or &classic-editor to outgoing links in order to forego the Gutenbeg editor)/ slashes in categories: it hangs while saving those)You can see the old versus new infrastructure by comparing these branches:
WordPress.com does not have the “Classic Editor” plugin, but just gradually discourages use of the old infrastructure which is far more feature rich, thereby screwing old users.
Some of these features from the old infrastructure that are gone (despite the pretentious name of the Gutenberg editor):
For reference, WordPress – Wikipedia: Gutenberg versus classic-editor:
WordPress 5.0 “Bebo”[edit]
The December 2018 release of WordPress 5.0, “Bebo”, is named in homage to the pioneering Cuban jazz musician Bebo Valdés.[90]
It included a new default editor “Gutenberg” – a block-based editor; it allows users to modify their displayed content in a much more user friendly way than prior iterations. Blocks are abstract units of markup that, composed together, form the content or layout of a web page.[91] Past content that was created on WordPress pages is listed under what is referred to as a Classic Block.[92] Prior to Gutenberg, there were several block-based editors available as WordPress plugins, e.g. Elementor, and following the release of Gutenberg Elementor was compared to existing plugins.[93][94]
Classic Editor plugin[edit]
The Classic Editor Plugin was created as a result of User preferences and helped website developers maintain past plugins only compatible with WordPress 4.9.8, giving plugin developers time to get their plugins updated & compatible with the 5.0 release. Having the Classic Editor plugin installed restores the “classic” editing experience that WordPress has had up until the WordPress 5.0 release.[95] The Classic Editor Plugin will be supported at least until 2022.[96]
The Classic Editor plugin is active on over 5,000,000 installations of WordPress.[97]
–jeroen
Posted in Classic editor, Development, Gutenberg editor, Power User, SocialMedia, Software Development, Web Development, WordPress, WordPress | Leave a Comment »
The Wiert Corner - irregular stream of stuff 