Defined links randomly stopped working

Once a plugin with definable links becomes enabled - i.e. the keyword links plugin - a menu item will appear under the content section (drupal 6) or at config/content (drupal 7). If an automatic links plugin is being used then no menu item will be available. This is just the mechanism by which the modules ability to separate automatic links from defined links is separated. I understand this is a bit confusing, and I will be adding a message to make it more clear. Expect this in the next update.

So, once the keyword links plugin is enabled go to content management >> Autolink links and create a new link group. Link groups are just like vocabularies in that they apply by content type. Click the link group to add links to the group similar to adding terms to a vocabulary. I'll be working on ways to improve this relationship tonight.

I committed some minor changes to the settings page. Now, when a definable links plugin is enabled a message appears with a link to the links overview page. I will leave this issue open though because I think I will be reorganizing the settings and links pages to be in the same location. The current setup simply follows the workflow of administrative pages - settings for settings and content for links - but I think it can be done better. Thanks.

Okay, in the next release all settings and link definition forms will be in the same location. Under content management >> autolink. If an automatic links plugin is enabled then it will simply go to the settings page, but if the plugin supports definable links then it will add tabs to the settings page for adding link groups and links. I'm thinking about even reorganizing the links overview so that groups and links can be seen in the same page. This may go into the next release.

I wasn't even paying attention to the version. This is a lot less straight forward in Autolink 6.x-2.0. So, in Autolink 7.x-2.0, once you have enabled a plugin in Autolink settings at configuration >> content >> Autolink settings another link will appear right above the Autolink settings link named Autolink links. So, links can be defined at administer >> configuration >> content >> Autolink links. This issue was resolved in Drupal 6 by putting the forms all under the same link, but I'm not sure it will be like that in d7. I will, however, be porting the new changes in 6.x to 7.x, but they are just changes in how the links overview for defined links is laid out. Links will still be grouped, but all links will be displayed on the same page separated into groups by fieldsets. Those are the changes that are about to be committed to 6.x. I will, however, be adding back in the message to go to the Autolink links page once a definable links plugin is enabled. Actually, because the menu system is different in 7.x I can even provide a direct link. That will be done in the next 7.x release with these updates - probably some time today. I'll mark this issue fixed once the changes are committed.

Thanks for your comments again. Even though this was realistically a support request, I want to take the chance while the module is young to work out the confusions in the interface. Much of the administrative interface was redesigned last night (been up all night). While link groups are still used, they are displayed on the same page as separate fieldsets, so all defined links can be seen on the same form. Also, when manipulating Autolink setting at administer >> configuration >> content >> autolink, once you enable the keyword links plugin and save the form a tab appears at the top of the form to List links. you may need to refresh the form because the menu may not rebuild before the page reloads the first time, but it's there. This is a lot more straightforward than it was before. I'd be interested in your opinion in you give it a try. It has gone in a new release in both d6 and d7 versions.

Thanks! And thanks for the report.

Whoah! Interesting. So it was working and now is not...

The 7.x version is a little behind 6.x and is certainly young as features have been being ported from 6.x to 7.x. The 6.x version was having caching problems before. Caching ended up being vital to performance, but it has caused some problems with links failing to load. And with caching between links and filters, there is a lot of data being saved, just sometimes just at the wrong time. I haven't ported the changes to 7.x yet, but I'll be working on it tomorrow and I'll also be planning on doing some extensive testing on the 7.x branch.

Proper title