Unclickable links on the new site

[Detroit70]

Unclickable links on the new site

[kumy]

I'm really sorry for that. Some data seems to have been lost during the transition GK description transition to markdown 😵

[kumy]

What could be done:

• create a new db migration to create a new column in the GK table
• import raw description from last GKv1 backup (Only me can do this step)
• implement a button to "revert to GKv1 raw content"
• Let user fix the formatting

Contributions are welcome!

[Detroit70]

From what you suggested, I would like to ask you to implement the following function on the new site, so that anyone can make edits on the new version in independent mode, transferring links from the old version, that is
implement a button to "revert to GKv1 raw content"

How can this be done and can we be helpful in carrying out this task?

[kumy]

So, I pushed 2 commits f6872f3 dc4407e

That will add a new button in from tof the "Mission" label

On click it open a modal with the raw old content

It is testable on https://new-theme.staging.geokrety.org

I will push to prod once the workflow finish (and I should not forget to import the data).
It will be available in v2.41.0

[kumy]

Done on prod.

How can this be done and can we be helpful in carrying out this task?

There are new strings to translate on crowdin, you may help here https://crowdin.geokrety.org/ 🤷

[kumy]

How can this be done and can we be helpful in carrying out this task?

Create a wiki page explaining how to accomplish "this" based on the commits linked in this issue

• f6872f3
• dc4407e
• 0987673
• geokrety/geokrety-ansible#100
• geokrety/geokrety-ansible#101
• #910
• #913
• geokrety/geokrety-ansible#103

[kumy]

I forgot to create the related Integration tests

[kumy]

tests added in ab3c0fa