This topic is currently marked as "dormant"—the last message is more than 90 days old. You can revive it by posting a reply.
1sunny
When trying to upload a picture for a venue I get
''Feb: 18, 2010. This feature is temporarily down as we transition the images to a new system."
''Feb: 18, 2010. This feature is temporarily down as we transition the images to a new system."
4sunny
Bump. Sigh.
Is this browser related? Or is it just me? I can't imagine nobody else wants to upload new venue pictures.
Is this browser related? Or is it just me? I can't imagine nobody else wants to upload new venue pictures.
5jcbrunner
I eagerly await the release of conceptdawg from the dungeon they are keeping him ... (Local is in dire need of improvements).
As for the reason of the interruption, Sonya emailed me back some weeks ago: "We're still working on where to hold the photos that aren't personally associated with you (unlike your gallery and junk drawer)."
As for the reason of the interruption, Sonya emailed me back some weeks ago: "We're still working on where to hold the photos that aren't personally associated with you (unlike your gallery and junk drawer)."
6timspalding
Sorry. It's on the list to work on. I wish I had the time to fix everything right now.
7justjim
Just rub the swab firmly on the inside of your cheek and send it back. Your new clone should be coding within a year.
8sunny
As long as there is a _reason_ for it being down it's ok. It just looked as if it had been forgotten.
Maybe add an update to the error message?
12SpacemanSpiff
Here's a question:
If the new version of this feature is not yet ready for transition, then why was the old version removed? In other words, why can't we continue to use the old version until the new version is ready to be unveiled?
After all, it's been six months that we've been patiently waiting....
Thanks.
If the new version of this feature is not yet ready for transition, then why was the old version removed? In other words, why can't we continue to use the old version until the new version is ready to be unveiled?
After all, it's been six months that we've been patiently waiting....
Thanks.
13theapparatus
Going to hold my breath until we get this feature returned.
:)
:)
14johninvienna
I have asked Lorax to add this to the long standing bug tracking thread (list). I hope she can do this or if not, someone else can take over the compilation. I found her idea great, but it needs to be kept up!
Greetings, john
Greetings, john
15lemontwist
bump
16davidt8
I am glad to learn that I am not the only one wondering about this. Sorry to learn that so far there is no progress.
See:
http://www.librarything.com/topic/98787
See:
http://www.librarything.com/topic/98787
17lorax
14>
It's a tracking thread, not a tracking post. Feel free to add it -- I'm not going to add everything to the initial post, that's not the intention. Sure, some people don't have the patience to read a whole thread, but the staff could, and they're the only ones who can actually do anything.
It's a tracking thread, not a tracking post. Feel free to add it -- I'm not going to add everything to the initial post, that's not the intention. Sure, some people don't have the patience to read a whole thread, but the staff could, and they're the only ones who can actually do anything.
18johninvienna
17>
Quote from LORAX:
I can read, and you stated in your e-mail:
"I started this thread to have a single point to track and reference long-standing LT bugs. The order here is entirely arbitrary (i.e. the order that I thought of them) and is not intended to indicate importance, duration, or perceived ease of fixing them. Reference threads likewise were the first I found, not necessarily the first report or the most comprehensive discussion of the issue. This list does not include absence-of-features, either those that used to exist and have been disabled for performance reasons or those that have been requested and not implemented.
As I track them down I will add thread references for each issue. I'm sure I have forgotten some; please add them and I'll edit the first post accordingly."
I liked the idea that you explained in your message, especially the last sentence. If you have changed your intentions, that is ok. But saying that was not the intention to....
Hey, guys/gals, who would like to keep up the "long standing bug tracking thread (list) started by LORAX?. It would be very useful to have a single list of the long-term bugs in one place. I would offer to, but I simply do not understand all of them. We need someone technically and editorially competent.
Anyway, thanks Lorax, it was a great idea! Let's see if someone can take it up.
Quote from LORAX:
I can read, and you stated in your e-mail:
"I started this thread to have a single point to track and reference long-standing LT bugs. The order here is entirely arbitrary (i.e. the order that I thought of them) and is not intended to indicate importance, duration, or perceived ease of fixing them. Reference threads likewise were the first I found, not necessarily the first report or the most comprehensive discussion of the issue. This list does not include absence-of-features, either those that used to exist and have been disabled for performance reasons or those that have been requested and not implemented.
As I track them down I will add thread references for each issue. I'm sure I have forgotten some; please add them and I'll edit the first post accordingly."
I liked the idea that you explained in your message, especially the last sentence. If you have changed your intentions, that is ok. But saying that was not the intention to....
Hey, guys/gals, who would like to keep up the "long standing bug tracking thread (list) started by LORAX?. It would be very useful to have a single list of the long-term bugs in one place. I would offer to, but I simply do not understand all of them. We need someone technically and editorially competent.
Anyway, thanks Lorax, it was a great idea! Let's see if someone can take it up.
19lorax
The original intent was that I'd add ones that had been long-standing at the time, but it's confusing if not misleading to edit a post from May or so to include bugs that didn't even exist at the time.
I'm not quite sure why you're so angry about this, and I'm very definitely not sure why you're so patronizing. I did a hell of a lot of work to put together that initial post, and to have it dismissed with a pat on the head and a call for someone "competent" (i.e. unlike me, apparently) is offensive in the extreme. I just moved 3000 miles. Cut me some slack.
I'm not quite sure why you're so angry about this, and I'm very definitely not sure why you're so patronizing. I did a hell of a lot of work to put together that initial post, and to have it dismissed with a pat on the head and a call for someone "competent" (i.e. unlike me, apparently) is offensive in the extreme. I just moved 3000 miles. Cut me some slack.
20jjwilson61
I can understand John's frustration but I didn't detect any anger in his post. He was merely responding to your patronizing post when he was merely following the directions that you yourself gave in that first post. A more fitting response from you would have been to apologize for not updating that first post when your intentions changed.
ETA: And I also think that your original intention was good. People can mistakenly post non-bugs in the thread or there can be long streams of discussion in the thread both of which make it no longer the desired list. Someone going through the list and updating the first post with an actual, vetted list would make the whole thread much more useful.
ETA: And I also think that your original intention was good. People can mistakenly post non-bugs in the thread or there can be long streams of discussion in the thread both of which make it no longer the desired list. Someone going through the list and updating the first post with an actual, vetted list would make the whole thread much more useful.
21johninvienna
Good grief, absolutely no anger. WE are all happy when someone like Lorax takes time to enumerate long standing bugs.
Anyway - no hick hack - but a new suggestion. Alfter discussion in a bug thread - new ones for each bug - what about entering it in:
http://www.librarything.com/wiki/index.php/Bug_tracking#Bug_tracking_points
There it states:
"This is a bug tracking page
We're trying to keep most bug talk on the Talk system, mostly in the Bug Collectors group. Talk is a better place to investigate problems, which usually requires dialogue."
We would need to update the list there - it seems to have stopped in 2007!!!
When the bug is fixed (hopefully all eventually) it can be moved to:
http://www.librarything.com/wiki/index.php/Bug_tracking/Fixed_or_resolved
I would suggest that a bug go on the list after two months. Then new members with the same bug can be told there is a list and we are watching it. Of course, it would be nice if LT themselves kept this up - but I think it could also be done by members.
Anyway - no hick hack - but a new suggestion. Alfter discussion in a bug thread - new ones for each bug - what about entering it in:
http://www.librarything.com/wiki/index.php/Bug_tracking#Bug_tracking_points
There it states:
"This is a bug tracking page
We're trying to keep most bug talk on the Talk system, mostly in the Bug Collectors group. Talk is a better place to investigate problems, which usually requires dialogue."
We would need to update the list there - it seems to have stopped in 2007!!!
When the bug is fixed (hopefully all eventually) it can be moved to:
http://www.librarything.com/wiki/index.php/Bug_tracking/Fixed_or_resolved
I would suggest that a bug go on the list after two months. Then new members with the same bug can be told there is a list and we are watching it. Of course, it would be nice if LT themselves kept this up - but I think it could also be done by members.
22Nicole_VanK
Apparently uploading venue pictures has been restored: http://www.librarything.com/topic/98874#

