X-Cart forums

[Ksenia]

Originally Posted by kevinrm

Anyone successfully upgrade from 4.5.5 who is also using XMultiCurrency mod? There were 4 files from that which I could not patch even after using latest version of them. Except for those for mod files, when I attempted upgrade everything went "OK" but after upgrade I get blank page. 4.6 version of this mod also not in my file area. No success in upgrading for me at all, thankfully I did it on a copied version in a subdirectory.

Trying the upgrade ( as well as any other change , be it module installation or modification) on a test version first -this is a golden rule, I'm so happy to see a person who follows it!

X-Multicurrency module v.4.5.5 is not 100% compatible with X-Cart 4.6, so you should download the distributional package of v.4.6. I've already sent it to you via message board, it's also available in FileArea.

The same about PDF-Invoices and other modules -if you want to use the module on v.4.6, you need this very version of the module. PDF-Invoices v.4.6 is NOT ready so far, but it will be uploaded to FileAreas shortly.

[elmirage001]

I've now successfully completed a database upgrade from 4.4.5 --> 4.5.0 and then used the upgrade pack from 4.5.0 --> 4.6.0 This morning I did an upgrade of my dev 4.5.5 site to 4.6.0 and both upgrades processed smoothly except for issues with the Hot Products Module. I have not experienced any of the issues the other posters have described. (patch applied)

The issue with the Hot Products Module involved the SQL which keeps the upgrade from fully completing. My files patched fine and then received the sql patch failed.

The x-hot-products.sql tries to add where they already exist so it fails. To get the SQL patch to finish I had to remove the following. I had used the 4.5.5 x-hot-products_remove but it does not remove them either.

ALTER TABLE xcart_products ADD on_sale binary(1) NOT NULL default 'N' AFTER title_tag;
ALTER TABLE xcart_products ADD mark_as_new enum('S','A','N') NOT NULL default 'N' AFTER on_sale;
ALTER TABLE xcart_products ADD show_as_new_from int(11) NOT NULL default '0' AFTER mark_as_new;
ALTER TABLE xcart_products ADD show_as_new_to int(11) NOT NULL default '0' AFTER show_as_new_from;
ALTER TABLE xcart_products ADD key sa (show_as_new_from, add_date);
ALTER TABLE xcart_products ADD key on_sale (on_sale);
ALTER TABLE xcart_categories ADD show_new_arrivals enum('Y','N') NOT NULL default 'Y' AFTER title_tag;

[cflsystems]

@Ksenia

Originally Posted by Ksenia

Yes, right now, if you install the store with 'use email as username' disabled, the admin's account username is set to 'master'. We don't think there's much risk as the unique password is generated in each store.

It's not only about risk. You are allowing admin to set any email as login but forcing "master" when email is not in use and "master" is well known XC out-of-the-box login. (Which means every one can login to admin even if they don't know the password - I will create a post for this in a minute - huge security whole for XC created by one of the XC modules)

Originally Posted by Ksenia

fCommercGo and Bestsellers still depend on Advanced statistics. The improvement which will allow to change 'bestsellers' and Facebook application so that they could do without this module are queued so far.

This module should have been taken out of core XC long time ago. As well as the HTML one as well as the Sales-and-Stats one... Their code is still in the core files while Sales-and-Stats was abandoned years ago....

Originally Posted by Ksenia

It was done for the sake of correct displaying Iframe ( X-Payments Lite interface) on checkout.

What was done there is that the OPC was broken so it accommodate another module... Do you think this is the right way to do it? Look at AC OPC - nothing like that....

Originally Posted by Ksenia

Since you state that 'there are no changes', it seems you have already reported the problem. Could you please provide me with the id of that bug report? I'm sorry I haven't found any, but I would like to avoid creating new and new tickets with the same issue .

Address book - there is no ticket open for this - at least not recently. There were couple but you guys closed them as overdue or resolved when adding additional fields to address book workaround was introduced. This workaround does not work good since you cannot position fields after adding them - read again - adding company field will add it at the end of the address book which is so wrong and looks weird, also on OPC this field will show after phone/fax and before email field.... Do you think this looks right?

Originally Posted by Ksenia

These issues have been reported into BugTracker. Not all of them were confirmed to be bugs, so one can hardly expect all of them to be fixed right away, but they're at least registered and queued for processing.

Actually I do expect bugs to be fixed with next release when they are reported. I do expect bugs to be fixed and not left for 2 years and with every new release... I do expect XC to fix bugs instead of working on new modules all the time... This has been mentioned here on the forum many times and I did mention it to Max and Alex at the meeting in Chicago - you would not release new version until all bugs reported for the previous one are fixed, or most of them... You should not release new version with same old bugs just so to introduce some new feature....

Originally Posted by Ksenia

Starting from v.4.4.0, the anonymous users data is stored in session. And after order is placed, the info about this customer is saved into order details. Record in xcart_customers is NOT being created. Will you please check again, or probably I've understood your statement incorrectly?

This happened after I created an order form admin - anonymous customer was saved in the customers table. Perhaps you are misunderstanding what I was saying - I was glad to see the anonymous customer saved in the customers table. What was introduced with 4.4.x - anonymous customers NOT treated as customers and NOT saved in customers table is wrong. Every one who places an order is a customer and their data must be saved in customers table not only in orders table. Orders table is for orders, this is completely separate and it should stay separate, this is table that holds what has happened already. Customers table is where all customers should be saved regardless of their registered status. Imagine a store with 10000 orders out of which 9999 are placed by customers who did not register. According to XC this store has only 1 customer Do you think this is correct? So we have one customer and 9999 orders from phantoms? No way to search for these anonymous customers. Not even a way to create an order for any of them in admin since they do not exist as customers in customers table... This is another piece that has been broken in XC since 4.4.x and if it still is - too bad - it is a bug - it has to be fixed.

[cflsystems]

For the first block above - master account - I mentioned security issue - http://forum.x-cart.com/showthread.php?p=359697#post359697

[ADDISON]

I agree Steve. All bugs reported should be fixed in the next version. I guess all the other shopping carts are doing the same way. We can talk a lot about ancient issues unsolved, they are many. I will also make my list and I do recommend everyone who reported bug inside Bugtracker or Forum over years to make an effort and check if that issue was solved or not - a top priority!

It is for the first time when I see an XC release without all modules updated for it. What is this 4.6.0 anyway? Some kind of testing software? Why we don't call it Release Candidate? I hate to see many numbers in a branch. I like the idea about security about speed, but let's do the other things professional - and the ball is in Qualiteam area.

Let me tell you just a stupid issue which is still unsolved. Fancy Category modules appears over the layout. Look at the z-index: thousands. This explains why this menu appears like an oasis when I would like to choose a currency, instead of being covered by a gray color too. Please check Bugtracker and Forum, I and Steve reported this annoying issue 3 times. I let you find out when we reported first time. Here are possible answers: 1 year ago, 2 or 3 years ago? But speed and security is a top priority. Good job!

[CenturyPerf]

QUESTION:

With the integration of TaxCloud, shouldn't the "TIC" field be included somewhere in import/export? This is a code that can vary by product class and would be a nightmare to manually edit if working with thousands of products.

MISSING:

Where is "Manufacturers" in Import/Export?

We are able to remove manufacturer data from the Tools page, but there is nowhere to import or export manufacturer data within the store tools. That is a lot of data to do by hand in moving from an older version of X-Cart. (clean URL, description, URL, title, META keywords, META description, etc)

[Jon]

Very good points brought up in this thread with regard to a need for bug fixes, not new features.

I've done a code comparison on 4.6 and 4.5.5 and compared to other branches there are not a lot of changes other than the new modules and the implementation of caching.

Sales and Stats code was finally removed.

[Ksenia]

Originally Posted by ADDISON

I agree Steve. All bugs reported should be fixed in the next version. I guess all the other shopping carts are doing the same way. We can talk a lot about ancient issues unsolved, they are many. I will also make my list and I do recommend everyone who reported bug inside Bugtracker or Forum over years to make an effort and check if that issue was solved or not - a top priority!

Originally Posted by cflsystems

Actually I do expect bugs to be fixed with next release when they are reported. I do expect bugs to be fixed and not left for 2 years and with every new release... I do expect XC to fix bugs instead of working on new modules all the time... This has been mentioned here on the forum many times and I did mention it to Max and Alex at the meeting in Chicago - you would not release new version until all bugs reported for the previous one are fixed, or most of them... You should not release new version with same old bugs just so to introduce some new feature....

Mr Addison, Steve, thank you for your critisism. There's no irony, we're very thankful, really.

We will concentrate the efforts on the work with rickets reported by the community in external bug-tracking system. Taking into account that some tickets contain improvement suggestions, not bug reports ( e.g. rewriting the Bestsellers module to work independently from Advanced statistics is rather an improvement), we do not promise to mark as 'resolved' all the issues you guys reported, however we will pay special attention to those tickets in our next release.

Originally Posted by ADDISON

It is for the first time when I see an XC release without all modules updated for it.

You're definitely right, there was a problem with the modules this time, and we're very sorry about it.

But the problem had been reported and escalated to the HeadStaff already, the solution had also been suggested ( it will be discussed during the next scrum) so it should not repeat in future.

[Ksenia]

Originally Posted by elmirage001

I've now successfully completed a database upgrade from 4.4.5 --> 4.5.0 and then used the upgrade pack from 4.5.0 --> 4.6.0 This morning I did an upgrade of my dev 4.5.5 site to 4.6.0 and both upgrades processed smoothly except for issues with the Hot Products Module. I have not experienced any of the issues the other posters have described. (patch applied)

The issue with the Hot Products Module involved the SQL which keeps the upgrade from fully completing. My files patched fine and then received the sql patch failed.

The x-hot-products.sql tries to add where they already exist so it fails. To get the SQL patch to finish I had to remove the following. I had used the 4.5.5 x-hot-products_remove but it does not remove them either.

Paul, unfortunately we can not tell for sure how exactly you're upgrading the store, but we assume that
*you have X-Cart Gold ( not GoldPlus where the module is available out of box) so the module is a an add-on.
* you're working with a dev copy ( and thus not afraid to lose any module data/settings).


You may now have 2 options:

OPTION 1

download and unarchive 'x-hot-products.4.6.0.tgz' in the store folder, as usually, run 'install-x-hot-products.php', select 'reinstall'. This procedure will remove the columns you list and recreate them.

OPTION 2
Apply the following SQL patch via 'patch/upgrade center':

ALTER TABLE xcart_products DROP COLUMN on_sale;
ALTER TABLE xcart_products DROP COLUMN mark_as_new;
ALTER TABLE xcart_products DROP COLUMN show_as_new_from;
ALTER TABLE xcart_products DROP COLUMN show_as_new_to;
ALTER TABLE xcart_products DROP KEY sa;
ALTER TABLE xcart_products DROP KEY on_sale;
ALTER TABLE xcart_categories DROP COLUMN show_new_arrivals; 

After that execute 'install-x-hot-products.php'(from v.4.6)

Note that both options will remove the columns and thus data in them. Module will be reinstalled from scratch, previous data may be lost. If you have some data that need to be preserved, you may contact our engineers via HelpDesk account and they'll give detailed instructions on how to patch the store manually AND not affect any module data.

Thank you and have a great day!

[Ksenia]

Originally Posted by CenturyPerf

QUESTION:
That is a lot of data to do by hand in moving from an older version of X-Cart. (clean URL, description, URL, title, META keywords, META description, etc)

If you move data from an older version to a newer one, we do not recommend using export/import. Not all types of data can be imported ( e.g orders), there can also be some mess with IDs or customers/products/categories.

Instead, you should upgrade the store, as a result you do not need to transfer any data manually at all.

But before taking any steps, please create a dev copy and use it as a sandbox.

*If your store is of version 4.5.0-4.5.5, you can download an upgrade pack and patch both files and database.

*If your store is of version 4.1.x-4.4.x, the most optimal way is to:
- save blowfish key
- upgrade DATABASE to v.4.5.0 by means of SQL upgrade patch ( in upgrade pack).
- assign the upgraded database to fresh 4.5.0, specify the blowfish key.
- upgrade from v4.5.0 to 4.6 by means of upgrade patches.

This is a very general instruction. Should you need a more detailed one, please request help in your HelpDesk account. Our engineers can also upgrade the store for you.
-