<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title>esoBB bug tracking - eso.chipmunk.land</title>
	<link href="https://eso.chipmunk.land/index.php/20/esobb-bug-tracking/" rel="alternate"/>
	<subtitle>bug, eso, esobb</subtitle>	<id>https://eso.chipmunk.land/index.php/feed/conversation/20/</id>
	<updated>2026-06-24T04:21:39Z</updated>
	<generator>esoBB</generator>
	<entry>
		<title>max</title>
		<link href="https://eso.chipmunk.land/index.php/post/78/" rel="alternate"/>
		<id>https://eso.chipmunk.land/index.php/post/78/</id>
		<updated>2026-06-24T04:21:39Z</updated>
		<author>
			<name>max</name>
		</author>
		<content type="html"><![CDATA[<p>On a side note, I wish I had actually bothered to learn SQL previously.</p>]]></content>
	</entry>
	<entry>
		<title>max</title>
		<link href="https://eso.chipmunk.land/index.php/post/77/" rel="alternate"/>
		<id>https://eso.chipmunk.land/index.php/post/77/</id>
		<updated>2026-06-24T04:20:30Z</updated>
		<author>
			<name>max</name>
		</author>
		<content type="html"><![CDATA[<p>esoBB is experimental software, and as would be expected has bugs. This is a thread for reporting and tracking such bugs, especially ones encountered &quot;in the wild&quot; / on this forum.<br/>Note that this forum runs a <a href='https://code.chipmunk.land/chipmunk.land/esoBB' target='_blank' class='external' onclick='return Conversation.externalLink()'>fork</a> of esoBB, which means we can get quicker bugfixes. When patches are finished, I will try to contribute them <a href='https://github.com/geteso/esoBB' target='_blank' class='external' onclick='return Conversation.externalLink()'>upstream</a>.</p><p>Currently known bugs:</p><ul><li>Flood checker making invalid queries and causing error 500 -<b></b> partially fixed in the fork (by commenting out the faulty code); a real fix would require changing the database schema to account for IPv6</li><li>The email regex is too strict -<b></b> partially fixed in the fork; note that the current regex in the fork doesn&#39;t account for all possible emails (especially ones with quoted local-parts) and the old regex is still scattered across various files.</li><li>RSS feed returns error 500 -<b></b> fixed by renaming the plugin to avoid collision of class names, patch submitted upstream.</li><li>Many database values are unsigned 32-bit ints which could overflow -<b></b> more of a risk than a bug, perhaps it&#39;s not really significant; note that php only supports directly handling 64-bit integers on 64-bit processors as of now, AFAIK.</li></ul>]]></content>
	</entry>
</feed>
