[image]Main CSS and mobile style not working after update "2.9.0.beta10" The temporary fix is to revert to Beta9 How I can revert? Thanks

[image] hiccup: How I can revert? Normally it is not recommended in my opinion, but the steps would be the following: In your app.yml, in the version tag (Uncomment the line), replace test-passed with “v2.9.0.beta9” (Corresponds to the tag on GitHub), and rebuild Although you will have to switch back to test-passed sooner or later samples/standalone.yml main db_default_text_search_config: "pg_catalog.english" ## Set db_shared_buffers to a max of 25% of the total memory. ## will be set automatically by bootstrap based on detected RAM, or you can override #db_shared_buffers: "256MB" ## can improve sorting performance, but adds memory usage per-connection #db_work_mem: "40MB" ## Which Git revision should this container use? (default: latest) #version: latest env: LC_ALL: en_US.UTF-8 LANG: en_US.UTF-8 LANGUAGE: en_US.UTF-8 # DISCOURSE_DEFAULT_LOCALE: en ## How many concurrent web requests are supported? Depends on memory and CPU cores. ## will be set automatically by bootstrap based on detected CPUs, or you can override #UNICORN_WORKERS: 3

Can I use the same steps to downgrade to the “Stable” version?

Theoretically, yes, but certainly that change could lead to a broken site.

I appreciate your help, i tried but it didn’t work I think I have to wait for an update to solve the BUG Unfortunately the site without css is so bad user experience

There’s nothing theoretical here. Migrations aren’t reversible. Downgrades without a backup are never an option.

i have old backup. So can i downgrades by edit app.yml version to “Stable v2.8.9 ”. and rebuild app ? is this possible ?

To avoid any database issues you will need to pinpoint the exact version in the backup and build a fresh instance on that, then restore your database. The issue here is that you upgraded a production site without testing it first, if your site is important then you need to reduce the risk of these updates by first testing it on a representative staging copy.

My old backup for “Discourse 2.8.9” How to build a fresh instance for 2.8.9?

Were you previously on tests-passed or beta? If you were on tests-passed then you need to do as I said above and check your backup for the precise version it was taken at.

backup for discourse 2.8.9 - previously on tests-passed . can you tell me the steps to build a fresh instance for this backup. How can install fresh discourse 2.8.9 so i can import my backup latter without risk? Thanks.

Reverting version after problematic update

Product Support Self-hosting

Stephen (Stephen) October 2, 2022, 6:19pm 14

Right, but it’s from test-passed, not b9 or stable.

It’s an update which broke compatibility, hence aiming for a known-good configuration.

Topic		Replies	Views
Could someone please let me know the version of Discourse as of May 11, 2023? Self-hosting	12	415	April 30, 2024
Can't downgrade from beta to stable Product Support	7	1643	November 13, 2017
How to install v1.9.0.beta1 version of discourse Self-hosting	6	1054	June 25, 2019
Problems with 2.9.0beta2 and roll back Product Support	8	887	February 24, 2022
Automatic update to beta version: questions Self-hosting	1	568	March 16, 2023

Reverting version after problematic update

Related topics