ReturnUrlComponent stored ?returnUrl= whenever it contained "http", and
layout.context sent the browser there after login or sign-up. That made the
login an open redirect, and a javascript: value could run script on the
Postiz origin. returnUrl is now kept only when it is an http(s) address on
the app's own origin, checked when it is stored and again when it is read.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The HubSpot app's redirect URL (/oauth/hubspot/callback) dropped people on
the bare calendar, so nothing said the install worked or what to do next.
It now lands on /launches?hubspot=installed, where HubspotInstalled opens a
modal with the next steps in HubSpot (Agent Builder > MCP Servers > Postiz
MCP) and then clears the param. returnUrl brings someone who has to sign in
first back to it. Two new strings in en and the 14 Lingo locales.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The frontend build fetched Plus Jakarta Sans from Google Fonts at build
time, and a few CI builds failed with "Can't resolve
'@vercel/turbopack-next/internal/font/google/font'". The font is now
loaded with next/font/local from woff2 files in the repo, so the build
no longer depends on Google.
The files are the variable fonts from tokotype/PlusJakartaSans commit
18d1cd2f (the same files google/fonts ships, SIL OFL 1.1, license
included), converted to woff2. All four layouts share one 500-700
upright + italic definition.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The connect command input had a controlled value without onChange,
which made React log a console error when opening the Telegram
connect modal.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The video is already live when thumbnails.set is rejected, but the post
ended in ERROR with no release URL, so users re-uploaded duplicates. The
provider now throws PublishedWithError with the video id and URL; the post
activity persists them through PostsService.updateResolvedRelease (the
existing org-scoped repository write, state untouched) and rethrows
BadBody, so every workflow version still marks the post ERROR while the
calendar can link to the live video.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The frontend proxy stored the team-invite token (org cookie) and the
selected-org cookie (showorg) for only 15 minutes. An invitee who opened
the invite link but finished signing up later lost the invite, even
though the link itself is valid for 2 days since #1643, and a member who
joined via the link fell back to the default org after 15 minutes.
Complementary to the invite token expiry extension in #1643: the org
cookie now lives 2 days to match the link, and showorg gets the same
365-day lifetime the backend already uses for it.
On a same-plan Monthly/Yearly switch the stored tier already matches
before the webhook, so the first poll wrote a stale snapshot that
reverted the period toggle and could restore cancelAt. showConfirmedPlan
now waits until both the stored tier and period match the change; the
webhook writes tier, period and cancelAt in one update.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The in-place plan change only updates Stripe, the stored plan follows
with the webhook, so refetching the credits right away still returned
the old plan's. The billing cycle card now takes its plan from the
stored subscription and, after a plan change, polls /user/subscription
until it matches, then writes the three credit counts and the
subscription into the cache together. Any failure or a webhook slower
than about 10 seconds leaves the previous values in place.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
getRenewalDate now returns { renewsAt, trialing }: while the Stripe
subscription is trialing, renewsAt is its trial_end and the card says
the free trial ends and the first payment is charged on that date.
After an in-place plan change the renewal date and the credits are
revalidated together with the invoices, so the counters don't mix the
new plan's totals with the old plan's remaining credits.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The global .dropdown-menu button rule sets a transparent background with
higher specificity than a plain Tailwind bg class, so the selected row's
bg-boxHover never showed and keyboard navigation had no visible cursor.
Use the dropdown's own hover color with the important modifier for the
selected row, and drop the hover class that the global rule overrode.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds a Billing cycle card between the plans and the payment method card:
the next renewal date from the payment provider (new getRenewalDate on the
provider interface, null by default, Stripe reads current_period_end of the
live subscription) via GET /billing/renewal, and the remaining AI images,
AI videos and clipping minutes of the current month from the existing
/copilot/credits endpoint.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The @mention suggestion list used hardcoded light colors (bg-white,
text-gray-800, bg-blue-100). In dark mode bg-white resolves to the dark
background while the label stays near-black, so results were invisible
and the list looked empty. Use the theme tokens the other menus use.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
When no showorg cookie is set (or it no longer matches), the auth
middleware fell back to the first org of an unordered query. Invited
team members who also own an empty personal org could land behind the
paywall instead of in the paid team org they joined. Prefer an org that
has a subscription before falling back to the first one. An explicit
showorg cookie still wins.
Deleting an account was blocked with "Please remove your team members
before deleting your account" whenever the org had any other member. When a
plan loses team members the subscription flow only disables them, it does not
remove them, so an owner of a cancelled org who could not reach the team
settings (billing paywall) was stuck and could never delete the account.
The owner's explicit confirmation now covers both effects instead:
- GET /user/delete-account-info returns hasSubscription / hasAdditionalMembers
across the orgs the user owns, and the confirmation dialog states that the
subscription will be cancelled and/or the additional team members removed
from the organization (four text variants).
- deleteAccount removes every other member of each deleted org, whether the
subscription is still active or already cancelled (members disabled).
- An org with another SUPERADMIN is not treated as owned: deleting the
account only removes the user from it and the org is left untouched.
Subscription cancellation itself is unchanged (cancelAllSubscriptions in the
controller, before deleteAccount).
Verified end to end in Stripe test mode with stripe listen: an org with an
active subscription and an enabled member, and an org whose subscription was
already cancelled with a disabled member, were both deleted; the Stripe
subscription ended up canceled, the Subscription row was removed and the
members kept their own orgs.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The downgrade and cancel confirmations always said "Your team members will
be removed from your organization" when moving from a plan with team members
to one without, even for an org with no members. They are not removed: the
subscription flow only sets userOrganization.disabled, and a later upgrade to
a team plan re-enables them.
moveToCheckout now loads /settings/team and adds the message only when the
org has a member other than the current user (or the list cannot be read),
and the text says the members are disabled until the org is on a plan that
includes team members again.
Verified end to end in Stripe test mode with stripe listen: a TEAM org with
a member downgraded to STANDARD (webhook disabled the member) and upgraded
back to TEAM (webhook re-enabled it).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>