I wonder how the indexation of freelinks works. indeed, on my test site, i create a lot of freelinks (5 or 6 per page) but when i go to the freelinking page, only few of them appear... Is there a special setting to confugue to have a whole indexation? is it working with the search module ?
Comments
Comment #1
eafarris commentedThey don't get stored in the db until they're "clicked," either through a user actually trying the link, or being hit by a crawler.
Comment #2
Roulion commentedok thanks
can a bot be done to make it? as a cronjob for example ?
Comment #3
Gerard McGarry commentedThat's interesting - I always assumed that the list was rebuilt periodically, on a cron job or something like that. Let's say I have a Freelink that doesn't exist - written as [[Droopal]] and I change it to [[Drupal]] - surely the freelinking list should update to delete the /freelinking/droopal entry and create a /freelinking/drupal entry instead?
Comment #4
eafarris commentedIt can't "update" the link, because it doesn't know that the old link ("[[Droopal]]" in your example) is gone. It would have to go through every node body looking for it before deleting it. So it doesn't delete anything. The limitations of the filter system are also at play here. Filters have no idea what they're working on. They don't know that it's a node, or anything. Drupal gives them a piece of text and they're to return a piece of text, and that's it.
I'd actually like to see the list gone entirely. I never needed it myself, I added it per a feature request long ago, and I've never been happy with how it worked.
Adding a cron job for this is an interesting proposal.
Comment #5
Roulion commentedHI
i tryed on a test version of my site the last version i i saw the freelinking list disappeared. I really need this stuff on my project because all my freelinks are my kind of to-do list...
I you could manage to keep it and ind a way to generate it with a cronjob it would be very nice for me..btw, if you can'ti think i'll keep my working version...
Comment #6
eafarris commentedVersion 3 of freelinking will not have the db table of links and therefore will not keep track of which links need to be created. If you require that functionality, you should stick with versions 1 or 2 of the module.
Comment #7
Grayside commentedIn it's next alpha release, FL3 will support Freelinking modules that may define a plugin as part of their behavior. You may implement any side database stuff in the course of link processing that you desire.
I am also working with an experimental FL3 feature to cache a unique list of rendered freelinks by path. If it works out, harvesting those links from the cache and building a master link table will be doable.
Unfortunately, I do not intend significant overhauls of the 1.x or 2.x lines of Freelinking. I am postponing this issue in hopes that someone interested in the feature steps forward with a patch.
Comment #8
Grayside commentedFreelinking 1.x is no longer open to new features.