simonpkerr / music-memories Goto Github PK

a timer needs putting on the search drop down so it doesn't disappear accidentally.

issues remain with IE7 layout

youtube search should be parallel with amazon search on listings page.

email needs to work for registration and feedback.

at present, default walls are just called 'my memory wall.' These need to be more personalised. Maybe use the username, an 's after it, then a random adjective (groovy, funky, cool, nice etc) then 'memory wall,' which would make them more fun.
also, assign a random image that the user can then change. this would make the gallery more appealing.

memory walls should be taggable including individual items on walls and when a search is done, an autosuggest could be created that searches the tags and suggest appropriate matches. Some way would need to be looked at to moderate the tags though

youtube search for many items is still irrelevant -
http://noodledig.com/mediadetails/B000UZPM76/amazonapi

users should be able to add comments to their walls as a whole or individual items on a wall. others should also be able to submit comments which can then be edited or removed by the wall owner, or the one who added the wall.

super admin should have rights over all sections of the site, including the ability to edit, update and delete memory walls of other users from the UI. This links with the acl issue that needs researching.

instead of deleting old cached data for MediaResourceListingsCacheRepository and ProcessDetailsStrategy there and then, either persist or merge the new data in the relevant method.

if a youtube search returns no results, log it and log the title of the item, allowing it to be added to the reg ex.

in IE, clicking the YouTube list item title does not cause the main panel title to change

so users can connect with each other and share links between walls. one user can send a request to another to create a mutual link between walls.

if the user searches just by keyword, a decade should try to be identified and used to categorise it. this could be the title (amazon products sometimes have year in square brackets) or one of the attributes of the item (this needs investigating)

when choosing items from the same decade, genre, etc, they are not being shown as recommendations

As well as adding items to walls, people will most likely want to comment on them. Others may want to as well. Each comment would have to be associated with a wall in the db and flaggable as inappropriate so it can be hidden/removed. Wall owners and those that add the comments should also be able to remove/edit their comments.

automated mechanism for people to submit comments, suggestions or complaints

a scrollable timeline of wall items including amazon, youtube, memory walls associated with decades and users (based on age).

use acl to determine who has rights to do what and in what level of detail - http://symfony.com/doc/current/cookbook/security/acl.html
this could be used for memory wall creating, editing, deleting, un-deleting, commenting, moderation etc.

when logged in, this should not appear.

to get round the caching issue with the site having to manually delete db entries, simply run a cron job on all xml files saved every 24 hours that checks whether the file is older than 24 hours and if it is, the file is deleted. this would remove the need for the app to delete db entries.
this development will have to happen once the caching mechanism has been updated to use xml files rather than saving flat xml in the db.

in the recent amazon statement, there are updated words that need to go with listings and details pages. include these.

add in a home button next to all the other controls in addition to the logo

at present, the only thing in the url identifying the wall is the name. if someone changes the name, the url will break if it has been sent to anyone. therefore, either the old names have to be stored as well as the current one, or the id of the wall has to be used in the url as well.
this way, if someone is linking to a wall that has had the name changed, the url will still work, if it only based on url.

use the sonata news bundle so that news items can be added to the home page. this would only be if facebook could be integrated into the home page. this would allow facebook updates to be integrated on to the home page.

news items could be auto-generated for each new user that is created or each new memory wall.

when finding recommendations use the decade and genre to find them. currently, if decade is null, the search is aborted. the recommendations could be extended so that if genre is not null the recommendations are based on that

When keywords are included in the search, from the details page, the 'return to listings' link does not include these

with the re-factoring of the styles to scss, the style needs to be made more responsive.

use users ages to determine and suggest things they may be interested in or walls they might like

try to find the lowest price for an item based on the api and store in the cached object.

if the name of the amazon product has a single quote in, it causes an error with the youtube search. titles need to be html encoded.

the only front end file working is app_devbrowser which doesn't show custom errors. This needs rectifying

in the edit-authentication page, the update profile form doesn't require a user to input the correct current password so can be set to anything.

when an amazon product is added to a wall, if the user clicks back on the browser to go back to the details page and then adds a YouTube item, it is added into the wrong area of the wall.

need to add t&c, privacy policy, and amazons disclaimers to the items as per updates from Amazon API

sm icons for twitter, facebook and email are only sharing the site, not the specific page that the user is on. Need to use some js to target the specific page that the user is on.

need to add google analytics

add in the ability to choose a layout method. either static, grid, list, or custom where the user can move things around themselves.

create a file for each item and just store a pointer to the file in the db

there needs to be an admin section so that I can remove content that is deemed offensive (or at least hide it).
The best way would probably be to have a 'flagged' table that marks any page as flagged, emails me and the page author, allows me to see the page and potentially disable it. This would most likely only apply to walls so the wall could be made private if it was flagged as inappropriate.