-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In favorites and webcovers facet pages show new crag summary cards #2823
Comments
Also I think for consistency we should swap the json nesting. ie instead of being a list of webcovers which contain a node, it should be a list of nodes which have a webcover. Do we care about showing two webcovers for those nodes which have more than one? |
I will do template data
Because it is a webcover search I think we want to show one webcover per area. If there are mulitple webcovers assigned then we should dup the node and show the expicit webcover. I am still committed to do the slide show webcovers at a crag area if there are multiple web covers. We just have to make sure it makes sense in the facet. |
@brendanheywood good call about restructuring the webcover facet data. This is now done and we get the rest of the issue done for free. You can pull from repo. Please close when you confirm it is what you want. Also let me know what you want for the home page. |
dev has old data, and for some reason the ajax to save webcovers is busted so I don't have nor can make any webcover test data. @scd can you please fix which ever is easiest? |
easiest is just to resync. I actually forgot to do the post release syncing which I have started this morning. I probably will not sync to your dev until this afternoon |
Dev has been resynced. |
Check this out: This is almost there but missing a few bits of data: @scd can you please:
|
Nice work. We should expose as missing nice image icon. One of these webcovers will end up on the home page, rotating every month or so? |
Something like that, more likely that we will fit 2-3 of them in a section. We can cross that bridge when we get to it. I've added a fallback to a map if it is located: and if not located then just a gradient placeholder.
|
@brendanheywood have you pushed all your code. I cannot find IncWebCovers |
doh try again |
On a cursory look it seems fine. One gothca here is that if a photo is associated with another copyright other than ours then you must have the copyright param included otherwise it will return nothing. The idea is that you should always be dealing with copyright when querying a copyrighted photo. There is the image bug you alluded to in #2837 so I am going to keep this open until this is also fixed. |
I re added the copyright param. From a performance perspective I prefer to do the With facets we have a list of nodes we need to get the web covers for, so typically I would do that outside the atomArea and pass through the results into atomArea. I am happy to just leave it as it is in the fav code for now. |
yeah sounds good, I was going to ask you to add the data but I was too keen to get it finished last night |
What you expected:
All this should be in exactly the same format as in the main index template
The text was updated successfully, but these errors were encountered: