View Full Version : Upgrade Script Errors
roban
11-17-2006, 05:32 PM
Using the Store Manager software supplied by CS Cart I am getting errors and unable to upgrade using it. This is one of the errors when I try to test or back up:
Cannot find "Start" marker in Script "<!--SHTML Wrapper-500 Server Error-->
Any help?
ETInteractive
11-17-2006, 06:42 PM
Did you fill in the "uploads folder" with your cs cart dir? w/o that it wont work.
roban
11-17-2006, 07:42 PM
Did you fill in the "uploads folder" with your cs cart dir? w/o that it wont work.
Yes it found it automatically. I am going to do a manual upgrade.
ETInteractive
11-17-2006, 08:08 PM
I found quite a few errors going from 1.3.3sp2 to 1.3.4 sp1
Here they are.
1- After upgrade completed and changes saved, my store tried to load customer default blue, which I dont use. I only use admin blue, my default skin is a custom folder name.
Error: Can't write template cache in the directory: /home/xxx/public_html/csupd/var/compiled/customerdefault_blue.
Please check if it exists, and has writable permissions.
So i create this var folder and make it writeable just to test it.
2- I get the following error after error 1
Database error: 1054 : Unknown column 'cscart_pages.page_inner_id' in 'field list'
Invalid query: SELECT cscart_pages_topics.topic_id, cscart_pages.page_inner_id, cscart_pages.page_type, cscart_pages.page_id, page_link, cscart_page_descriptions.page FROM cscart_pages LEFT JOIN cscart_pages_topics ON cscart_pages_topics.page_id=cscart_pages.page_id LEFT JOIN cscart_page_descriptions ON cscart_pages.page_id=cscart_page_descriptions.page _id AND cscart_page_descriptions.lang_code='EN' WHERE cscart_pages.avail='Y' AND cscart_pages_topics.topic_id IN ('0','') ORDER BY cscart_pages.position, cscart_page_descriptions.page
Backtrace: File:/home/xxx/public_html/csupd/index.phpLine:69Function:includeFile:/home/xxx/public_html/csupd/include/common/customer_common.phpLine:37Function:includeFile:/home/xxx/public_html/csupd/include/common/topics.phpLine:45Function:fn_get_topicsFile:/home/xxx/public_html/csupd/core/fn_cms.phpLine:276Function:db_get_hash_multi_array File:/home/xxx/public_html/csupd/core/fn_database.phpLine:158Function:db_queryFile:/home/xxx/public_html/csupd/core/db_mysql.phpLine:89Function:db_debug_error
i also noticed some funky table names, I compared a fresh install of 1.3.4 vs the upgrade 1.3.4 sp1 tables.
two tables are different names
in 1.3.4 original
cscart_conf_sections
cscart_conf_section_descriptions
----
in 1.3.4 sp1 upgrade
cscart_conf_steps
cscart_conf_step_descriptions
something isnt right there.
roban
11-17-2006, 08:24 PM
Nope something is not right. I will wait until the bugs are ironed out before trying to upgrade. I imported the new database tables and that went ok through phpMyAdmin but that's as far as I am going with this. My store works with 1.3.3.sp2 and that's where it stays.
ETInteractive
11-17-2006, 08:32 PM
Yea, I just did this as a 'test run'....i stll have my original 1.3.3 site....i just made a copy and tried it....it has alot of potential, the tool, like the backup utility, which is really cool...
like all v1.0 things, it needs work.
roban
11-17-2006, 08:35 PM
I ran into the same developmental issues at Cube Cart. Releases were made before they were ready and were not tested in Beta (not to mention Alpha). Too bad the developers are bending to pressure. I hope they update and test future releases.
compernicus
11-17-2006, 08:39 PM
Nope something is not right. I will wait until the bugs are ironed out before trying to upgrade.
There are certainly some issues in the new upgrader. Might I suggest, however, that people don't just "wait until the bugs are ironed out". That is fine regarding your live site, but if people have sites that are not live, the best thing that could happen is people attempt test upgrades so that all of the bugs can actually be found. That way we will have a stable product much sooner. Also, a live site can always be duplicated for practice upgrade purposes. I can imagine that a practice updgrade would be the wisest first step for a live site anyway.
So, let's all try this thing out and find any issues, report them, and help the CS developers get the upgrader stable.
compernicus
11-17-2006, 08:55 PM
Too bad the developers are bending to pressure. I hope they update and test future releases.
I agree that beta testing is very important, and that with the Updater, there probably should have been an official beta testing cycle among CS-Cart users.
Regarding CS-Cart itself, however, they have always had beta releases. And usually, there are just a small number of people who take the time to evaluate the beta releases. I have also noticed that it is usually the people who are creating the "pressure" that you mentioned who don't participate in the beta testing. During the 1.3.4 beta cycle for example, I saw several people repeatedly asking when the next release will be out, but I rarely saw any bug reports or constructive feedback posted by those same individuals.
Over the last week, the same situation has occurred regarding the update packages. Many people have been taking cheap-shots at the developers because the upgrade wasn't out yet. Now that the upgrader is out, for all intents and purposes as a beta product, we will surely see people taking cheap-shots about the bugs.
Unfortunately, we can't have it both ways. We cannot have bug free releases without beta periods and diligent beta testers. And we cannot have overnight releases without bugs. My opinion is that the only solution is that people start to set realistic expectations and start to participate in the process a little more constructively. If we get enough people doing that, then I think we will see great results.
zardos
11-17-2006, 10:12 PM
Hi compernicus
Well said, i found know issues with the upgrade tool, but obviously when you have a design that goes way beyond the standard templates you are going to have issues, as i have. Well done to CS-Cart for at leased putting something together to help us upgrade.
roban
11-17-2006, 11:00 PM
I can imagine trying to put something this complicated together is a herculean task. My version of 1.3.3 runs so well that I am in no hurry to upgrade. Kudos to the development team for the nifty Store Manager software. Whether working or not, it's brilliant and I'm sure in time there'll be updates based on current events.
ETInteractive
11-18-2006, 03:32 AM
Ok, I got farther with help from compernicus's eyes.
somehow my config.php wasnt updated so now my site works..
HOWEVER
the site blew away comopletely my custom skin and skin folder.
and its no longer a choice to install.
so i had a folder called /custom1/ in /var/skins_respository/
it complete deleted that and only gives me the choice for the CS standard skins.
edit...im adding that folder back in by hand to be able to select it for customer front end skin.
This isn't going to work in that case....will need to be addressed.
jobosales
11-18-2006, 04:12 AM
Like others, I am having trouble using the upgrade script. I am just running this on a test setup going from 1.3.4 to 1.3.4 sp1. Store Manager coreectly finds and uses the settings from config.php but fails at the "Test settings" stage with the following errors:
Webserver and database ...FAILED
followed by:
Can't find "Start" marker in script "http://xxxxxxxx/backup/test.php
The program seems to be failing at creating the directory /backup . I am using the same U/P I use for FTP but there seems to be a permissions issue.
Anyone found a way around this?
Thanks for your help.
Bob
ETInteractive
11-18-2006, 04:17 AM
You have a blank Upload folder inyour settings, you need to select the folder that cscart is in for upgrade.
once you do that it works.
jobosales
11-18-2006, 06:04 AM
Thanks for the response, ET.
Actually, I selected the upload directory using the file browser and received a message stating
Found directory and settingd file for "CS-Cart". Do you want to use it?
I respond yes and it fills in the DB info and store URL. The program tehn fails when I test the settings. The upload directory is the webroot for the server. Is that a problem? Or am I misunderstanding what goes here?
Thanks for your help.
Bob
compernicus
11-18-2006, 06:53 AM
Actually, I selected the upload directory using the file browser and received a message stating
I respond yes and it fills in the DB info and store URL. The program tehn fails when I test the settings. The upload directory is the webroot for the server. Is that a problem? Or am I misunderstanding what goes here?
The steps you followed seem to be correct. The test could fail, however, if the database or directory information in the config.php file is incorrect. Also if the config.php has been moved from its default location, it could cause an error. Don't know if either of these apply in your situation, but it is something to consider.
nwsco
11-18-2006, 10:13 AM
i'm waiting for version 1.3.4sp1 in one download and do it all again.........
this doesnt "feel" right for me........i dont want to have a feeling i have a buggy shop......
roban
11-18-2006, 10:48 AM
Maybe it is an error in my config.php file. The 2 entries that I am not sure of are these at around lines 48 to 54:
$cscart_http_host = 'www.vitaminlink.net';
$cscart_http_dir = '';
// Host and directory where cs-cart is installed on secure server
$cscart_https_host = 'www.vitaminlink.net';
$cscart_https_dir = '';
This is what I have for my 1.3.3 sp2 and the store works. Any thoughts on whether these lines are correct?
zoom4267
11-18-2006, 11:47 AM
i'm waiting for version 1.3.4sp1 in one download and do it all again.........
this doesnt "feel" right for me........i dont want to have a feeling i have a buggy shop......
does 1.3.4sp1 make it a one shot deal? would that be a smooth upgrade. i am very nervouse about upgrading.
i know everyone has put in alot of time and effort and you guys are doing a great job
jobosales
11-18-2006, 08:53 PM
The steps you followed seem to be correct. The test could fail, however, if the database or directory information in the config.php file is incorrect. Also if the config.php has been moved from its default location, it could cause an error. Don't know if either of these apply in your situation, but it is something to consider.
The location of config.php and the information it contains appear to be correct. Both the storefront and the admin are working fine and both use the info in config.php.
I was thinking maybe a permissions issue (e.g., unable to create the directory backup and the test.php within) but I litearrly copied and pasted the values from my FTP bookmark to the Store Manager. I can create the directory without any problems using FTP.
The only thing I can see that is different is that we are currrently running the store using an IP address until we finalize our domain name. This does not seem to be a problem for the shopping cart software but I wonder if it presents a problem for the Store Manager software.
Fortunately, we are not in a hurry to get this site up but we do want to have ample time reviewing all the software and making whatever mods are necessary plus customizing the look.
Any other thoughts?
Bob
jobosales
11-19-2006, 01:02 AM
I checked the log and find these errors being generated when I run Store Manager;
[2006-11-18 19:51:02]: error: directory is writable by others: (/home/xxxxxxx/public_html/backup)
and
[Sat Nov 18 19:51:02 2006] [error] [client xxx.xxx.xxx.xxx] File does not exist: /home/xxxxxxx/public_html/500.shtml
[Sat Nov 18 19:51:02 2006] [error] [client xxx.xxx.xxx.xxx] Premature end of script headers: /home/xxxxxxx/public_html/backup/test.php
The /backup directory does not exist when checking via FTP or in cPanel File Manager. It looks like this is a permissions issue when Store Manger tries to write the /backup directory.
So, what obvious thing am I missing?
Thanks for any help-
Bob
compernicus
11-20-2006, 03:49 AM
The /backup directory does not exist when checking via FTP or in cPanel File Manager. It looks like this is a permissions issue when Store Manger tries to write the /backup directory.
So, what obvious thing am I missing?
Your store doesn't happen to be in a password protected directory does it? I was playing around with the upgrader, and found that I got the same error messages you did when the store directory was protected with password protection.
If that is not it, then I would have to guess that it may be some other permissions related issue.
davidnetk
11-20-2006, 04:48 AM
I tried upgrading and have the following errors:
- Can't find "Start" marker in Script "<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">"
The solution for this one was to unprotect the directory (thank compernicus ^^). Once I did that this error did NOT show up anymore and I was able to advance in the upgrade process. However now I had a different error:
- Can't find "Done" marker in script "Status: Creating archive"
Any insight would be greatly appreciated.
jobosales
11-20-2006, 05:38 AM
compernicus-
The store is installed in the root web directory without any password. I changed the permissions on the directory to '777' and still got the same error. The original install of 1.3.4 installed and runs just fine.
I may try installing this on a server running X-Cart; I figure the server requirements should be nearly identical and it will at least provide another data point.
Bob
JesseLeeStringer
11-20-2006, 10:40 AM
I've just created a new store in 1.3.4,
Upgraded to 1.3.4 SP1 via copying files from 'latest' (upgrade-134-134sp1) to server, went right through to reinstalling.
Stopped short when asked if I want to re-write table.
Clicked 'Cancel' / Page went back to the installation page
otherwise I have 1.3.4 SP1 installed... not via the CS-CART store manager client.
*YAY*
Trailhunter
11-20-2006, 11:30 PM
I too was getting the same error stating that it failed the MAKE directory comment when I tested the settings. I tried deleting the backup folder and now the test succeeded.
jobosales
11-21-2006, 01:46 AM
Trailhunter-
Are you saying that the directory "/backup" was created even though you received the error the first time? That was my first hunch when it failed but I could not find the "/backup" directory anywhere.
If it is as simple as manually creating or deleting a directory to get the Store Manager working, that is at least a good temporary fix.
Bob
Southice
11-21-2006, 07:46 AM
I tried to upgrade from cscart_v1.3.3 to cscart_v1.3.4 with the upgrade file upgrade-133sp2-134sp1.tgz with the Store Manager.
(By the way what are the sp1 and sp2 versions of cscart, is it something I need to be concerned about since my v1.3.3 file's name is just cscart_v1.3.3.tgz)
The Store Manager made a nice backup of the site and proceeded to upgrade the site.
When it finished I tried out the frontend. The images in the Featured Products section didn't show up but I think it's because I have a custom template and the images show up in the categories so I'm not to worried about that. (I think I should just change my custom template according to the new templates)
My problem now is when I wanted to go to the Admin section to see if the new default templates showed images in the Featured Products section, I got the following error just by going to admin.php:
Database error: 1064 : You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'as a LEFT JOIN as b ON b.status=a.status AND b.lang_code='EN'' at line 1
Invalid query: SELECT a.status, b.description FROM as a LEFT JOIN as b ON b.status=a.status AND b.lang_code='EN'
Any ideas what went wrong?
Otherwise I'll restore the old site and try to upgrade again. And if it fails again I'll have to leave it as the previous version which is a bummer since I wanted to try some of the new features of cscart_v1.3.4.
Fixed Solution:
When I upgraded and had to decide what files to keep that were in conflict I choose to keep my config file since it had my database information.
What I neglected to notice is that in the config file the Database tables aliases array are created and since the new version has extra tables when it tried to call the new tables with the array it had no value.
So I downloaded my config.php file, overwrited the $db_tables array with the new version's $db_tables array and uploaded it again.
Now I can log into my admin.
Yay!!
davidnetk
11-21-2006, 03:25 PM
Does anyone knows what is being done to fix all these errors? Have the programmers issued an explanation, a troubleshoot guide or something?
Is there certain steps I could follow to be able to upgrade my store?
PLEASE IF ANYONE KNOWS, I'M DESPERATE!
StrangeRanger
11-21-2006, 03:35 PM
Does anyone knows what is being done to fix all these errors? Have the programmers issued an explanation, a troubleshoot guide or something?
Is there certain steps I could follow to be able to upgrade my store?
PLEASE IF ANYONE KNOWS, I'M DESPERATE!
Folks, be patient, I'm sure they're working like fiends to figure this out. I'll bet they're more freaked than you are.
The gurus at CS-Cart work very hard and provide an awesome product, please get off their backs and give them some space to work.
Keep in mind, if your store is working fine, you are under NO pressure at all to upgrade. Yeah, the upgrade might add some cool features, but it is not required for your store to survive.
j
davidnetk
11-21-2006, 04:04 PM
I'll bet they're more freaked than you are.
You're right StrageRanger. I'll be honest, it makes me feel like an ass to be so pushy, but it is because it's a chain reaction.
You see, I think I'm more freaked out than my own client (who is the store owner) but it is because they wanted to go live before Christmas, but anyway, I know what you say is true, I just wanted some news, just to calm myself down...
wwgreen
11-21-2006, 05:06 PM
FWIW, I just did a fresh install of 1.3.4sp1 (available in helpdesk). No problem.
Restored previous database as well. No problem.
Cart seems to be working as normal. CS is still unable to automatically restore any previous changes made to templates and graphics, but that is nothing new.
I know this doesn't help those who want to upgrade, but current version seems as stable as previous versions when installed fresh. (I also tried the 1.3.4 to 1.3.4sp1 upgrade through manager, showed as successful, but no templates were available. ?)
mpjbay
11-21-2006, 08:36 PM
i got this error when trying to upgrade from .4 to .4sp1
http://mirkury.com/upgrade%20error.jpg
mpjbay
11-21-2006, 08:37 PM
using store manager
davidnetk
11-21-2006, 08:57 PM
using store manager
I got the same one!
http://www.mirkury.com/upgrade%20error.jpg
mpjbay
11-21-2006, 09:20 PM
i emailed tech support, hopefully they will get back to me soon.
JesseLeeStringer
11-22-2006, 01:26 PM
Does anyone knows what is being done to fix all these errors? Have the programmers issued an explanation, a troubleshoot guide or something?
Is there certain steps I could follow to be able to upgrade my store?
PLEASE IF ANYONE KNOWS, I'M DESPERATE!
In personal opinion it's best that you hold your ground and tell your client that it is not feasible for this to be ready prior to Christmas, explain the situation, offer him your attention to detail or thosewise,
If necessary get the store a new 1.3.4 install, upgrade it.
It's quicker then awaiting fixes.
Then you've got a store ready for movement.
In honest opinion you're wasting your time awaiting a fix that may not be cleared up for a while since it's such a large update.. think Windows XP SP2...
Jesse
mpjbay
11-22-2006, 04:50 PM
if i do a fresh install days of work will be lost.
mpjbay
11-22-2006, 05:01 PM
i am going to do a side by side install and see if i can get the database and skin to import into the fresh install of .4sp1
compernicus
11-22-2006, 05:32 PM
if i do a fresh install days of work will be lost.
Even if the updater was working without any bugs, you would still need to make a decision about every individual file that has been changed by both yourself in the prior version and the CS developers in the latest version. You will need to determine whether you want to keep your changes, overwrite your changes with the changes the CS-Cart developers have made, or even more likely, manually edit the files to keep both sets of changes.
This is really not much different than installing a fresh install and using a good file comparison tool, such as the free open source WinMerge, and comparing all the files in your old setup with all the files in the new version. Then any files that are different will have to be reviewed to determine what has changed, and edited appropriately.
I sincerely doubt that doing a manual upgrade with a file comparison tool and doing a couple of manual SQL inserts will take much longer than doing it with the upgrade tool if you have already done alot of changes to the templates or the core code.
jobosales
11-23-2006, 12:40 AM
Restored previous database as well. No problem.
Did you have to do anyhting to update the database?
Bob
roban
11-23-2006, 02:43 AM
Not to steal the thread but I updated the db manually although Store manager will take care of it as well.
wwgreen
11-23-2006, 02:43 AM
jobo - Nope. Just did a backup/dump of the db in 1.3.3 and in 1.3.4. (had both installed to test at the time). I simply did the clean install of 1.3.4sp1 as I mentioned, and restored the backup db from either. All info was transferred successfully afaik from before (except for the template and other code changes). Hope that answers your question.
jobosales
11-23-2006, 05:02 AM
Unfortunately, I am still unable to get the Store Manger to run. I have tried running it on two different computers. In both cases, I get the following program termination:
AppName: store_manager.exe AppVer: 0.0.0.0 ModName: store_manager.exe
ModVer: 0.0.0.0 Offset: 0001a493
Bob
STUFFretail.com.au
11-23-2006, 11:25 AM
Unfortunately, I am still unable to get the Store Manger to run. I have tried running it on two different computers. In both cases, I get the following program termination:
I got past that by going into file properties (my OS is Windows XP) - Then I disabled the asian fonts and blind text stuff and made it run in 256 color mode in a 640 resolution... it didn't fix the 'test settings' error I recieved, however I did upgrade my store via backup after disabling all that was not needed on it to run. Oh yeah, I made it think it was running on Windows 98.
All updated successfully... until I logged into admin side ... start logon page was just as before, after logging on though, all that I got was SQL error text... I submitted another ticket to the help desk, they've been taking a while to respond lately, but I guess their busy with the bugs 8-P
Anyway, hope in some random way that helped someone .. somewhere (the method I used that is)
jobosales
11-23-2006, 08:42 PM
I submitted another ticket to the help desk, they've been taking a while to respond lately, but I guess their busy with the bugs 8-P
I wish the would release an update process using the Upgrade Center. This would give them plenty of time to work out whatever issues they have with Store Manager and also, hopefully, port Store Manager to OS X and Linux.
Bob
xgonnahaveitx
11-25-2006, 03:58 PM
My $0.02 worth,
If you recall correctly from when you installed 1.3.3 sp2 in the instructions you were supposted ot give the ./ directory 777 permission, as well as a few others. That is the permission issue you are having. If the program can not write to the var folder to create the backup folder, then it would fail. Also from what I have read, if you create a backup directory, make sure you chmod it to 777.
Just a thought anyhow.
smoked1
12-18-2006, 10:04 PM
I miss having a standard PHP upgrade script.
JesseLeeStringer
12-18-2006, 10:43 PM
I miss having a standard PHP upgrade script.
Same here, but I improvise :)
smoked1
12-19-2006, 05:45 PM
Has anyone been able to get this sorted out? I still can't upgrade my site.
StrangeRanger
12-19-2006, 07:50 PM
Sh!t! Thought I had figured out a work-around, but alas, NOT.
If anyone is REALLY desperate to upgrade this is an option:
I figured out that I can export my 1.3.3sp2 inventory/catalog as a csv file and then import it into a clean install of 1.3.4sp2 and it worked nicely. But it does not export the CMS Topics Pages that I had created. I'm not recreating those 30+ pages.
So close.......!
j
Sh!t! Thought I had figured out a work-around, but alas, NOT.
If anyone is REALLY desperate to upgrade this is an option:
I figured out that I can export my 1.3.3sp2 inventory/catalog as a csv file and then import it into a clean install of 1.3.4sp2 and it worked nicely. But it does not export the CMS Topics Pages that I had created. I'm not recreating those 30+ pages.
So close.......!
j
This is fine unless you have modded the hell out of your store, which most have from what I read on the forums..
2 Weeks ago, I upgraded but my site had no mods... I certainly wouldnt even dare attempt an upgrade now as I have spent god knows how long getting it to work almost the way I require..
wwgreen
12-20-2006, 09:55 PM
Just for kicks, I tried testing the 1.3.4sp1 to 1.3.4sp2 upgrade, no go. Cannot find "Done" marker error.
I'll stay with 1.3.4sp1 for awhile, already bringing up quite a few issues to the Helpdesk with this version. Still a great cart with serious potential.
travis@blueheronbags.com
03-20-2007, 10:10 PM
Hello All!
I too am getting the same error message everyone else is with the backup/test.php file thing...has anyone been able to successfully use the store manager to upgrade a 1.3.3sp2 installation over to the new 1.3.4sp3 upgrade after getting this error? Thanks a bunch!!!
Cheers,
Travis
vBulletin® v3.6.5, Copyright ©2000-2009, Jelsoft Enterprises Ltd.