Archive for the ‘WordPress’ Category
Posted by jpluimers on 2023/07/02
I quickly hacked together this JavaScript Bookmarklet today, so it is without any checks and assumes you have enabled one Mastodon account for publishing, that you are hosting your blog on WordPress.com, and using the Classic Editor:
javascript:(function(){
publicizeFormEditHref = document.getElementById('publicize-form-edit');
publicizeFormEditHref.click();
mastodonCheckboxes = document.getElementsByClassName('wpas-submit-mastodon');
mastodonCheckboxes[0].checked = true;
publicizeFormHideHref = document.getElementById('publicize-form-hide');
publicizeFormHideHref.click();
updateButtonHref = document.getElementById('publish');
updateButtonHref.click();
})();
The above code is the state of [Wayback/Archive] JavaScript Bookmarklet for the WordPress classic editor which enables mastodon publishing (assuming you have one mastodon publishing account enabled … ) and due to be improved in a later blog post.
This will enable the currently edited post to be published to Mastodon, then update/publish the post.
On enabling one Mastodon account for publishing:
Read the rest of this entry »
Posted in Bookmarklet, Development, HTML, JavaScript/ECMAScript, Mastodon, Power User, Scripting, SocialMedia, Software Development, Twitter, Web Browsers, Web Development, WordPress, WordPress | Leave a Comment »
Posted by jpluimers on 2022/06/21
If you are still on Atom, try to see if other cross platform open source editors suit your needs.
Myself, I have moved to Visual Studio Code quite some time ago as, though based on Electron – the core of Atom, it is way faster and much better supported than Atom.
The official announcement is at [Wayback/Archive] Sunsetting Atom | The GitHub Blog.
Various sites reported it in different phrasings:
Read the rest of this entry »
Posted in .NET, atom editor, Development, Missed Schedule, Power User, SocialMedia, Software Development, Text Editors, vscode Visual Studio Code, WordPress | Leave a Comment »
Posted by jpluimers on 2022/03/28
Suddenly, a while ago, because of a stuck modifier key I suddenly had the WordPress classic editor running in full screen without any indication to go back, nor an opportunity to save the content.
It wasn’t the usual “Shift-Alt-W” [Wayback] Distraction Free Writing – Make WordPress Support (which still allows you to hover over the sidebars to make them visible, and has a visual indication of the mode).
After lot’s of trying, I figured out the toggle “Shift-Ctrl-F” toggles between normal and full screen mode. It seems unavailable in the new editor, so that might be a reason ([Wayback] Keyboard Shortcuts | WordPress.org)
The shortcut is odd too, as in most tooling “Ctrl-F” modifications like “Shift-Ctrl-F” have something to do with find or replace operations.
It was quite tough finding any reference to this shortcut, as my initial search revealed none: [Wayback] “WordPress” “Shift-Ctrl-F” full screen – Google Search.
Later I reversed the modifiers in [Wayback] “WordPress” “Ctrl-Shift-F” full screen – Google Search and found [Wayback] How to disable non-system hotkeys on Windows – gHacks Tech News
Simple Disable Key is a free software program for Microsoft Windows devices that enables you to block non-system hotkeys.
…
Not all hotkeys are useful however. When I work on a WordPress site for instance, I sometimes press the shortcut Ctrl-Shift-F by accident. This switches the editor to full screen view which I never use.
First time I invoked the full screen editor I had to look up the shortcut as I could not reproduce it.
–jeroen
Posted in Development, SocialMedia, Software Development, Web Development, WordPress, WordPress | Leave a Comment »
Posted by jpluimers on 2022/03/18
For my link list as WordPress.com is actively hiding them:
- Posts:
- Categories:
- Tags:
- Comments:
- Pages:
- Blogroll???
- Post:
Notes
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):
- Posts/Pages/Tags/Categories/Comments overviews are paginated, can be filtered and have bulk-actions
- Classic-Editor has lots of useful keyboard shortcuts and allows for nested quotes
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 »
Posted by jpluimers on 2021/10/21
I have used other on-line HTML cleanup tools in the past (especially for including parts of web-pages in a blog post), but so far none beats HTML Washer: [Wayback] HTML cleanup tool & simplifier. For basic & clean HTML 🔧
An online tool that reduces HTML to basic tags and attributes. Removes scripts, CSS, and other non-basic elements like , , etc… Also, corrects errors and formats the HTML doc or a fragment.
–jeroen
Posted in Development, HTML, Power User, SocialMedia, Software Development, Web Development, WordPress | Leave a Comment »
Posted by jpluimers on 2021/10/08
Preparing for another PowerShell article, I found this blast from the past, as somehow this missed the publishing schedule back in 2014!
Original text
After struggling with [Wayback] PowerShell ISE for a while ([Wayback] it started as a proof of concept and wasn’t meant to be an IDE you know) reading [Wayback] Powershell Studio vs Primal Forms Free CE vs PowerShellPlus Pro (also free) – Spiceworks, I’ve started using the free [Wayback] PowerGUI IDE for PowerShell by Dell.
The [Wayback] free PowerGUI used to be maintained by Quest, and after [Wayback] the acquisition of Quest by Dell in 2012, it is still free and is now at Product Support – PowerGUI Pro.
It is great (even got [Wayback] full support for PowerShell 3.0) and you can get it at the [Wayback] PowerGUI Downloads.
Notes:
–jeroen
Posted in Development, Missed Schedule, PowerShell, Scripting, SocialMedia, Software Development, WordPress | Leave a Comment »
Posted by jpluimers on 2021/10/01
Having spurious non-breaking spaces seems to be unavoidable: [WayBack] Unwanted non-breaking spaces ( ) | WordPress.org.
Deleting them is tough:
- in the visual editor, deleting a non-breaking spaces will mess up at least lists,
pre and code blocks.
- the text editor is the only reliable place to remove them. Search for
.
–jeroen
Posted in Blogging, Power User, SocialMedia, WordPress | Leave a Comment »
Posted by jpluimers on 2021/08/25
[WayBack] html – CSS Display an Image Resized and Cropped – Stack Overflow (thanks [WayBack] roborourke!); see full answer link for runnable snippet and HTML (the WordPress editor keeps fucking up preformatted code blocks with html or XML in it).
You could use a combination of both methods eg.
.crop {
width: 200px;
height: 150px;
overflow: hidden;
}
.crop img {
width: 400px;
height: 300px;
margin: -75px 0 0 -100px;
}
You embed the img in a div with class .crop, or in-line the styles in the img and div tags.
--jeroen
Posted in CSS, Development, HTML, HTML5, SocialMedia, Software Development, Web Development, WordPress, WordPress | Leave a Comment »
Posted by jpluimers on 2020/01/29
After years with “missed schedule” posts on (paid!) wordpress.com based sites, WordPress has documented that the scheduler officially does not support more than 100 posts:
[WayBack] Warning: Please do not schedule more than 100 posts. Any posts scheduled beyond that amount will not be published.
In practice this is not fully true, so lets explain that a little.
Background
Imagine the list of scheduled posts as a list of posts to be posted anywhere from the near future (lets call that tail) until far in the future (for now head).
As long as you schedule posts in head to tail order, then there is no problem. You can schedule 100s of posts (usually I’ve between 700 and 1200 posts scheduled that way).
The problems appear when:
Read the rest of this entry »
Posted in *nix, Development, Missed Schedule, Monitoring, Power User, SocialMedia, Software Development, Uptimerobot, Web Development, WordPress, WordPress | Leave a Comment »
The Wiert Corner - irregular stream of stuff 