Good morning! Set up the demo site last night and got it running locally. During the process of updating the config file introduced some bad characters (I'm working with French and english texts) and now when I go to run the site locally I'm getting - jekyll 3.8.5 | Error: invalid byte sequence in UTF-8 -
I'm going back to check all the pieces I changed but I think a big problem is my CSV file of metadata. Trying to figure out the best way to clean that but I'm stuck. I tried running this ' value.reinterpret("utf-8") ' in OpenRefine it returned nothing .
Been working on the search tonight and can't get it to work. Just noted that it is also not working on the demo site - https://minicomp.github.io/wax/search/ Wondering if it could be something with /js/lunr-ui.js ?
banner:
collection: bofh
*pid: ms107*
y: 30%
@sarahseverson can you describe the problems you're having on https://minicomp.github.io/wax/search/ ? When I type 'i' or 'iran', matches pop up on my end.
Still haven't gotten https://sarahseverson.github.io/wax-bofh/search/ to work on my site. But will go back in and continue to compare this with your demo code. If you have any suggestion on where to look let me know.
I would try regenerating the index with the UI using
bundle exec rake wax:lunr UI=true
If it's still weird let me know
I'd like to add a few more items. I'm assuming all then I will re-run all three sets of tasks from https://minicomp.github.io/wiki/wax/running-the-tasks/. Correct?
Hi all -- I'm new to Wax and was just following the instructions in https://github.com/minicomp/wax/blob/master/README.md it says to clone the gh-pages branch, and then run
bundle install but that branch no longer seems to have a Gemfile? I see that gh-pages just had some big changes 4 days ago, so maybe things are in flux at the moment?
Hi @edsu, yes, we're getting ready to release a real 1.0 in the next week, so things are in an embarrassing amount of flux with the expectation that they'll be fully stable shortly. The mnyrop and minicomp repos are being consolidated, as are the master and gh-pages branches. If you'd like to keep going now, please feel free to work from the 1.0.0 branch with the expectation that the documentation will be incorrect at times. Otherwise, I'll send you a message when the theme, the tasks, and the docs are fully in sync and released.
If you go the former route, I'd be happy to answer questions as you go; any issues you have will clue us into documentation that needs updating, so it could be mutually beneficial.
I seem to have
wax_tasks (1.0.0.pre.beta) installed. Is this something you've run into before?
@mnyrop here is what the config looks like https://gist.github.com/edsu/992c50f13d477e05aa403a00993c9928
@JoshuaGOB also, if you @ me I'll likely be able to notice / respond sooner, depending on the circumstances.
(for folks who have original metadata messing up the orientation of the image of the viewer)
(feel free to make a private one and add me as a collaborator)
Hey folks! First off, thanks @elotroalex @mnyrop et al for Wax! I'm just wondering if it's possible to embed one specific image of a multi-image object in an exhibit? In other words, with {% include inline_image.html collection='collection' pid='obj1' %} I need image 04 from obj1. Thanks in advance!
Hi @bradleypallen custom sorting is not currently a feature, but I would be happy to point you in the right direction to implement this for your own site. This is where you'd want to make a slight change: https://github.com/minicomp/wax/blob/1adf4f462865d543dc5e1ffb3b83ca288b9a5c73/_includes/collection_gallery.html#L4
And you'd want to use the
sortfilter in liquid to do it: https://www.siteleaf.com/blog/advanced-liquid-sort/
Happy to go into more detail if needed.
@mnyrop that was easy to change to get the behavior I was looking for, thanks so much! The only remaining issue I have is that I am getting errors reported from the Jekyll server when I go to a collection item page of the form: "`/wax/img/derivatives/iiif/images/brion_gysin_dream_machine_1/full/306,/0/default.jpg' not found." Else everything is working as advertised.
@bradleypallen does everything look fine in the UI when you play around? if so, i wouldn't worry about it. the IIIF viewer should be able to dynamically provide a different image size if the one requested isn't available. this is somewhat normal as long as the actual behavior is correct, and is likely just a symptom of jekyll serve being so verbose.