The refork of WordPress, that was decided in late 2022, which is going to be ClassicPress v2.0, is happening right now. Its based on WP 6.2 and does not contain Gutenborg (ie. the Block Editor), but compatiblity layers for allowing “regular” block-focused plugins to continue working. So CP 1.6 is supposed to be the last version based on WP 4.9.
\nI’m going to test the current alpha / nightly release of CP v2.0 soonish under a separate subdomain. It should allow for using newer WooCommerce versions, which in turn would enable me to do a “proper” fork of WooCommerce with most things up-to-date and working, instead of having to rely on WC 3.9.x and a lot of backporting / rearranging.
\n“Soonish”, because these days, I’m quite busy with work and cannot exactly say when I’m going to have some spare time left to do a proper installation. Proper installation includes the complete data of THIS blog, with a potentially updated / enhanced theme (I’d love to switch this one over to the amalgam of Bootstrap 4 and 5 I’ve been using for client projects lately), and all the plugins that mostly stopped working.
\nI’d also like to test if WP Super Cache works again with CP 2, or if I still need to do a soft-fork. From what I could see from comparision of commits is: The incompatiblity is non-existent, its a decision made by the developers, changing the “Compatiblity” setting in the plugin identification block to “at least 5.x”, but the plugin by itself works perfectly well even in WP 4.9.x and CP v1.x, as soon as one changes the resp. line to “4.9”.
So I finally decided to disable Bogo, which has been a shoddy solution from the very start. But now its a shoddy solution only supporting the other shoddy, WP-6-only solution, ie. Gutenborg. Tried a few workarounds, but in the end, its wasted time and efforts to get this shoddy piece really working.
\nHence I’m probablly going the dirty’n’hard way, as in: its not quick, but its gonna work somehow: Use meta fields to assign language, add fancy stuff to the theme to indicate the language of the current post or page, connect posts and pages using meta fields, and so on. Maybe also add a simple translation / i18n shortcode for quick inline sections, and a simplified language switcher to the sidebar / navigation.
\nMaybe release a simple tutorial + micro plugin, too. All to be seen in the nearby future.
\n", "content_text": "So I finally decided to disable Bogo, which has been a shoddy solution from the very start. But now its a shoddy solution only supporting the other shoddy, WP-6-only solution, ie. Gutenborg. Tried a few workarounds, but in the end, its wasted time and efforts to get this shoddy piece really working.\nHence I’m probablly going the dirty’n’hard way, as in: its not quick, but its gonna work somehow: Use meta fields to assign language, add fancy stuff to the theme to indicate the language of the current post or page, connect posts and pages using meta fields, and so on. Maybe also add a simple translation / i18n shortcode for quick inline sections, and a simplified language switcher to the sidebar / navigation.\nMaybe release a simple tutorial + micro plugin, too. All to be seen in the nearby future.", "date_published": "2023-05-12T04:29:05+02:00", "date_modified": "2023-05-12T04:29:05+02:00", "author": { "name": "fwolf", "url": "https://wp-devil.com/author/fwolf/", "avatar": "https://secure.gravatar.com/avatar/c2a31599f60eec1232806bfc26066ed2?s=512&d=mm&r=g" }, "image": "https://wp-devil.com/wp-content/uploads/2021/06/ukzhlkoz1ie.jpg", "tags": [ "ClassicPress", "development", "Life and let die", "wordpress" ] }, { "id": "https://wp-devil.com/micro-plugin-mastodon-profile-verification-link/", "url": "https://wp-devil.com/micro-plugin-mastodon-profile-verification-link/", "title": "Micro-Plugin: Mastodon Profile Verification Link", "content_html": "Just finished building a quick micro plugin for ClassicPress and WordPress, which allows you to add a verification link pointing back to your mastodon profile.
\nBut not to just one, but to ALL your potential profiles (eg. I got two: one for my main stuff, and the other is for DJing + artsy fartsy).
Lazy being that I am, the settings are being displayed under Settings > Discussion => “Mastodon Profile URL(s)”. One profile URL per line.
\nTested with ClassicPress 1.4. Released under the GNU GPL v2.
\nGet it yourself from the gist / source code. drop it in your plugin directory (preferable in its own sub-directory), activate, et voila!
View the code on Gist.
\n", "content_text": "Just finished building a quick micro plugin for ClassicPress and WordPress, which allows you to add a verification link pointing back to your mastodon profile.\nBut not to just one, but to ALL your potential profiles (eg. I got two: one for my main stuff, and the other is for DJing + artsy fartsy).\nLazy being that I am, the settings are being displayed under Settings > Discussion => “Mastodon Profile URL(s)”. One profile URL per line.\nTested with ClassicPress 1.4. Released under the GNU GPL v2.\nGet it yourself from the gist / source code. drop it in your plugin directory (preferable in its own sub-directory), activate, et voila!\nView the code on Gist.", "date_published": "2022-11-07T07:10:33+01:00", "date_modified": "2022-11-07T07:29:03+01:00", "author": { "name": "fwolf", "url": "https://wp-devil.com/author/fwolf/", "avatar": "https://secure.gravatar.com/avatar/c2a31599f60eec1232806bfc26066ed2?s=512&d=mm&r=g" }, "image": "https://wp-devil.com/wp-content/uploads/2021/06/jdgtvgzqmgq.jpg", "tags": [ "ClassicPress", "development", "mastodon", "wordpress" ] }, { "id": "https://wp-devil.com/how-to-change-the-admin-page-title-to-something-useful/", "url": "https://wp-devil.com/how-to-change-the-admin-page-title-to-something-useful/", "title": "How to change the admin page title to something useful", "content_html": "Fix the HTML title of the post editor in the WordPress admin to something much more useful.
\nVery helpful when editing multiple posts, but also, when changing lots of images (eg. post thumbnail or product gallery etc.).
View the code on Gist.
\n", "content_text": "Fix the HTML title of the post editor in the WordPress admin to something much more useful.\nVery helpful when editing multiple posts, but also, when changing lots of images (eg. post thumbnail or product gallery etc.).\nView the code on Gist.", "date_published": "2022-08-15T15:40:06+02:00", "date_modified": "2022-09-27T11:53:31+02:00", "author": { "name": "fwolf", "url": "https://wp-devil.com/author/fwolf/", "avatar": "https://secure.gravatar.com/avatar/c2a31599f60eec1232806bfc26066ed2?s=512&d=mm&r=g" }, "image": "https://wp-devil.com/wp-content/uploads/2022/06/c2zhshtnl5i.jpg", "tags": [ "development", "wordpress" ] }, { "id": "https://wp-devil.com/woocommerce-setting-a-specific-stock-number-for-all-products-but-a-selected-few/", "url": "https://wp-devil.com/woocommerce-setting-a-specific-stock-number-for-all-products-but-a-selected-few/", "title": "WooCommerce: Setting a specific stock number for all products but a selected few?", "content_html": "Client wanted to have inventory management, but the items are all produced on-demand – except for unique specimens, which are either custom-made pieces which have been returned, or have been produced as a side or test run.
\nSo, we decided to enable inventory management, and set the stock number for all items in any category BUT the “Einzelst\u00fccke” (singular pieces) to 999, and items in that specific category to 1.
\nThere certainly are plugins and a few screencasts / tutorials how to do achieve this, but the crafty developer who’s at least a bit versed with SQL might just prefer the following approach:
\n_stock is the meta field used for inventory management by WooCommerce.UPDATE {prefix}postmeta SET meta_value = '999' WHERE meta_key = 'stock'\nsolves the issue with pre-existing products
UPDATE {prefix}postmeta SET meta_value = '999' WHERE meta_key = 'stock' AND post_id IN (SELECT ID FROM {prefix}posts WHERE product_type = 'product' AND post_status = 'publish')\nTomorrow, ie. Thursday, 18th of March, 2021, I gonna start the first test run of my new show called Code of Dark Joy, which is specifically aimed towards live coding. It’s still gonna contain the element of music, as a lot of it focused on the topics of building up your OBS interface and its related periphery, for streaming Music on Twitch, YouTube and other live video platforms.
\nFor starters, I’ve planned to work on the overall interface of the new show, maybe get the cover “flow” / display I have been pondering about started, do a quick “ask me anything” Q & A, and spin some nice dark music (whatever rocks my boat, but yes, also taking requests) \ud83d\ude42
\nAt the end, I’m going to raid over to DJ Hatemiors "Day Drunk", which starts at 17:00 UTC+0 / 18:00 CET.
\nIf everything works out nicely, I intend to turn this into a weekly occurance, although I cannot promise that its always going to happen on a Thursday.
\nTwitch Channel: https://twitch.tv/gothicforesttroll
\nTips & Donations: https://gothicforesttroll.org/donations
\nFB Event: https://fb.me/e/y5Zj30aa
A random collection of a bunch of things I want to do this year, ie. 2021 \ud83d\ude42
\n
For one, I’ve been planning and preparing to write several lengthy, detailed articles about how to use Icecast in combination with OBS, eg. to solve the “current song” issue most DJs run into, when streaming live to platforms like Twitch or YouTube. But also, what you can do further with OBS, just by relying on the the magic of the web (ie. HTML 5, CSS 3 and Javascript).
\nThe other topic is how-tos and articles just about the environment of Twitch and online DJing in general. That includes gathering statistical information from multiple sources, eg. quite a few point towards the statistical result, that the sweet spot for shows per week are only TWO. Anything further supposedly decreases the viewing time or viewers per show per se. Etc.
\nNext on, I want to add several services to my existing web development “empire” (of dirt), specifically aimed towards DJs, musicians, projects / bands. That includes building or restructuring WordPress-based websites towards their needs, and offering plugins, and extensions which allow you to connect your own site with eg. Twitch, at least to some extent. Not to mention I plan to build own plugins to improve my own site and publishing cycles (eg. multiposting to other platforms, straight out of ClassicPress / WordPress), which eventually will be turned into premium plugins.
\nTalking about plugins: Lets not forget about Classic Forms 8, a fork of Contact Form 7 for CP and WP 4.9.x. Gotta get it working till the end of January 2021 \ud83d\ude42
\nLast but not least, I intend to improve on my own channel and shows, trying to get it down to 1 1/2 shows per week = primary show is on Sunday, 4 – 9 pm EST = 21:00 – 02:00 UTC+0, but I also do a different show, once every few weeks, on Thursday afternoon (ie. Central European Time = usually starting around 17:00 CET). This I want to change into bi-weekly, so eg. every odd or every even week. Further improvements include saving money for a decent workstation and streaming computer. Plus improved audio hardware.
\nNeed to get the backlog uploaded to Mixcloud. Its currently sitting at shortly afte November 16th, 2020, spanning 11 recordings. Thus, improving the website (Gothic-Forest-Troll.org) and turning it into a CP-powered site, with optional frontend members only etc. pp. is a totally nice goal for the next few months. Maybe folks might even be inclined to join one of the the Steady subscription plans? \ud83d\ude42
\nAccording to several sources, CPU power still overrules GPU power, when it comes to streaming video, at least with common streaming software like OBS; hence I plan to either get a AMD Ryzen 4750G Pro (essentially a SoC with a Ryzen 7 3700 + Vega 11 GPU), or a Ryzen 9 3900X / 3950 X plus a simple GPU like the nVidia GTX 1650.
\nThus, the rough setup is going to be:
\n– CPU: AMD Ryzen 7 4750G Pro or Ryzen 9 3900X / 3950 X, plus a nice Noctua 14/15 cm CPU fan
\n– GPU: either SoC / APU or nVidia GTX 1650
\n– Case: probably Cooler Master HAF XB Evo or the Corsair 4000D Airflow; but no fancy bullshit RGB / LED light garbage \ud83d\ude42
\n– Case Fans: Noctua + Scythe Flex ..
\n– RAM: 32 GB, 3200 MHz, CAS 15 timings (to aim for the 10 – 11 ns sweetspot)
\n– Storage: 1 TB NVMe + raid of regular SSDs (Goodram SSD IRDM PRO Gen2 1TB, Intel SSD D3-S4510 or maybe Seagate Nytro 1000)
\n– OS: Linux triple / multiple boot, one with Kubuntu / KDE Neon base, and the second system is gonna be Manjaro; maybe even with a Windows 10 Pro partition
After intense studies and research, my personal sweet spot seems to be the Rode Procaster, which is surprisingly flexible in its usage. Aside of being a really good microphone for talk and moderation – which is what I want to get back into strongly, having done web radion since the early 2000s – it is also quite comfortable to use as a directional microphone for recording the sound of instruments; which was my initial idea behind getting a Samsung E845 S.
\nNot “hardware” per se, but I finally want to get some decent percussion “hardware”, ie. a nice cajon plus bass or 2-in-one cajon, maybe a bongo or two, very possibly an african conga, and others \ud83d\ude42
\nAnd finally, there is those things like with the extended lockdown in Germany till mid of February, and all that stuff going on .. trying out yoga, and picking up sport / stunt kiting again. Actually, my parents both did yoga even before my birth, so its .. both familiar, but also new. Also, I did sport kiting for over 10 years, and that was kind of the only real type ofsport I liked, aside of cross-country skiing.
\n", "content_text": "A random collection of a bunch of things I want to do this year, ie. 2021 \ud83d\ude42\n\nFor one, I’ve been planning and preparing to write several lengthy, detailed articles about how to use Icecast in combination with OBS, eg. to solve the “current song” issue most DJs run into, when streaming live to platforms like Twitch or YouTube. But also, what you can do further with OBS, just by relying on the the magic of the web (ie. HTML 5, CSS 3 and Javascript). \nThe other topic is how-tos and articles just about the environment of Twitch and online DJing in general. That includes gathering statistical information from multiple sources, eg. quite a few point towards the statistical result, that the sweet spot for shows per week are only TWO. Anything further supposedly decreases the viewing time or viewers per show per se. Etc.\nNext on, I want to add several services to my existing web development “empire” (of dirt), specifically aimed towards DJs, musicians, projects / bands. That includes building or restructuring WordPress-based websites towards their needs, and offering plugins, and extensions which allow you to connect your own site with eg. Twitch, at least to some extent. Not to mention I plan to build own plugins to improve my own site and publishing cycles (eg. multiposting to other platforms, straight out of ClassicPress / WordPress), which eventually will be turned into premium plugins.\nTalking about plugins: Lets not forget about Classic Forms 8, a fork of Contact Form 7 for CP and WP 4.9.x. Gotta get it working till the end of January 2021 \ud83d\ude42\nLast but not least, I intend to improve on my own channel and shows, trying to get it down to 1 1/2 shows per week = primary show is on Sunday, 4 – 9 pm EST = 21:00 – 02:00 UTC+0, but I also do a different show, once every few weeks, on Thursday afternoon (ie. Central European Time = usually starting around 17:00 CET). This I want to change into bi-weekly, so eg. every odd or every even week. Further improvements include saving money for a decent workstation and streaming computer. Plus improved audio hardware.\nApropos further improvements:\nNeed to get the backlog uploaded to Mixcloud. Its currently sitting at shortly afte November 16th, 2020, spanning 11 recordings. Thus, improving the website (Gothic-Forest-Troll.org) and turning it into a CP-powered site, with optional frontend members only etc. pp. is a totally nice goal for the next few months. Maybe folks might even be inclined to join one of the the Steady subscription plans? \ud83d\ude42\nPlans for the workstation are:\nAccording to several sources, CPU power still overrules GPU power, when it comes to streaming video, at least with common streaming software like OBS; hence I plan to either get a AMD Ryzen 4750G Pro (essentially a SoC with a Ryzen 7 3700 + Vega 11 GPU), or a Ryzen 9 3900X / 3950 X plus a simple GPU like the nVidia GTX 1650.\nThus, the rough setup is going to be:\n– CPU: AMD Ryzen 7 4750G Pro or Ryzen 9 3900X / 3950 X, plus a nice Noctua 14/15 cm CPU fan\n– GPU: either SoC / APU or nVidia GTX 1650\n– Case: probably Cooler Master HAF XB Evo or the Corsair 4000D Airflow; but no fancy bullshit RGB / LED light garbage \ud83d\ude42\n– Case Fans: Noctua + Scythe Flex ..\n– RAM: 32 GB, 3200 MHz, CAS 15 timings (to aim for the 10 – 11 ns sweetspot)\n– Storage: 1 TB NVMe + raid of regular SSDs (Goodram SSD IRDM PRO Gen2 1TB, Intel SSD D3-S4510 or maybe Seagate Nytro 1000)\n– OS: Linux triple / multiple boot, one with Kubuntu / KDE Neon base, and the second system is gonna be Manjaro; maybe even with a Windows 10 Pro partition\nPlans for audio hardware:\nAfter intense studies and research, my personal sweet spot seems to be the Rode Procaster, which is surprisingly flexible in its usage. Aside of being a really good microphone for talk and moderation – which is what I want to get back into strongly, having done web radion since the early 2000s – it is also quite comfortable to use as a directional microphone for recording the sound of instruments; which was my initial idea behind getting a Samsung E845 S.\nNot “hardware” per se, but I finally want to get some decent percussion “hardware”, ie. a nice cajon plus bass or 2-in-one cajon, maybe a bongo or two, very possibly an african conga, and others \ud83d\ude42\nAnd finally, there is those things like with the extended lockdown in Germany till mid of February, and all that stuff going on .. trying out yoga, and picking up sport / stunt kiting again. Actually, my parents both did yoga even before my birth, so its .. both familiar, but also new. Also, I did sport kiting for over 10 years, and that was kind of the only real type ofsport I liked, aside of cross-country skiing.", "date_published": "2021-01-21T08:22:34+01:00", "date_modified": "2021-01-21T08:34:00+01:00", "author": { "name": "fwolf", "url": "https://wp-devil.com/author/fwolf/", "avatar": "https://secure.gravatar.com/avatar/c2a31599f60eec1232806bfc26066ed2?s=512&d=mm&r=g" }, "image": "https://wp-devil.com/wp-content/uploads/2020/09/mmezn_tfzso.jpg", "tags": [ "2021", "audio", "djing", "Hardware", "plans", "resolutions", "sports", "thoughts", "ClassicPress", "DJ", "Life and let die", "Linux", "Musick", "wordpress" ] }, { "id": "https://wp-devil.com/breaking-the-curse-of-the-admin-redirection-loop/", "url": "https://wp-devil.com/breaking-the-curse-of-the-admin-redirection-loop/", "title": "Breaking the Curse of the Admin Redirection Loop", "content_html": "Second time this has happened to me: A WordPress site needed to be updated to WP 5.x and switched over to a temporary subdomain. After doing the usual dance of backup, duplicate and manual update of WP, when I was trying to access the frontend, I’ve got redirected again to the backend. The usual suspects like deleting all cookies, replacing all occurences of the old site URL in the database etc. didn’t work ..
\nBut then I remembered: Last time this happened to me, the cause were left-over transients – specifically of the PolyLang plugin. Apparently it’s storing some auto-redirection info in a transient, prefixed with _pll_. Delete THAT, and The Curse of the “Infininite Admin Interface Redirection Loop” will be broken \ud83d\ude42
\n", "content_text": "Second time this has happened to me: A WordPress site needed to be updated to WP 5.x and switched over to a temporary subdomain. After doing the usual dance of backup, duplicate and manual update of WP, when I was trying to access the frontend, I’ve got redirected again to the backend. The usual suspects like deleting all cookies, replacing all occurences of the old site URL in the database etc. didn’t work .. \nBut then I remembered: Last time this happened to me, the cause were left-over transients – specifically of the PolyLang plugin. Apparently it’s storing some auto-redirection info in a transient, prefixed with _pll_. Delete THAT, and The Curse of the “Infininite Admin Interface Redirection Loop” will be broken \ud83d\ude42", "date_published": "2019-12-02T23:37:20+01:00", "date_modified": "2019-12-03T00:18:13+01:00", "author": { "name": "fwolf", "url": "https://wp-devil.com/author/fwolf/", "avatar": "https://secure.gravatar.com/avatar/c2a31599f60eec1232806bfc26066ed2?s=512&d=mm&r=g" }, "image": "https://wp-devil.com/wp-content/uploads/2019/12/tejq7cyc-za.jpg", "tags": [ "polylang", "site relocation", "transients", "development", "wordpress" ] }, { "id": "https://wp-devil.com/cryptic-characters-in-shortcode-attributes/", "url": "https://wp-devil.com/cryptic-characters-in-shortcode-attributes/", "title": "Side note: Strange cryptic characters in shortcodes", "content_html": "Note: Also available in German \ud83d\ude42
\nA colleague of mine today: There is a shortcode with strange-looking, cryptic characters in one of its attributes.
\nSomething like this:
eyJoYWxsbyI6IndlbHQiLCJzb25nLXRpdGVsIjp7Im1laW4iOiJnZWhpcm4iLCJkZWluIjoiZ2VoaXJuIn0sInVybCI6Imh0dHBzJTNBJTJGJTJGdXNhYmlsaXR5LWlkZWFsaXN0Lm5ldCUyRiUyM2tvbnRha3QiLCJlaW5zX3BsdXMiOnRydWV9\n
My comment: Looks a bit like rot13 ..
\nHis reply a bit later on: Yes, it is base64, and the result is a JSON string.
View the code on Gist.
\nYep … works \ud83d\ude42
\nThis is how the Uncode plugin is saving its data into shortcode attributes, and a few themes use it as well, to store their settings, eg. as a transient.
Well, right after moving a site, search & replace utterly fails with this. Ergo this is a really rotten habit. Yes, of corpse I do understand why one would go so far and store data this way – because (at least older version of) Visual Composer doesnt give any options to create direct connections between shortcodes and eg. meta fields. But still, if it was me who had to develop something like this, I’d still strived to get it done with meta fields, and maybe a shortcode attribute acting as ID. Because with that lengthy search, after those “hidden URLs”, my colleague wasted most of the day. That is time and money, he wont get back. At all.
\n", "content_text": "Note: Also available in German \ud83d\ude42\nA colleague of mine today: There is a shortcode with strange-looking, cryptic characters in one of its attributes.\nSomething like this:\neyJoYWxsbyI6IndlbHQiLCJzb25nLXRpdGVsIjp7Im1laW4iOiJnZWhpcm4iLCJkZWluIjoiZ2VoaXJuIn0sInVybCI6Imh0dHBzJTNBJTJGJTJGdXNhYmlsaXR5LWlkZWFsaXN0Lm5ldCUyRiUyM2tvbnRha3QiLCJlaW5zX3BsdXMiOnRydWV9\nMy comment: Looks a bit like rot13 ..\nHis reply a bit later on: Yes, it is base64, and the result is a JSON string.\nPutting the rule to the test:\nView the code on Gist.\nYep … works \ud83d\ude42\nThis is how the Uncode plugin is saving its data into shortcode attributes, and a few themes use it as well, to store their settings, eg. as a transient.\nWhat effects does this have?\nWell, right after moving a site, search & replace utterly fails with this. Ergo this is a really rotten habit. Yes, of corpse I do understand why one would go so far and store data this way – because (at least older version of) Visual Composer doesnt give any options to create direct connections between shortcodes and eg. meta fields. But still, if it was me who had to develop something like this, I’d still strived to get it done with meta fields, and maybe a shortcode attribute acting as ID. Because with that lengthy search, after those “hidden URLs”, my colleague wasted most of the day. That is time and money, he wont get back. At all.", "date_published": "2019-08-19T20:41:53+02:00", "date_modified": "2019-08-19T22:38:36+02:00", "author": { "name": "fwolf", "url": "https://wp-devil.com/author/fwolf/", "avatar": "https://secure.gravatar.com/avatar/c2a31599f60eec1232806bfc26066ed2?s=512&d=mm&r=g" }, "image": "https://wp-devil.com/wp-content/uploads/2019/08/4lnpasdxn9i.jpg", "tags": [ "development", "wordpress" ] }, { "id": "https://wp-devil.com/slashing-back/", "url": "https://wp-devil.com/slashing-back/", "title": "Slashing back ..", "content_html": "This is a little test .. lets see:
\nQuoting from somewhere else:
\n(unter Windows, bitte \u201e/\u201c durch Backslash ersetzen \u2013 WordPress kann das offenbar nicht darstellen
Translates roughly to “under Windows, please replace “/” with the back slash – WordPress is apparently not able to display it”.
\nWell, lets see about that: Hello, Back Slash!
\nAddendum: After adding and switching over to the german version of this post, Backslash #1 and #3 were gone, and #2 was had turned into a single one. The cause is probably some input sanitization, either when the content of the post editor form is being transfered to server (eg. sanitize_text_field) or before the data is saved in the database.
\nAddendum #2: Fitting music for the lil back slashes.
\n\nAddendum #3: Nice typo in the initial post: “Black Slash” – wouldn’t that be a fitting name for a BDSM Queer superhero? \ud83d\ude00
\n", "content_text": "This is a little test .. lets see:\nQuoting from somewhere else: \n(unter Windows, bitte \u201e/\u201c durch Backslash ersetzen \u2013 WordPress kann das offenbar nicht darstellen\nTranslates roughly to “under Windows, please replace “/” with the back slash – WordPress is apparently not able to display it”.\nWell, lets see about that: Hello, Back Slash! \n\n\\ – one lil back slash\n\\\\ – two lil back slashes (or one escaped lil back slash)\n“\\” – a lil back slash in quotes ..\n\nAddendum: After adding and switching over to the german version of this post, Backslash #1 and #3 were gone, and #2 was had turned into a single one. The cause is probably some input sanitization, either when the content of the post editor form is being transfered to server (eg. sanitize_text_field) or before the data is saved in the database.\nAddendum #2: Fitting music for the lil back slashes.\n\nAddendum #3: Nice typo in the initial post: “Black Slash” – wouldn’t that be a fitting name for a BDSM Queer superhero? \ud83d\ude00", "date_published": "2019-05-15T16:47:18+02:00", "date_modified": "2019-05-15T17:16:11+02:00", "author": { "name": "fwolf", "url": "https://wp-devil.com/author/fwolf/", "avatar": "https://secure.gravatar.com/avatar/c2a31599f60eec1232806bfc26066ed2?s=512&d=mm&r=g" }, "image": "https://wp-devil.com/wp-content/uploads/2019/01/eahydobqpoq-e1557932304897.jpg", "tags": [ "wordpress" ] } ] }