10

I have 2 custom views(block types) 'view_A' and 'view_B', one shows content the other shows orders. I need to cobmine them in a single page displaying in 2 different tables. Really dosen't make sense to bundle events and orders in one table.

I tried creating a page, but I can't select 'block' for the context type. I can only select nodes. What's the best way using the UI in Drupal 7 to do this?

  • Did you manage to sort this out? Which technique did you go with? – dibs Dec 4 '14 at 19:40
8

A simpler way can be:

Current Setup:

  1. View A (show content)
  2. View B (show orders)

Steps:

  1. Create a new "page display" of the View A and set the path and menu if you have to.

2 a. Then on the view header or footer (depending if you want the View B before or after View A) add a global view area that will show the View B when viewing View A page.

Global View Area

2 b. Select from your existing views the View B

Select View B

2 c. Apply the change to the current display and you are done.

| improve this answer | |
  • When I check off "Global view area" and hit Apply, I get "Changes cannot be made to a locked view." What is this and how can I get around it? – Rayhan Muktader Dec 23 '15 at 18:41
  • That message indicate that the view is lock by other user or session in the edit mode. This usually have a message in top saying to "break" the lock. – Emil Orol Dec 25 '15 at 1:41
3

You could just make a blank page with a custom path (i.e. /my-empty-page) and no content.

Then in the structure>blocks menu assign the blocks to the content region and set them to only show up on the URL for the page you just made?

| improve this answer | |
2

You can use the Views Field View as well. So you create 2 separate views and then decide which one do you want to place in which region i.e header or footer and based on that add the Global: View (Views field view) from the global section.

The only difference which I know from the above method is this module allows you to pass arguments as well from the parent view and has token integration as well.

| improve this answer | |
0

inserting one view in another cause pagination problem

for example in root view you have only 3 rows, but in child - 200.

pagination of child view will show in ALL PAGES 3 rows of root view at the top

| improve this answer | |
0

I think you need to set 'pager ID' to a higher value (greater than 0) in Views pager settings for each of the combined views. Then, the pagination problem will not occur.

Thanks!

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.