@andileco No it's not from a contributed module. Just using Charts with Highcharts to display a graph on a term page.
https://ibb.co/nMZZfKk
https://ibb.co/3RHyQM1
https://ibb.co/C7ZZf3W
I wonder if there is a way to combine them, and display something like this (the graph field from all terms combined):
@maxilein the problem is that the data is coming from a field that's already a Graph Field. I can't select this field as a data field. It renders as a graph, but is actually an array of values. Unfortunately, I don't have clue how to rewrite this and combine all graph fields in one.
Correct, didn't spot that one. Fixed it myself by removing the html tags for now, will follow that topic.
Thank you!
It looks like the problem is in the commentary in the file toolbar.module. The two strings '' on line 65 en 66 are being rendered incorrectly, for some reason.
I also have this problem. Turning off the messages is not really a help, as the translation does not come through anyway.
Same here!
Alright, I finally found the way to do this!
First of all, I used only one importer. The body field and term field of the node was imported twice, like you said, with the Dutch hierarchical path as the source. I did use the Feeds Tamper Term Hierarchy plugin, so I set the the reference to Term ID.
The result here was a bit unexpected; all Dutch nodes had the correct hierarchical term path, but their translations seemed to have skipped the root term. Strange! Luckily I found an option that let me 'Update Taxonomy Terms Parents'* at the content overview. After running this on all the French nodes, everything works like a charm!
I totally forget where I found this plugin, it's not a seperate module, nor is it a patch. I'll update this post when I find it. Perhaps it comes with the CSHS module → ?
Hi Chris,
Thanks for your quick response! I will try the above and get back to you as soon as possible.
What I've just discovered: if I uncheck the option that users can translate the term field (when editing the node fields), then everything works as intended. It has a few other consequences on other stuff (especially with EVA), but the nodes are linked successfully, with translated terms!
This is very confusing.
Works like a charm. Many thanks!
Thanks! I've added the file to Plugin/ Field / Fieldformatter directory and renamed it to .php.
But no extra formatter is appearing (caches were cleared).
Should I do anything else besides this?
Getting this error as well after updating with this patch 🐛 Taxonomy tree is not showing Fixed in Drupal 10.
Apart from overriding the formatter, you may change the prprocess function in office_hours_theme.inc file.
Sadly, that's beyond my knowledge :)
The problem is, as far as I can see, is that the 'Exception Day Widget' is only available at the node Form Display tab. My idea was to set it up in views (one field formatted as the regular office hours, one field only exception days), but you can't format it that way, it seems.
Rendering the entity twice directly in Twig, but with different display modes, doesn't work as well. Like so:
{{ drupal_entity('node', 68, 'office_hours') }}
{{ drupal_entity('node', 68, 'exception_days') }}As soon as you hide the days, the exception days dissapear as well.
Oh sorry, I forgot to mention I was trying to do this with views. Is it possible as well? Don't see any formatting options there.
Reopening because I still have this problem. Is it possible the autocomplete is not working because it has problems with the domain it's on?
I'm developing a site on the address website.synology.me:8888/website.be/www/nl/. The input element has this attribute:
data-autocomplete-path="/website.be/www/nl/search_api_autocomplete/zoeken?display=block_search_products&&filter=search"
The url "http://website.synology.me:8888/website.be/www/nl/search_api_autocomplet..." works fine, but maybe the relative path resolves to "http://website.synology.me/website.be/www/nl/search_api_autocomplete/zoe...", which isn't working. Or doesn't that make any sense?
The thing is: the autocomplete does work in the views preview, but not on the actual page.