Re: Adding to your queue

From: Stefan Kaczmarek <stefan_at_thezonie.org>
Date: Wed, 18 Apr 2007 21:32:19 -0700

So, I accidentally uploaded the following files (my files) into the
root folder of the web server instead of the /zonie folder (whoops!):

search.php
media.php
func.php
library.php
history.php
queue.php

If there were files that were similarly named, they've now been
whacked. I deleted my files, so if there were files there that got
stepped on, they'll be missing now.

Doh.

- Z

On Apr 18, 2007, at 8:46 PM, Stefan Kaczmarek wrote:

> Ok, so now there's an "Add to Queue" link on the media page. It
> will only poop on itself if the item is already in the queue, but I
> am assuming that we can get that remedied manana.
>
> - Z
>
> On Apr 18, 2007, at 8:32 PM, Stefan Kaczmarek wrote:
>
>> Actually, if the want to add something to their queue, why not
>> just shoot it to the top of their queue instead and not return an
>> error? Since that'll pretty much give the same effect.
>>
>> I still want an empty json callback of some kind, just so that I
>> know that it happened. (For async feedback, basically.)
>>
>> - Z
>>
>> On Apr 18, 2007, at 8:24 PM, Stefan Kaczmarek wrote:
>>
>>> D,
>>>
>>> Right now if you try and add something to your queue that is
>>> already in there, it returns "DB Error: already exists" ... which
>>> isn't valid JSON. If there's an error, how about you return a
>>> JSON string with an 'error' param with some sort of
>>> descriptor ... or something ... I guess just don't return
>>> text ... Hell, you could put "DB Error: already exists" as the
>>> 'error' value. I don't care. :)
>>>
>>> Because right now, when there's a successful add, you return
>>> nothing, right? Just returning an empty JSON would be cool by
>>> me ... or an 'error' 'none' or '0' or something. Just so that I
>>> know shit completed correctly.
>>>
>>> - Z
>>
>
Received on Fri Sep 14 2007 - 10:55:57 BST

This archive was generated by hypermail 2.2.0 : Sun Sep 16 2007 - 22:19:46 BST