-
Notifications
You must be signed in to change notification settings - Fork 34
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
Blank Timeline #454
Comments
@ERB13 What version of Neatline and Neatline-simile widget are you using? versions of Omeka? Looks like the simile-widgets script is getting requested over |
@jeremyboggs Hi Jeremy, It's Neatline 2.3 and I'm not sure about the simile widget. Where would I find that? I didn't install Neatline myself so I'm a tad new to where Omeka stores information like that. Thanks! |
@ERB13 No worries! If your Omeka user is a superuser, you should be able to log in to the administrative panel, click the 'Plugins' link in teh top menu, and see the version numbers for any plugins you have in your Omeka instance. I definitely recommend upgrading plugins, and use the latest releases of Neatline and related widgets. See if that helps. |
Hi Jeremy,
This the information I got from our installer :
Neatline-Widget-SIMILE-Timeline-2.0.4
Neatline-2.6.1
At the time of installation I believe it was the most up to date version.
Does this help?
…On Wed, Apr 25, 2018, 8:17 AM Jeremy Boggs ***@***.***> wrote:
@ERB13 <https://github.com/ERB13> What version of Neatline and
Neatline-simile widget are you using? versions of Omeka? Looks like the
simile-widgets script is getting requested over http and not https. Might
be a bug on our end.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#454 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AkwbV0lHxnG5S8zzWxDCHjNYGmlReunuks5tsHdMgaJpZM4Tcgbf>
.
|
Howdy,
I'm having this issue and I'm honestly not a programmer by any means. The timelines created are completely blank. It's a test site, s I'm not really sure if that's what's causing the issue or not, but it doesn't seem like it is.
The text was updated successfully, but these errors were encountered: