All of a sudden I am unable to link an Omeka item to a Neatline record. When I select the item I see the dublin core data, and then I hit save at the bottom. I get the message: "There was an error - the record was not saved". The record I'm linking worked previously so this is odd. Also I noticed I am able to link older Omeka records, but not any that were created recently. Thanks for any help you can provide! Amy
Hi aherman,
What browser and platform are you on? The web console or developer tools might show you an error message. Or we might have to look on the server.
Also, did anything change on your server or in your set-up?
Hi erochest,
I am using Mac OSX 10.7.5 and Firefox, but have tested the issue on other browsers and had the same result. I did notice today that for any new record I create, when I plot a point on the map BEFORE linking to an Omeka item, the record will save correctly. I don't remember having to do it that way before though. I contacted our IT dept to see if anything had changed on the server and here is their response:
"Nothing was changed on the back-end. I checked the error log for the web service however, and find these errors repeated several times:
PHP Fatal error: Call to a member function getText() on a non-object in /www/omeka-2.2.2/plugins/NeatlineFeatures/lib /NeatlineFeatures/Utils/View.php on line 525, referer: http://omeka.bard.edu/admin/neatline/editor/16
PHP Notice: Trying to get property of non-object in /www/omeka-2.2.2/plugins/NeatlineFeatures/lib /NeatlineFeatures/Utils/View.php on line 167, referer: http://omeka.bard.edu/admin/neatline/editor/16
PHP Notice: Trying to get property of non-object in /www/omeka-2.2.2/plugins/NeatlineFeatures/lib /NeatlineFeatures/Utils/View.php on line 416, referer: http://omeka.bard.edu/admin/neatline/editor/16
PHP Notice: Trying to get property of non-object in /www/omeka-2.2.2/plugins/NeatlineFeatures/models/Table/Table _NeatlineFeature.php on line 187, referer: http://omeka.bard.edu/admin/neatline/editor/16
I also note that here are no files in the web content area of the server that have been modified in the last five days to account for this issue."
Try disabling NeatlineFeatures plugin and saving the item again. This looks like an issue we've seen coming from NeatlineFeatures (https://github.com/scholarslab/NeatlineFeatures/issues/81).
Wayne
Perfect! That fixed it. My Neatline Features plugin is version 2.0.1 - would upgrading to 2.5 fix this bug and allow me to keep it activated?
Unfortunately we've not quite tracked down what's going on with this, but I'll update that ticked with this information which will help us figure out what's going on.
I'm getting a similar error message when attempting to link an Omeka item to a Neatline record. I don't have the Neatline Features plugin installed, so I can't uninstall it. We have Neatline 2.3.0. Any suggestions?
Could you tell me what operating system and browser you're using? We'll need to get more information, and once I have that, I can tell you how to get the extra information that might help us.
I'm on Mac OS 10.10.1, using Chrome version 40.0.2214.115 (64-bit)
Great. Could you open the JavaScript console (under the menu View > Developer > JavaScript Console).
Once, that's open, try to link an Omeka record again. There will probably be an error message in the console.
Could you let us know what that is?
Thanks
The main error is:
PUT http://geosciencecollections.milne-library.org/neatline/records/17 net::ERR_TIMED_OUT
Here is a screen shot of the error console with additional details. (The first two erros are minor broken links in the descriptive text of the entry, which was can successfully change and save)
https://www.dropbox.com/s/c1wd802ljn52pmx/Omeka%20Javascript%20Error%20console.png?dl=0
swoger, there's a cross domain issue between geosciencecollections.milne-library.org and www.geosciencecollections.milne-library.org. Try putting 'www' at the beginning of your URL when you're logged in (or taking it off as the case may be).
We tried correcting for the cross domain issue but still got the same error message.
