A website/blog engine.
Decent. I switched to this because I didn't really want to get into making my own thing. I can tolerate WordPress because of BlogText.
NOTE - WordPress is controlled by a dictatorship of tyrannical assholes. This won't matter to most people, but it will for some.
--
- Why I will move away from WordPress, guaranteed
- 2022-06-09 - 6.0 on PHP 8.1.6
- 2020-11-19 - 5.5.3 on PHP 7.3.21
- 2019-04-17 - 5.1 on PHP 7.3
- 2014-08-07 - Switched from MediaWiki
2022-06-09 - 6.0 ∞
403 Forbidden error with www.yola․com ∞
- Disable all plugins
- Create a new post
- Type www.yola․com
- Click
preview
-
(a 403 error is seen)
- works: Removing
www.
- works: Using the Unicode
ONE DOT LEADER
(U+2024
,e2 80 a4
) which generates a․
-
Fails: Using the HTML entities
.
or.
which generate a.
2020-11-19 - 5.5.3 ∞
403 Forbidden error with $
{
∞
I get an 403 Forbidden error when the source of a page contains $
and then a {
immediately afterward.
This has been reproduced with all plugins disabled.
This did not use to happen with earlier versions of WordPress, but I do not know when this problem was introduced.
2019-04-17 - 5.1 ∞
WordPress 5.1 with PHP 7.3 "white screen of death" ∞
This was not solved for me by disabling themes or plugins, though maybe I didn't do the disabling correctly.
The problem is indicated in error_log
, which was a memory limit problem.
The solution is:
- edit
wp-config.php
- locate the "Happy Blogging" line
-
Above that line, add:
define('WP_MEMORY_LIMIT', '256M');
MediaWiki-related WordPress stuff ∞
- WordPress users integrated into MediaWiki
- Useful Extensions for WordPress and MediaWiki
- mediawiki + wordpress synchronize registration
- authpress for mediawiki
- Converting your WordPress and Mediawiki data into RDF on-the-fly
More stuff ∞
-
https://www.smashingmagazine.com/2014/12/what-to-consider-when-choosing-a-wordpress-theme/ 1
- Also links to other similar posts
-
https://www.smashingmagazine.com/2009/05/100-amazing-free-wordpress-themes-for-2009/
- Gallery2
Usage and Troubleshooting ∞
See also WordPress configuration
Bookmarks / bookmarklets / search engines ∞
drafts
https://example.com/wp-admin/edit.php?post_status=draft&post_type=post
login
https://example.com/wp-login.php
new post
https://example.com/wp-admin/post-new.php
search
https://example.com/?s=%s
search title
https://example.com/__/%s
tag
https://example.com/tag/%s
tags
https://example.com/wp-admin/edit-tags.php?taxonomy=post_tag&post_type=post&s=%s
View page from editor
javascript: /* FIXME - only use this on example.com */ /* Note that drafts will not rewrite the ?post=0000 */ window.location = window.location.href /* WordPress editing */ .replace( 'wp-admin/post.php?post=' ,'?p=' ) /* WordPress editing, classic editor */ .replace( '&action=edit&classic-editor' ,'' ) /* alert( window.location.href + "\n" + ) */
PhpMyAdmin database search and replace (safely!) ∞
2023-08-10 - PhpMyAdmin 5.2.1
- 1. Select the database on the left
- 2. Select "SQL" at the top tabs
- 3. Look at the column of tables on the left. Determine the name of the table you want. It is likely something like
wp_posts
. -
4. Read, understand, and customize, the following:
-- Customize these: SET @table_name = 'wp_posts'; -- Be aware that there might be a character limit, although it's likely in the tens of thousands of characters. -- If you want to use the single quote ( ' ) then type two ( '' ). For example, to search for "don't" you instead search for "don''t" -- Note that this is a basic search and not a regular expression; trust me, you really don't want to use regular expressions. SET @search = 'SEARCH STRING'; -- Transactions: -- https://dev.mysql.com/doc/refman/8.0/en/commit.html START TRANSACTION; -- (autocommit is now disabled) -- Construct the query for dry run using prepared statement and parameter binding SET @dry_run_query = CONCAT( 'SELECT `ID`, `post_title` FROM ', @table_name, ' WHERE `post_content` LIKE ?' ); -- Prepare the dry run statement PREPARE dry_run_stmt FROM @dry_run_query; -- Execute the dry run statement with parameter binding EXECUTE dry_run_stmt USING CONCAT('%', @search, '%'); -- Deallocate the prepared dry run statement DEALLOCATE PREPARE dry_run_stmt; -- Since TRANSACTION is being used, autocommit is disabled, and therefore no changes have been made.
- 5. Paste it into the query box, customize it, and press
control-enter
. -
6. Scroll down to examine the results.
- If you do not like what you see, scroll up and click "Show query box", then make changes to the code.
-
7. Once you like your changes, then click "Show query box", paste the following code, make the same changes, and press
control-enter
.
-- Customize these: SET @table_name = 'wp_posts'; -- Be aware that there might be a character limit, although it's likely in the tens of thousands of characters. -- If you want to use the single quote ( ' ) then type two ( '' ). For example, to search for "don't" you instead search for "don''t" -- Note that this is a basic search and not a regular expression; trust me, you really don't want to use regular expressions. SET @search = 'SEARCH STRING'; SET @replace = 'REPLACE STRING'; -- Transactions: -- https://dev.mysql.com/doc/refman/8.0/en/commit.html START TRANSACTION; -- (autocommit is now disabled) -- Perform the update SET @query = CONCAT( 'UPDATE ', @table_name, ' SET `post_content` = REPLACE(`post_content`, ?, ?) WHERE `post_content` LIKE ?' ); PREPARE stmt FROM @query; EXECUTE stmt USING @search, @replace, CONCAT('%', @search, '%'); DEALLOCATE PREPARE stmt; -- Perform the SELECT to show changed rows SET @query = CONCAT( 'SELECT `ID`, `post_title` FROM ', @table_name, ' WHERE `post_content` LIKE ?' ); PREPARE stmt FROM @query; EXECUTE stmt USING CONCAT('%', @replace, '%'); DEALLOCATE PREPARE stmt; -- Since this is within a TRANSACTION, the changes are not automatically committed. This will do so: COMMIT;
Last updated 2023-08-11 at 12:06:46
HTML testing
Most HTML entities work as-expected. This is just some testing..
Regular text
Line breaks
and paragraphs are respected.
<hr>:
a - links
b - bold
em - emphasis
i - italics
ins
strong
img:
<br>: line one
line two
<code>
Will automatically convert & < > etc.
<b>bold</b>
I forgot to add my WordPress 5.1 with PHP 7.3 "white screen of death" misadventure.
- dumping in my final notes
- concluded porting WordPress
- adjusted the date
Finally found the problem with $ and then { causing "403 Forbidden" errors.
WordPress 5.8 and PHP 8.0.9 minimum PHP modules
The site broke overnight, and upgrading to PHP 8.1 works, and with only one module loaded.
documenting a yola 403 issue
added bookmarks / bookmarklets / search engines