Get post data, Zend Framework

Question

I want to fetch posted data. But I am using no form. The data is postet by a jquery script with method post and I would like to fetch it.

I know how to fetch parameters

$id = $this->getRequest ()->getParam ( 'id', null );

and form values

$message = $form->getValue ( 'message' );

however I want to access post data and not parameters or form values. Any ideas?

DarkLeafyGreen · Accepted Answer · 2011-02-28T14:10:22.273

59

Here is my solution;)

$this->getRequest()->getPost('id', null);

edited Feb 28 '11 at 14:10

answered Sep 19 '10 at 14:27

DarkLeafyGreen

14

NULL is the default value, no need to specify it. – takeshin Sep 19 '10 at 14:45
6

Typical ZF2 - found what I was looking for here but not in the ZF2 documentation.. Thanks – someuser Feb 05 '13 at 08:02
if nothing is passed to getPost, then it will return all the data. It will act like $_POST. Just used it and it worked fine. Thanks for sharing. – Altaf Hussain Dec 23 '13 at 11:29
How to have Lazy mode on? like $post= $this->getRequest(); and then anywhere access it like $post->username where username is the $_POST['username'] ? – Jan 29 '17 at 10:59

Richard Ayotte · Answer 2 · 2017-05-16T20:11:40.933

18

Actually, this might be more of what you're looking for.

$this->getRequest()->getRawBody();

edited May 16 '17 at 20:11

answered Mar 24 '11 at 13:36

Richard Ayotte

Is there a way to get them as array(key value pairs). – AbdulBasit Jul 17 '14 at 18:34
@AbdulBasit please expand; I'm not sure I understand your question. – Richard Ayotte Jul 17 '14 at 22:24

score 7 · Answer 3 · answered Jan 16 '15 at 16:59

7

Here is an other example:

$this->getRequest()->getPost()->toArray()

answered Jan 16 '15 at 16:59

2

`$this->getRequest()->getPost()` seems to already be an array, and thus calling `toArray()` on it results in an error. This is what I needed though, +1 – Shautieh Mar 29 '17 at 12:46

score 2 · Answer 4 · edited Mar 05 '15 at 18:51

2

Try this:

$request = $this->getRequest();
$request->getPost('field_name');

edited Mar 05 '15 at 18:51

Utsav Dawn

answered Mar 05 '15 at 18:29

dhirendra

While this answer is probably correct and useful, it is preferred if you include some explanation along with it to explain how it helps to solve the problem. This becomes especially useful in the future, if there is a change (possibly unrelated) that causes it to stop working and users need to understand how it once worked. – Kevin Brown-Silva Mar 06 '15 at 00:07

4 Answers4