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 | Demo | Docs | Install
  1. Cloudron Forum
  2. OmekaS
  3. Bugs (CSS, CSRF Token) in Omeka S after latest Cloudron update

Bugs (CSS, CSRF Token) in Omeka S after latest Cloudron update

Scheduled Pinned Locked Moved OmekaS
3 Posts 2 Posters 22 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    difficult222
    wrote last edited by
    #1

    Hey,

    after the latest update to 1.4.0 the functiontality to add a new item/object in Omeka S is not working anymore:

    URL.com/admin/item/add
    

    see screenshot for adding a new object:

    Screenshot:
    c908769f-5239-44fa-ba54-eff7b093ecac-grafik.png

    At least CSS is not found, also a lot of functionality on that page seems gone.

    This seems to be the only page accessible in the backend where this behaviour arises.

    Also, a user reports that they can't login in Safari anymore, because of missing or wrong CSRF Token:

    e35a9c3a-e161-462a-9727-d15138ee3cf2-grafik.png

    Could you check that?

    Thanks!

    1 Reply Last reply
    1
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote last edited by
      #2

      I tried to reproduce the issue of adding items in a new instance of omeka, but that seems to work fine.

      Given that the stylesheet seems to be missing in your case, can you try if hard refreshing the page in the browser fixes the issue? Maybe this is a caching problem.

      Otherwise do you see any errors in the app logs on the server side? It could also be, that the app is crashing and thus not serving up the css right after the crash while it is restarting.

      For the CSRF issue in safari, unfortunately I do not have access to a safari browser to test this. Chrome and firefox seem to work fine. here.

      1 Reply Last reply
      1
      • D Offline
        D Offline
        difficult222
        wrote last edited by
        #3

        I looked into the logs and it was the outdated Commons module. Thanks for your help and keep up the great work with cloudron!

        1 Reply Last reply
        1
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

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