profile and event pages

[hashplan]

Please style "reset search" button in #3276b1.

On http://hashplans.com/user/events/all page:

1) the title of the page should be "Events in " . $metroarea ." Area".

2) would be cool if instead of the profile picture of the user, the iframe of the map was shown of the metroarea. Let me know how easy this is. I know currently for the event modal we use venue name and city for each specific event, but our event results search and location filtering are based on metroareas.

3) All events that the user adds to their calendar/profile should not disappear from the "all" list. They should instead have the In favourites or a similar one if they add to calendar to identify that they already have that event favorited or on their calendar.

4) we should remove the "Profile options" from the events page

On http://hashplans.com/user/events page:

1) please update public function index() { $this->my(); } in controllers/user/events to load $this->all(); by default

2) depending on how we determine user's location in profile options, 1) above should default to user's location.

[romasolot]

All done except №2 (map is supposed to be used instead of user avatar)

[hashplan]

I am taking off the "fixed" label so that we can do No 2 above.

[romasolot]

I've invented three variants so far:

1) User selects location using the map only 2) User can insert his address to the line or select using the map 3) User selects country from the lists (maybe a state, so that to reduce the list of cities), metroarea (it is necessary to have the list of all cities of the available countries)

If the crawler is related to the stubhub structure (the stubhub metroarea id is used), we'll have to store a temporary metroarea, which is filled in by user if it has not been parsed by crawler. Once such metroarea shows up, we relate user to this metroarea.

In case crawler gets the name only and inserts metroarea to the table itself (not relating to the external id), then we define metroarea once user has entered the data or selected POI on the map, and if there is no such metroarea in the table, we create it and relate to user.

What do you think about it? Which variant would work the best for you? Or maybe you got any other ideas regarding this?

[hashplan]

Lets wait for this one until we take a look at the crawler.