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

2.7 testing/documentation #887

Closed
zerocrates opened this issue May 13, 2019 · 1 comment
Closed

2.7 testing/documentation #887

zerocrates opened this issue May 13, 2019 · 1 comment
Assignees

Comments

@zerocrates
Copy link
Member

  • Plugin and theme update notifications (on their respective admin pages)
    • you can manually set back version numbers if needed
    • config.ini setting versionNotifications set to false should disable the notifications
  • Tag browse for items should sort alphabetical by default (this is the browse accessible from public item browse pages, not the Tags browse in the admin)
  • New config.ini settings mail.force_from and mail.force_from_name: make all outgoing mail originate from the given address (and optionally the given "friendly" name), useful for situations where your server can only send mail from a particular address or domain (required by some cloud hosts, and often necessary to have mail actually successfully delivered)
  • New config.ini setting sslTrustProxy: if the ssl setting is enabled, whether to trust the contents of the "X-Forwarded-Proto" HTTP header (useful if you want to use the ssl setting but are hosting Omeka behind a proxy server)
@mebrett
Copy link

mebrett commented May 13, 2019

Update notifications only display on a theme when it's active; themes not in use as the primary theme have no indication of status.

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

No branches or pull requests

2 participants