I've successfully installed Neatline and have imported Omeka items, but they are not coming up in the editor and I'm also missing the "New Record" button.
I saw this mentioned on a previous post, which went off tangent a bit, but wanted to bring it up again, as their solutions didn't work for me.
I'm running Omeka 2.1.4 with Neatline 2.2.1
I had the CSV plugin installed, but uninstalled it to make sure there were no conflicts. That didn't fix it.
I also tried uninstalling Neatline, deleting it from the server and then unzipping and installing a fresh copy.
This sounds like a configuration problem on the server that's breaking the records API. First, what version of PHP are you running? I know there's a bug in old versions of the PHP MySQL extension that can produce a warning related to the geometry columns that Neatline uses in the database - and if the server isn't suppressing warnings in production, the error output breaks the JSON API.
Second, let's try to get the actual error output from the server. Do this:
1) Open up the Neatline editor in Chrome (the page where the "New Record" button is missing).
2) Open up the developer tools by clicking on the little icon with three horizontal bars at the top right, then clicking Tools > Developer Tools.
3) Click the "Network" tab, and refresh the page. You should see a whole bunch of requests listed - click on the little "filter" icon at the top and search for "records." You should get 2-3 results, and one or more of them will be listed in red, meaning that they failed. Click on one of the red results, and then click on the "Response" tab in the sub-form that comes up. Can you paste in the content of that tab?
I'm running PHP 5.2 (FastCGI)
<b>Warning</b>: mysqli_stmt::bind_result() [mysqli-stmt.bind-result]: Server returned unknown type 255. Probably your client library is incompatible with the server version you use! in <b>/home3/libserv1/public_html/omeka/application/libraries/Zend/Db/Statement/Mysqli.php</b> on line <b>255</b>
It was the PHP version...updated to 5.4 and all is well.
Great. I'll try again to figure out how to fix the problem with 5.2, since I know other people have had trouble with that in the past. Let me know if anything else comes up!