{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreictyzv2gjtwkezhmq2mwww3b673n356lmjpj45krbc4pwqfglm3hu",
    "uri": "at://did:plc:qfsyszxhq5agxsg2n5zo4lno/app.bsky.feed.post/3mni4t6mivxn2"
  },
  "path": "/t/bug-with-two-commerce-elements-on-one-page/118924?page=2#post_24",
  "publishedAt": "2026-06-04T16:22:44.000Z",
  "site": "https://forum.infinityfree.com",
  "tags": [
    "iFastNet"
  ],
  "textContent": "OK, let me try to untangle this, because a few separate things are getting tangled together.\n\nFirst: the permanent suspension. The timing of the different suspensions and extremely high hit count doesn’t look like legitimate traffic. It has the fingerprint of an attack, which unfortunately is a thing that happens when a brand new URL gets posted somewhere public. The forum does ask for a site link so people can actually reproduce and look into issues, and I know that this can expose a site to attacks, but I haven’t found a good alternative yet that’s easy to use for everyone involved.\n\nThe ticket you submitted goes to iFastNet, who handle the infrastructure side, and the automated read of it was the usual “too many hits, consider upgrading” because that’s what the numbers look like at a glance. That response misses what actually happened here. I’ve also messaged iFastNet with the request to have a look again considering the specific circumstances here. No promises on what they’ll do with this though.\n\nOn the Site.Pro side, since it caused a lot of confusion earlier: paying for Site.Pro buys you extra features, removal of the page limit, and removal of the Site.Pro branding. That’s it. It’s not a hosting upgrade and doesn’t change your hosting at all, so the same CPU and hits limits apply as on any other free account. It’s a bit like buying a paid WordPress theme or a software license: if the free hosting underneath hits a limit, that’s not the theme’s fault and it’s not the hosting being free that’s at fault either, they’re just separate things stacked on top of each other.\n\nOne detail worth knowing: Site.Pro doesn’t tell us who’s upgraded. I can sometimes tell by hand from the branding on a site, but our system has no way to give a paid Site.Pro user preferential treatment, because we simply don’t have that information.\n\nAnd you’re right that locking the site builder during a suspension isn’t ideal. The reasoning is that you can’t publish while the account is down anyway, but I take the point that you might still want to prepare changes or export your work, so that’s something worth revisiting.",
  "title": "Bug with two commerce elements on one page"
}