In no particular order, here are some items I've noticed during working with Links SQL 2.1.1.
1) The detailed.html template does not seem to define $cat_linked or $title_linked (only $title) for linking back to the category. Kinda tough to navigate if using the next/previous detailed links and wanting to get back to the category... I'm not sure about $cat_linked's availability, but the default detailed.html says $title_linked should be available.
2) In review_search_results.html, $cat_linked isn't defined above the foreach($Review_Loop) loop, making it a bit difficult to customize the display to look like other pages throughout Links.
3) Any reason not to put reviews into the detailed page (or at least make it an option)? That seems like an intuitive place for them. Otherwise, the detailed page becomes pretty redundant unless you add some custom fields to fill it out.
4) Forward slashes in link titles get converted to whatever category separator symbol you use (> in my case, : by default) in the detailed.html template when displaying it with $title (doesn't happen with $Title, so presumably wouldn't be an issue if $title_linked worked in the template).
5) After updating a review (through the user interface), I got these errors followed by a second page (inline) showing the received review:
Column Review Owner cannot be left blank.
Column Review Rating cannot be left blank.
Column Review Date cannot be left blank.
Column Review Subject cannot be left blank.
Column Review Contents cannot be left blank.
Column Review Validated cannot be left blank.
It doesn't look like the review actually got updated, though... Nothing was submitted to the admin email address, nothing waiting to be validated, no changes made, etc.
6) What is the 'Review Validated' yes/no field for in addition to the validate/reject options?
7) What exactly is $Review_ByLine intended for? Seems redundant with reviewer's name and subject already shown... I tried corresponding it to something in Amazon's review setup (which the Links reviews look to be closely modeled after) and could not.
8) !$cfg_user_review_required in review_add_success.html still shows the anononymous name/email fields even when turned on (yes) in admin options. Should that be $anonymous like in review_add.html?
Dan
1) The detailed.html template does not seem to define $cat_linked or $title_linked (only $title) for linking back to the category. Kinda tough to navigate if using the next/previous detailed links and wanting to get back to the category... I'm not sure about $cat_linked's availability, but the default detailed.html says $title_linked should be available.
2) In review_search_results.html, $cat_linked isn't defined above the foreach($Review_Loop) loop, making it a bit difficult to customize the display to look like other pages throughout Links.
3) Any reason not to put reviews into the detailed page (or at least make it an option)? That seems like an intuitive place for them. Otherwise, the detailed page becomes pretty redundant unless you add some custom fields to fill it out.
4) Forward slashes in link titles get converted to whatever category separator symbol you use (> in my case, : by default) in the detailed.html template when displaying it with $title (doesn't happen with $Title, so presumably wouldn't be an issue if $title_linked worked in the template).
5) After updating a review (through the user interface), I got these errors followed by a second page (inline) showing the received review:
Quote:
Column Review Link ID cannot be left blank. Column Review Owner cannot be left blank.
Column Review Rating cannot be left blank.
Column Review Date cannot be left blank.
Column Review Subject cannot be left blank.
Column Review Contents cannot be left blank.
Column Review Validated cannot be left blank.
It doesn't look like the review actually got updated, though... Nothing was submitted to the admin email address, nothing waiting to be validated, no changes made, etc.
6) What is the 'Review Validated' yes/no field for in addition to the validate/reject options?
7) What exactly is $Review_ByLine intended for? Seems redundant with reviewer's name and subject already shown... I tried corresponding it to something in Amazon's review setup (which the Links reviews look to be closely modeled after) and could not.
8) !$cfg_user_review_required in review_add_success.html still shows the anononymous name/email fields even when turned on (yes) in admin options. Should that be $anonymous like in review_add.html?
Dan