Bug #0000701: Add "Run Now" toolbar button to Agents grid
Fixes #0000660: Order's user could reset to Guest during payment gateway processing
Fixes #0000661: Possible no permission error, while accessing shipping type details on Front-End
Bug #0000857: Customized form blocks were not using "form_row" design resulting fatal error
1. Fixes #0000610: Title preset missing on shipping zone edit screen
Bug #0000591: Double border under toolbar on editing/config templates
Bug #0000787: Design for block with error message
Bug #0000803: Got fatal sql error, when adding paid listing type
Bug #0000814: Missing groups on section "Permissions" tab
Fixes #0000789: Several warnings on order edit shipping tab, when shipping quote engines are used
Fixes #0000790: Fatal error, when changing shipping mode setting of order
Bug #0000828: Auto-redirect from non-mod-rewrite url becomes very unstable
Releasing version 'branches/5.2.x' (copy from 'branches/5.1.x') of 'w/in-commerce' module.
Releasing version 'releases/5.1.0' (copy from 'branches/5.1.x') of 'w/in-commerce' module.
Fixes #0000788: Shipping quote engine small refactoring
Bug #0000357: Form modification detector (it's php part) works strange
Releasing version 'releases/5.1.0-RC1' (copy from 'branches/5.1.x') of 'w/in-commerce' module.
Bug #0000776: Change usage of "lu_rootcategory_name" Language label
Bug #0000779: Upgrade from 4.3.9 to 5.1.0-RC1 of In-Portal fails
Bug #0000772: Phrases are incorrectly splitted between Front-End and Admin language packs
Bug #0000758: Prepare 5.1.0 release
Merge of "w/in-commerce/releases/5.0.4@13731" to "w/in-commerce/branches/5.1.x@13704".
Releasing version 'releases/5.0.4' (copy from 'branches/5.0.x') of 'w/in-commerce' module.
Bug #0000726: Prepare 5.0.4 release
Releasing version 'releases/5.0.4-B2' (copy from 'branches/5.0.x') of 'w/in-commerce' module.
Fixes #0000766: Incorrect paths for In-Commerce & In-Auction gateway scripts
Bug #0000763: Incorrect join result during product editing in administrative console
Got a suggestion or an issue? Discuss it on the Atlassian Community or visit Atlassian Support for other options.
