| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
I don't know, a lot of stuffses happened that I don't quite remember anymore. Goodness, that's not good.
|
| |
|
|
|
| |
Previously, when a post was deleted, it's adjacent posts displayed nothing for the respective Next/Previous link because there was no post with an ID
exactly one before or after it. Now, blog.php just looks for the next or previous ID, regardless of if it's actually adjacent.
|
| |
|
|
|
| |
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.
|
| |
|
|
|
| |
After you voted on the POTW, the resulting page used to be very strange and hideous. This has finally, after being like this since the beginning of
the third layout, been fixed.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
| |
They look better up there. :)
|
| |
|
|
|
| |
As KFM is pretty much dead, there is no need for an incomplete comic viewing module. Anyway, if I was ever going to start KFM again, the comics would
be displayed on the main blog.
|
| | |
|
| |
|
|
|
| |
Because pingbacks just aren't comments, they shouldn't be stored in the comments table. So, a new table has been created for them and the blog post
view pages have been accomodated to show them at the bottom just like the related posts are shown.
|
| |
|
|
|
|
| |
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.
|
| |\ |
|
| | |
| |
| |
| |
| | |
Apparently people actually do like the sixth layout. It was just me
being paranoid, they were busy over there.
|
| |/
|
|
|
| |
It turns out that FeedBurner somehow gets a hold of the original URLs for blog posts instead of the rewritten ones, so users clicking on them go there. I've fixed the
problem by checking for "index.php" in the URL in blog.php, and redirecting if it finds it. This was the problem with the Pingback thing.
|
| |
|
|
| |
Oh so many people complained at the new, pretty layout. The decision was reached in the Poll of the Week: Layout 6 had to go.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
phpsvnclient.php was previously used to interface the Four Island Subversion Repositories so changesets could be seen via the RSS feed, but not only
not many people want this in their RSS feed, and the people that did could get a seperate feed, but Four Island no longer uses Subversion, instead it
uses the better, distributive Mercurial.
|
| |
|
|
| |
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.
|
| |
|
|
| |
Really, there is no reason to have a CAPTCHA on a Login page. reCaptcha can be re-added to Four Island when a registration page is created.
|
| | |
|
| |
|
