Our site www.viart.com site is operated by latest Viart Shop 5 with default Clear design
Topic Information
Enrique (Guest)
Enrique (Guest)
I replaced all the files with those in the 3.5 ZIP file, and when I tried running admin_upgrade.php, I got the error:
 
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 6291456 bytes) in C:\wamp\www\ViArt_shop\admin\admin_upgrade.php on line 8103
 
I've tried increasing the memory allocation in php.ini but it didn't change anything. Anyone have any ideas?
 
Monk
Monk
From PHP version 5.2.0 the default value for memory_limit is 128M, so in case if you have PHP5 you can try to set it value to 128M
 
It's from PHP documentation
"8M" before PHP 5.2.0
"16M" in PHP 5.2.0
"128M" in PHP > 5.2.0
 
Enrique (Guest)
Enrique (Guest)
Thanks Monk, but as I said before, I was increasing allocated memory. Turns out my WAMP installation was giving me the wrong php.ini to edit and so memory was never increased.
 
HOWEVER, now that I've solved that issue, I have another: I know that I have to update my database after updating the files, however when I try to access ANYTHING in /admin, I get this error:
-------------------------------------------------
DB ERROR 1054
 
We are very sorry, but an error has occurred while processing your request. Please try the operation again by either pressing the Refresh button on your browser, or by going back one page using the Back button. If the error persists, please contact our web development team.
 
The details of the error are shown below. Please quote this in any correspondance regarding this problem.
 
Page URL: http://localhost/ViArt_shop/admin/admin.php
Referrer URL: http://localhost/ViArt_shop/admin/admin_upgrade.php
Database error: Invalid SQL: SELECT setting_value FROM va_global_settings WHERE setting_type='global' AND setting_name= 'site_url' and site_id=1
MySQL Error: Unknown column 'site_id' in 'where clause'
------------------------------------------
 
So clearly somewhere between 3.2 and 3.5, the DB structure changed, unfortunately, according to ViArt's manual, in order to update the database, I have to use admin_upgrade.php, which is generating the above error. So it's a catch 22, I have to update the database in order to update the database :P
 
Julio (Guest)
Julio (Guest)
I have the exact same problem trying to upgrade to the lastest version.. Anyone from Viart care to comment on this?
 
Eugene (Guest)
Eugene (Guest)
Hi,
 
Regarding DB ERROR 1054 please apply the following patch and upgrade should become available
http://www.viart.com/fix_for_admin_common_php_for_release_3_5.html
 
WBR,
ViArt Support team
 
Enrique (Guest)
Enrique (Guest)
Hi Eugene, thanks for the reply. This file seems to have done the trick, but there was an error in the DB upgrade, please view my reply in the link you provided :)
 
Ken (Guest)
Ken (Guest)
Wall Bash
 
I have done everything upgraded the common php file and am still getting:
 
DB ERROR 1054
 
 
Page URL: http://www.perfecthairdays.com/admin/admin_upgrade.php
Referrer URL: http://www.perfecthairdays.com/admin/admin_upgrade.php
Database error: Invalid SQL: SELECT setting_name,setting_value FROM va_global_settings WHERE (setting_type='global' OR setting_type='products') AND site_id=1
MySQL Error: Unknown column 'site_id' in 'where clause'
 
Can someone PLEASE advise? I did a fresh install of 3.5 but copied the database from ver 3.2.2 I have MySQL 5 on a hosted server What the heck am I doing wrong? This is so frustrating
 
Thanks
 
Ned
Ned
 
sheath (Guest)
sheath (Guest)
I am getting the following error after upgrading.
 
Database error: Invalid SQL: SELECT setting_name,setting_value FROM va_global_settings WHERE (setting_type='global' OR setting_type='products') AND site_id=1
PostgreSQL Error Message: ERROR: column "site_id" does not exist
Session halted.
 
 
Any suggestions?
 
eugene
eugene
Hi sheath,
 
looks like upgrade was not successfully finished as va_global_settings still miss site_id field. Try to contact to support in order to fix your issue.
Last modified: 1 Oct 2008 4:05 PM
 
thebirdman
thebirdman
I like this responce :)
 
Try to contact to support in order to fix your issue......