summary refs log tree commit diff stats
path: root/theme/images/icons
diff options
context:
space:
mode:
authorStarla Insigna <hatkirby@fourisland.com>2008-12-19 20:40:26 -0500
committerStarla Insigna <hatkirby@fourisland.com>2008-12-19 20:40:26 -0500
commitc9968db2dddd42760e7adba2e9e5475925c4996c (patch)
treea83d6d3d0aae9f74cd489aebd87be1e9e02e776e /theme/images/icons
parent11565550e7ab6ef9987a298a0729fc016960252b (diff)
downloadfourisland-c9968db2dddd42760e7adba2e9e5475925c4996c.tar.gz
fourisland-c9968db2dddd42760e7adba2e9e5475925c4996c.tar.bz2
fourisland-c9968db2dddd42760e7adba2e9e5475925c4996c.zip
Fixed Admin's movePending output
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.
Diffstat (limited to 'theme/images/icons')
0 files changed, 0 insertions, 0 deletions