I have created some new functionality for Glossify so that it can support the Backlinks module.
The Backlinks module (in 5.x) provides a wiki-style "what links here" filter for Views. For Drupal 6.x, the Backlinks module has been incorporated into Views 2.
In the current versions of Glossify, $node->body has links added to it only when you view the page. And then the content with the new links is not added to the search index.
I added an $op for update/insert that finds nodes that have the title being saved in them and I re-index the search with them.
I also added an administrative setting that defaults to false for this Backlinks support.
Also in this patch, I changed the delimiters for the preg_replaces from '/' to '#'. I was encountering errors with the former.
I did update the documentation with this new feature.
Thanks to Seth for his contributions.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | glossify5x-backlinks-V2.patch | 5.67 KB | miche |
| #1 | glossify5x-backlinks.patch | 4.85 KB | miche |
Comments
Comment #1
micheHere you go!
Comment #2
micheThere appears to be a bug in the above patch where the search index is getting overwritten with only some of the links. I am working on it.
Comment #3
micheI made some changes to the saving of the preg_replace in the original code and also in my insert/update.
It now assigns $node->body to $newbody and continually adds the links into $newbody. It then takes $newbody and puts it back into $node->body.
Comment #4
rsvelko commentedI will look into it and will give feedback soon.
Comment #5
kansaj commentedhi I tired your patch, but unexpected problem appeared. after login out of the admin and login in , all glossify's backlinks disappear.
Actually really nice patch !
Comment #6
rsvelko commentedI can re-roll for the latest version.
I grasped the idea of the patch...
I am not sure if just adding a save-links-into-actual-body-text option will solve the same issue and do even more....
Comment #7
WorldFallz commentedunsupported version. feel free to open a new issue against the current version if this is still applicable.