| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The following changes were also made in this revision:
* All HTML was changed to XHTML and a !DOCTYPE was included to reflect this
* Rewrote quotes tracking system to be much less complicated and actually working
* Changed quotes rendering to look more like Chirpy than Rash
* Fixed comment textarea bug
* Rewrote a ton of CSS so it's not as bloated
* Added a JavaScript confirmation when deleting a comment
* AJAXified voting on the POTW
* AJAXified voting and flagging quotes
* AJAXified commenting
* AJAXified voting on posts
* Added DateFinder back after it was accidentally deleted in Layout 4.5
The following database changes must be performed as soon as possible:
* Fix title of NO <!DOCTYPE> post (the < is missing the semicolon)
* Restore post Frasty Tha Snaman from a backup
* Reset "flag" field of all rows in "rash_quotes" to 0
* Remove the "vote" and "flag" columns of "rash_tracking"
* Rename the "quote_id" column of "rash_tracking" to "vote"
The following external code changes must also be performed as soon as possible:
* Add the following line to the end of the // Four Island block in The Fourm's functions.php:
require('/svr/www/hatkirby/fourisland/main/includes/specialdates.php');
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the comments table referenced users by username. However, if user ever changed their username, everything would become messed up. To fix
this, the index has been changed to the user ID. This change obviously requires maintenance:
This SQL must be run: "ALTER TABLE `comments` ADD `user_id` INT( 11 ) NOT NULL AFTER `page_id`;"
This PHP will generate some SQL that must be run:
<?php
$getusers = "SELECT DISTINCT username FROM comments WHERE is_anon = 0";
$getusers2 = mysql_query($getusers);
while ($getusers3 = mysql_fetch_array($getusers2))
{
$getuser = "SELECT * FROM phpbb_users WHERE username = \"" . $getusers3['username'] . "\"";
$getuser2 = mysql_query($getuser);
$getuser3 = mysql_fetch_array($getuser2);
echo("UPDATE comments SET user_id = " . $getuser3['user_id'] . " WHERE username = \"" . $getuser3['username'] . "\" AND is_anon = 0;<BR>");
}
$getusers = "SELECT * FROM anon_commenters";
$getusers2 = mysql_query($getusers);
while ($getusers3 = mysql_fetch_array($getusers2))
{
echo("UPDATE comments SET user_id = " . $getusers3['id'] . " WHERE username = \"" . $getusers3['username'] . "\" AND is_anon = 1;<BR>");
}
?>
This SQL must be run: "ALTER TABLE `comments` DROP `username`;"
|
| |
|
|
|
| |
There was a bug where, if an anonymous commenter used a username that was being used by an actual member, Four Island would think the anonymous
commentor was actually the member.
|
| | |
|
| |
|
|
|
|
| |
Also fixed spelling of maintenance in places where it was incorrectly spelled.
Maintenance Required: Rename "mantainenceMode" config to "maintenanceMode"
|
| |
|
|
| |
Now, changes can be remotely pushed to the central repository and updated using the Admin panel.
|
| |
|
|
|
| |
Many SQL queries were using the function addslashes() to escape their content. They have been replaced with the more secure
mysql_real_escape_string() function.
|
| |
|
|
|
|
| |
Previously, if a draft was being moved into the pending queue, it would be deleted instead. The problem turned out to be the fact that when the tag
system was changed (409d99f03471), the single instance in the admin panel of a draft being changed into a pending post was not fixed as the rest
were. The extra column in the "INSERT" query annoyed MySQL as that column no longer exists.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Certain posts, when moved around, were strangely deleted from the pending queue. This was actually two seperate bugs, both causing the same problem.
1. When looking for the post to swap with, the movePending command would search for the next post with an ID greater than or less than the current
ID, but it wouldn't actually sort the results correctly so that the corrent posts wouldn't neccessarily always be the post shown. This resulted in
a seemingly random pending posts being deleted. This has been fixed by adding a simply "ORDER BY" clause to the SQL "SELECT" commands.
2. When re-inserting the pending posts into the queue (after swapping IDs), if one of the posts contained invalid characters requiring escaping,
MySQL would reject the post without error and simply not insert it, resulting in one or more of the posts involved in the switch to be deleted.
This has been fixed by wrapping the text of the post in the mysql_real_escape_string() function.
|
| |
|
|
|
| |
The admin panel's movePending was suffering the same Every Item Is Exactly One ID Away From One Another syndrome that the main blog was facing in
changeset 8c0096629f88 (Fixed blog post Next/Previous links)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The movePending command is used to re-arrange the pending queue. However, it's output had two errors:
1. If the move completed sucessfully, the pending queue would be shown again. However, the URL would still be the movePending command, with it's
parameters. Because of this, if the user refreshed, it would try to re-arrange the queue again, which could cause some strange things to happen as
the post in question had already been moved. This problem has been fixed by redirecting to the managePending command after executing the
movePending command instead of simply running the managePending command internally as used to be the problem.
2. As a collary of the preceding error, if the move failed, the error would simply back up the browser's history and refresh. If the previous page
was the output of a sucessful movePending command, strange things would happen. This was fixed dually by the previous solution and the fact that
now the error messages simply link to the managePending command.
|
| |
|
|
|
| |
I decided that, because I use the :) emoticon so often, I might as well replace it with an actual image. I've added a Smiley parsing system to
complement the BBCode parsing one.
|
| |
|
|
|
| |
Previously, Four Island posted a blog, and then searched through the table looking for it so it could retrieve its ID. Now, the "mysql_insert_id()"
function is used instead.
|
| |
|
|
|
| |
For some reason, the source is full of www subdomain links. The rewriting engine doesn't seem to rewrite correctly, so most www subdomain links
forward to the original URL, not the rewritten URL, which is the base of the Pingback error.
|
| |
|
|
|
|
| |
This new tag system has a seperate table for tags. This way, a tag cloud can be made much more easily than if using the previous system.
This changeset requires manual maintinence.
|
| |
|
|
|
|
| |
Previously, the blogging engine only allowed for three tags per post, and it also stored each in seperate fields. Now, all tags are stored in one
field and there can be more than three. The only functionality that has been removed because of this is that now, on archive pages, tags are not
shown next to the current month's posts as they used to be, because the Four Island templating system does not yet support sub-blocks of sub-blocks.
|
| | |
|
| | |
|
| |
|
|
| |
Since MediaWiki was introduced to Four Island, the old wiki module hasn't been used, so it is not necessary to be present.
|
| |
|
|
|
| |
Fixed the Quotes Management module in the admin panel so that comments with line breaks in them would actually show up on individual lines. Also, the
quotes can be distinguished from one another by every other row in the table being shaded differently.
|
| | |
|
| |
|
