Beta branch - Help with testing

[fccview]

Hi all!
Hope you are having a fantastic time with Jotty.

The app is ever evolving and it always helps having a community testing new features before they go live.
This is why I am making the develop branch the official beta branch.

Changing your docker compose file to use ghcr.io/fccview/jotty:develop will give you early access to unreleased features.

DISCLAIMERS

• The develop branch is not stable
• Backup your data, always, especially if you use the develop branch, I can't guarantee data safety
• Make sure to read the release note in the open develop -> main pull request. There always will be one when new features/bugfixes are happening, so you can keep tracking on what's gonna be in that branch (and if i know something is broken will be also added there).

example pull request: #175

Feel free to share any develop branch you find in this discussion ❤️

[himsin]

@fccview #172 is still not fixed in this. I'm still seeing a flash of default theme.

[fccview]

@fccview #172 is still not fixed in this. I'm still seeing a flash of default theme.

On the develop flag?
can you clean your browser data? I can't replicate it..

[himsin]

Yes on develop tag. I just changed the docker image tag in docker compose file. I'll clear the cookies and browser data and see if it still persist.

[fccview]

Yes on develop tag. I just changed the docker image tag in docker compose file. I'll clear the cookies and browser data and see if it still persist.

Did you do docker compose pull and restart the container?
Do you see 1.10.0 in the login form version?

[himsin]

Yes, app version shows 1.10.0. I can see new custom CSS option in admin dashboard. Tried in both chromium and firefox browsers, same issue.

[himsin]

@fccview Custom CSS also doesn't do anything. I tried your sample CSS as well.

@import "https://fonts.googleapis.com/css?family=Tangerine";

body, p, a, span, label, strong, h1, h2, h3, h4, h5, h6 {
  font-family: 'Tangerine', serif;
  font-size: 48px;
}

[fccview]

Ok managed to replicate the custom css issue, I'll fix it in the latest develop soon!!
Still can't replicate the system theme flashing before custom theme issue tho, do you have console logs at all?

[himsin]

Just below SSL error repeating:

jotty  | yarn run v1.22.22
jotty  | $ next start
jotty  |    ▲ Next.js 14.0.4
jotty  |    - Local:        http://localhost:3000
jotty  | 
jotty  |  ✓ Ready in 426ms
jotty  | Session check error:  [TypeError: fetch failed] {
jotty  |   cause:  [Error: 3862D7BF1C7F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354:
jotty  | ] {
jotty  |   library: 'SSL routines',
jotty  |   reason: 'wrong version number',
jotty  |   code: 'ERR_SSL_WRONG_VERSION_NUMBER'
jotty  | }
jotty  | }

I doubt this is causing the issue. If there's a way to increase verbosity of logs then I can try that too.
Also, does every commit in develop creates the tagged docker image?

[fccview]

@fccview Custom CSS also doesn't do anything. I tried your sample CSS as well.

@import "https://fonts.googleapis.com/css?family=Tangerine";

body, p, a, span, label, strong, h1, h2, h3, h4, h5, h6 {
  font-family: 'Tangerine', serif;
  font-size: 48px;
}

After pulling the latest develop edit your docker-compose.yml file to have ./config:/app/config:rw instead of ./config:/app/config:ro and you should be able to set your custom css that way.

Still trying to understand what's going on with the theme flashing, i can't replicate it.
Your ssl error MAY actually be related, you can set a DEBUGGER=true env variable to get more verbose logs.

But I was asking about logs in your browser console, rather than in the docker container

[himsin]

Custom CSS started working. But flash issue is still there. Console only shows below error on login screen:

login:1 Banner not shown: beforeinstallpromptevent.preventDefault() called. The page must call beforeinstallpromptevent.prompt() to show the banner.

No other console error shows on page reload.