In SpikerSoft Stacker, users who already own a valid license can still select the “Me” option and attempt to purchase another license for themselves. The system should prevent this action and provide clear visual feedback indicating that the user already holds a license. Currently, the app allows the purchase attempt, triggers a POST request, and reloads the page.
Issue Description
When a user with an active license accesses the license purchase page, the “Me” checkbox remains enabled. Selecting it and clicking “Buy a license — $39.99” sends a POST request to https://api.spikersoft.com/api/stacker/license/checkout, resulting in an HTTP 409 conflict and a page reload. The lack of feedback or disabled state for existing license holders creates confusion and poor user experience.
Environment
Property
Value
Application
SpikerSoft Stacker
Module
License Purchase
Environment
Production
Browser
Firefox / Chrome
Operating System
Windows 11
Version
v2026.10.04e
Device
Desktop
Preconditions
User already owns a valid Stacker license.
Steps to Reproduce
Log in to SpikerSoft Stacker with an account that already has a license.
Navigate to the License Purchase page.
Select “Me” and click “Buy a license — $39.99.”
Observe the POST request and page reload.
Expected Result
The “Me” checkbox should be disabled for users who already own a license.
The interface should display a visual message confirming that the user already has a license.
No POST request should be triggered.
Actual Result
The “Me” checkbox remains active.
Clicking Buy a license sends a POST request and reloads the page.
No feedback is provided to the user.
Evidence
Screenshot shows the license purchase interface with the active “Me” option and console output: POST https://api.spikersoft.com/api/stacker/license/checkout [HTTP/1.1 409].
Impact
Confuses users who already own a license.
Causes unnecessary API calls and page reloads.
Minor but recurring UX issue.
Frequency
Always
Reproducibility
100%
Severity
Medium
Suggested Fix
Disable the “Me” checkbox when a license is detected in the user’s profile.
Add a visual feedback message such as “You already own a license.”
Prevent duplicate purchase attempts by validating license ownership before initiating checkout.
Optionally, redirect users to their license management page instead of reloading.
## Summary
In **SpikerSoft Stacker**, users who already own a valid license can still select the **“Me”** option and attempt to purchase another license for themselves. The system should prevent this action and provide clear visual feedback indicating that the user already holds a license. Currently, the app allows the purchase attempt, triggers a POST request, and reloads the page.
## Issue Description
When a user with an active license accesses the license purchase page, the **“Me”** checkbox remains enabled. Selecting it and clicking **“Buy a license — $39.99”** sends a POST request to
`https://api.spikersoft.com/api/stacker/license/checkout`, resulting in an HTTP 409 conflict and a page reload. The lack of feedback or disabled state for existing license holders creates confusion and poor user experience.
## Environment
| Property | Value |
|-----------|--------|
| Application | SpikerSoft Stacker |
| Module | License Purchase |
| Environment | Production |
| Browser | Firefox / Chrome |
| Operating System | Windows 11 |
| Version | v2026.10.04e |
| Device | Desktop |
## Preconditions
User already owns a valid Stacker license.
## Steps to Reproduce
1. Log in to **SpikerSoft Stacker** with an account that already has a license.
2. Navigate to the **License Purchase** page.
3. Select **“Me”** and click **“Buy a license — $39.99.”**
4. Observe the POST request and page reload.
## Expected Result
- The **“Me”** checkbox should be **disabled** for users who already own a license.
- The interface should display a **visual message** confirming that the user already has a license.
- No POST request should be triggered.
## Actual Result
- The **“Me”** checkbox remains active.
- Clicking **Buy a license** sends a POST request and reloads the page.
- No feedback is provided to the user.
## Evidence
- Screenshot shows the license purchase interface with the active **“Me”** option and console output:
`POST https://api.spikersoft.com/api/stacker/license/checkout [HTTP/1.1 409]`.
## Impact
- Confuses users who already own a license.
- Causes unnecessary API calls and page reloads.
- Minor but recurring UX issue.
## Frequency
Always
## Reproducibility
100%
## Severity
Medium
## Suggested Fix
- Disable the **“Me”** checkbox when a license is detected in the user’s profile.
- Add a **visual feedback message** such as “You already own a license.”
- Prevent duplicate purchase attempts by validating license ownership before initiating checkout.
- Optionally, redirect users to their **license management page** instead of reloading.
Thanks for the clear write-up. The steps, the environment table and the console line with the 409 made this quick to confirm.
What we found
You were right about the main problem. The /stacker buy card never checked whether you already owned a license, so Me stayed selectable and Buy a license sent the checkout request.
The page did give feedback after the 409: a line saying "This account already has a license. Find your key in your profile." It was shown above the "Who is this license for?" choices, though, so it was easy to miss. Worth knowing for next time: the line was there, it was just badly placed.
There's no page reload. The button briefly reads "Opening checkout…" and then switches back, which can look like a reload. In DevTools, the Network tab's "Preserve log" option plus the request's Initiator will tell you whether a real navigation happened.
When you're signed in, the page now checks which licenses you already have. Me is disabled and marked "· already licensed". The same goes for a child you've already bought a license for.
If the selected person already has a license, the buy button is replaced by the "already has a license — find your key in your profile" line.
No checkout request is sent in that case. The server's 409 is still there as a safety net.
Tip for future reports: when you say "no feedback," a screenshot taken a second or two after the click helps a lot. Messages that appear late, or somewhere other than where you're looking, are exactly what we need to see.
Closing this now. If you still see it after the next deploy (the version badge should be newer than v2026.10.04e), please reopen and include your version.
Thanks for the clear write-up. The steps, the environment table and the console line with the `409` made this quick to confirm.
**What we found**
- You were right about the main problem. The `/stacker` buy card never checked whether you already owned a license, so **Me** stayed selectable and **Buy a license** sent the checkout request.
- The page did give feedback after the `409`: a line saying "This account already has a license. Find your key in your profile." It was shown *above* the "Who is this license for?" choices, though, so it was easy to miss. Worth knowing for next time: the line was there, it was just badly placed.
- There's no page reload. The button briefly reads "Opening checkout…" and then switches back, which can look like a reload. In DevTools, the Network tab's "Preserve log" option plus the request's *Initiator* will tell you whether a real navigation happened.
**What changed** (spikerj/spikersoft-angular#1479, now merged)
- When you're signed in, the page now checks which licenses you already have. **Me** is disabled and marked "· already licensed". The same goes for a child you've already bought a license for.
- If the selected person already has a license, the buy button is replaced by the "already has a license — find your key in your profile" line.
- No checkout request is sent in that case. The server's `409` is still there as a safety net.
**Tip for future reports:** when you say "no feedback," a screenshot taken a second or two *after* the click helps a lot. Messages that appear late, or somewhere other than where you're looking, are exactly what we need to see.
Closing this now. If you still see it after the next deploy (the version badge should be newer than v2026.10.04e), please reopen and include your version.
spikerj
added the bug label 2026-10-05 20:28:39 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
In SpikerSoft Stacker, users who already own a valid license can still select the “Me” option and attempt to purchase another license for themselves. The system should prevent this action and provide clear visual feedback indicating that the user already holds a license. Currently, the app allows the purchase attempt, triggers a POST request, and reloads the page.
Issue Description
When a user with an active license accesses the license purchase page, the “Me” checkbox remains enabled. Selecting it and clicking “Buy a license — $39.99” sends a POST request to
https://api.spikersoft.com/api/stacker/license/checkout, resulting in an HTTP 409 conflict and a page reload. The lack of feedback or disabled state for existing license holders creates confusion and poor user experience.Environment
Preconditions
User already owns a valid Stacker license.
Steps to Reproduce
Expected Result
Actual Result
Evidence
POST https://api.spikersoft.com/api/stacker/license/checkout [HTTP/1.1 409].Impact
Frequency
Always
Reproducibility
100%
Severity
Medium
Suggested Fix
Thanks for the clear write-up. The steps, the environment table and the console line with the
409made this quick to confirm.What we found
/stackerbuy card never checked whether you already owned a license, so Me stayed selectable and Buy a license sent the checkout request.409: a line saying "This account already has a license. Find your key in your profile." It was shown above the "Who is this license for?" choices, though, so it was easy to miss. Worth knowing for next time: the line was there, it was just badly placed.What changed (spikerj/spikersoft-angular#1479, now merged)
409is still there as a safety net.Tip for future reports: when you say "no feedback," a screenshot taken a second or two after the click helps a lot. Messages that appear late, or somewhere other than where you're looking, are exactly what we need to see.
Closing this now. If you still see it after the next deploy (the version badge should be newer than v2026.10.04e), please reopen and include your version.