Closed milindalvares closed 10 years ago
According to the client I have done the following changes
- Toilets dont show up in the property specs - DONE
- Sanad; when you click on yes, still comes as No. - DONE
- Facilities and Built Up area should only show up when filled in. - DONE
- Basic alignment of the property specs (One below the other would be there) - KEPT AS PER THE REPO
- Price to show as Rs.3,00,00,000/- instead of Rs.30,000,000/- - _DONE in property.erb _
- In Land Search, 1bhk, 2bhk, 3bhk should not come up. Settlement, Orchard and Agriculture should come. - DONE
@milindalvares
- Should I upload the same to the server for the client to review or first complete testing?
- The database is reset so the same will get uploaded to the server. is it OK?
Don't delete the old database, but yes, replace.
Please drop gpc-default-thumb.jpg in the dropbox
Just suggestions:
@allyrods @hashaxel Check out the 'tests' branch for a behavioural change in the way filters work. Critical feedback is welcome on the direction.
As of now , besides the animations the reset is not functional. Have some concerns. Will share tomorrow. On 26-Aug-2014, at 7:43 am, Milind Alvares notifications@github.com wrote:
@allyrods @hashaxel Check out the 'tests' branch for a behavioural change in the way filters work. Critical feedback is welcome on the direction.
— Reply to this email directly or view it on GitHub.
@allyrods
@milindalvares
when 'Property Type' filter is selected, 'Location' filter shrinks too.
By design. Shows only locations which have properties of those type. Unless that's not the bug you're talking about.
@allyrods This is not reflecting on the live server.
when 'Property Type' filter is selected, 'Location' filter shrinks too. By design. Shows only locations which have properties of those type. Unless that's not the bug you're talking about.
@hashaxel @allyrods Hold on to that filter. Some bug has crept in.
The branch merged on the production is master are the changes in the master branch?
On 9 September 2014 15:47, hashaxel notifications@github.com wrote:
@allyrods https://github.com/allyrods
when 'Property Type' filter is selected, 'Location' filter shrinks too. By design. Shows only locations which have properties of those type. Unless that's not the bug you're talking about.
This is not reflecting on the live server.
— Reply to this email directly or view it on GitHub https://github.com/HashCookies/goaprop/issues/9#issuecomment-54949839.
Regards,
Alistair Rodrigues.
Pushed some code to the master. Let me know when deployed.
Note that the code will break wherever the _property.erb partial is called because it now requires another variable. Trying to find where all the calls are.
I also make a solemn oath never to share the DB again. so pains. much frustrating.
@milindalvares I think we are good to go. I like the idea of putting in the recently viewed properties side by side with recommendations, although, rendering the pin instead of just the title of the properties might lead to unnecessary scroll in cases where viewer checks out multiple properties. No?
Render what? (Is your sentence consistent with what you had to say?)
Let me break it down further. Right now, the recently viewed properties displays the tiles similar to the ones displayed in search results. My concern is when recently viewed properties are let's just say 6, those 6 tiles will add an unnecessary scroll. So why not just go with the title of the properties like before?
Recently viewed are capped at 3.
On 09-Sep-2014, at 5:20 pm, hashaxel notifications@github.com wrote:
Let me break it down further. Right now, the recently viewed properties displays the tiles similar to the ones displayed in search results. My concern is when recently viewed properties are let's just say 6, those 6 tiles will add an unnecessary scroll. So why not just go with the title of the properties like before?
— Reply to this email directly or view it on GitHub.
(Y)
You forgot the nipples. ( . Y . )
@allyrods Please make the changes live. Want to test with live content.
@allyrods One more thing, on the live server, the Porvorim tab in the Locations filter is larger than the rest.
Still? With the new code?
On 09-Sep-2014, at 5:31 pm, hashaxel notifications@github.com wrote:
@allyrods One more thing, the Porvorim tab in the Locations filter is larger than the rest.
Resolve the Porvorim tab — Reply to this email directly or view it on GitHub.
We'll see when live.
Tried it locally and it works fine. — http://hashcooki.es
On Tue, Sep 9, 2014 at 5:35 PM, Milind Alvares notifications@github.com wrote:
Still? With the new code? On 09-Sep-2014, at 5:31 pm, hashaxel notifications@github.com wrote:
@allyrods One more thing, the Porvorim tab in the Locations filter is larger than the rest.
Resolve the Porvorim tab — Reply to this email directly or view it on GitHub.
Reply to this email directly or view it on GitHub: https://github.com/HashCookies/goaprop/issues/9#issuecomment-54959222
It's Live.
The block which shows similar properties is not rendering. — http://hashcooki.es
On Tue, Sep 9, 2014 at 5:55 PM, Alistair notifications@github.com wrote:
It's Live.
Reply to this email directly or view it on GitHub: https://github.com/HashCookies/goaprop/issues/9#issuecomment-54961074
Are you sure this is the case? If there aren't any similar properties, it won't render.
Its rendering here.
@milindalvares Maybe you're right. Can we then layout the recently viewed properties horizontally after the similar properties grid? Grid of 3 properties in a row would look tight enough. Might also help in cases no similar properties and an empty space showing up.
That'll happen when @allyrods deploys the new changes.
On 09-Sep-2014, at 6:18 pm, hashaxel notifications@github.com wrote:
@milindalvares Maybe you're right. Can we then layout the recently viewed properties horizontally after the similar properties grid? Grid of 3 properties in a row would look tight enough. Might also help in cases no similar properties and an empty space showing up.
— Reply to this email directly or view it on GitHub.
Not going to set them after the similar properties though. I wanted to tie visually keep recently-viewed close to the inquiry form.
@allyrods
@milindalvares Sticky nav causing issues on property search page as well with so many locations added.
Removed sticky from the js. And some misc changes.
Merged Tests branch.
Made the changes live.
@allyrods Pushed some content edit on services to master
noticing an error on server "App 22519 stderr: W, [2014-09-25T00:00:49.208504 #22538] WARN -- : attack prevented by Rack::Protection::SessionHijacking"
I guess it has something to do with our sessions usage in the app.
After this at some points there is a save error. Log file in dropbox
Things I am working on in new and edit views
@allyrods
@allyrods @milindalvares
So I hear there aren't any errors in the multi hosts droplet GPC. @allyrods What's happening with the new 1GB droplet? Let me know if you aren't doing anything with it so I can delete it.
Milind
On 29-Sep-2014, at 1:58 pm, Alistair notifications@github.com wrote:
Option to put a Layout Plan. Option to put up a Master Plan. Requirement Form Inquiry Form to have: Name, Number and E-mail ID and display Brokerage Fee — Reply to this email directly or view it on GitHub.
If there are no complaints from GPC then you can go ahead and delete the droplet. I was working on it but if its not needed then delete it.
@hashaxel @milindalvares done this but please check it from your side. Its live.
Okay, so we're almost there.
I've refactored a bunch of things. Mostly should work smoothly, but just keep an eye for where properties are being linked to (the url now includes /:slug). Images also have the property id in their name.
Client said this stuff: Seems to work on my local server, so check it out.