# Discourse is feeding js to archive.org again
**URL:** https://meta.discourse.org/t/discourse-is-feeding-js-to-archive-org-again/101902
**Category:** Bug
**Created:** [November 13, 2018, 4:58am UTC](https://meta.discourse.org/t/discourse-is-feeding-js-to-archive-org-again/101902 "2018-11-13T04:58:00Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Artoria2e5](https://meta.discourse.org/u/Artoria2e5)
#### Post date: [November 13, 2018, 4:58am UTC](https://meta.discourse.org/t/discourse-is-feeding-js-to-archive-org-again/101902/1 "2018-11-13T04:58:00Z")
I archived [https://meta.discourse.org/t/add-category-to-top-menu-so-that-category-can-be-landing-page/101668](https://meta.discourse.org/t/add-category-to-top-menu-so-that-category-can-be-landing-page/101668) into [https://web.archive.org/web/20181113043546/https://meta.discourse.org/t/add-category-to-top-menu-so-that-category-can-be-landing-page/101668](https://web.archive.org/web/20181113043546/https://meta.discourse.org/t/add-category-to-top-menu-so-that-category-can-be-landing-page/101668). The resultant page is blank, but “view source” shows some content loaded. A quick glance at the console reveals tons of js errors. I archive the pages through `open('https://web.archive.org/save/'+document.location)`, which should be the same as the click-to-archive function.
The crawler detection seems to still work with google’s bot. [archive.org](http://archive.org) has not significantly changed its UA according to [Webmaster Tools on Whoishostingthis.com | Whoishostingthis.com](https://www.whoishostingthis.com/tools/user-agent/), so I have no idea what’s wrong this time. (I did try to peek at `access.log` for hints, but for some reason I am only seeing my UA `GET`ting the pages around the archived timestamps on my instance… The robots.txt crawls by archive’s UA are present in the logs though.)
* * *
Discourse also feeds js to archive.is, which should’ve been fine because it does run the js into a final DOM and does not use a special UA, so there’s no detection for it anyway. I am ready to file bugs to them for failing to run the JS though…
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [November 13, 2018, 5:24am UTC](https://meta.discourse.org/t/discourse-is-feeding-js-to-archive-org-again/101902/2 "2018-11-13T05:24:26Z")
I’m pretty sure this has _never_ worked? See existing topic.
> [@Make Discourse play nice with the Wayback Machine](https://meta.discourse.org/t/make-discourse-play-nice-with-the-wayback-machine/34579):
>
> I’ve noticed that when archiving Discourse topics using [archive.org](http://archive.org), the CSS is mangled. Here is an [example](https://web.archive.org/web/20151014020610/https://meta.discourse.org/t/core-dump-when-running-the-mybb-import-script/34332/9):
Closing this as we don’t need a dupe.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [November 13, 2018, 5:24am UTC](https://meta.discourse.org/t/discourse-is-feeding-js-to-archive-org-again/101902/3 "2018-11-13T05:24:29Z")