There are corresponding MySQL/MariaDB system variables which can be used to override this behavior by including a custom (empty) stopword file: ft_stopword_file and innodb_ft_user_stopword_table .

Thank you for the tip, I have removed the stopwords accordingly. I didn't currently switch from ...

This visual blemish was not intentional and was a result of a class name collision (phpBB applies a class named bbcode-key to the button itself). Fixed.

I looked at this. phpbb_forums.forum_posts_unapproved is a column of type mediumint(8) unsigned . All of the rows have a value of either 0 or 1. I can only find one other reference online to the same issue. No clue what's wrong here, I don't think changing the type of the column to bigint is the ...

It looks like the registration page was broken after an upgrade of the wiki software. The issue should be resolved now. Sorry about the trouble!

I am sorry you've lost your post. There are always things to improve.

We have phpBB cofigured to keep the contents of deleted posts, so I have checked the database. Unfortunately, it looks like phpBB treats disapproved posts differently from deleted ones, and voids them completely. ( ref )

So this is something to note for moderators in the future. We may want to ...

Apologies, this should be fixed now.

Sorry about that, all versions of 2.0.72 should be correctly set to stable now.

aka13 wrote: Thu Oct 30, 2025 11:15 am This seemingly now broke prosilver_wide entirely, 500 on opening topics :lol:
I surrender, I will use the white text on black background

Looks like the cache wasn't properly cleared, does it work for you now?

aka13 wrote: Tue Oct 28, 2025 7:07 pm The simple spoiler breaks in prosilver again, just FYI.

Fixed.

Shirasik wrote: Mon Oct 20, 2025 9:05 am As for the meme. I triggered because it looks like you laughing at developers, not with them.

It's alright, I find the meme funny. It reminds me of my own meme in response to Version 1.1.66, which was (unintentionally) a completely blank release, unlike this one.

It appears that the binary has suffered from some form of corruption during the deploy process, but so far we've been unable to determine the root cause. It may be a compiler bug, a hardware issue, or a bit flip caused by a cosmic ray. The build server does have ECC RAM and reported no issues so far ...

The team believes the Factorio Lua engine is not affected by this bug.

So I went ahead and changed the fulltext_mysql_min_word_len setting to 2 manually in the database. After clearing the cache and together with the change made to MySQL/MariaDB earlier, it seems like it is now possible to search for old mod version as Koub wished. 3- and 2- character words are no ...

I've set the MySQL variables ft_min_word_len and innodb_ft_min_token_size to 2, confirmed that the setting is applied on the server, and rebuilt the post index, but so far I can't see a difference in the search results...

Let me offer some insight into the search situation. phpBB offers three search backends that we can use: phpBB Native Fulltext , MySQL Fulltext , and Sphinx Fulltext .

We were using phpBB Native Fulltext for years. There were reports that it had multiple issues, such as not supporting words with ...

No worries. I wonder if the text in the error message could be improved to bring clarity to such issues.

Hmm, so the issue is with the current version on disk?
I notice the timestamp on this file is Jun 23, 2025, the other files in the folder have a date of Apr 14, 2025.
Quite possible I mistakenly modified this file, I do poke around.


Yes, something must have modified the file. The original ...

I got myself a MacOS setup and I was able to upgrade to 2.0.67 (Space Age) from both 2.0.66 and 2.0.65 without a problem. I would like to know why that particular file on your system has different contents, than the Factorio updater expects. If you could upload /Applications/factorio.app/Contents ...

Implemented in version 2.0.66.