I did an update to 2.4.0beta10 (I think from beta8). Some of the topics from one of my categories are no longer visible. However, they appear in the main front-page topic link. For example: [Screenshot 2020-02-09 at 17.40.05] If I click on the topic Bela Lugosi drum beat (Bauhaus) , you see this; …

This has nothing to do with the database, it is just your clipboard theme component causing a CSP violation. Try to disable that theme-component.

Argh, that’s pretty terrifying. I’m very concerned of making things a lot worse if I start poking around. I don’t know the schema at all and don’t even know how to get into the database console. I’m also doubly worried that I can’t even roll back to a backup if I totally mess things up :frowning:

@Falco - amazing, thanks. I definitely would never have figured that out myself. Strange that it only started up recently, but I guess that’s the nature of a moving platform…

That solves the immediate problem of a topic not rendering. That done, what @sam said still applies. The log you shared earlier shows an underlying problem with your database. You may want to debug that, or hire someone to, sooner rather than later, because having broken backups is a very bad thin…

Yes, good point - but lol @ the idea of hiring someone. Sonic Pi is an open source project and I’m struggling to find enough money to support me - never mind paying someone to do anything specific like this. I’ll see if I can figure it out myself. However, if I mess things up - I guess there’s no w…

Also, how might I test whether things are fixed without attempting to actually roll back to a backup. Is there a way of doing a dummy roll-back?

You could download the backup locally and try to restore it using pg_dump. As it appears to be a duplicated entry, maybe you can try to detect the error by issuing a select (maybe even using data-explorer ) over the duplicated columns.

I love sonic pi and the mission of sonic pi it is one cool project. We could host you under our free plan, is the only sticking point here that you want to keep your domain? We can waive that. If you move to our hosting we would sort out the backup as part of the migration to our servers.

Crikey - that would be remarkably kind of you. To be honest, I hadn’t even realised that you offered a free plan. Was that there from the start? By now, the domain is pretty tied in with the identity so it would be wonderful if you could allow me to continue using it after migration. What do I nee…

Hey Sam, Our free plans have been around for a while: [이미지] Free Hosting for Open Source v2 Nearly two years ago we started very carefully experimenting with free hosting of open source projects. Today we’re announcing the next iteration of our free hosting program, casting a much wide…

2.4.0beta10로 업데이트 후 특정 카테고리의 일부 주제를 볼 수 없습니다

지원

sam (Sam Saffron) 2월 10, 2020, 12:20오전 2

This looks like an index corruption to me, I am guessing you somehow have duplicate data in that table.

Maybe start by deleting the duplicate row, not sure how it happened.

We have seen a similar corrupt index here:

글		댓글	조회수
Can't restore due to corrupt indexes (with some clues on how to deal with corrupt indexes) Self-hosting	12	4893	1월 6, 2020
Restore problem: relation "theme_fields" does not exist Self-hosting	10	2922	6월 5, 2020
Get Error Oops The software powering this discussion forum encountered an unexpected problem after upgrade Self-hosting	18	724	8월 4, 2024
Unable to restore backup data, unique index is duplicated Self-hosting backups	3	923	4월 12, 2020
Restore fails: could not create unique index Self-hosting	10	1326	2월 13, 2022

2.4.0beta10로 업데이트 후 특정 카테고리의 일부 주제를 볼 수 없습니다

Related topics