Force update pkgdown site after changing GoatCounter's site code

Publishing Your Results
1

I'm using Goat Counter for web analytics of my pkgdown sites.

I recently updated my GoatCounter's site codes to make them more consistent across my different pkgdown sites. One site properly updated the code but not the other one which is still using the old code.

Here's the _pkgdown.yml file.

  includes:
    after_body: >
      <script data-goatcounter="https://gh-plume.goatcounter.com/count"
        async src="//gc.zgo.at/count.js"></script>

And here's a screenshot of the web inspector for that particular pkgdown site:

Capture d’écran 2024-10-11 à 15.13.17
Capture d’écran 2024-10-11 à 15.13.171148×170 37.2 KB

As you can see, the pkgdown site is using arangacas not gh-plume.

Is there a way to force the change without releasing a new version of my package? Surprisingly, that worked with the other site without doing anything special.

1 Like
3

The old site code is in the actual HTML, so I don't see how clearing the cache would fix my issue. I'm using GitHub actions provided by the usethis package. There's a sort of deployment protection to ensure the pkgdown site remains up to date with the actual CRAN release. There's certainly a way to bypass it but not sure how I could implement the new GoatCounter code only.

1 Like
4

What exactly is this protection ?

There's certainly a way to bypass it but not sure how I could implement the new GoatCounter code only.

You could do manual replacement in your built website. That would be the way to really be sure only this content is changed. However, not ideal at all.

You could also do a manual deployment of your website from local environment. You would git checkout to release state of your package, do the change in the config file, render and deploy your website.

Hope this gives you idea. Usually for such need and more complex project and website, there is some branches to both maintain a release and pre-release version of the website. But I think you could without it.

5

What I mean is that the pkgdown site doesn't update every time I commit something to keep the website up to date with the released version of the package. I guess this is the line controlling it:

Yes, this is probably the solution. However, deploying the website manually now will also update the package version with the development version, right?

I do have a branch for the pkgdown site with many deployments. I assume this is for the pre-released version.

Maybe it's simpler to wait for the next version of the package. I made a new goatcounter site with the old code to keep track of the traffic in the meantime…