Hi @adriandw,
The connection identifiers, such as the blog/site ID used to identify a given site on our systems, are not stored locally on your site. Only our systems are privy to that information. You may be able to find local caches of the connection tokens in your database, but that is also validated against what is on our system.
If you can tell us more about why you need these connection IDs, maybe we can help out better. That said, if you are having trouble connecting Jetpack because the connection tokens are invalid or expired, you should be able to resolve that by reconnecting Jetpack (reinstalling if necessary).
Regards.
Thread Starter
Adrian
(@adriandw)
thanks – that’s helpful.
A follow-up question:
On the wordpress.com Account Settings page, how can I delete a self-hosted site?
It’s currently the primary and only site connected to the account.
Obviously I can delete it by closing the account, but is there another option?
Hi @adriandw
We can disconnect the site on our end so that it won’t show up under your list of sites.
Could you please post the site URL here so that we can have a look?
If you want it to remain private, you can also contact us via this contact form. If you choose to reach out directly, please include a link to this thread.
Thanks!
I had the same question as @adriandw — where do I get the Jetpack site ID? It is extensively used on the code (interestingly, more on JavaScript than on PHP) and it seems that it is ‘required’, to an extent, when importing/exporting WXR files.
I’m writing a WXR exporter for a very specific (and ancient!) CMS, and the more data I know how to export, the less issues I’ll have when importing the file. This is by no means my ‘first’ legacy-to-WordPress exporter (I’ve been doing that for well over a decade, for other CMSes that have been abandoned so long ago that not even archive.org can get their snapshots 🙂 ), but, with each ‘new’ exporter, I try to support even more ‘features’ of the WXR file. How exactly the Site ID was generated was always a mystery to me; one assumed that it was some sort of hash, or checksum, based on who-knows-what fields, which however would persist when switching the site from one installation to a different one (thus the reason why it would be included on the WXR file).
I now understand that this is just irrelevant for my case. A site running under a different CMS will not have any Site ID… because you can only get one if your site runs WordPress and has Jetpack installed & configured 🙂
This was by no means obvious for me, so thanks for your clarification. Clearly nobody (outside Automattic, that is) is supposed to ‘know’ what the Site ID is, and should not worry about its existence. I’ll proceed to ignore that line on the WXR file 🙂
