Viart people, thank you for the new release!
 
To others:
Ok, did anyone succeed at updating? I failed, as of admin panel works, db converted, but the site itself shows (http://kamistore.com/index.php) you can see what it shows... Waiting for support to give it a look, meanwhile wondering if it worked out for others just fine and how does it feel? Any hints as to how you got it to work would be very much appreciated too.

Hi Kami,
 
Seems user under which web server (Apache?) is running doesn't have permissions to read files in folder 'blocks' in the root of the shop. It may occur while using Safe Mode because this folder was created by the user other than the one under which web server is running. So we may recommend to the following section in php.ini configuration file and add full path to folder 'blocks' to the setting 'safe_mode_include_dir'.
 
;
; Safe Mode
;
safe_mode = On
 
; By default, Safe Mode does a UID compare check when
; opening files. If you want to relax this to a GID compare,
; then turn on safe_mode_gid.
safe_mode_gid = On
 
; When safe_mode is on, UID/GID checks are bypassed when
; including files from this directory and its subdirectories.
; (directory must also be in include_path or full path must
; be used when including)
safe_mode_include_dir =
 
 
WBR,
ViArt Support Team

Thanks for suggestion.
Just did the modification under .../zend/php.ini - no difference. I did restart apache.

/usr/local/Zend/etc whole path - so guess I changed the right file...

In admin_message.php line 51 there is an extra \ before"constant.....". Should it be there?
 
regards
kim

well, I didn't change anything - so I assume it should be.
But I'm surprised nobody else is responding. Either it worked well for all and everyone is happy or... don't know...
I hope support would have a look at it, would be frustrating to put back the older version, while there must be some simple thing I'm missing. Too bad not a coder.

Oki, Viart support fixed it! Thanks!
Solution:
"Group and owner for your blocks subfoder were incorrectly configured.
We've set the group as 'users' and owner as 'www-data' and it fixed the error."
So if anyone runs into same problem - that is the solution :)
Hope Viart doesn't mind me quoting them.