Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: "J.O. Aho" <user@example.net>
Newsgroups: comp.lang.php
Subject: Re: 2D array by POST
Date: Fri, 19 May 2023 20:29:41 +0200
Lines: 66
Message-ID: <kcptglFs4adU2@mid.individual.net>
References: <1qaxqzf.194a8511hkkk6aN%liz@poppyrecords.invalid.invalid> <kcn3tdFehn1U1@mid.individual.net> <u465s8$8kf$13@gallifrey.nk.ca> <kcnkirFh5ehU1@mid.individual.net> <1qayusl.14by37z1ufi932N%liz@poppyrecords.invalid.invalid> <u4867n$nduf$1@jstuckle.eternal-september.org> <kcptd9Fs4adU1@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: individual.net C9KSOntIcolDZxHTblKbNAJ+xl1w75Mvc5VR89p7KIANUFLPHW
Cancel-Lock: sha1:eCe4Df4j7dxDm6DgHD3VPHK4yx8=
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
Content-Language: en-US-large
In-Reply-To: <kcptd9Fs4adU1@mid.individual.net>
Xref: csiph.com comp.lang.php:19469

On 5/19/23 20:27, J.O. Aho wrote:
> On 5/19/23 17:56, Jerry Stuckle wrote:
>> On 5/19/2023 2:19 AM, Liz Tuddenham wrote:
>>> J.O. Aho <user@example.net> wrote:
>>>
>>>> On 5/18/23 23:38, The Doctor wrote:
>>>>> In article <kcn3tdFehn1U1@mid.individual.net>,
>>>>> J.O. Aho <user@example.net> wrote:
>>>>>> On 5/18/23 18:04, Liz Tuddenham wrote:
>>>>>>> I need to send a 2-dimensional array from one file to another by 
>>>>>>> POST.
>>>>>>> The array is $item[][] with contents that are entirelyintegers.
>>>>>>>
>>>>>>> I have tried :
>>>>>>>     Print "<INPUT TYPE=hidden NAME=item[] VALUE=$item>";
>>>>>>> with
>>>>>>> $item = stripslashes($_POST['item']);
>>>>>>> but it does not work.
>>>>>>>
>>>>>>>     Any suggestions?
>>>>>>
>>>>>> 1. use session, store the value in the session and then use it in the
>>>>>> next page directly from the session.
>>>>>>
>>>>>> 2. serialize the variable and base64 encode the serialized data, post
>>>>>> this in the form and then base64 decode and unserialize.
>>>>>>
>>>>>
>>>>> Is base64 strong enugh?
>>>>
>>>> It's not about the encryption, it's about not making the html to break
>>>> as you don't know what the serialized data may contain.
>>>>
>>>> if the data is sensitive or you want to avoid user manipulation of the
>>>> data, then store the data in session and that is way it was number 1 of
>>>> the suggestions.
>>>
>>> The data isn't particularly sensitive, it is just a 'shopping list'
>>> passed from one part of a shopping program to another.  It could have
>>> been sent as dozens of individual variables, but that seemed clumsy as
>>> they were already nicely wrapped up in an array.
>>>
>>>
>>
>> J.O. has the right idea.  The way to do this is to store the data in 
>> the $_SESSION variable to pass it on to the next page.
> 
> You have the thread "Replace punctuation in an associative array" where 
> you can see an example on how it could be possible to work with the 
> session, I do not claim it's the best solution, but based on the 
> "requirements", it's a good solution for a half hour work.
> 
> 
>> This is especially true if it has things like prices - which the user 
>> can change if you give them access to it via a web page.
> 
> Yeah, I tend to favor to take prices from the database each time, this 
> more to keep the prices up to date, as then if someone changes a price 
> on a product that price change will get trough at once on all orders 
> that are not finalized.

Sorry, thought I replied to Liz, the two section I write was more 
intended for her than replaying to you.

-- 
  //Aho