Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
thetaPC
commented
Sep 15, 2026
| :::note | ||
|
|
||
| If you are building an Ionic Angular app, the styles need to be added to a global stylesheet file. Read [Style Placement](#style-placement) in the Angular section below for more information. | ||
| If you are building an Ionic Angular app, the styles need to be added to a global stylesheet file. |
Contributor
Author
There was a problem hiding this comment.
The section only existed in v5.
thetaPC
commented
Sep 15, 2026
| :::note | ||
|
|
||
| If you are building an Ionic Angular app, the styles need to be added to a global stylesheet file. Read [Style Placement](#style-placement) in the Angular section below for more information. | ||
| If you are building an Ionic Angular app, the styles need to be added to a global stylesheet file. |
Contributor
Author
There was a problem hiding this comment.
The section only existed in v5.
thetaPC
commented
Sep 15, 2026
| ``` | ||
|
|
||
| This error is an error code from Xcode that can be caused by provisioning issues or outdated cordova dependencies. To fix this error first make sure a provisioning profile has been generated using the above instructions and then try to [run the app from Xcode](../developing/ios.mdx#running-with-xcode). | ||
| This error is an error code from Xcode that can be caused by provisioning issues or outdated cordova dependencies. To fix this error first make sure a provisioning profile has been generated using the above instructions and then try to [run the app from Xcode](/developing/ios.mdx). |
Contributor
Author
There was a problem hiding this comment.
That section only existed in v5 and v6.
thetaPC
commented
Sep 15, 2026
| ``` | ||
|
|
||
| This error is an error code from Xcode that can be caused by provisioning issues or outdated cordova dependencies. To fix this error first make sure a provisioning profile has been generated using the above instructions and then try to [run the app from Xcode](../developing/ios.mdx#running-with-xcode). | ||
| This error is an error code from Xcode that can be caused by provisioning issues or outdated cordova dependencies. To fix this error first make sure a provisioning profile has been generated using the above instructions and then try to [run the app from Xcode](/developing/ios.mdx). |
Contributor
Author
There was a problem hiding this comment.
That section only existed in v5 and v6.
thetaPC
commented
Sep 15, 2026
|
|
||
| :::note | ||
| If you are building an Ionic Angular app, the styles need to be added to a global stylesheet file. Read [Style Placement](#style-placement) in the Angular section below for more information. | ||
| If you are building an Ionic Angular app, the styles need to be added to a global stylesheet file. |
Contributor
Author
There was a problem hiding this comment.
The section only existed in v5.
thetaPC
commented
Sep 15, 2026
| ``` | ||
|
|
||
| This error is an error code from Xcode that can be caused by provisioning issues or outdated cordova dependencies. To fix this error first make sure a provisioning profile has been generated using the above instructions and then try to [run the app from Xcode](../developing/ios.mdx#running-with-xcode). | ||
| This error is an error code from Xcode that can be caused by provisioning issues or outdated cordova dependencies. To fix this error first make sure a provisioning profile has been generated using the above instructions and then try to [run the app from Xcode](../developing/ios.mdx). |
Contributor
Author
There was a problem hiding this comment.
That section only existed in v5 and v6.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue URL: internal
What is the current behavior?
The Japanese site renders 724 broken links. English renders 21, plus 50 broken anchors nobody had noticed. The archived v5, v6 and v7 docs carry the same defects and have never been checked, because they are not built.
Nearly every broken link is one defect: links hardcode the
/docsbaseUrl. Docusaurus prepends the baseUrl of the locale being built, and the Japanese one is/docs/ja/, so the prefix doubles into/docs/ja/docs/theming/basics. English hides it, because a value that already starts with its own baseUrl is passed through untouched.The anchors are unrelated: fragments pointing at headings renamed years ago.
#style-placementand#optimizing-your-buildwere v5 sections, dead through four majors.What is the new behavior?
English is at 0 broken links and 0 broken anchors. Japanese links drop 724 to 152, with nothing left that originates in an English source file. Built with all five versions, the archived trees come out clean apart from five links noted below.
/api/toolbar.mdx. The extension matters: the resolver only fires on.mdand.mdx, and it searches the localized content path first, which makes this the one style that is both locale correct and version correct.hrefattributes take the same path without an extension, since no resolver runs there and the value goes straight toLink.Does this introduce a breaking change?
Other information
60 anchors will still be reported, and all 60 work. Docusaurus collects anchors only from components that call
collectAnchor, so a raw<section id="cli">written straight into MDX is invisible to it. The v5 and v6 glossaries are built that way. These should not be "fixed".5 links stay broken in v5. They come from
@ionic/docs@5, which uses a relative link style dropped after v5, and exist only in a build-time partial, so there is no file to edit. v5 is not built.Japanese broken anchors rise 66 to 148. That is not new breakage: links that used to 404 now land on the correct translated page, whose heading slug is Japanese, so the fragment misses instead.
ja never builds in PR previews, so none of this is visible from the preview link. I verified with a local two-locale build, and again with v5, v6 and v7 temporarily added to
versions.json.Everything still broken lives in
translation/jp. The plan is this PR, then a normal main to jp sync, which carries most of the prose fixes as conflicts to resolve, then a small jp PR for the rest. 103 of the Japanese leftovers are a single missing heading id in the jpfundamentals.mdx, on a heading whose slug is Japanese.