Closed (fixed)
Project:
Glossify
Version:
6.x-3.0-beta1
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Sep 2010 at 23:02 UTC
Updated:
16 Sep 2010 at 15:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
Ivo.Radulovski commentedPlease be a bit more specific about your issue, what is getting referenced and which check-box do you mean?
Thanks for your interest/feedback
Comment #2
Macronomicus commentedWell ive fixed it in my dev copy patch attached. My first patch ever so please be kind! lol
Anyways here are the details of what was happening.
1. The checkbox to turn on/off 'reference' style was being ignored, So it was still displaying [Terms referenced] at bottom of posts. I've not fixed this but did fix the output to be more appropriate, just a list of links rather than printing the whole body of each reference.
2. The hovertips were in my case gigantic and stretched way beyond what was good so I used $term->teaser instead of $term->body plus added a read more link.
Nothing magical but at least its usable for me now. Just need to get onto some css & more hopefully.
Thanks for the awesome module this new 3.x branch is fantastic. Im building a school site that uses a lot of high level language & this is exactly what we were looking for to handle the glossary.
Im also guessing we could do some related posts output too, currently my Global is set so that many content_types are injected with references from one Glossary content type; however I think I could also (in a 2nd configuration) allow the other content_types to be referenced by each other right? Or are there better modules for doing such things?
Cheers!
Comment #3
Macronomicus commentednot sure if that itty bitty patch warrants review but well its protocol and all lol.
Comment #4
Macronomicus commentedoops disregard the Trim Body Text for hovertip function glossify_trim_text is not actually in use as I went with the teaser instead which seemed simpler.
Comment #5
Ivo.Radulovski commentedThanks for your effort, the output is still very barebones, i only just overtook this project recently and rewrote pretty much everything 2 weeks ago, while implementing the old output methods i was thinking it might be neat to implement a way for people to theme the output to their needs and not limit them to these fixed values, like getting the full $body, etc.
I will discuss this with one of the higherups and see what can be done, i will also look into the settings error. Thanks for your input.
Comment #6
Macronomicus commentedNice! ...looking forward to see what you guys come up with in the theme area, I must say I'm loving it so far, its super fast and gets the job done plus its node based which I absolutely wanted. Keep up the great work, I hope to help out where I can.
This thing could do potentially all sorts of interesting stuff .... ever seen vibrantmedia dot com? Could so do the whole embeded video and other cool stuff. That would likely require some ajax aha loading though.
Cheers!
Comment #7
Macronomicus commentedNow that I think about it looking at other posts you seem to be heading towards using views.
It'll be interesting to see how views ties into this so I'd love to hear what you propose ...im going to investigate some myself too.
Comment #8
Ivo.Radulovski commentedWith the recent rewrite many different possible directions have opened, right now we're trying to get these new features to work properly for the final 3.0 release. From there on we have many different tasks/features we want to implement and work on.
Ok, the new dev release is out, please try that one and send me your thoughts/input.
Comment #9
Ivo.Radulovski commented