I noticed a strange behavior in the Shopify admin under Content > Blog posts.
When opening any blog post page and selecting an app through the More actions menu, the id parameter in the URL is correct.
However, after refreshing the page and navigating to another blog post, the More actions menu for all apps still uses the previous blog post’s id, not the current one.
It seems like the id value is being cached/memoized and not updated properly.
Steps to reproduce:
- Go to Content > Blog posts.
- Open any blog post.
- Use the More actions menu to open any app → observe that the
id in the URL is correct.
- Refresh the page.
- Navigate to a different blog post.
- Use the More actions menu again → the
id in the URL still points to the previous post.
Expected behavior:
The id in the More actions menu should always reflect the currently opened blog post.
Actual behavior:
The id in the More actions menu remains the same as the first blog post visited and does not update after navigation.
Additional context:
I’m attaching a video to this post as an example.
Hey @256_agent, I tried to replicate this on my end, but the more actions links are all passing to the correct post.
Have you done any local troubleshooting with this:
- Test incognito window
- Clear cache and cookies
- try in a different browser/machine.
Hey @256_agent, Are you still experiencing this issue, or can I mark this as solved?
Hey @KyleG-Shopify, thanks for checking in.
I’ve done some additional troubleshooting on my side:
- Windows + Chrome → this was my initial testing when I wrote the original post, issue was reproducible there.
- MacBook + Chrome → issue is reproducible (even after clearing cache/cookies).
- Linux + Chrome → issue is reproducible (also in incognito mode).
- Firefox → couldn’t reproduce the issue, seems to be Chrome-specific.
I also asked a colleague to test it on a different machine and a different network — he experienced the exact same behavior: works fine in Firefox, but the problem is still there in Chrome.
So it looks like the problem is Chrome-related rather than tied to a specific machine or setup.
Also, I should clarify: it’s not just happening to me — a few of our clients have also reached out to our support reporting the same behavior.
Let me know what other data I can share that might help reproduce this on your side.
Thanks for sharing that and for the detailed testing. Today I was able to replicate. I was missing that refresh step.
Have you noticed this in any other sections, or is it specific to blog posts?
I’ve passed this in to our team so we can look in to it. 
Thanks a lot @KyleG-Shopify for taking the time to look into this more closely — really appreciate it!
So far we’ve only been able to reproduce the issue with blog posts and pages. It doesn’t seem to affect other resources — looks like it’s specific to entities tied to the online store.
Hey @256_agent, I want to close the loop on this thread here. Our team has created an issue to investigate further why this is happening. I’ll keep an eye on it and update here when I can. I don’t have a timeline at this point though.
Thanks @KyleG-Shopify — we’ll be looking forward to the resolution. Really appreciate your efforts on digging into this 