Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange behavior with multi-site Omeka S instance #14

Open
mcoonen opened this issue Jan 18, 2023 · 1 comment · May be fixed by #15
Open

Strange behavior with multi-site Omeka S instance #14

mcoonen opened this issue Jan 18, 2023 · 1 comment · May be fixed by #15

Comments

@mcoonen
Copy link

mcoonen commented Jan 18, 2023

Hi Daniel,

Imagine an Omeka S instance with multiple sites.

  1. Name: Foo, site_id=1
  2. Name: Bar, site_id=2

In the Global Settings, there is an option for Default Site. Here, I can select 3 possible values:

  • No default (show index of sites)
  • Foo
  • Bar

When the Clean Url module is activated, there is some strange behavior with this site setting. When navigating to the Omeka base URL in my browser (e.g. http://omeka.local/ ) I always end up at the site with site_id=1, regardless of what is chosen in the global setting.
It does not make any difference whether I choose No default, Foo or Bar.

Furthermore, we would like to have this frontpage with the index of sites - example from Omeka docs - working when activating the Clean Url module. This is currently not the case, as one is immediately forwarded to the site with site_id=1.

Would you be able to fix this?
Best regards,
Maarten Coonen

Versions used

Omeka S 3.2.3
Clean Url 3.17.4.4

@mcoonen
Copy link
Author

mcoonen commented Feb 1, 2023

Hi,

I think this issue will be solved with my PR above.

Cheers,
Maarten

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant