You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: remove paid plan requirement for Legacy API tokens
API tokens are now available on all Ycode Legacy plans, not just paid
ones. Remove the warning callout and troubleshooting entry that told
users to upgrade to a paid plan first.
Made-with: Cursor
Copy file name to clipboardExpand all lines: content/getting-started/migrate-from-legacy.mdx
-7Lines changed: 0 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,12 +32,6 @@ The migration brings over your full project:
32
32
-**Site settings** — Global configuration, SEO settings, and custom code
33
33
-**Subscription** — Your current billing plan transfers to the new Ycode
34
34
35
-
## Before You Start
36
-
37
-
<Callouttype="warning"title="Important">
38
-
Make sure your Ycode Legacy project is on a **paid plan**. API tokens are only available on paid project plans, and you need a token to authorize the migration.
39
-
</Callout>
40
-
41
35
## Migration Steps
42
36
43
37
<Steps>
@@ -102,7 +96,6 @@ Your subscription plan from Ycode Legacy carries over to the new Ycode automatic
102
96
103
97
| Issue | Solution |
104
98
|-------|----------|
105
-
| "Tokens are available on paid project plans" | Upgrade your Legacy project to a paid plan before creating an API token |
106
99
| Token not working | Ensure you copied the full token. If lost, create a new one in Legacy under Settings → API Tokens |
107
100
| Migration seems stuck | Large projects with many assets may take longer. Wait for the process to complete before refreshing |
108
101
| Missing content after migration | Check that the content existed in the Legacy project before migration. Some draft or deleted items may not transfer |
0 commit comments