Hi! I’m hoping to get some help - we’ve recently (last day or two) seen a string similar to this one being printed at the top of our blog, as well as a similar string where the tag links are:
__aSyNcId_<_bZpwo_JT__
I can see this on a few other ghost blogs as well, does anybody know what might be causing it?
Thanks!
Adam
What’s your URL? This is the easiest way for others to debug your issue Blog — ShopPop
What version of Ghost are you using?
2.17.1
What configuration?
What browser?
Chrome/Safari/Firefox
What errors or information do you see in the console?
Uncaught TypeError: Cannot read property ‘replace’ of undefined
What steps could someone else take to reproduce the issue you’re having?
Issue visible on production blog
Hi @Adam_Passingham The __asyncId_ text can appear when async helpers get nested, this is most likely coming from usage of the {{#get}} helper (it’s listed as a limitation in the docs).
Are you able to pinpoint where in your templates the __asyncId__ is appearing? If you can it would be useful if you can share the template code so we can debug further.
Replying to Kevin - the async ID is showing in three places on our blog at the moment: above and below the header/footer, as well as within the c-footer-widget__body class in the footer where we are performing a {{#get}} for all tags. I’ve searched our codebase for instances of nested {{#get}} calls but I can’t see any obvious culprits. Below is a copy of our footer.hbs for reference:
I’m not seeing the issue at all on local, appears only in production.
It’s disappeared from our blog now, but is still visible on the sites that I posted in reply to Hannah. It has disappeared and reappeared once already today, so I will keep an eye out and let you know if it returns!
Oooooooops - we were convinced you were self-hosting by your original statement and have been chasing a bug in 2.17.1 or earlier.
I just double-checked - your production site is on Ghost(Pro) and running 2.19.2. We have a fix for this bug, which appears only in 2.19.2 and are already in the process of rolling the fix to Ghost(Pro) sites, so you should see the issue disappear shortly.
If you ever have any other issues with your Ghost(Pro) blog, please contact support@ghost.org We’ll be able to help much more quickly that way!