Jonathan Posted December 9, 2015 Report Posted December 9, 2015 Pretty weird one. Using the solus module, add say 20 IPs to a service. It doesn't matter if you pro-rate the addition or not (that works fine). Through the service view that lets you specifically delete certain IPs, remove one. The first one gives a pro-rata credit as it should. The second-* removals will generate credits equal to double what it should (consistently). This can be recreated over and over. As you can see in the SS, after the first, it doubled.
Jonathan Posted January 18, 2016 Author Report Posted January 18, 2016 Friendly bump before 4.0 comes out
Tyson Posted January 27, 2016 Report Posted January 27, 2016 Pretty weird one. Using the solus module, add say 20 IPs to a service. It doesn't matter if you pro-rate the addition or not (that works fine). Through the service view that lets you specifically delete certain IPs, remove one. The first one gives a pro-rata credit as it should. The second-* removals will generate credits equal to double what it should (consistently). This can be recreated over and over. As you can see in the SS, after the first, it doubled. Just had some time to test this issue, but I wasn't able to duplicate it. For me on v3.6.1, removing multiple IP addresses one at a time from the admin or client UI creates a transaction of the expected prorated credit amount. None of my transactions are showing a doubled credit. Is your config option for the extra IPs set to the Step of 1 as mentioned in the documentation? I don't recall exactly what behavior will occur if you set the step higher than one, but if it were set to 2, that could explain the credit doubling.
Tyson Posted February 22, 2016 Report Posted February 22, 2016 Can anyone that encounters this issue provide details on a service (i.e. package and package options) along with steps that can be followed to consistently duplicate this doubled-credit problem?
Jonathan Posted February 22, 2016 Author Report Posted February 22, 2016 I've chalked this up to a custom modification to core that may be causing it. The only thing making me doubt that is @cyandark's claim that this happens to him too.
Tyson Posted February 22, 2016 Report Posted February 22, 2016 I have the same problem. @cyandark, can you provide any more details on how you experience this issue, and perhaps include a set of steps to duplicate it as I mentioned above? Abdy 1
Abdy Posted February 23, 2016 Report Posted February 23, 2016 @cyandark, can you provide any more details on how you experience this issue, and perhaps include a set of steps to duplicate it as I mentioned above?I don't have more the problem, is a mistake from me creating the Configurable Option.I resolved the problem with this settings. http://fotos.subefotos.com/b73e39db74b7ce881174d509c2d918c7o.png
Tyson Posted February 23, 2016 Report Posted February 23, 2016 I don't have more the problem, is a mistake from me creating the Configurable Option. I resolved the problem with this settings. http://fotos.subefotos.com/b73e39db74b7ce881174d509c2d918c7o.png Your values seem odd. One extra IP is set to 0, and two extra IPs is set to 1, etc. I would expect the values to match, i.e. 0 extra IPs = 0, 1 extra IP = 1, 2 extra IPs = 2, etc. As long as an IP can be selected for every integer in the set (e.g. [1,4]), removing them should function correctly because there is always a valid config option value of 1 lower. I also see that your config option is not assigned to any package groups. Are you no longer using it? In any case, it seems as though the credit-doubling issue may not be a bug with Blesta. If anyone is able duplicate it, then please describe steps in order to do so and I'll take a look again. Michael 1
Recommended Posts