Assign new Alinks maintainer

would like that too.

i started updating the module file with coder module, first version as attachment. Will create a patch if finished.

regards pebosi

Unfortunately it does not work for me with Drupal 6.4. When I try to install, I get the following error:

Parse error: syntax error, unexpected ';' in /.../sites/all/modules/alinks/alinks.module on line 119

Any idea?

rc.otto

Подписываюсь! Хороший модуль! Хак не работает с 6.3 :-/

I have developed alinks for drupal6,
and I want to share it for drupal.org
although I applied a CVS account,but I don't kown how to connect with the maintainer.
and I want to share it in project/alinks
I have shared the alinks module for drupal6 as follow url:
http://drupal.org/node/309227
every one can download it and test it.
thank you!
========
chinajason

It appears there was work on development in January, but no reply to this thread, so does anyone know if the coder is continuing this project? If not, I will seek an alternative.

Can anyone confirm that this module has been abandoned?

Hi,

we would like to become the new maintainers of the Alinks module!

We (rsvelko and segments) are the maintainers of the Glossify module and since we have been closely studying the Alinks module's code for merging it into Glossify - this is a good chance to keep Alinks alive.

Greetings.

#16 rsvelko

I have been using alinks on D6 for ages without major hitch, and would like to see it continue, though I am not sure about merging with Glossify. I have not used Glossify, so maybe you can clarify some things for me

In the description from Glossify i see " looks for node titles in node bodies and makes them inbound links"

In alinks the user defines which strings should be linked and where too, the above description implies that there is an automated system.

In my case an automated system, would not be wanted, or even necessarily a good idea. This is because there are instances on my sites where node titles can be duplicated, though accessed by different paths. There is also a situation where some titles may include a string which is another node title in itself.

Asssuming my understanding is correct, as long as you can switch modes on/off so that the alinks function can run as existing, I would welcome the merge, as I could then use the new facilities on future sites, without the need for re-engineering exisiting sites.

I have marked #715366: Offering to maintain Alinks as duplicate of this report.

Both modules are quite small. Why not just merge and let Glossify provide an upgrade path for Alinks users?

Just in case the current maintainer doesn't reply: who should be made maintainer of the module?

I'd very much like to see rsvelko continue this module so that we can all benefit. When do you (rsvelko) foresee taking over the project, and do you plan on making any changes immediately, or do you believe the current version of alinks is stable and worth adding to a site immediately?

Short answer to #26 - yes Alinks is usable now and if you are happy with the features - go for it. Be careful that your alinks are not html-reserved-words cause your html may get mangled then (glossify's beauty is that it knows how to touch only outside of html tags... took me a while to write/reuse this from the simplehtmldom project... )

I need to think a little bit more if it is strategically fine to let you input your keywords just now into alinks and live happy when glossify and alinks merge ... Give me a couple of days to sleep on it.

Then give me probably 2 weeks to finnish the merge and present to you the awesome basic(alinks)+advanced(glossify) NEW module.

Somebody with name proposals? My best name so far is "Alinks SEO" (with an optional "++" suffix or a "Plus Plus" suffix) ;)

-- longer text begins here.

Here are the bugs - http://drupal.org/project/issues/search/alinks?text=&assigned=&submitted=&participant=&categories[]=bug&version[]=6.x&issue_tags_op=or&issue_tags=

this page basically says that the module is usable.

There are problems with non-latin scripts and umaluts. (both problems have already solved in the glossify module and with the merge of alinks and glossify alinks will benefit a lot from the html parser magic of g. This is why I am so excited.)

Another set of problems is scalability (when one has a LOT of keywords/alinks) - two parts of this problem - the parsing/db maintenance on one side and the admin UI .

See - glossify currently does not have an db-table-index (while alinks has one ) and conversely alinks has problems when you have 150+ links defined.... Both issues are solvable and it is nice that I know how.

hi!

2 weeks are over...any response on this issue?

cheers,
RI

The ownership of the project has been passed to rsvelko.

The previous maintainer still has access as co-maintainer; please don't change that.

I have made alinks for drupal7.x , I will commit it recently, who wants it ?