Short description:
Views Inject View Results module allows to inject results into view from other view.
The results are injected at position set as per 'position' field which should be in filtered content type - for the view that is to be injected.
The injected results will remain in fixed position (value of the 'position' field) while the primary view results will 'roll' around.
Use-case:
The news timeline with injected adds, where the adds are in fixed position and news are sorted by publish date and rolling around the adds.
How does it work:
Adjust 'main view' query for the rows to be injected.
Insert rows from 'view to inject' into 'main view' results.
Rows to be injected contain extra info with view: name, display_id and order_field: table and field.
The extended views style plugin render_fields() is able to switch the view and display if it finds above mentioned extra info.
This way user has total flexibility to theme/style the results from both views independently.
Project page link: https://www.drupal.org/sandbox/michael_dajewski/2896782
Git clone command:
git clone --branch 7.x-1.x https://git.drupal.org/sandbox/michael_dajewski/2896782.git views_inject_view_results
Comments
Comment #2
PA robot CreditAttribution: PA robot commentedThere are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpsgitdrupalorgsandboxmichael_dajewski2896...
Fixed the git clone URL in the issue summary for non-maintainer users.
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #3
Michael Dajewski CreditAttribution: Michael Dajewski commentedFixed majority of reported errors.
RE: some errors in views plugins.
Suggested corrections would make the declarations incompatible with parent declarations.
Comment #4
jonnyhocks CreditAttribution: jonnyhocks commentedRunning https://git.drupal.org/sandbox/michael_dajewski/2896782.git through Code Sniffer is reporting numerous issues that are recommended fixes.
Link to review report
Comment #5
Michael Dajewski CreditAttribution: Michael Dajewski commented@jonnyhocks thanks for the comment.
RE:
Cannot use $form_state['values'] because it is not available.
RE:
and
"Method name ... is not in lowerCamel format" errors do not apply since the methods are defined in the parent class (see: views module).
"Visibility must be declared on method/property" errors. The default visibility is public. All methods are declared in views module without 'visibility'.
"The var keyword must not be used to declare a property" errors - again this is how the properties are declared in the parrent classes - see views module.
"Type hint "array" missing for [variable_name]" error. Using hint would make render_grouping_sets() method incompatible with definition in the parent class.
RE:
These lines are in doc blocks:
I do not see nowhere in the core code nor in views module above comments adding parameter type.
Comment #6
Michael Dajewski CreditAttribution: Michael Dajewski as a volunteer commentedComment #7
sleitner CreditAttribution: sleitner commentedAutomated Review
Review of the 7.x-1.x branch (commit 2ef371b):
This automated report was generated with PAReview.sh, your friendly project application review script.
Manual Review
The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.
If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.
This review uses the Project Application Review Template.
Comment #8
apadernoIf you are still working on this application, you should fix all known problems and set the status to Needs review. (See also the project application workflow.)
Please don't change status of this application if you aren't sure you have time to dedicate to this application, or it will be closed again as won't fix.
I am closing this application due to lack of activity.