Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "J.O. Aho" Newsgroups: comp.lang.php Subject: Re: Session array passing Date: Thu, 8 Dec 2022 16:05:45 +0100 Lines: 37 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net RYkLwa1Lg4D9VY9071IF7A2E6OVLzW4Z+oboho68cdHm66G8ZT Cancel-Lock: sha1:9gk5kEYvUi/JGo6AvEV+x4oI01Y= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.1 Content-Language: en-US-large In-Reply-To: Xref: csiph.com comp.lang.php:19202 On 08/12/2022 14.09, The Doctor wrote: > In article , > Arno Welzel wrote: >> The Doctor, 2022-12-06 02:27: >> >>> Has there been a change of passing seesion arrays in 8.1 different from 7.X ? >> >> What do you mean with "passing session arrays" exactly? Do you have a >> code example? >> > > > error_reporting(E_ALL); > if(!empty($_SESSION['sessiondata'])){ > } > ?> Did you set the $_SESSION['sessiondata'] value earlier? Have you enabled the session use? check your session.use_cookies. Have you the right type of save handler for the session (session.save_handler)? files seems to be the most common type. Is the path assigned for session.save_path writeable by the user running the php engine (apache/www-data/nobody/...)? are you using 'session.cookie_secure = 1' and then use http connection? are you using a custom serializing service? check your session.serialize_handler -- //Aho