sovaa / foursquared

Automatically exported from code.google.com/p/foursquared
Apache License 2.0
0 stars 0 forks source link

category of new venues not displayed #198

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. add a new venue
2. assign a category with android (in add-dialog)
3. hostpory-page of foursquare.com does not show category

What is the expected output? What do you see instead?
Venue can not be reassigned, because server says "Hmmm... looks like this 
category is already assigned to that venue"

What version of the product are you using? On what operating system?
Android v2010-06-16 (Desire)

Please provide any additional information below.

Original issue reported on code.google.com by stefan.b...@gmail.com on 23 Jun 2010 at 1:33

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
"hostpory-page" is a "history-page" ;)

Original comment by stefan.b...@gmail.com on 24 Jun 2010 at 7:48

GoogleCodeExporter commented 9 years ago
Could it be that the venue is getting the category, but it's not being assigned 
as the "primary category" (which I think isn't the default for foursquare 
venues, but should be)

Original comment by mitch.fi...@gmail.com on 24 Jun 2010 at 10:09

GoogleCodeExporter commented 9 years ago
At least it IS somehow assigned, because you cannot assing it again, but it's 
not shown. If you assign another category - it is the only one displayed, but 
not as primary. You can make the "second one" to the primary, but still you are 
not able to assign the "first" one (still not shown) to the venue.

Original comment by stefan.b...@gmail.com on 25 Jun 2010 at 11:12

GoogleCodeExporter commented 9 years ago
it works again!? I could at least assign a category now (the category which was 
not possible). 
i haven't tried to add a new venue.

Original comment by stefan.b...@gmail.com on 28 Jun 2010 at 4:38

GoogleCodeExporter commented 9 years ago
This works ok, was probably a serverside issue at the time you were trying it.

Original comment by mar...@gmail.com on 28 Jul 2010 at 3:29