SimWhite Posted February 23, 2014 Report Posted February 23, 2014 I'm trying to rename package and change it price, when I click "save" I receive an error: "The term could not be removed because it is used by one or more services." When I change payment type to reccuring payments everything is OK, when I select "One time" I get an error again. CORE-1056 is installed. Path: /admin/packages/edit/1/ OS: Debian Blesta: 3.1.1 PHP: 5.4.4 MySQL: 5.5.35 Screenshot: http://dl.dropbox.com/u/2332741/Screenshots/imc125j9ikkm.png
Paul Posted February 23, 2014 Report Posted February 23, 2014 Did you remove any terms, or just change the price of an existing term? In 3.1, we made it so that terms can't be removed if they are attached to an existing service, because it effectively removes pricing from the service.
SimWhite Posted February 23, 2014 Author Report Posted February 23, 2014 Just change the price of exiting term. Neither removing nor adding.
Paul Posted February 24, 2014 Report Posted February 24, 2014 Just change the price of exiting term. Neither removing nor adding. That's odd, it shouldn't affect changing the price. Anyone else experiencing this?
Alk Posted February 24, 2014 Report Posted February 24, 2014 Yes, I also came across this issue the other day. So I have a package that I created in version 3.0. Like SimWhite, it is set for "one time". I don't even edit the package, click the update button and receive the same error message. The term box is greyed out because it is "one time" and I therefore assume that this is were the issue is.
Paul Posted February 24, 2014 Report Posted February 24, 2014 Ah, one time price option. I wonder if that's related to CORE-1056.
Alk Posted February 25, 2014 Report Posted February 25, 2014 Ah, one time price option. I wonder if that's related to CORE-1056. I'm not sure - you may need to investigate this further because according to SimWhite's original post, the fix for CORE-1056 has been installed already... CORE-1056 is installed.
SimWhite Posted February 25, 2014 Author Report Posted February 25, 2014 Yeah, fix is installed. Can it be because package was buyed by client?
Tyson Posted February 25, 2014 Report Posted February 25, 2014 Can you provide steps to duplicate the issue? We need to know what settings you have configured, then what data you changed that resulted in the error. For example, what module are you using on the package? How many pricing options do you have setup? Which fields did you change? What values were the fields before and after? etc. The more details you can provide, the better chance we have of determining the cause.
SimWhite Posted February 25, 2014 Author Report Posted February 25, 2014 1. Create Product named "Product" at Universal Module.Label: TestName: testType: SelectRequired: YesEncrypt: NoValues: 1:some|2:thing|3:here2. Create Package.Name: PackageStatus: ActiveQuantity: UnlimitedModule: Universal ModuleProduct: ProductTest: somePricing: term inactive, period one time, currency EUR, price 0.99, setup and cancel fee 0.00, no tax and cancel checkboxes.Group: Group3. Add file into Download plugin.Must be logged inAvailable to Client Groups is offAvailable to Packages is onSelected Packages: PackageNext, client bought this package and download file created at step three. After that I tried to change price of this package and receive an error mentioned above. Also I tried to change period from one time to recurring - everything is going well, but when select "one time" I receive an error again. As I have already mention, CORE-1056 is already was installed.
Alk Posted February 25, 2014 Report Posted February 25, 2014 To clarify; if you are trying to create a "one time" pricing term package (or attempting to add a "one time" pricing term to an existing package) you will hit the error from CORE-1056. Whereas the issue that we are both experiencing (and I'm speaking for SimWhite here but it sounds as though it's the same situation) is because the package is already existing from v3.0 and we are trying to edit it. I am using the cPanel module and I do not have to edit any fields in the package to have this error appear. So, I click to edit the package -> without changing any data -> click the Update package button -> receive the error. I have included screenshots of before and after. I hope that this is clearer.
Alk Posted March 29, 2014 Report Posted March 29, 2014 This bug is fixed in the latest 3.1.3 release. Thank you Blesta
Recommended Posts