I will bring it up (again) - I did so after the previous post but I think those who work on web side of things have been swamped lately dealing with the usual new site stuff that comes up. [import]uid: 52491 topic_id: 19305 reply_id: 115021[/import]
Another 2 months have past. 
As of today this error still exists. [import]uid: 51401 topic_id: 19305 reply_id: 122975[/import]
While the Forum`s Search does not work as expected I think that bit.ly does not matter at all before getting the search working nicely first IMHO.
PS: BTW Ive never seen this bit.ly working here. However for me it isnt a problem at all too - first important things come first - the Forum`s Search Engine.
My .2c.
Rodrigo. [import]uid: 89165 topic_id: 19305 reply_id: 122977[/import]
Hey guys. Yes, sorry, this has taken longer. But as Rodrigo says, the bit.ly thing is pretty low priority. It pre-dates me here, but I suspect it has not worked in a very, very long time
This is not an excuse - I hate the idea of us having something sitting there that doesnt work, but with so much to do we just have to prioritize things (especially core SDK things) and this one is not near the top. For what it’s worth, it’s on our list to either fix soon or just get rid of it.
David
[import]uid: 10668 topic_id: 19305 reply_id: 123006[/import]
I agree that the focus should be on more important things.
Unfortunately to me, as a customer, it creates the impression that CoronaLabs isn’t on top of things. Now, before I get flamed to hell and back, I said that’s the impression that gets created. I’ve been attacked by users and even the creator of CoronaSDK about this. The fact that this has been going on for so long doesn’t really inspire confidence. I wholeheartedly agree that other issues concerning the website should be resolved first.
My vote would be to just get rid of this feature. There is no reason why the option should still be available if it hasn’t work for such a long time. [import]uid: 51401 topic_id: 19305 reply_id: 123106[/import]
kodewulf - I agree with you. Rest assured we are on top of things, especially on the SDK side, where it counts the most (for now). On the web/forum side, I completely acknowledge that we can be better and will get better because it’s important.
I have no real excuse for this “feature” just being there and not working for a long time now. It also drives me crazy and I agree that we will probably just get rid of it. So thanks again for the feedback - no flaming from us.
David [import]uid: 10668 topic_id: 19305 reply_id: 123396[/import]
Another 2 months have past. As of today this error still exists. [import]uid: 51401 topic_id: 19305 reply_id: 122975[/import]
While the Forum`s Search does not work as expected I think that bit.ly does not matter at all before getting the search working nicely first IMHO.
PS: BTW Ive never seen this bit.ly working here. However for me it isnt a problem at all too - first important things come first - the Forum`s Search Engine.
My .2c.
Rodrigo. [import]uid: 89165 topic_id: 19305 reply_id: 122977[/import]
Hey guys. Yes, sorry, this has taken longer. But as Rodrigo says, the bit.ly thing is pretty low priority. It pre-dates me here, but I suspect it has not worked in a very, very long time
This is not an excuse - I hate the idea of us having something sitting there that doesnt work, but with so much to do we just have to prioritize things (especially core SDK things) and this one is not near the top. For what it’s worth, it’s on our list to either fix soon or just get rid of it.
David
[import]uid: 10668 topic_id: 19305 reply_id: 123006[/import]
I agree that the focus should be on more important things.
Unfortunately to me, as a customer, it creates the impression that CoronaLabs isn’t on top of things. Now, before I get flamed to hell and back, I said that’s the impression that gets created. I’ve been attacked by users and even the creator of CoronaSDK about this. The fact that this has been going on for so long doesn’t really inspire confidence. I wholeheartedly agree that other issues concerning the website should be resolved first.
My vote would be to just get rid of this feature. There is no reason why the option should still be available if it hasn’t work for such a long time. [import]uid: 51401 topic_id: 19305 reply_id: 123106[/import]
kodewulf - I agree with you. Rest assured we are on top of things, especially on the SDK side, where it counts the most (for now). On the web/forum side, I completely acknowledge that we can be better and will get better because it’s important.
I have no real excuse for this “feature” just being there and not working for a long time now. It also drives me crazy and I agree that we will probably just get rid of it. So thanks again for the feedback - no flaming from us.
David [import]uid: 10668 topic_id: 19305 reply_id: 123396[/import]