X-Cart forums

[Cpt.Crashtastic]

Originally Posted by ADDISON

Drupal connector is a strong piece to use for its extensions.

Absolutely. I don't understand why it's not included as an option with the install. With Drupal/Xcart you have a very powerful solution right out the box.

I suppose it could be considered that the learning curve with this combination is a little on the steep side. Xplorer has said the the connector will be available as a module. That will be an interesting experience I hope they release it with the connector option as I feel it not the right thing omitting this option.

The LiteCommerce 1.1.0 RC is nigh on identical and includes Drupal. If you disable the xcart skin in xcart new, surprise, surprise, you have litecommerce.

[tartaglia]

I haven't had a chance yet, but has anyone loaded up a XCN store with lots of products and categories (12000+ products, 3-4 levels of category depth) and assessed its performance/resource needs etc. One of the reasons I started migrating to XC from LC (only this past Feb, my LCv2x store is still active) was that I had learned over the years with LC (from my host and from QT themselves) that LC just wasn't the best solution for large catalogs. How does XCN stack up?

[cflsystems]

Most of what I have to say is probably already said and reported but here are my findings


1. Upload archive to server, extract and just browse to that domain - XC will output on the screen bunch of php errors for required files and not being able to load them - long list - and at the end of that list there is "ERROR: "XCN_NOT_INSTALLED" (N/A) - Probably X-Cart is not installed. Try to run install.php" - YES XC is not installed but there is no reason to output all the error messages instead of only one error - XC not installed, run install.php

2. Running install.php outputs this on the screen before anything else - on every step of the installation and on every page load after store is installed

Notice: require_once(): 1. h->opened_path=[XXXXX/xcn110/top.inc.php] h->filename=[XXXXX/xcn110/top.inc.php] in XXXXX/xcn110/Includes/install/init.php on line 57 Notice: require_once(): 1. h->opened_path=[XXXXX/xcn110/error_handler.php] h->filename=[XXXXX/xcn110/error_handler.php] in XXXXX/xcn110/top.inc.php on line 46 Notice: require_once(): 1. h->opened_path=[XXXXX/xcn110/top.inc.PHP53.php] h->filename=[XXXXX/xcn110/top.inc.PHP53.php] in XXXXX/xcn110/top.inc.php on line 47 Notice: require_once(): 1. h->opened_path=[XXXXX/xcn110/Includes/Autoloader.php] h->filename=[XXXXX/xcn110/Includes/Autoloader.php] in XXXXX/xcn110/top.inc.PHP53.php on line 80 Notice: require_once(): 1. h->opened_path=[XXXXX/xcn110/lib/Doctrine/Common/ClassLoader.php] h->filename=[XXXXX/xcn110/lib/Doctrine/Common/ClassLoader.php] in XXXXX/xcn110/Includes/Autoloader.php on line 147 Notice: require_once(): 1. h->opened_path=[XXXXX/xcn110/lib/Doctrine/Common/Persistence/Proxy.php] h->filename=[XXXXX/xcn110/lib/Doctrine/Common/Persistence/Proxy.php] in XXXXX/xcn110/Includes/Autoloader.php on line 148 Notice: require(): 1. h->opened_path=[null] h->filename=[XXXXX/xcn110/lib/Doctrine/ORM/Proxy/Autoloader.php] in XXXXX/xcn110/lib/Doctrine/Common/ClassLoader.php on line 163 Notice: require_once(): 1. h->opened_path=[XXXXX/xcn110/lib/PEAR2/Autoload.php] h->filename=[XXXXX/xcn110/lib/PEAR2/Autoload.php] in XXXXX/xcn110/Includes/Autoloader.php on line 167 Notice: include_once(): 1. h->opened_path=[XXXXX/xcn110/Includes/Utils/ConfigParser.php] h->filename=[XXXXX/xcn110/Includes/Utils/ConfigParser.php] in XXXXX/xcn110/Includes/Autoloader.php on line 100 Notice: include_once(): 1. h->opened_path=[XXXXX/xcn110/Includes/Utils/AUtils.php] h->filename=[XXXXX/xcn110/Includes/Utils/AUtils.php] in XXXXX/xcn110/Includes/Autoloader.php on line 100 Notice: include_once(): 1. h->opened_path=[XXXXX/xcn110/Includes/Utils/FileManager.php] h->filename=[XXXXX/xcn110/Includes/Utils/FileManager.php] in XXXXX/xcn110/Includes/Autoloader.php on line 100 Notice: include_once(): 1. h->opened_path=[XXXXX/xcn110/Includes/Utils/URLManager.php] h->filename=[XXXXX/xcn110/Includes/Utils/URLManager.php] in XXXXX/xcn110/Includes/Autoloader.php on line 100 Notice: include_once(): 1. h->opened_path=[XXXXX/xcn110/Includes/Utils/Converter.php] h->filename=[XXXXX/xcn110/Includes/Utils/Converter.php] in XXXXX/xcn110/Includes/Autoloader.php on line 100

3. Step 3 - configuration - Why does it say "Configuring LiteCommerce"? This is XC Next right? Installation still does not create database - it has to be manually created before runing the instalaltion

4. Step 4 - building cache - same require_once/include_once notices show in the working window; "Re-building cache [step 5 of 5], please wait..." stays even after all this
Run the "Templates_Plugin_ViewLists" plugin... [2.49sec, 10.3MB (9.6MB)]
Run the "Templates_Plugin_Patcher" plugin... [0.21sec, 10.3MB (128b)]
Run the "Templates_Plugin_Compiler" plugin... [3.68sec, 18.3MB (8.0MB)]
Run the "ModuleHandlers" plugin... [7.65sec, 29.9MB (11.6MB)]
Run the "PHPCache_Plugin_APC" plugin... [0.03sec, 30.0MB (-24b)]
Run the "FinishCacheBuildingHandler" plugin... [0.64sec, 30.1MB (86kB)]
Cache is built successfully

5. Step 5 - create admin account - text boxes height - cuts off letters

6. Installation complete - with message - "LiteCommerce software has been successfully installed and is now available at the following URLs:" - again LiteCommerce; email sent is also from LiteCommerce

7. Database - all tables prefix - xlite - implies LiteCommerce

8. Going to store front or admin now produces fatal error -
ERROR: "Includes\ErrorHandler::FATAL_ERROR" (code 2)
Call to a member function log() on a non-object


SO XCART NEXT DOES NOT WORK. THIS IS THE FILE SENT TO ME BY QT, NOW GOING TO NEXT.X-CART.COM TO DOWNLOAD FROM THERE AND INSTALL AGAIN

Now it looks like LiteCommerce has been replaced by X-Cart Next wording. Still get the same require_once/include_once notices show at the top of the screen
And then same error after installation
ERROR: "Includes\ErrorHandler::FATAL_ERROR" (code 2)
Call to a member function log() on a non-object


From the error log
[18-Aug-2012 20:15:41] PHP Fatal error: Call to a member function log() on a non-object in XXXXX/xcn11x/var/run/classes/XLite/Logger.php on line 214
[18-Aug-2012 20:15:41] Error (code: 1): Call to a member function log() on a non-object
Server API: apache2handler;
Request method: GET;
URI: /xcn11x/cart.php;
Backtrace:
#0 Includes\ErrorHandler::logInfo(Call to a member function log() on a non-object, 1) called at [XXXXX/xcn11x/Includes/ErrorHandler.php:197]
#1 Includes\ErrorHandler::handleError(Array ([type] => 1,[message] => Call to a member function log() on a non-object,[file] => XXXXX/xcn11x/var/run/classes/XLite/Logger.php,[line] => 214)) called at [XXXXX/xcn11x/Includes/ErrorHandler.php:182]
#2 Includes\ErrorHandler::shutdown()

Commenting out line 214 in XXXXX/xcn11x/var/run/classes/XLite/Logger.php fixes the problem and cart displays but this is not how it's supposed to be and it's not a fix

-----------------------------------------------------------------
CUSTOMER SIDE
- all text boxes are very narrow - their hight barely fits the text (same applies to admin)
- no way to create admin and customer account using same email - unnecessary limitation - existing XC allows for that
- after few back and forth with different pages now cart allows for same email for admin and customer account, go figure
- now shows I am logged in but at check out I still have the new customer block and the login block - they should not show - I am logged in already
- it seems like every time you enter email and check the box "create account" on checkout page an account is created - this is not good behaviour - many customers will do this just to see what happens and the store can end up with many "fake" accounts for no reason
- address shows as - address, country, state, city, zip - anyone thinks this is wrong? no way to change how this info shows or what to show, at least I could not find where to do that
- checkout page - asking for shipping address only - this is the other way around from what it should be; billing address comes first and then you can have "same as billing" or not for shipping address; but asking to fill out shipping address first is like building a house and start with the roof then pour the foundation
- with all the ajax in this version "terms" link on checkout page opens new browser window with the whole store instead of popup with "terms" only
- print invoice button doesn't open the invoice page anymore but the print dialog - no way to know what it will print - the whole store page or the invoice only
-----------------------------------------------------------------
ADMIN SIDE
- environment in admin still says - LiteCommerce core version: 1.1.0-beta
- again missing important order statuses - cancelled, backorder, refunded - unless QT thinks that every single order is good order and customers never return anything (that would be nice)
- importing - this is very important - "Importing will overwrite the existing product information. This operation connot be undone." and "The importing starts immediately upon selecting the data file. " - so first there is no data check if it complies or not with XC Next format and second - does this means now all the information has to be included in the import file? if we want to import and change products prices and quantity only we have to include all the other info as well in the import file? If some column is not included will it be overwritten with default values?
- there is no export - only products data can be exported - I will assume that only products data can be imported then

------------------------------------------------------------------------
MISC
- XC Next has session issues just like XC 4.1.x - using same browser to login to admin then in different tab load customer side it shows as logged in - log out from customer side and you are logged out from admin as well
- the above is even worst - log in as admin and go to store in different tab - go to checkout - fill out an email and check "create an account" - the login email for the admin account you are logged in with is replaced with the email entered on customer side - now your admin account has different email as login
- Why a lot of css classes, variables and constants are refer to as LC_something - implies LiteCommerce and not X-Cart
- Why again the main page is not index.php/.html but cart.php (see htaccess)
- Hard coded phones # in phones.tpl
- <font> tag used in phones.tpl - depricated
- Actually the config file says it directly - LiteCommerce configuration file - this was in the first archive I received, the one downloaded says X-Cart Next
- I like that there are very few files in root and everything else is organized in directories. Keeps it nice and clean

I am sure this is just the top of the iceberg but for the few hours I spent on this version this is what is pocking my eyes...

I don't know about LiteCommerce but X-Cart Next is definatelly not ready at all

[rogue]

I'd like to be in the Beta test.

[Cpt.Crashtastic]

Originally Posted by cflsystems

Most of what I have to say is probably already said and reported but here are my findings

Steve,
Somethings not working well for you. I've had to modify my php.ini to get things to work properly but I sincerely have little or no problem with it. I running locally on ubuntu and on Emmersons servers. I have had no issues with installs. It works very well. There are some bugs but they seem to be fixing them up pretty quickly.

It is Litecommerce. Disable the xcn skin module and you will see exactly what it is. There are some differences but I can't think of them off the top of my head. I can't see any point in releasing two separate systems when xcart can sit on Litecommerce as a module, after all xcart is just an extended feature set for Litecommerce. There is no point in rewriting the core to reflect the xcart name. What is needed is more functionality that is different to Litecommerce, for example, variants.

My only disappointment is that it is not going to be released at present with the Drupal connector. Combined with Drupal it would be a very powerful system. Maybe the fact that Drupal has a severe learning curve that could put people off has influenced this decision or perhaps Drupal 8 being on the horizon is an issue.

I will post some info on creating skins later this week. Although the Wiki is helpful, it's not so easy for everyone to understand. A bit of sample code helps.

In conclusion, I believe this is an excellent system, but there is not enough at the moment to justify paying for a license as Litecommerce offers a near identical feature set. I'm sure there is more coming in the next few weeks!! Drupal Connector should be an option at install. It will be available as a module but it would most probably be a headache to install. There is a learning curve for skins and module development. This is not the old xcart with code here there and everywhere. It's very well structured, but by being well structured it requires more discipline so it's hard work to start with but it will be worth it.

[cflsystems]

You see this is what it's holding a lot of users back - the insecurity and unknown of the X-Cart future. It is NOT LiteCommerce. It is supposed to be X-Cart Next (working name from 3-4 years ago - X-Cart 5). LiteCommerce died couple years ago. I think QT released the new platform under LiteCommerce name so it can get tested in real stores with less traffic and gain some support before it's officialy released as X-Cart 5(Next). That didn't happen. From day one QT was saying that LC and XC5 will share same code but LC will be "free" light version of XC. Now we have mixed up names, almost same platform but somewhat different, confussion...

The test I did was installed on Linux machine with 4GB memory, php5.3.x and MySQL 5.1.x. Nothing special. Working machine for any XC 4.2.x, 4.3.x, 4.4.x and 4.5.x. I also had LC installed on it for testing few months back and all worked out ok.

The XC Next install - 2 of them from different packages - neither one worked properly. I don't know why and had no time go into detailed investigation - I just wanted to get into some of it. And actually I would expect from a beta version to have issues and different problems on different machines, that's why I am glad QT went back to beta. And giving the fact that XC Next does not have basic features like variants, import/export, user profile fields control, etc. I can easily say - not ready for prime time. The LC one you are using is maybe with less bugs and works great but if you can't compare it with XC 4.4.x or 4.5.x....

Yes - the platform is very promising and hopefully in a year or so it will be a killing machine hope that's not too late - other shopping carts developers don't sleep you know and the technology is moving fast... But what I saw so far and from looking at the code - I am impressed and I see some light at the end of the tunnel

I personally am not very excited about Drupal and this would be the last thing to do if you ask me - we need modern up to date shopping cart not CMS/Blog software with shopping cart capabilities.

I think QT should release (in this order)
1. XC Next - paid shopping cart software. Pricing - either raise the price of the cart with cheap/free modules or have lower price for the core and everything else is paid modules. XC users want stability, clear road map, affordable ecommerce solution. Most of us stay with XC because of pricing, control over the code, no SaaS, the ability to choose developer and support, hundreds of 3rd party mods.... Losing all or part of this will be catastrophic for XC
2. X-Payments, PP Advanced and other payment modules not included in core cart
3. Database upgrades at least from 4.4.x and 4.5.x and LC - release upgrade and not just saying "we may be able to do this for you..."
4. Scrap the whole LC thing existing right now, use the same core XC Next cart and release it as XC Next Lite - free core cart with limitations; to jump over the limitations one has to buy XC Next
5. Drupal connector

At the end when anyone searches for shopping cart they should get "XC Next" in search results not LiteCommerce/XC...

[photo]

Originally Posted by cflsystems

I personally am not very excited about Drupal and this would be the last thing to do if you ask me - we need modern up to date shopping cart not CMS/Blog software with shopping cart capabilities.

I could not agree more!

[ADDISON]

Drupal is very powerful with thousands of modules, themes. But comparing with Joomla it has a big problem, it is not UI friendly. That's why Joomla is so popular. Out of the box it comes with a lot of features. In Drupal case you have to add extensions, if you not familiar with them it is waste of time. I am one that was with Joomla! from the very beginning, "ancient" times, and a big fan!

[totaltec]

The CMS should not be a concern in my opinion. I think XCN should be developed primarily as a stand alone application, with options or add on modules to connect with a CMS.

[philrisk]

Count me in