Known Bugs

This article is for any known errors in E-Hentai that are believed to be non-intentional.

E-Hentai

Aesthetic - Underscores (such as those in usernames) may appear as spaces in the GP Exchange/Hath Exchange. Varies based on browser and font settings. (Screenshot)

Bug - Existing articles may fail to properly redirect or display as red links if not yet cached. In such cases, red links still lead to the article and the redirect works every second visit.
- Workaround for red links - Make a minor edit and remove the linefeed at the end of the article. This does not count as an edit but forcefully refreshes the article.
  - This bug usually only triggers for articles linking to each other or articles posted almost simultaneously.

Aesthetic - Field usage warnings do not take certain characters into account when attempting to throw an alert with current character usage with priority over the board error message.
- Workaround - If the native IPB system throws in a "field too long" error, keep shortening the field - that means it still is over the allowed limit.
Bug - Using leading zeroes in any of the boards' text input fields will cause the board system to silently discard them as unacceptable characters. Also applies to other allowed characters treated by PHP as empty characters at the beginning of fields.
- Display name change - The desired display name still appears with leading zeroes in the user's name change history.
- Workaround - Use full-width characters if you wish to use such characters.

Bug - New comments may take some time to appear. This is due to URL changes in the gallery system; comments will show up once everything has been cached.
Bug? - Full-width whitespaces as well as other invisible characters are accepted, allowing for empty titles.
Bug? - Lo-Fi galleries do not use namespaces.

Aesthetic - Client settings may report minimum requirements as 100KB/s burst speed, 100MB hourly limit and 2GB cache after a shutdown.
- The actual requirements still are 200KB/s, 300MB and 10GB (or static range count*175MB, whichever is higher) respectively. Anything below this will return an error if set and fail to apply.
Bug - Clients do not retain the year they were last seen and will report "Today, hh:mm" each year after being last seen (they will not show "Yesterday, hh:mm" on the next day but "M dd, hh:mm" again). It is yet unknown whether this directly affects the pruning process.
- Idle clients do not get pruned one year after being last seen on the network, which may be related to an internal change in the pruning process.