Closed (fixed)
Project:
Drupal.org security advisory coverage applications
Component:
module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Mar 2013 at 13:37 UTC
Updated:
4 Jan 2014 at 02:58 UTC
Jump to comment: Most recent

Comments
Comment #1
Seppe Magiels commentedAutomated review
The automated review indicates serveral problems, these problems should be fixed.
Manual review
The code looks very good, however I do have a few remarks.
1) For comments, like the one below, you should follow the documentation and comment guidelines.
2) Custom hooks should start with your module name. hook_apachesolr_taxonomy_link_alter should be e.g. hook_taxonomy_to_apachesolr_link_link_alter.
Further you should add a link to your sandbox page to the issue above.
Good job so far, keep it up! ;)
Comment #2
PA robot commentedWe are currently quite busy with all the project applications and I can only review projects with a review bonus. Please help me reviewing and put yourself on the PAReview: review bonus high priority list. Then I'll take a look at your project right away :-)
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #3
Cristobal Wetzig commentedThank you for your patiance Seppe!
Comments
Thank you! should be sorted.
is now:
Automated review
I reviewed and fixed!
http://ventral.org/pareview/httpgitdrupalorgsandboxcristobalwetzig192808...
Sanbox url
I misunderstood the link to the sandbox, for some reason I thought it was the sandbox-repo url.
I added the sandbox url. Sorry about that. It was pretty clear in the guideline.
Comment #4
musicalvegan0 commentedHi there,
Good job so far. A couple more things to look at:
Other than these minor issues, everything looks good to me. Good luck!
Comment #5
musicalvegan0 commentedForgot to change the application status to "needs work."
Comment #6
Cristobal Wetzig commentedfixed
Comment #7
kscheirerWhy do the README instructions start with 2? The search path should probably be a site-wide setting instead of a per-field setting, since it would always remain the same. Or even better just grab the value from the solr module directly. I don't see where you're using $settings['target'], taxonomy_to_apachesolr_link_field_formatter_view() doesn't seem to make use of it? Are taxonomy fields guaranteed to be im_* in solr?
No major issues though, this looks like a handy module.
----
Top Shelf Modules - Enterprise modules from the community for the community.
Comment #8
Cristobal Wetzig commentedGood catch! fixed.
The search path should probably be a site-wide setting instead of a per-field setting, since it would always remain the same. Or even better just grab the value from the solr module directly.I disagree, for example, you might want to use a certain path for lets say a custom solr search experience for lets say users.
I don't see where you're using $settings['target'], taxonomy_to_apachesolr_link_field_formatter_view() doesn't seem to make use of it?Correct, thats embarrassing. Fixed. Thanks!
Are taxonomy fields guaranteed to be im_* in solr?No, but drupal standard, and 99.9% user case? There is a drupal_alter function available to change the output for any other case.
Comment #8.0
Cristobal Wetzig commentedAdded a sandbox link
Comment #8.1
Cristobal Wetzig commentedadded one review
Comment #8.2
Cristobal Wetzig commentedadded review link
Comment #8.3
Cristobal Wetzig commentedlink had no href
Comment #8.4
Cristobal Wetzig commentedadded review link
Comment #9
Cristobal Wetzig commentedApplying to PAReview: review bonus
Comment #9.0
Cristobal Wetzig commentedadded review
Comment #10
kscheirerThanks for making those fixes, +1 from me.
Comment #11
Cristobal Wetzig commentedHi Kscheirer, thank you!
Btw!
I revised your point about
And you are right! Although you want to change it on field basis, you should be able to change the default value for all fields. I added a simple admin.page.inc to enable users to do so. Cheers for pointing that out.
Comment #11.0
Cristobal Wetzig commentededit
Comment #12
klausimanual review:
But that are not blockers, so ...
Thanks for your contribution, Cristobal Wetzig!
I updated your account to let you promote this to a full project and also create new projects as either a sandbox or a "full" project.
Here are some recommended readings to help with excellent maintainership:
You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and get involved!
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
Thanks to the dedicated reviewer(s) as well.
Comment #13
Cristobal Wetzig commentedCool! I will crack open a beer!
In theory this module could be used without apachesolr installed, (it could be using another drupal solr search).
Dammit! thanks.
This is really for nodes, and users. for example you have a tag on a usernode. When you click on the tag on the user or node teaser, you want to be directoed to the taxonomy term search (filtered) served by apache.)
Sloppy, thanks!
Comment #14.0
(not verified) commentedremoved automated review