Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I tried to port it yesterday.
It's definetely not complete but I needed it urgently so it's an "ugly" port.
It works for what I need...
So handle with care because I don't take any responsibility for the result.
To get it working, here's a simple manual:
- copy to your modules folder
- enable module
- browse to admin/config/glossify (not integrated yet in the config tab)
- apply settings (links and reference should be working)
- update your text formats and add the glossify filter as first priority
- perform an update of all your nodes so the titles get parsed
- clear your caches
- check the result
port was tested, but without successes to make it work, some problem appeared:
- on node view
Notice: Trying to get property of non-object in glossify_node_load() (line 226 of /users/planiram/public_html/planiram/sites/all/modules/glossify/glossify.module).
Notice: Trying to get property of non-object in glossify_node_load() (line 227 of /users/planiram/public_html/planiram/sites/all/modules/glossify/glossify.module).
-on node list
Notice: Use of undefined constant bundle - assumed 'bundle' in _glossify_process() (line 454 of .../sites/all/modules/glossify/glossify.module)
Notice: Use of undefined constant entity_id - assumed 'entity_id' in _glossify_process() (line 452 of .../sites/all/modules/glossify/glossify.module).
Notice: Trying to get property of non-object in glossify_node_load() (line 226 of .../sites/all/modules/glossify/glossify.module).
Notice: Trying to get property of non-object in glossify_node_load() (line 227 of .../sites/all/modules/glossify/glossify.module).
Did you base the port off of the version 2 or version 3? Just wonderin' since I have a friend who needs this like RIGHT NOW, and so I'm going to get hacking on it, too, I guess.
Hi, Ive got a few replies but no commitment for potential financial support. I'll estimate now how many hours of development it will take and then we can see where the funds will come from.
I need it myself soon so the chances are now higher of having a D7 version sometimes soon.
We will fix some current issues first in any case. At 2000$ we will port it to Drupal7. At 4000 we will add several new functionality and at 5000 we will make sure that it stays up to date for some time!
Thank you for porting this module to D7. Ivo, can we expect to see the final version soon? This is one of the best modules I have used in Drupal, absolutely great for SEO! It always worked fine for me and I am disappointed that there is not a single alternative neither for D6 nor D7. Another reason to (impatiently) wait for the next official release.
I've just recently taken over maintainership of this module and the first order of business will be to get the 6.x-3.x version republished and officially released. Then I'll work on the upgrade to d7. So hang tight for now.
It anyone wants to help, patches for d7 rolled against the 6.x-3.x dev branch is the best way to contribute.
The beta11 release is just a tag on the current dev. The previous maintainer had actually fixed the security issue but never followed up to get it republished. So yes, patches should be against the current dev.
And the file in #1 isnt a patch but i'll take a look at though the d7 version will likely be an entity based rewrite.
Comments
Comment #1
krisjansen commentedI tried to port it yesterday.
It's definetely not complete but I needed it urgently so it's an "ugly" port.
It works for what I need...
So handle with care because I don't take any responsibility for the result.
To get it working, here's a simple manual:
- copy to your modules folder
- enable module
- browse to admin/config/glossify (not integrated yet in the config tab)
- apply settings (links and reference should be working)
- update your text formats and add the glossify filter as first priority
- perform an update of all your nodes so the titles get parsed
- clear your caches
- check the result
Don't forget to add in your themed node.tpl.php
in case you want to see the Referenced pages on the bottom of your node
not functional:
- taxonomy-linking
- hovertips (it needs a port as well)
- ... (and others)
Good luck,
Kris
Comment #2
cesareaugusto commentedwhich is the status of the official port to drupal 7?
Comment #3
Ivo.Radulovski commented@krisjansen
Thanks for the efforts till now!
Will check the code soon and see how we can go on!
Thanks again.
@cesareaugusto
You can test the zip file by Kris Jansen and seewhat the state is.
Regards!
Ivo
Comment #4
kansaj commentedport was tested, but without successes to make it work, some problem appeared:
- on node view
Notice: Trying to get property of non-object in glossify_node_load() (line 226 of /users/planiram/public_html/planiram/sites/all/modules/glossify/glossify.module).
Notice: Trying to get property of non-object in glossify_node_load() (line 227 of /users/planiram/public_html/planiram/sites/all/modules/glossify/glossify.module).
-on node list
Notice: Use of undefined constant bundle - assumed 'bundle' in _glossify_process() (line 454 of .../sites/all/modules/glossify/glossify.module)
Notice: Use of undefined constant entity_id - assumed 'entity_id' in _glossify_process() (line 452 of .../sites/all/modules/glossify/glossify.module).
Notice: Trying to get property of non-object in glossify_node_load() (line 226 of .../sites/all/modules/glossify/glossify.module).
Notice: Trying to get property of non-object in glossify_node_load() (line 227 of .../sites/all/modules/glossify/glossify.module).
Comment #5
gberm commentedsubscribing
Comment #6
gberm commentedAny word on this?
Comment #7
lishevita commentedDid you base the port off of the version 2 or version 3? Just wonderin' since I have a friend who needs this like RIGHT NOW, and so I'm going to get hacking on it, too, I guess.
Comment #8
anton-staroverov commentedsubscribing
Comment #9
himagarwal commentedsubscribing, does anyone know similar module in drupal 7?
Comment #10
myfarmertan commentedsub
Comment #11
sachbearbeiter commentedsub
Comment #12
clashar commented+1
Comment #13
Jb33 commentedI think it is a very useful module, so porting it to Drupal 7 would be good! +1
Comment #14
Ivo.Radulovski commentedI'm trying to get some funds so we can assure the further development...maybe at Drupalcon there will be progress...
Comment #15
Canadaka commentedsubscribing
Comment #16
basicmagic.net commentedsubscribe
Comment #17
kaztur commented+1
Comment #18
Starminder commentedsub
Comment #19
Ivo.Radulovski commentedHi, Ive got a few replies but no commitment for potential financial support. I'll estimate now how many hours of development it will take and then we can see where the funds will come from.
I need it myself soon so the chances are now higher of having a D7 version sometimes soon.
Thanks,
Ivo
Comment #20
anybody+1
Comment #21
dockstaderj commentedSubscribe
Comment #22
marcoka commentedfor the future...take a look at the BIG green button on the top right to follow issues.
Comment #23
daniorama commentedAdding bulk operations and international stemmer would be really great!
Comment #24
kingdee40 commentedD7 port, any update? You can create a chip-in if you need $ to get the ball rolling.
Comment #25
Ivo.Radulovski commentedhi we are starting again with Glossify
the goal is to fix issues, port it to D7 and extend functionality for what we need about 5k all in all:
http://glossify.chipin.com/glossify
We will fix some current issues first in any case. At 2000$ we will port it to Drupal7. At 4000 we will add several new functionality and at 5000 we will make sure that it stays up to date for some time!
Thanks,
Ivo
Comment #26
danielnolde commentedIvo, what's the status on this regarding...
1. Fix of the security issue
2. D7 port - there's Kris' approach, can we take it as basis
?
Kris, does your port also fix the security issue? What about the status of your port, what needs to be done for it to be glossify-7.x-?.x?
Comment #27
Ivo.Radulovski commentedHi Daniel,
the fix is not inside 2.5 - it's a small issue I think
we have now a working version of Glossify 2.5 for Drupal 7 - you might want to help and co-maintain the module?
Ivo
Comment #28
danielnolde commentedwe could help in porting or security-fixing, but since we use the module only sporadically, i might not be the right person to co-maintain.
How, specifically, can we help best?
Where exactly is what work to be done for fixing the security issue?
Comment #29
1mundus commentedThank you for porting this module to D7. Ivo, can we expect to see the final version soon? This is one of the best modules I have used in Drupal, absolutely great for SEO! It always worked fine for me and I am disappointed that there is not a single alternative neither for D6 nor D7. Another reason to (impatiently) wait for the next official release.
Comment #30
danielnolde commentedHey Ivo,
how can we help to fix the security hole in the D7 version?
cheers,
daniel
Comment #31
WorldFallz commentedI've just recently taken over maintainership of this module and the first order of business will be to get the 6.x-3.x version republished and officially released. Then I'll work on the upgrade to d7. So hang tight for now.
It anyone wants to help, patches for d7 rolled against the 6.x-3.x dev branch is the best way to contribute.
Comment #32
jamesbisset commentedWith the resurrection of the project and the beta at v11 (2012-Jul-31) are we still invited to patch against the dev branch (2011-Feb-25)?
And is the patch by krisjansen at #1 good enough to kick things off?
Comment #33
WorldFallz commentedThe beta11 release is just a tag on the current dev. The previous maintainer had actually fixed the security issue but never followed up to get it republished. So yes, patches should be against the current dev.
And the file in #1 isnt a patch but i'll take a look at though the d7 version will likely be an entity based rewrite.
Comment #34
WorldFallz commenteddone. D7 snapshot is now available.