Forums / Developer / passing $view_parameters to pdf

passing $view_parameters to pdf

Author Message

Pierre Tissot

Tuesday 04 April 2006 1:25:13 am

Hi,

I'm confused if this is really possible or not. I have a object that a user can, by a form, chose a set of his attributes, and i want to generate a pdf from this choices, that's why i need to access parameters from pdf. Is this possible? if not anyone can give a tip?

in the forums I found two contradiction:

In this one seems that no way to do that:
https://ez.no/bugs/view/6970

In this one seems possible:
http://ez.no/community/forum/general/create_pdf_from_search_results_showing_all_results/re_create_pdf_from_search_results_showing_all_results

What is the veredict?

Best regards
Pierre Tissot

Präßler Sven

Thursday 06 April 2006 9:59:50 am

I also tried to pass view_parameters to the pdf template and it didn`t worked but passing http POST Variables to the pdf template and reading them with the ezhttp operator in the pdf template worked so i managed this by passing the variable with http POST.
Hope this helps.

Kåre Køhler Høvik

Friday 07 April 2006 12:31:34 am

Hi

I've fixed this bug, so expect it to be working in the next stable releases eZ publish.

Kåre Høvik

Pierre Tissot

Thursday 01 June 2006 8:32:58 am

Can somebody check this, I have a site that all the parametrs are passed to the pdf under mozilla.....but under i.e nothing is being passed?!??!??!
This is very strange...in my experience this should be a server side problem and not a browser problem....but i dont understand the diference between the two browser view the same object...not with a pdf file.

Pierre Tissot

Friday 02 June 2006 2:38:48 am

Ok i solved the problem...first I clean all the errors message of the template..without any sucess.

with mozilla this works

ezhttp("radio_0")

with IE no way.

Then I change the submit of the form from a POST to a GET and load the value like this:

ezhttp("radio_0","get")

and work for the two browser. I know that sounds wird to talk aboout browsers in a problem that seems in the server side and not in the client side....but maybe the way of the browser send the information is handle in diferents ways in the server.
Maybe anybody can expolain this better.

Cheers all
PiR