Need Uploader help? (was: Report Uploader Errors)

MrsHand · Post by **MrsHand** » February 26th, 2014, 7:50 pm

Is anyone else getting notification that none of the librivox.org pages are able to be found? I can't get the catalog, uploader or workflow to pull up. Says "website is not available" in all three of my browsers (Chrome, IE, Firefox).

ETA: Also now seeing "server refused connection" in the MW on chrome.

Post by **MaryAnnSpiegel** » February 26th, 2014, 7:54 pm

Kristen,
Yes, this started just a few minutes ago. Forums work ok, but no uploader or MWs. I've reported it to the admin team.
MaryAnn

BillyShakespeare · February 26th, 2014, 10:37 pm

The uploader is not working

Purplemoon · Post by **Purplemoon** » February 26th, 2014, 11:03 pm

Hello,

When I tried to open the link to upload the file, the link refuses to open. I am using Window 7. Any recommandations?

Thanks, Purpelmoon

RuthieG · Post by **RuthieG** » February 26th, 2014, 11:13 pm

Only recommendation is to wait, I'm afraid, until we can contact the sysadmin to put this right. I have emailed him.

Ruth

Post by **TriciaG** » February 27th, 2014, 7:09 am

Should be up and running now, per the sysadmin.

BillyShakespeare · Post by **BillyShakespeare** » March 3rd, 2014, 4:32 pm

I am having trouble with the uploader it is giving me this message, Error SyntaxError: JSON.parse: unexpected character.

Post by **annise** » March 3rd, 2014, 5:42 pm

From the FAQ thread:

Q. After Uploading a file I am getting one of the following messages:
SyntaxError: JSON.parse: unexpected character (Firefox)
SyntaxError: Unexpected token (Chrome)

A. Refresh the uploader page to make absolutely sure that you are logged in, and upload again. This error seems to occur when you have become logged out unbeknown to you, perhaps a program updating in the background might be the cause

Purplemoon · Post by **Purplemoon** » March 11th, 2014, 12:18 am

Hello,
I am having problem exporting the mp3 file. Audacity and lame library seemed downloaded ok for Mac ox. but every time i try to export, I got message: unable to open target file for writing. What I have been doing wrong? Thanks for help.

Purplemoon

YouTube · Post by **Darvinia** » March 11th, 2014, 12:34 am

Purplemoon,
If you post your question as a New Topic here:
viewforum.php?f=23
in the 'Need Help? Got Advice?' forum you will reach more people that will be able to answer your question. This forum is more for reporting bugs and glitches with our software.

Unfortunately I know nothing about Macs.

Purplemoon · Post by **Purplemoon** » March 11th, 2014, 12:54 am

Thanks Darvinia for your advise. I have posted it to the link you provided.
Thanks, Purplemoon

praChirp · Post by **praChirp** » March 13th, 2014, 8:56 pm

Hello,

Not an error per se, but is it a potential security problem that I can go to https://librivox.org/uploads or uploads.librivox.org and freely access ALL files on the librivox server? Even the abandoned project, bloopers, unofficial stuff, etc. And I was not logged in with my librivox account at the time, so the general public can access it. I took a screenshot but you can go there yourself: http://uploads.librivox.org/bloopers/lv_uploads.zip

Perhaps the folder permissions need to be changed so that only certain users or groups have access? I imagine having the folders public leaves LV open to bad hacker things.

-Prachi

ekzemplaro · Post by **ekzemplaro** » March 14th, 2014, 5:55 am

Hello Prachi san,

I'm afraid you are confusing between 'write permission' & 'read permission'.
If the mentioned folders are writable, you're correct. But you can write nothing there.

We are open to public. What's wrong?

Cheers,
Masa

Post by **TriciaG** » March 14th, 2014, 6:46 am

Thanks, Prachi! Masa is correct - it's not an error.

I can't remember the exact discussion when developing this, but I THINK we cannot put restriction on the "read" access without putting restrictions on the files in the MW themselves. That would mean that one-off, newbie PL's couldn't listen to the files to PL. The cost didn't justify the benefit of locking them up.

gypsygirl · Post by **gypsygirl** » March 14th, 2014, 12:39 pm

TriciaG wrote:Thanks, Prachi! Masa is correct - it's not an error.

I can't remember the exact discussion when developing this, but I THINK we cannot put restriction on the "read" access without putting restrictions on the files in the MW themselves. That would mean that one-off, newbie PL's couldn't listen to the files to PL. The cost didn't justify the benefit of locking them up.

That can't have been the reason. Hiding the directory listing doesn't have anything to do with permissions. I think maybe it was left that way so that BC's could have a way to check on uploaded files without needing to be given ftp access.