Commerce renewal term text (price) display bug

[PatrickRQ]

The issue is as follows:

Have package with multiple renewal terms:

1. 30 days / $10
2. 180 days / $30 (add to base price)
3. 360 days / $60 (add to base price)

Select 2 or 3. The price will display:

"First 30 days $XX" always. If "add to base price" is selected it should display 180 or 360 days for 2 and 3. Otherwise it claims that first 30 days cost price + renewal.

 

Issue lays somewhere in {{$priceDetails = $package->fullPriceInfo();}}

Quick solution would be appreciated.

Edited January 12, 2022 by PatrickRQ

[Marc]

I would need an example I can take a look at on your site in order to determine what is happening here. If you can provide this, we can certainly take a look

[PatrickRQ]

I noticed it on my test site while preparing to launch after migration, the site is not accessible yet. Unless you can access my PC via e.g. team viewer and then see the board directly.

Edited January 12, 2022 by PatrickRQ

[Marc]

Could you screenshot what you have set up. I can then set it up this end and see whats going on there

[PatrickRQ]

Sure thing Marc, Configure product with such pricing/renewals

Then go to that product in store front and start changing the renewal terms. You will notice that when you select any of renewals where "add to base price" is selected the system will keep saying that this is price for first 30 days. Where it should be price for selected renewal term length.
 

[Marc]

Please could you also screenshot the issue itself, as Im not sure where there is an issue here. From what you have said, it sounds to be correct

[PatrickRQ]

Image above is correct for first renewal term, which say: "First 30 days: 530" then "55/30 days". This is first renewal.

Now, switch to renewal 2 or 3 which is 180 or 360 days and adds the renewal value to the base price

As you can see it still says "First 30 days" but the price is already 530 + 275. The text should say now:

"First 180 days: 805" then "275/180 days". This is because the renewal price is selected to be added to base price, so in real customer pays here for the period of 180 days.

Makes a sense to you now? Current behavior is like not considering the value of renewal was added to base price so customer pays upfront for entire period.

In short, when "add to base price" is selected for specific renewal term then you should pull the actual term length to display for the area saying "First X days"

Edited January 12, 2022 by PatrickRQ

[Marc]

Yes, it does indeed. I was looking at the values there, when its actually the days  that are an issue. Please bear with me while I take a look, and will likely need to get this submitted as a bug

[Marc]

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

 

[PatrickRQ]

By any change, could I request a hoitfix I may apply myself?

[Randy Calvert]

If a hot fix is ever available, it would show up in the Support section of your ACP. Where it says:

Quote

Invision Community
Version 4.6.9

Running latest version

It would note than an optional patch is available.  

With that being said, all that has happened so far is that the issue has been confirmed and added to their internal bug tracker.  It does not mean a fix has been made and it does not note when the fix would be released (if it would make it into the next release or later).   

The best thing you can do is watch the Hump Day updates by @Jordan Miller as he frequently posts the changes/fixes that have been made recently and due to be added to the next scheduled release.  

[Marc]

10 hours ago, PatrickRQ said:

By any change, could I request a hoitfix I may apply myself?

This isnt something we are able to hotfix, as there isnt actually a fix yet available. Its been added to our bug tracker, but hasnt, as of yet, been resolved

Just to add to this, if you keep your aye on this topic you will see the prefix change to "In future release" when its actually been resolved

[PatrickRQ]

Hoping to see a fix soon. It is a bit misleading for potential buyer and causes many questions we could avoid by fixing it.

Edited January 24, 2022 by PatrickRQ

[Marc]

43 minutes ago, PatrickRQ said:

Hoping to see a fix soon. it is a bit misleading for potential buyer and causes many questions we could avoid by fixing it.

Fully understood, and Im sure we will have a fix available for this soon

[PatrickRQ]

Any news please? the issue starts to be pain in the ... please.

[Jim M]

Sorry, this is still being investigated at this time.

[Marc]

This issue has been resolved in 4.6.12, which has just been release. Please let us know if you still have any issues once you have upgraded to that release.