Hello again.
OK, so here is the end result:
! 1 [one]
editing the php.ini didn't effect anything on the server. Hence, I went ahead and used WHM' php ini editor and these are the values I had to set it to, to get Prestashop working without throwing any errors. Well, so far, at least, after having checked some (not all) of the pages which threw me the errors. You may want to keep this as reference for anyone after me running into the same problems. BTW, changing the session.save_path to '/tmp' didn't do anything.
Though, take note of the "Note" below! Since I have Prestashop installed on a sub-domain, e.g.: www.presta.mydomain.com, I am not sure what Prestashop's doing now and if it's collecting the garbage at all. (Any ideas on that?)
Here my changes on the server side .ini file:
Quote; Defines the probability that the 'garbage collection' process is started
; on every session initialization. The probability is calculated by using
; gc_probability/gc_divisor. Where session.gc_probability is the numerator
; and gc_divisor is the denominator in the equation. Setting this value to 1
; when the session.gc_divisor value is 100 will give you approximately a 1% chance
; the gc will run on any give request.
; Default Value: 1
; Development Value: 1
; Production Value: 1
; http://php.net/session.gc-probability
session.gc_probability = 1; Defines the probability that the 'garbage collection' process is started on every
; session initialization. The probability is calculated by using the following equation:
; gc_probability/gc_divisor. Where session.gc_probability is the numerator and
; session.gc_divisor is the denominator in the equation. Setting this value to 1
; when the session.gc_divisor value is 100 will give you approximately a 1% chance
; the gc will run on any give request. Increasing this value to 1000 will give you
; a 0.1% chance the gc will run on any give request. For high volume production servers,
; this is a more efficient approach.
; Default Value: 100
; Development Value: 1000
; Production Value: 1000
; http://php.net/session.gc-divisor
session.gc_divisor = 1000; After this number of seconds, stored data will be seen as 'garbage' and
; cleaned up by the garbage collection process.
; http://php.net/session.gc-maxlifetime
session.gc_maxlifetime = 1440; NOTE: If you are using the subdirectory option for storing session files
; (see session.save_path above), then garbage collection does *not*
; happen automatically. You will need to do your own garbage
; collection through a shell script, cron entry, or some other method.
; For example, the following script would is the equivalent of
; setting session.gc_maxlifetime to 1440 (1440 seconds = 24 minutes):
; find /path/to/sessions -cmin +24 -type f | xargs rm
Interesting here is to know the most important of the three: 'session.gc_divisor'
Setting the value to just Anything lower than 1000, speak 100, 10, even 1, would still result in Prestashop throwing still errors (for as low as value 1-10. 10-100 will get rid of the error but the pages still won't show, instead throw a 500 error. Only when I went ahead and chose 1000, THAT did it!.
Hm, ...scratching my head.
'