Try harder - Create tickets for the author.
BlogText >
- 1 Broken image links disrupt tag viewing
- 2 Nested lists
- 3 Table syntax
- 4 Pages rendering images
- 5 Large images
- 6 Arseniya
- 7 Many images don't display
- 8 "Today" has a different background title.
- 9 Today
- 10 "Introduction" has a different style.
- 11 Introduction
- 12 Editing one particular page previews to another
- 13 Images are not resized in HTML
- 14 Oddly-styled area
Broken image links disrupt tag viewing ∞
Posts which have broken image references will screw up viewing a tag.
For example, if I viewed /tag/blogtext
- .. and one entry had a broken image reference.
- .. that entry will give a wall of errors, and not the one-line error I would see if I viewed that post.
-
.. and that tags list would not show any entries after that error-post.
Nested lists ∞
A list which ends with a two-level nested item will display that two-level nested item with an extra carriage return prepended.
The solution is to end the list with a bullet point that ends with %% (the double-percent comment syntax).
Interestingly, this does not occur inside of <blockquote> tags.
Example list:
* first level ** second level
Renders like:
-
first level
-
second level
-
Add a comment like so:
* first level
** second level
* %%
So it looks like this:
-
first level
- second level
I believe this problem is because BlogText makes the final entry in a list a <p>, as evidenced by:
p { text-indent: 1em; }
Regular paragraphs will be effected, but so will the final entry in all lists.
Triple-nested lists ∞
Nesting lists with a third level will not render as-expected. This is almost certainly related to the above nested list bug.
* one ** two *** three ** four * five
-
one
-
two
- three
- four
-
-
five
I don't have a workaround. The only things which can be done is to only use double lists or use indented text like so:
* one ** two three ** four * five
-
one
- two
three - four
- two
-
five
Table syntax ∞
A single-item table using its simple syntax cannot render properly and includes the remaining text of a page into the table. The workaround is to create a second cell, with its contents being %% (the double-percent comment syntax).
These do not work:
| example table
This also does not work:
| example table |
The workaround:
| example table | %%
Pages rendering images ∞
e.g. https://blog.spiralofhope.com/page/1
Pages will not render images if they are in a table in the first line of a post. Content, or a double-percent and space above the table solves this.
I do believe I also solved this by using a more complex table.
Large images ∞
BlogText cannot handle very large images.
Arseniya ∞
This particular image is not processed correctly. At best, it can display but with junk underneath it. I cannot find anything to do with that text on this blog. I have tried renaming and editing this image to reduce its Q-factor, neither of which changed anything.
[[image:Arseniya-2012-11-18-arseniya-iii-by-Jens-Klettenheimer1.jpg]]
https://soundcloud.com/londongrammar/london-grammar-nightcall-lg-re-edit" alt="Arseniya, Germany | " target="_blank">https://soundcloud.com/londongrammar/london-grammar-nightcall-lg-re-edit"/>
Many images don't display ∞
If I have many image links, not only will they not display but they will prevent any additional content from rendering.
- If I have no text after, then it will simply render this page without the images.
-
If I have text after, then a preview will only display the content of the first page.
{| class="single-row"
| [[image:firefall-tiny-head.jpg|150px|link=source]]
| [[image:firefall-thumping-with-npc-help.jpg|thumb]]
| [[image:firefall-thumping-on-water.jpg|thumb]]
| [[image:firefall-thumping-cheese-location.jpg|thumb]]
| [[image:firefall-thumping-cheese-2.jpg|thumb]]
| [[image:firefall-thumping-cheese-1.jpg|thumb]]
| [[image:firefall-the-headless-horseman-poses.jpg|thumb]]
| [[image:firefall-thats-a-lot-of-turrets.jpg|thumb]]
| [[image:firefall-stacking-players-seeing-eyeballs.jpg|thumb]]
| [[image:firefall-stacking-players-2.jpg|thumb]]
| [[image:firefall-stacking-players-1.jpg|thumb]]
| [[image:firefall-stacked-enemies.jpg|thumb]]
| [[image:firefall-salvaging.jpg|thumb]]
| [[image:firefall-riding-a-bike-wrong.jpg|thumb]]
| [[image:firefall-quest-mobs-behind-terrain.jpg|thumb]]
| [[image:firefall-odd-wall.jpg|thumb]]
| [[image:firefall-npc-on-top-of-a-player.jpg|thumb]]
| [[image:firefall-invisible-bike.jpg|thumb]]
| [[image:firefall-hell-yes-I-died.jpg|thumb]]
| [[image:firefall-health-station-placement.jpg|thumb]]
| [[image:firefall-headless-horseman-keepaway-in-base-2.jpg|thumb]]
| [[image:firefall-headless-horseman-keepaway-in-base-1.jpg|thumb]]
| [[image:firefall-floating-turret.jpg|thumb]]
| [[image:firefall-floating-object-2.jpg|thumb]]
| [[image:firefall-floating-object-1.jpg|thumb]]
| [[image:firefall-fighting-a-melding-tornado.jpg|thumb]]
| [[image:firefall-falling-to-my-death.jpg|thumb]]
| [[image:firefall-everything-at-once.jpg|thumb]]
| [[image:firefall-drop-pod-on-my-bike.jpg|thumb]]
| [[image:firefall-double-thumper-with-npc-help.jpg|thumb]]
| [[image:firefall-dead-in-the-melding.jpg|thumb]]
| [[image:firefall-dead-in-a-hole.jpg|thumb]]
| [[image:firefall-crashed-thumper-parts-lined-up-3.jpg|thumb]]
| [[image:firefall-crashed-thumper-parts-lined-up-2.jpg|thumb]]
| [[image:firefall-crashed-thumper-parts-lined-up-1.jpg|thumb]]
| [[image:firefall-cowardace.jpg|thumb]]
| [[image:firefall-awesome-gun.jpg|thumb]]
| [[image:firefall-bike-warp-1.jpg|thumb]]
| [[image:firefall-bike-warp-2.jpg|thumb]]
| [[image:firefall-bike-warp-3.jpg|thumb]]
| [[image:firefall-bike-warp-4.jpg|thumb]]
| [[image:firefall-turret-attacking-a-cage-1.jpg|thumb]]
| [[image:firefall-turret-attacking-a-cage-2.jpg|thumb]]
| [[image:firefall-turret-attacking-a-cage-3.jpg|thumb]]
|}
This is some example text.
"Today" has a different background title. ∞
A title of "Today" will appear with a different background colour than other h1 entries. The existence of text above or below does not effect this. An example follows.
- The workaround is to follow the title with . TOC still appears correctly.
-
This is not seen with h2
Today ∞
"Introduction" has a different style. ∞
- The workaround is to follow the title with . TOC still appears correctly.
-
This is not seen with h2
Introduction ∞
Editing one particular page previews to another ∞
- Edit https://blog.spiralofhope.com/wp-admin/post.php?post=12080&action=edit
-
Click preview
- I am expecting a preview of that page. https://blog.spiralofhope.com/12080
-
Instead, I get https://blog.spiralofhope.com/6553
I have tried:
- Deleting the offending post and creating it again (which is how it became 12080).
- Deleting all content from (and saving) 12080.
- Changing the title from 12080.
- Changing the title of and deleting all content from (and saving) 12080.
- Deleting all content from (and saving) 6553.
-
Clearing the BlogText cache for all pages.
Images are not resized in HTML ∞
I don't know, and don't think, this is an issue with BlogText, but I'll put it here for reference.
There is no combination of using the img tag and having it resize.
<img src="/wp-content/uploads/Andromeda-s01e20.jpg" width="150">
Renders as:

Oddly-styled area ∞
Ending a section with = #s turns it into something rather odd:
(arbitrary title) ∞
(arbitrary text)
Last updated 2021-11-11 at 10:47:18
