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


Skip to content

OmekaS

5 Topics 46 Posts
  • OmekaS - Package Updates

    Pinned Locked
    27
    0 Votes
    27 Posts
    10k Views
    Package UpdatesP
    [1.5.1] Update omeka-s to 4.2.1 Full Changelog Block titles for the IIIF page blocks were not properly escaped The IIIF presentation page block did not respect the site's configured IIIF viewer setting for the Mirador theme Some fields were not aligned properly on the admin advanced search Themes could not use the Ckeditor form elements to allow HTML input for theme settings Unnecessary spacing when listing data types in resource template browse Modules using older code for database queries could encounter errors related to core events like those used for processing fulltext search The Asset add form only allowed a fixed list of file types regardless of what types were specified in config The confirm password check did not properly run when the confirm box was left blank
  • Bugs (CSS, CSRF Token) in Omeka S after latest Cloudron update

    3
    2
    1 Votes
    3 Posts
    461 Views
    D
    I looked into the logs and it was the outdated Commons module. Thanks for your help and keep up the great work with cloudron!
  • Omeka S on Cloudron as host for embedded exhibits - CORS

    7
    3 Votes
    7 Posts
    3k Views
    girishG
    @GeHo said in Omeka S on Cloudron as host for embedded exhibits - CORS: Because the HTML itself delievered by Omeka loads scripts, images, css etc. from the domain of origin. This causes the CORS issues. aren't all these covered by same origin policy exceptions ? https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy#cross-origin_network_access
  • page template files - edit or not?

    3
    0 Votes
    3 Posts
    2k Views
    jeauJ
    @timconsidine yes, it looks like the wordpress templates
  • What is the RAM usage for this?

    6
    0 Votes
    6 Posts
    3k Views
    girishG
    @jeau For the PHP apps, we follow the customizable php.ini pattern. Line 26-29 basically. This way people can tweak those values as needed. One important thing to remember when packaging this way is that the app's WORKDIR has to be set to /app/code and not /app/data because apache behaves differently when it is started in a directory which has php.ini in it!