I'm using a date display in a calendar block, and using insert_view to include that in a page. The navigation doesn't work correctly, seemingly because the arguments aren't passed correctly to the block.

If I hardcode a parameter in the page it works fine, e.g.

[view:training_calendar==2010-01]

But I need it to take the argument from the URL, which looks like this:

?q=node/12&=training-calendar/2010-01/training_event

Is there anyway to inherit the argument from the url in the view tag?

Comments

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

no, and that url does not even look good..
you can use arguments from url with patch #419880: Various improvements, but it is not an argument in your url example..

I would suggest to render the calendar block, not the view, but I do not know which module are you using exactly..

wally’s picture

wally commented

I've created a new view "training_calendar" of type calendar, with block display, page display, and a date browser display attached to both. It's using the "Calendar" module for the view.

If I link to the view page display directly (?q=training-calendar) then the month navigation works fine, but I want to include it in a page with other content around it.

The way I'm currently doing it the URL looks that way when I click the [next] or [previous] links.

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
Version: 6.x-1.0 » 6.x-2.x-dev
Status: Active » Postponed (maintainer needs more info)

is it still not working?

igor mashevskyi’s picture

igor mashevskyi commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (outdated)

D6 reached its EOL back in February 2016, and there is no active release for D6 for this module anymore.
Development or support is not planned for D6. All D6-related issues are marked as outdated in a bunch.

Everyone can apply the patch above (not tested by the maintainers, tested by the community) to their D6 projects.
If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.

Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.