# Debugging the page change API after migration
**URL:** https://meta.discourse.org/t/debugging-the-page-change-api-after-migration/398132
**Category:** Support
**Created:** [March 11, 2026, 6:15am UTC](https://meta.discourse.org/t/debugging-the-page-change-api-after-migration/398132 "2026-03-11T06:15:12Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@mattyoung](https://meta.discourse.org/u/mattyoung)
#### Post date: [March 11, 2026, 12:37am UTC](https://meta.discourse.org/t/debugging-the-page-change-api-after-migration/398132/1 "2026-03-11T00:37:02Z")
please help take this from area in theme admin customization to the js tab in admin interface:
```plaintext
```
I am looking at the example of
```plaintext
export default apiInitializer((api) => {
// Your code here
});
```
and this has worked great for like api.renderInOutlet but this onPageChange does not have updated examples that I could find.
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [March 11, 2026, 2:16am UTC](https://meta.discourse.org/t/debugging-the-page-change-api-after-migration/398132/2 "2026-03-11T02:16:38Z")
What if you just moved this:
```js
api.onPageChange(() => {
if ( window.location.href === "https://apple.com/123" ) {
window.location.replace( "https://dell.com/234" );
}
});
```
into
> [@mattyoung](#):
>
> `// Your code here`
?
---
### Author:  [@mattyoung](https://meta.discourse.org/u/mattyoung)
#### Post date: [March 11, 2026, 3:42am UTC](https://meta.discourse.org/t/debugging-the-page-change-api-after-migration/398132/3 "2026-03-11T03:42:06Z")
ha. you are being sarcastic right? yes i tried that immediately. failed.
here is what worked:
```plaintext
import { apiInitializer } from "discourse/lib/api";
export default apiInitializer("1.0", (api) => {
api.onPageChange((url) => {
// url is typically the path
// but in some contexts it can be a full URL, so we handle both.
const path = url?.startsWith("http") ? new URL(url).pathname : url;
if (path === "/123") {
window.location.replace("https://dell.com/234");
}
});
```
---
### Author:  [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [March 11, 2026, 6:15am UTC](https://meta.discourse.org/t/debugging-the-page-change-api-after-migration/398132/4 "2026-03-11T06:15:12Z")
> [@mattyoung](#):
>
> ha. you are being sarcastic right? yes i tried that immediately. failed.
My apologies. I misunderstood your question.
> [@mattyoung](#):
>
> `but in some contexts it can be a full URL, so we handle both.`
I’m curious - what are these situations? I’ve never seen the `https` in the url before, because IIRC `onPageChange` is for Ember’s paths.
---
### Author:  [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [March 11, 2026, 6:27am UTC](https://meta.discourse.org/t/debugging-the-page-change-api-after-migration/398132/5 "2026-03-11T06:27:48Z")
Hi, just as some housekeeping I moved this from the original release notes thread to a new topic to keep the thread a little more tidy and to improve visibility. Good luck 👍
However I did notice in your later example that you are no longer checking `window.location.href`. Is that the problem?