Closed (cannot reproduce)
Project:
Glossify
Version:
6.x-3.0-beta1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Dec 2009 at 12:56 UTC
Updated:
30 Jul 2013 at 14:02 UTC
I am running this on a V6 site running the latest release of Views and Panels and glossify does not parse these pages. I have some static generic pages, and these are parsed correctly, but nothing at all on the panels pages.
Is this a know issue? Is there a workaround?
Thanks
Gareth
Comments
Comment #1
rsvelko commentedHi,
I am not sure if this is a bug or a feature request.
Do you know what exactly is this text that is not getting parsed - it is not a node - maybe a view of nodes?
Glossify works only on node bodies and teasers for now. Any info/help/money are welcome.
Comment #2
gazzer82 commentedHi,
Thanks for the reply!
The content that is not being parsed are all nodes being displayed by a custom view within a panels page.
If you need any more info let me know, if you wish to take a look at the site it is at http://www.stagesoundservices.co.uk it's the projects and sound/video pages that i really want parsed.
So from what your saying i guess this will not work for now on my site, is there a time frame for implementing this?
Many Thanks
Gareth
Comment #3
rsvelko commentedYup, glossify does not work with nodes into views. Maybe if I implement a node save function - this will fix ya and be not a problem.
Comment #4
rsvelko commentedThere is currently no timeframe for this feature (views support and/or node save). I honestly do not know. Maybe if someone really needs this and can donate a bit - I will move it to the front in my schedule...
As usual all patches are welcome.
------
Price/time estimates:
- node save option/feature - about 3 hours x 20 eur/h = 60 eur
- parse nodes into views - honestly don't know - I have no idea how to do that there. (Maybe a views style plugin ?)
------
PS. How do you find the module? Helpful? Slick? Correct html parsing?
Comment #5
rsvelko commentedUpdate: Will it be enough if I supply an API function that looks like:
Currently I've not packed such a func but it will be quite easy...
Stay tuned. Soon you will be able to use this function somewhere where you need it (in your views templates maybe a good place for your use case) .
How about that idea?
Comment #6
Ivo.Radulovski commentedviews support sounds nice...will think about sponsoring this idea
Comment #7
rsvelko commentedComment #8
gazzer82 commentedHi,
Sorry for the delay at coming back to you on this one, it's been crazy and i am only now getting the chance to revisit it.
This may well be something we could look to sponsor as it would be very very helpful on our site where we have projects with lists of equipment that need linking back to there nodes, which doing manually is a PITA!!
So do you have any more of an idea how you might implement this now? Or indeed how long it might take?
In general i find the module good, although so much of our site is custom views in panels that it only functions on a minute part of the site, but if it worked site-wide it would be awesome, both for people browsing the site and the all important SEO!!
Thanks
Gareth
Comment #9
Ivo.Radulovski commentedHello!
We have rewritten the module.
Please get in contact with me to discuss the implementation of panels support.
Ivo
Comment #10
kompressaur commentedHello jut to confirm. Does this work with Panels? I am willing to pay for a bit of custom work to make it work if it doesnt. Thanks.
Comment #11
WorldFallz commentedno clue about the current status, but I won't get to this for a while. If anyone can confirm whether or not the bug still exists (and close this if not), that would be great.
Comment #12
WorldFallz commentedqueue cleanup. almost a year old.