Sorry, it was my mistake. I haven't worked with static files served with their modTimes in a while...
A refresh in Chrome fixed it. The camliContent is shown in publisher with the CL, and also the UI works fine now. Attila On 19.01.2017 18:01:02, Mathieu Lonjaret <[email protected]> wrote: On 19 January 2017 at 17:32, Attila Tajti <[email protected] [mailto:[email protected]]> wrote: This doesn't seem to work for me, but I'm not sure it is related to your publisher change, so I'm responding here. Ubuntu 16.04.1 LTS Camlistore: 2017-01-18-eba4897 Go: linux/amd64 go1.7.4, cgo=true djpeg: djpeg available When I add a permanode of a jpeg image to my publisher root as camlipath:face then publisher shows only the title of the image (IMG_20150410_141410.jpg, which is correct), the image is missing. Apart from this attr, I've the followin attrs: title = "My pictures" camliRoot = mypics camliMember = sha-xxx (multiple members from my first attempt setting up publisher) camliPath:szk = sha-yyy (permanode set, works in publisher) camliPath:face = sha1-300831992389538979400db5cc8e587bc6316ff8 (permanode with camlicontent, only title is shown) I get the following in javascript console: Navigated to http://linda:3179/pics/face [http://linda:3179/pics/face] publisher.js:97 Your current jQuery version is: 2.2.3 publisher.js:21 error creating file container: full blobref for prefix sha1-pics not found the fact that you're getting this message means the check if !strings.Contains(basePath, "/-") { didn't work, and face didn't get detected as a "top node" Can you add a println(basePath) right after isTopNode := false and report what it says please? What is strange I can't access the permanode on the UI from http://linda:3179/ui/sha1-300831992389538979400db5cc8e587bc6316ff8 [http://linda:3179/ui/sha1-300831992389538979400db5cc8e587bc6316ff8] either, the XHR http://linda:3179/my-search/camli/search/query [http://linda:3179/my-search/camli/search/query] responds with { "error": "can only sort by ctime when all results are permanodes", "errorType": "Internal Server Error" } But that blob seems to be a permanode: ata@linda:~/src/camlistore.org [http://camlistore.org]$ camget sha1-300831992389538979400db5cc8e587bc6316ff8 {"camliVersion": 1, "camliSigner": "sha1-5c788ddba4fa84a820119282054100e5ae51c928", "camliType": "permanode", "key": "sha1-a2b5a6c48b1ae1ac2166154222e3b6abf9cb9e27" ,"camliSig":"wsBcBAABCAAQBQIAAAAACRA9fFgva8QEPQAAyA8IAKwzhD7hdfhIhCm2Z4igiHWOfpPXcLSM7eotuWAL9m8+GEEq8yOTZotu8MNheIvQQ407eZ9BcFoac8gNHG3mVQcvAQWhn1k1DmNDvRhU7XFB3n03Mo93VaA3hxBr84Ubvv6zu6KHH2m6PrhAxSvX1UPlJuK84q4XJV1FQ6HDkiR6+33tgQxaFCecUufe3dTP2oJEHVQf80noq/MqIcWK238B6D8ooNyT2lbVYZckmZ94eCQilXnRWNVD3szeR9QxeC+hoWOlQjcshmfDHUPwK8PYTO3yoys7cOsloufs0CtxGdYCsnwl/ETSs8eR1nwRAbZ+ItMAmhFGZZb+/U84gbY==o0Bt"} The camliContent of sha1-300831992389538979400db5cc8e587bc6316ff8 is sha1-1abe01663003b2b7beabdf34e7f2babd796eaa16: ata@linda:~/src/camlistore.org [http://camlistore.org]$ camget sha1-1abe01663003b2b7beabdf34e7f2babd796eaa16 {"camliVersion": 1, "camliType": "file", "fileName": "IMG_20150410_141410.jpg", "parts": [ { "blobRef": "sha1-f69e3908f5d520640e5b777801e4bd96c2f2e7bd", "size": 262144 }, { "blobRef": "sha1-d537820ce88a0d3dd6af83dd7af1424643117f53", "size": 23186 } ], "unixMtime": "2015-04-22T08:31:38Z", "unixPermission": "0666" However http://linda:3179/ui/sha1-300831992389538979400db5cc8e587bc6316ff8?q=%20 [http://linda:3179/ui/sha1-300831992389538979400db5cc8e587bc6316ff8?q=%20] (note query parameter) seems to work. This means also pressing enter in a permanode view breaks the view, because it removes the query parameter. This happens with all permanodes I've checked. Attila On 19.01.2017 16:54:01, Mathieu Lonjaret <[email protected] [mailto:[email protected]]> wrote: Since I have no experience with publisher, my question if one should publish image permanodes or sets with children? I've checked the CL and the issue, and the issue mentions how one should be able to access "subdirectories" under /pics/. Should the URL ("foo" and "bar" in the example in the issue) be set through camliPath, camliMember/title? The camliRoot itself only supports camilPath, so foo and bar are camliPath attributes set on the camliRoot, such as: camilPath:foo = sha1-foo camliPath:bar = sha1-bar sha1-foo (and sha1-bar) should be either a permanode with some camliContent, or a permanode with some camliMembers. But I notice that a permanode with camliContent (directly at the root) seems to be broken. I'll look into it. PTAL: https://camlistore-review.googlesource.com/9186 [https://camlistore-review.googlesource.com/9186] -- You received this message because you are subscribed to a topic in the Google Groups "Camlistore" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/camlistore/vIM2dAFsyTo/unsubscribe [https://groups.google.com/d/topic/camlistore/vIM2dAFsyTo/unsubscribe]. To unsubscribe from this group and all its topics, send an email to [email protected] [mailto:[email protected]]. For more options, visit https://groups.google.com/d/optout [https://groups.google.com/d/optout]. -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] [mailto:[email protected]]. For more options, visit https://groups.google.com/d/optout [https://groups.google.com/d/optout]. -- You received this message because you are subscribed to a topic in the Google Groups "Camlistore" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/camlistore/vIM2dAFsyTo/unsubscribe [https://groups.google.com/d/topic/camlistore/vIM2dAFsyTo/unsubscribe]. To unsubscribe from this group and all its topics, send an email to [email protected] [mailto:[email protected]]. For more options, visit https://groups.google.com/d/optout [https://groups.google.com/d/optout]. -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
