HTML and JSON for threads are no longer built when using an SQLite3 database #212
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: tslocum/tinyib#212
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Super weird issue. The board index builds fine, but it only contains thread OPs and no replies. In the management panel, all threads and replies appear normally and behave properly. But, even after clicking "Rebuild all", nothing is created in the /res/ folder.
Strangely, in extended testing, I've had a few instances where it appears to correctly build these files for one or two random threads? If I proceed to reply to one, that reply is entered into the database and shows up in the management panel, but that thread's HTML isn't rebuilt to make the reply visible. The specifics of the issue are difficult to pin down.
I'm guessing this was introduced in the "Add TINYIB_AUTOHIDE" commit, just because that was the most recent one to touch the database code. After reverting past that commit on my local instance, I'm able to properly rebuild the board again.
Thanks for reporting this. Please let me know if the recent commit and its instructions resolve this.
Anyone affected by this issue may need to run the following query, replacing
TINYIB_DBPOSTS
with its value in settings.php:Thanks! I've found out that SQLite only supports a subset of ALTER TABLE functionality, and a column cannot be changed with it. Is there an equivalent query I could use?
SQLite users:
Back up your database, then run the following query, replacing
TINYIB_DBPOSTS
with your posts table name:You can run the above query via the SQLite3 CLI:
Fantastic, everything seems to be resolved and a rebuild works as expected now. Thanks for the timely response.