Home/ Questions/Q 7689677
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T20:13:10+00:00

I have got a the following problem: I have got multi-step form where in

  • 0

I have got a the following problem: I have got multi-step form where in one step user upload image to server and then few steps further supplies other information, when this information is invalid no data should be commited – also the image should be deleted.

I was thinking about PHP session, but I’ve read here PHP – Store Images in SESSION data? that it is inefficient way. Every time you proceed step in the form the image is reloaded (in the session) and as somebody mentioned “You will want it to only be as big as it needs to be and you need to delete it as soon as you don’t need it because large pieces of information in the session will slow down the session startup.” – here i got a question: will it slow down the stratup the session of user who upload file or sessions of all users?

I have to mention that I’m looking for solution that doesn’t rely on operating system scripts (cron or etc) – I have no permission to run such scripts.

The perfect solution for me would be: saving image on disk (for example in some folder named after session id) then after the latest step of form move this image or delete depending on form validation. If user unexpectedly destroy the session (for example closing the browser) of course the folder with image should be deleted. In nutshell I need somethig like callback to event “destroying session”.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The best solution would be to save the image in on the disk in a temporary location. You can then store the filename of the file in the user’s session.

    Regarding cleaning up orphaned sessions, you can write your own session save handler and set it using session_set_save_handler().

    Effectively, you will need to write your own handlers for opening, saving, reading, writing, destroying and garbage collecting sessions.

    In your case, you would have an extra bit of code in the destroying and garbage collecting that also removes unwanted images connected to that session.

    Here’s a pretty good blog post about writing your own custom session handler. The example uses MySQL as the storage backend, but you should be able to adapt it to your storage handler of choice.

    • 0