X-Cart forums - X-Cart v4.4.3 released

X-Cart forums (https://forum.x-cart.com/index.php)

- News and Announcements (https://forum.x-cart.com/forumdisplay.php?f=28)

- - X-Cart v4.4.3 released (https://forum.x-cart.com/showthread.php?t=59213)

X-Cart v4.4.3 released

We are glad to announce that the new X-Cart v4.4.3 is now available for downloading in the "File area" section in your HelpDesk account at https://secure.qtmsoft.com, or at http://www.x-cart.com/download.html.

v4.4.3 is a minor bug-fix release which also features improved stability and performance. This version also includes some improvements, here are some of them:

- USPS API updated to versions RateV4 and IntlRateV2.
- Amazon Checkout integration reworked.
- Beanstream payment method updated.
- Support for MySQL 5.5.x added.
- CKEditor updated to version 3.5.3.
- JSON library updated to version 1.0.3
- jQuery API updated to version 1.5.1.
- and more...

For the detailed changes description see the CHANGELOG file included into the distribution package.

Find the installation guide at http://help.qtmsoft.com/index.php?title=X-Cart:Installation

NOTE: The upgrade packs will be available in a week approximately. You will be updated in this forum thread.

UPDATED:

The upgrade packs for X-Cart from 4.4.0-4.4.2 to v4.4.3 have been released and available for downloading in the "My licenses" section in your personal Helpdesk:

http://help.qtmsoft.com/index.php?title=Using_your_Qualiteam_Account#My_li censes

Re: X-Cart v4.4.3 released

Changelog part 1

Quote:

------------------ X-CART v4.4.3 RELEASED

*CHECKOUT*
[*] 11 Feb 2011, aim - Improvement (0104194): Added new API for getting/setting cart paymentid.
[!] 18 Feb 2011, aim - Bug (0105228 ): Fixed some bugs with zero total_cost.[*] 21 Feb 2011, aim - Improvement (0100686): Store requires billing details for orders with zero total cost. Fixed.
[!] 24 Feb 2011, aim - Bug (0099947): 'Save as a new address' and 'Update existing address' check boxes do not work properly on the One-Page Checkout page. Fixed.
[!] 28 Feb 2011, aim - Bug (0100609): Shipping cost sometimes appears empty on the One-Page Checkout page. Fixed.
[!] 01 Mar 2011, aim - Bug (0100941): minicart total fails to update on address change. Fixed.[*] 07 Mar 2011, aim - Improvement (0105521): Some changes related to the infinite loop in the checkout with an invalid payment method.[*] 21 Mar 2011, aim - Improvement (0106517): Added the Amazon_Checkout integration.func_cart_is_need_shipping function.[*] 08 Apr 2011, aim - Improvement (0101500): Reworked Amazon_Checkout integration.
[!] 18 Apr 2011, aim - Bug (0106083): AJAX queries do not work in PHP4. Fixed.

*DESIGN AND APPEARANCE*

[!] 14 Jan 2011, aim - Bug (0103484): Default site Title tag fails to appear on the home.php page. Fixed.
[!] 27 Jan 2011, aim - Bug (0104250): nbsp character not converted properly for category description, product description, etc. Fixed.
[!] 09 Mar 2011, aim - Bug (0084099): Product and account tabs fail to appear properly in the webmaster mode. Fixed.
[!] 09 Mar 2011, aim - Bug (0102818 ): W3C errors in customer area. Fixed.
[!] 14 Mar 2011, aim - Bug (0105368 ): JS error on printable pages. Fixed.
[!] 12 Apr 2011, aim - Bug (0104429): 'Submit' button fails to lock in the IE8 browser. Fixed.
[!] 25 Apr 2011, aim - Bug (0107843): Incorrect position of the 'Apply' button. Fixed.
[!] 25 Apr 2011, aim - Bug (0104938 ): HTML entities like &thetasym; Ο   € ‚ fail to appear properly. Fixed.
[!] 29 Apr 2011, aim - Bug (0107951): CSS aggregator fails to work correctly with cloud-zoom jQuery plugin, Detailed_Product_Images module. Fixed.

*IMAGES*

[!] 20 Jan 2011, aim - Bug (0103860): Problem with image manipulation related to lower_case_table_names MySQL settings in Windows OS. Fixed.
[!] 14 Mar 2011, aim - Bug (0105323): Import routine generates unnecessary zero-length thumbnails. Fixed.

*INTERFACE*
[*] 16 Feb 2011, ferz - Improvement (0104460): Improved description for the 'Number of columns to display the product list in' option.[*] 08 Apr 2011, ferz - Improvement (0107091, 0106625): Adjusted some email notification option texts.[*] 03 May 2011, aim - Improvement (0100421): Updated CKEditor to version 3.5.3.

*LANGUAGES*
[*] 14 Apr 2011, aim - Improvement (0107548 ): Removed duplicate lbl_fedex_address_2 label.[*] 28 Apr 2011, aim - Improvement (0107839): Small changes in labels.
[!] 29 Apr 2011, aim - Bug (0108055): _lng SQL tables fail to refresh when the related language is deleted. Fixed.

*ORDERS*

[!] 02 Feb 2011, aim - Bug (0103528 ): Orders placed with the Google/Amazon Checkout payment methods could not be found. Fixed.
[!] 08 Feb 2011, aim - Bug (0104714): Store returns wrong provider commission values. Fixed.
[!] 18 Apr 2011, ferz - Bug (0107567): Payment CC data fails to show in the admin order notification message even with the option 'Add order details (including credit card information) to admin order...' enabled. Fixed.
[!] 20 Apr 2011, ferz - Bug (0107668 ): Fails to show customer information for orders with deleted users. Fixed.
[!] 21 Apr 2011, ferz - Bug (0100838 ): Product quantity fails to change when order status changes from 'Backordered'. Fixed.

*SHIPPING*

[!] 28 Jan 2011, ferz - Bug (0103960): FedEx Priority Overnight shipping method fails to appear. Fixed.
[!] 28 Jan 2011, aim - Bug (0100768 ): 'Select a carrier' functionality fails to work properly in One-Page Checkout. Fixed.
[!] 13 Apr 2011, aim - Improvement (0103715): Updated USPS API to versions RateV4 and IntlRateV2.
[!] 14 Apr 2011, ferz - Bug (0107528 ): Intershipper fails to get shipping rates if the request contains spaces and special characters. Fixed.

*TAXES*

[!] 11 Apr 2011, aim - Bug (0104642): Wrong ST/DST+SH taxes when free shipping products are combined with regular products in the cart. Fixed.

*USERS*

[!] 20 Jan 2011, aim - Bug (0103840): 404 Not found error on some pages related to the user_modify.php?user={.id} link. Fixed.
[!] 21 Jan 2011, aim - Bug (0102815): 'Require to change password on next log in' option on the user modify page does not work. Fixed.[*] 08 Feb 2011, aim - Improvement (0104675): Added new API for getting/setting anonymous_userinfo.
[!] 09 Feb 2011, ferz - Bug (0104703): Obsolete 'login' field used instead of 'userid'. Fixed.
[!] 01 Mar 2011, ferz - Bug (0105651): Unnecessary data remains in the database when a customer profile is deleted. Fixed.
[!] 04 Mar 2011, aim - Bug (0105673): Incorrect error message on the user modify page in the admin area. Fixed.
[!] 25 Apr 2011, aim - Bug (0100420): Names like d'Artagnan fail to appear properly for anonymous customers in One-Page Checkout. Fixed.
[!] 27 Apr 2011, aim - Bug (0105143): Search users by address feature does not work. Fixed.

*PAYMENTS*
[*] 25 Jan 2011, aim - Improvement (0099622): Added new option 'Enable CVV2' for the Beanstream payment method.[*] 27 Jan 2011, ferz - Improvement (0104227): Updated Authorize.Net information variables.[*] 04 Feb 2011, aim - Improvement (0093809): Added new-generation algorithm for the SHA1 signature (SHASign).[*] 10 Feb 2011, aim - Improvement (0104815): Updated links for the 2Checkout payment gateway.
[!] 15 Feb 2011, aim - Bug (0101429): CC info visible in PayPal WPP Direct Payment when using X-Payments. Fixed.[*] 01 Mar 2011, ferz - Improvement (0105617): Updated Beanstream payment method.[*] 09 Mar 2011, aim - Improvement (0088553): Added the 'Fraud check service' option for the HSBC XML payment gateway.
[!] 10 Mar 2011, aim - Bug (0101140): Customers enter CC number twice for the First Data Global Gateway - Connect payment gateway. Fixed.
[!] 10 Mar 2011, aim - Bug (0106040): Incorrect number format used with eSelect Plus - Hosted Paypage payment gateway. Fixed.[*] 21 Mar 2011, aim - Improvement (0106491): Minor changes in the default shipping rate in the Google Checkout module.[*] 22 Mar 2011, aim - Improvement (0101906): Added new 'Display the "Checkout with Amazon" button at the top of catalog pages' setting for the Amazon Checkout module.
[!] 22 Mar 2011, aim - Bug (0105549): Google_Checkout/Amazon_Checkout works only with some other payment method enabled. Fixed.
[!] 29 Mar 2011, ferz - Bug (0106138 ): Bibit/RBS Worldpay payment server declines transaction when login is not stored in customer profile. Fixed.
[!] 30 Mar 2011, ferz - Bug (0105339): Payment method configuration page redirects to HTTPS in the admin area when the payment protocol is set to HTTPS. Fixed.
[!] 04 Apr 2011, ferz - Bug (0089861): Adjusted Netbanx payment note in the admin area.
[!] 07 Apr 2011, aim - Bug (0107260): Wrong reject duplicate 'NEW-ORDER-NOTIFICATION' logic. Fixed.

*PRODUCTS*

[!] 27 Jan 2011, aim - Bug (0102394): Search by_shortdescr by_fulldescr fails to work in the admin area. Fixed.
[!] 02 Mar 2011, ferz - Bug (0082907): Advanced product search does not recognize zero values in search parameters. Fixed.
[!] 03 Mar 2011, ferz - Bug (0100300): File on the Internet (enter image URL) functionality does not work on some servers. Fixed.

*IMPORT/EXPORT*

[!] 14 Feb 2011, aim - Bug (0104970): Address book fails to export properly. Fixed.
[!] 01 Mar 2011, ferz - Bug (0105587): Order export routine in the format 4.0.x exports ZIP-4 on a separate line. Fixed.
[!] 30 Mar 2011, ferz - Bug (0105264): Phone and fax values absent in order export CSV files. Fixed.

Re: X-Cart v4.4.3 released

Changelog part 2

Quote:

*PERFORMANCE*

[!] 17 Jan 2011, aim - Bug (0103462): The Speed Up CSS tool fails to support constructions like url("/path_to_image.image.jpg"). Fixed.[*] 18 Jan 2011, aim - Improvement (0103699): Added new 'Use cached buy_now.tpl template calls' check box on the general settings page.[*] 20 Jan 2011, aim - Improvement (0103848 ): Adjusted condition for invalidating cache in the func_get_default_fields function.[*] 11 Feb 2011, ferz - Improvement (0104803): Optimized some queries in banner statistics.[*] 24 Mar 2011, aim - Improvement (0106652, 0099127): Slightly optimized the 'Change user authentication mode' functionality.
[!] 14 Apr 2011, aim - Bug (0105061): 'Language labels and customer fields' fail to appear properly in multilingual stores. Fixed.
[!] 21 Apr 2011, aim - Bug (0106486): Fixed var/cache overload.[*] 22 Apr 2011, aim - Improvement (0102163): Optimized module initialization.[*] 28 Apr 2011, aim - Improvement (0104799): Optimized Advanced Statistics module.[*] 28 Apr 2011, aim - Improvement (0105901): Optimized Survey module.

*BACKUP/RESTORE*

[!] 14 Apr 2011, aim - Bug (0105036): DB backup/restore functionality fails to work properly. Fixed.

*PATCH/UPGRADE*

[!] 26 Apr 2011, aim - Bug (0105527): Patch tool inserts hunks after the ?> tag. Fixed.

*MISCELLANEOUS*
[*] 12 Jan 2011, aim - Improvement (0103380): Minor change related to the installation_auth_code comment.
[!] 17 Jan 2011, aim - Bug (0103701): PHP notices fixed.
[!] 17 Jan 2011, ferz - Bug (0103628 ): Duplicate code found in the install.php script. Fixed.
[!] 18 Jan 2011, aim - Bug (0103725): PHP notices fixed in logging in to the admin/provider area.[*] 18 Jan 2011, aim - Improvement (0103709): SQL error status improved in the upgrade procedure.
[!] 18 Jan 2011, aim - Bug (0099823): Shipping methods not available on the offer configuration page (Special_Offers module). Fixed.
[!] 18 Jan 2011, aim - Bug (0103758 ): PHP notices fixed on the General settings page.
[!] 18 Jan 2011, aim - Bug (0103760): PHP notices fixed on the offer configuration page, Special Offers module.
[!] 19 Jan 2011, aim - Bug (0103770): PHP notices fixed on the product page in the customer area.
[!] 19 Jan 2011, aim - Bug (0103769): Typo related to the x_error_reporting variable and PHP 5.3 error-level reporting logic. Fixed.
[!] 20 Jan 2011, aim - Bug (0101556): Multiple fixes related to 'Provider commissions'.
[!] 24 Jan 2011, aim - Bug (0104030): HTML tags fail to appear properly on the 'News lists' page in the admin area. Fixed.
[!] 24 Jan 2011, ferz - Bug (0093549): Updated ProxyPay3 integration.[*] 26 Jan 2011, aim - Improvement (0104018 ): JSON library updated to version 1.0.3. IE7 problem related to Content-type: application/x-javascript header fixed.
[!] 27 Jan 2011, aim - Bug (0104228 ): PHP notices fixed during functional tests.
[!] 31 Jan 2011, ferz - Bug (0103067): The admin side fails to stay in the HTTPS mode. Fixed.
[!] 01 Feb 2011, aim - Bug (0103398 ): USPS shipping label generator fails to work properly with the new shipping methods. Fixed.
[!] 07 Feb 2011, aim - Bug (0101410): Maximum thumbnail width/height settings are ignored on the Products Map page. Fixed.
[!] 07 Feb 2011, aim - Bug (0104638 ): Fixed access to uninitialized variables.
[!] 09 Feb 2011, aim - Bug (0104802): Fixed SQL errors.
[!] 14 Feb 2011, aim - Bug (0104968 ): Fixed the 'Cache_Lite : Unable to remove cache' error.[*] 03 Mar 2011, aim - Improvement (0104538 ): jQuery API updated to version 1.5.1.
[!] 03 Mar 2011, aim - Bug (0102569): Address book fails to provide correct shipping address to the checkout page. Fixed.
[!] 10 Mar 2011, ferz - Bug (0104096): Obsolete value in the COMPATIBLE_VERSION constant in the installation script. Fixed.
[!] 16 Mar 2011, ferz - Bug (0106246): E-mail message header is not RFC compliant. Fixed.[*] 22 Mar 2011, ferz - Improvement (0104564): SEO: Improved the canonical tag.
[!] 07 Apr 2011, aim - Bug (0107274): 'Call to undefined function func_cart_set_flag' error fixed.
[!] 08 Apr 2011, ferz - Bug (0106953): Same 'Contact us' form cache used in the Customer, Partner and Admin areas. Fixed.
[!] 11 Apr 2011, aim - Bug (0107403): SQL error fixed on the cart page related to the Special Offer module.
[!] 14 Apr 2011, ferz - Bug (0107161): 'Operate as this user' feature fails to restore cart content. Fixed.[*] 14 Apr 2011, aim - Improvement (0103629): Changed min MySQL version to 4.0.18 (for 4.0) and 4.1.2 (for 4.1). Added support for MySQL 5.5.x.
[!] 15 Apr 2011, aim - Bug (0105559): Libcurl used in the func_http_get_request function even when disabled in the General Settings. Fixed.
[!] 15 Apr 2011, aim - Bug (0089959): Code strings fail to paste properly to the command line. Fixed.
[!] 21 Apr 2011, aim - Bug (0107570): Regular expression not quoted. Fixed.
[!] 25 Apr 2011, aim - Bug (0102888 ): Installer fails to create new database. Fixed.[*] 29 Apr 2011, ferz - Improvement (107472): Removed obsolete code.[*] 04 May 2011, aim - Improvement (0108185): Changed ads management.

Re: X-Cart v4.4.3 released

great, i have waited for this stable version more than 1 year already!

Re: X-Cart v4.4.3 released

Woossshhh ... Finally :)

Re: X-Cart v4.4.3 released

And what is the upgrade procedure for this?

Re: X-Cart v4.4.3 released

It depends on the version you use. See Upgrading X-Cart.

The upgrade packs ==> 4.4.3 will be available in a week.

Re: X-Cart v4.4.3 released

Good to see this release out and lots of the reported bugs marked as fixed. Is it possible to get a report showing bugs reported between 4.4.2-4.4.3 release dates that were NOT fixed? Without going to the bug tracker

Re: X-Cart v4.4.3 released

Quote:

Originally Posted by qualiteam

It depends on the version you use. See Upgrading X-Cart.

The upgrade packs ==> 4.4.3 will be available in a week.

Thanks, I'm using 4.4.2 I'm just concerned about having to rebuild the customization in the template.

Re: X-Cart v4.4.3 released

You don't have to - 4.4.3 is a bug fixing release/upgrade so you keep same templates

Re: X-Cart v4.4.3 released

What if I'm currently using 4.4.1? Do I need to upgrade to 4.4.2 first, or can I use the upgrade pack to go straight to 4.4.3?

Re: X-Cart v4.4.3 released

I'm not quite sure as upgrade packs are not available yet.
But usually upgrade is incremental 4.4.1 -> 4.4.2 -> 4.4.3.

Re: X-Cart v4.4.3 released

Thanks, I haven't done a minor upgrade since I started using X-Cart. I didn't know :grin:

Re: X-Cart v4.4.3 released

Quote:

Originally Posted by cflsystems

You don't have to - 4.4.3 is a bug fixing release/upgrade so you keep same templates

I just want to double check everything, I have a skin deisgned by QT for 4.4.2, and I want to use 4.4.3.

I have all 180+ files (php,tpl and etc). Can I just install X-Cart 4.4.3, copy the 180+ files and expect that the skin (if it is called a skin - maybe template??) would work?

Kindly advise.

Thanks!

Re: X-Cart v4.4.3 released

This is an interesting entry in the changelog:

Quote:

Improvement (0104799): Optimized Advanced Statistics module

Can someone expound on this and the improvements to One-Page Checkout? There are some folks who are not very confident in these two systems.

Re: X-Cart v4.4.3 released

am i correct in thinking that all the changes have been made to files outside the "skin" folder so if i install this from scratch, i can just copy and paste my skin folder from 4.4.2.

Re: X-Cart v4.4.3 released

There are probably edits to the skin files too, so just copying your skin folder may not fix all the bugs - I'd run the upgrade and manually patch any files that were customized and won't patch.

Re: X-Cart v4.4.3 released

Quote:

Originally Posted by nickff

What if I'm currently using 4.4.1? Do I need to upgrade to 4.4.2 first, or can I use the upgrade pack to go straight to 4.4.3?

I think there will be 4.4.1->4.4.3 upgrade pack

Re: X-Cart v4.4.3 released

Quote:

Originally Posted by Sunray Sales

It doesn't work that way. It may work for some files but how can you be sure? You have to go through the upgrade process

Re: X-Cart v4.4.3 released

I've not preformed a 4.4.x upgrade, but it would seem to me that upgrades associated with the template files requires extra care if you followed a strategy where you created your own skin directories and avoided editing anything in the common_files.

On pre 4.4, you would run the upgrade patch, and you would get a report of all the files that could not be patched. You would work from that "could-not-patch" list to make your updates.

On 4.4, if the QT upgrade method is the same, you could get a report that all files are patched successfully - but it might not know about the changes in your skin directories.

If the upgrade script is not aware that you have used a strategy where you did not modify common_files, but instead created your own skin directory, then it seems you would need to review all those files against the upgrade list file, and hand patch any that changed. (Changes in skin files could be dependent on changes in core php files, and vice versa.)

As I understand it, there have been no improvements to the architecture (until v5), so upgrading is as it always has been - even if you separated your changes to new skin directories. Even upgrades within minor versions can be complex and require careful review of all impacted template files that you have modified.

---

Re: X-Cart v4.4.3 released

It would make sense if the upgrade would check to see which skin is selected and compare against that skin as well as common_files. Not sure if anyone has those details.

Re: X-Cart v4.4.3 released

Quote:

Originally Posted by gb2world

Ah ok QT made all modifications to the common files folder, not a dedicated skin folder.

Meaning the upgrade from 4.4.2 to 4.4.3 should be easy?

Or is it better to install 4.4.4 then apply the skin manually, in code line by line if it works?

Thanks!

Re: X-Cart v4.4.3 released

would it be possible for qualiteam to simply list which files have had modifications made to them?

this would allow us to work out which files could just be copied and replaced directly from 4.4.2 (which we have changed) and which ones we need to re-code manually.

Re: X-Cart v4.4.3 released

Quote:

Meaning the upgrade from 4.4.2 to 4.4.3 should be easy?
Or is it better to install 4.4.4 then apply the skin manually, in code line by line if it works?

I would not use the word "easy" about any upgrade, minor or major, until you see the upgrade pack. The possibilities are wide open. There could many relatively easy changes to a large number of files, few complex changes to few files or any combination of those possibilities. The other important factor is the number and scope of changes that you have made to your own skins & php files. If you understand all the changes that were made, that puts you at an advantage if/when the upgrade requires similar changes near your own modifications. Another factor is patches. If you have already applied patches, the upgrade will attempt to re-apply them.

Another possibility is that all your customizations are to files not impacted by the files in the upgrade - then you don't have to worry about the tedium of looking at the diff files.

Even when changes are easy, upgrades are almost always tedious. The best approach for you to take depends on the above factors plus your own patience and understanding of your customizations.

For past upgrades, on heavily modified shops - I find it best to get a report of the could not patch files, then patch them one by one looking at the diff files provided in the patch. If the shop is not heavily modified, the QT upgrade kits get you almost all the way there. Then you can use the word "easy". The more customizations you have done - the more tedious you can expect the upgrade to be.

Quote:

would it be possible for qualiteam to simply list which files have had modifications made to them?

This list has been a part of the upgrade kits in the past (file.lst). In addition to the upgrade links provided by QT above - I have found this sticky post to contain very good advise about upgrading: http://forum.x-cart.com/showthread.php?t=35125

---

Re: X-Cart v4.4.3 released

Installed 4.4.3 in a sub-folder of my active 4.1.10 x-cart. Have copied and pasted all of my shipping, payment and other settings.

So far everything seems flawless.

My database is so far apart, I plan to export the products and categories manually via CSV files and import them, then copy the images folders from the old cart to the new one.

Will see what happens, but so far it is looking very positive!

thanks,

Re: X-Cart v4.4.3 released

Installed this today, but I didn't retain my old skin. The purpose of upgrading from 4.1.3 was mostly to implement a new skin - I bought the smart-template from Phil Jones and have it up and running too, nicely.

I had no problem migrating the database over (there were probably a couple of hundred products).

The whole upgrade process went very smoothly. I renamed my old store root folder and created a new one to run side-by-side. Once I'd completed the database upgrade the old store was pretty much not required anymore.

The only thing I needed to do in addition to the simple step-by-step process was to copy my image files from oldstore/images over to the newstore/images folder.

So far I've been happy with the upgrade, but I am getting a strange bug when I log into (or more to the point, struggle to log into) the admin interface. It askes me for an email address and a password. It won't accept any combination of username/email/password. I have to reset it each time.

To do this I need to enter 'master' into the 'forgot password?' request to get it to send the 'reset password' email to my email address. Weird. I'd like to figure out how to fix this so that I can just simply log into the admin section instead of resetting it each time..

-Paul

Re: X-Cart v4.4.3 released

Quote:

Originally Posted by a333

QT provided me with all the necessary documentation and files to make the skin from scratch if needed. Meaning the diff file, all 180+ files they modified, the SQL changes made and etc.

In theory yes I can manually check each file to see if the upgrade from 4.4.3 would require me to make modifications, or be a simple copy and paste/overwrite existing file.

Hard to say at this point. I am still re-working on a 4.4.2 development site, then once that is complete. I plan on working on a 4.4.3 development site and push that one to be my Final and Live website.

Either way for me it will be a long and tedius process. I had a slightly modified 4.4.1 dev site (basic skin), and I tried to upgrade to 4.4.2 and it didn't work for me.

This makes me a little weary of doing upgrades, since my experience has been a litte bleak at the moment.

In the coming weeks I hope to have a 4.4.3 dev site running and hope the skin implementation wouldn't take too much time.

Thanks for all the suggestions though.

Re: X-Cart v4.4.3 released

Quote:

Originally Posted by Paul Jones

So far I've been happy with the upgrade, but I am getting a strange bug when I log into (or more to the point, struggle to log into) the admin interface. It askes me for an email address and a password. It won't accept any combination of username/email/password. I have to reset it each time.

To do this I need to enter 'master' into the 'forgot password?' request to get it to send the 'reset password' email to my email address. Weird. I'd like to figure out how to fix this so that I can just simply log into the admin section instead of resetting it each time..

-Paul

try creating a new user admin profile and see if email login works using that.

Re: X-Cart v4.4.3 released

hi seyfin, i want to buy a nice skin for my xcart store, can you suggest me a seller?
best regards- ratnesh

Re: X-Cart v4.4.3 released

Quote:

Originally Posted by K9sport

hi seyfin, i want to buy a nice skin for my xcart store, can you suggest me a seller?

http://marketplace.x-cart.com/skins-templates/

Re: X-Cart v4.4.3 released

I see upgrade packs in my file area. WOO-HOO!

=)

Re: X-Cart v4.4.3 released

Quote:

Originally Posted by FiberGuy

I see upgrade packs in my file area. WOO-HOO

Brill!

Re: X-Cart v4.4.3 released

The upgrade packs for X-Cart from 4.4.0-4.4.2 to v4.4.3 have been released and available for downloading in the "My licenses" section in your personal Helpdesk:

http://help.qtmsoft.com/index.php?title=Using_your_Qualiteam_Account#My_li censes

Re: X-Cart v4.4.3 released

Ok, I unpacked the update, and ftp the whole thing to my xcart directory. But in the admin upgrade page it says No patches available. What do I need to do to make this work? Oh wait, I uploaded the containing folder, do I upload only the contents, not the main folder?

<edited to add>

good news, I got the update working, all went well. One hickup, the Patch.sql failed, I asume because I had previously used the USPS rates patch. My question now, is will this be a problem with the database, or is all good because it was already fixed with the shipping update?

Re: X-Cart v4.4.3 released

Ok this may be something totaly wrong with me but will post anyway, just so everybody be more cautious.
So I tried the 4.4.2-4.4.3 upgrade today. All ok, I had to manually patch/check like 5 files due to patches applied earlier. After the upgrade though some areas of the site became inoperational. For example orders.php in admin, cart.php, adding product to cart as a customer returns error. Each of this scripts ends with a screen "500 internal server error". My guess is the upgrade changed some permissions. I had to revert back to 4.4.2 from a backup and all works just fine. I will give it another try but in the meantime - anybody done 4.4.2-4.4.3 upgrade yet? Any problems?

Re: X-Cart v4.4.3 released

Ok next - let's start with the bugs - 4.4.3

http://forum.x-cart.com/showpost.php?p=312270&postcount=195

Reported on March 10 and here we are 2 months later this is not fixed. I am still to check with fake order if the userid=0 is fixed or not but looking at the code seems it's not fixed. Then the second part about the Advanced Statistics / Recommended Products is carried to 4.4.3 again. Am I reading this wrong or QT just ignores some reports?

This is how the upgrade "fixes" these bugs

Code:

 

-            'userid'            => $userinfo['id'] ? $userinfo['id'] : 0,

-            'membershipid'      => $userinfo['membershipid'],

-            'membership'        => addslashes($userinfo['membership']),

+            'userid'            => !empty($userinfo['id']) ? $userinfo['id'] : 0,

+            'membershipid'      => @$userinfo['membershipid'],

+            'membership'        => addslashes(@$userinfo['membership']),

Again I think the 0 userid will still happen.

Code:

 

-                if (!empty($active_modules['Recommended_Products'])) {

+                if (

+                    !empty($active_modules['Recommended_Products'])

+                    && !empty($userinfo["id"])

+                ) {

Again - why "Recommended Products"? Are they pulled off of the stats table?

So QT - does this fixes the bugs or not? Do I need to again report in the bugtracker? Or these are not bugs?

Re: X-Cart v4.4.3 released

An answer to my previous post #38 above:

A warning to everyone doing an upgrade to 4.4.3 - the upgrade script (at least 4.4.2-4.4.3 one) will set permissions on all php files modified by the script to 600 (read/write owner of the file only) which on some systems may result in non-working stores. Make sure to check and setup permissions to all php files to 644 after the upgrade

QT is there a reason for this?

Re: X-Cart v4.4.3 released

Just so everyone's aware, we're finding that 4.4.3 is breaking most 3rd party modules out there. So be ready to get some help/support if you have 3rd party modules (i.e. don't upgrade on the fly on the weekend when there's less support).

Thanks,

Carrie

Re: X-Cart v4.4.3 released

Quote:

Originally Posted by BCSE

we're finding that 4.4.3 is breaking most 3rd party modules out there.

The module initialization routine has been changed and optimized in 4.4.3. Here are the patch which describes the main changes: DIFF_55111.patch.txt

Basically, to initialize your module in X-Cart 4.4.3, you should modify your module's configuration file, for example:

modules/Your_Addon_Module/config.php

and add the following code:

Quote:

$_module_dir = $xcart_dir . XC_DS . 'modules' . XC_DS . 'Your_Addon_Module';
/*
Load module functions
*/
if (!empty($include_func))
require_once $_module_dir . XC_DS . 'func.php';

/*
Module initialization
*/
if (!empty($include_init))
include $_module_dir . XC_DS . 'init.php';

before this line:

Quote: