Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps - Status | Demo | Docs | Install
U

ulka

@ulka
About
Posts
10
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • OAuth configuration disappearing - and my solution
    U ulka

    I'm looking forward to it. Danke!

    FreeScout

  • OAuth configuration disappearing - and my solution
    U ulka

    No, it's almost perfect for me now. The only issue is that Cloudron fails to set a valid configuration if the Cloudron instance name contains unusual characters. If I remove them, all is shiny. (And these characters are quite common in German.)

    FreeScout

  • OAuth configuration disappearing - and my solution
    U ulka

    Yes, it's Cloudron user management.

    What about the idea of passing a HTML-encoded String containing ü? I don't know which mechanism is used. Does Cloudron save this data directly into the database?

    FreeScout

  • OAuth configuration disappearing - and my solution
    U ulka

    Hi,

    for some months I had the problem that every time I restarted FreeScout the OAuth configuration was gone. The setting was using an OpenID-Client configured in the Cloudron user section.

    Now I found out that the app deletes the configuration from the database every time it restarts. It sets up a new configuration which is faulty, the app does not start and displays an error message. I noticed some mysterious characters in the configuration - the Cloudron instance name is used as the OAuth name, and in my instance it contains German characters like ü and Ü in a quite strange coding. The FreeScout OAuth module cannot handle these.

    Maybe I am not the only one who has this problem. It would be a great improvement if the name could be made more robust.

    FreeScout

  • Please update to 6.15.14
    U ulka

    Thanks a lot!

    LimeSurvey

  • Please update to 6.15.14
    U ulka

    The new version's change history confirms that there is a problem:
    https://community.limesurvey.org/release/250924/

    LimeSurvey

  • Please update to 6.15.14
    U ulka

    I found these hints too, but that doesn't help really when survey participants get this error. Unfortunately they do.

    LimeSurvey

  • Please update to 6.15.14
    U ulka

    Is there another way to get to the previous version than using the last backup? That would result in data loss.

    That is the error message right after logging in:
    grafik.png

    LimeSurvey

  • Please update to 6.15.14
    U ulka

    That's what you should do. Meanwhile LimeSurvey cannot be used - so we are desperately waiting for the update.

    LimeSurvey

  • Please update to 6.15.14
    U ulka

    Hi,

    the LimeSurvey version 6.15.13 is buggy - in fact it does not run at all. Version 6.15.14 is available here:
    https://community.limesurvey.org/downloads/

    Thanks
    uk

    LimeSurvey
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search