hafizchin
commented
1 year ago Hi @beckej13820,
Thank you for checking out this plugin. This module was initially developed to address Omeka-S' lack of support for multiple domains (Similar to Wordpress Multisite). So the intention was to map sites to a domain and to make url's more clean and friendly, instead of the default omeka-s url https://domain-name/s/site-name
Regarding the future of this module, this is just a proof of concept. Feel free to fork it and make any changes.
Hi everyone,
At SUNY Oneonta, we were testing your Omeka Module to try to map some, but not all of our sites to custom domains.
So for example, we have 3 sites on our network currently, and we would like to map them
Our Landing Page root site: exhibits.library.oneonta.edu Our custom domain: cgpcommunitystories.org A directory site: exhibits.library.oneonta.edu/s/kitchen-table-conversations
Our vision is that we would have some sites use the default Omeka S behavior of directories, and some other sites be mapped to custom domains.
Is that possible to achieve with your plugin?
Current Behavior
Currently, if I try to use a directory in the admin screen, I get an error, and any url with a / is rejected.
If that screen is left blank, then the links in the admin dashboard and autocreated by Omeka are broken in the dashboard, for example a link from the admin dashboard tends to lead to {rootsite.url}///{site slug}
However the site still appears for visitors to the website at the default Omeka S location {rootsite.url}/s/{site slug}
What we hope will happen
So my ideal behavior would just being able to inform your plugin that some sites will be directories, or use the default omeka naming conventions.
Perhaps the configure screen for the domain manager plugin could have 3 columns:
Site / map to custom domain? (checkbox) / custom domain (only available if previous column is checked)