Question 1

How to fix Markdown bold text (wrapped in **) not showing as bold in Firefox but working in Chrome?

Accepted Answer

This issue affects projects using the 2018 version of `materialize.min.css` (e.g. Wikidocs, and is not a bug in Wikidocs itself): the stylesheet sets `` tags generated by Markdown `**bold**` syntax to `font-weight: 500`. Firefox only renders font weights ≥501 as bold, while Chrome treats weights ≥500 as bold. Fix options: 1. Recommended: Add the following rule to your custom stylesheet (e.g. `styles/styles-custom.css` for Wikidocs) or inject it directly via a `

Question 2

Why are long subsub page titles invisible in the Wikidocs sidebar?

Accepted Answer

This is caused by a space character in `template.inc.php` that forces a line break for long, unbroken `subsub_index` titles. Upgrade to Wikidocs **1.0.82 or later**, where the issue is fixed by PR #270. As a workaround on versions 1.0.76–1.0.78, edit `template.inc.php`, locate the template markup rendering the `subsub_index` title, and remove the extra space character causing the unwanted line break.

Question 3

How to fix 404 error when logging in or editing WikiDocs on Hiawatha webserver?

Accepted Answer

The 404 error on login/edit routes (e.g. `/homepage?auth`) occurs because WikiDocs relies on Apache-style `.htaccess` URL rewrite rules to route requests to `index.php`, which are not natively supported by Hiawatha. Fix steps: 1. Refer to Hiawatha's official URL rewrite guide: https://hiawatha.leisink.net/howto/url_rewrite_rules 2. Convert the following default WikiDocs Apache mod_rewrite rules to Hiawatha configuration syntax: ```apache RewriteEngine On # Use / for root domain installation, replace /subfolder/ with your actual subdirectory path if applicable RewriteBase /subfolder/ # Redirect direct .md file requests to root RewriteCond %{REQUEST_URI} \.md$ [NC] RewriteRule ^.*$ /subfolder/ [R=301,L] # Route all non-existent file requests to index.php RewriteCond %{REQUEST_FILENAME} !-f RewriteRule ^(.*)$ index.php?doc=$1 [NC,L,QSA] ``` Easier workaround: Deploy WikiDocs with Apache, Nginx, or Docker, which support the default rewrite rules out of the box.

Question 4

How do I fix Wikidocs redirecting to http://wikidocs/homepage?auth behind an nginx reverse proxy with a custom domain?

Accepted Answer

The redirect uses the container name because nginx forwards its upstream Host (`wikidocs`) instead of your public domain and does not tell Wikidocs the original request was HTTPS. Update your nginx location block: ```nginx location / { proxy_pass http://wikidocs:80; proxy_set_header Host $host; proxy_set_header X-Forwarded-Proto https; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Port 443; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; client_max_body_size 0; } ``` Validate and reload nginx, for example: ```bash docker exec nginx -t docker exec nginx -s reload ``` Then log in through `https://wiki.mydomain.com`. The service name `wikidocs` can remain the Docker/DNS upstream name; it should not be used in externally generated links. If redirect headers still need rewriting, add `proxy_redirect http://wikidocs/ https://wiki.mydomain.com/;` as a temporary workaround.

Question 5

How do I fix the missing php-mbstring dependency when installing WikiDocs on Ubuntu with Nginx?

Accepted Answer

Install the required PHP extension on Ubuntu:

```bash
sudo apt update
sudo apt install php-mbstring
```

Restart PHP-FPM and Nginx afterward, for example:

```bash
sudo systemctl restart php8.1-fpm
sudo systemctl restart nginx
```

Use the setup script to verify all required PHP dependencies, since the Nginx documentation section may not mention it explicitly. The official Docker image already includes `mbstring`.

WikiDocs

Core Features

What It Can't Do

Use Cases

Tags

Getting Started

Similar Projects