Admin screen needs a pager

Just updating to D6 branch as problem still exists

Additional information. As the list of alinks grow, the load time increases, I am now experiencing upto 5 minutes or more, so tend to avoid editing, and go straight to the database. (165 links)

Hi rsvelko,

Looking forward to the new ships captain, assuming the old one is lost at sea :)

Pager is the first item to consider, that way the number of items*variables can be limited, so an out of memory situation is less likely to occur. Filtering as an addition would be a second great feature.

I have been running RC1 for over a year now, and on several websites, with no real issues. The only other thing that may be useful is to make entries multiple lines, probably 2, as when you tab to the right to find delete, it can bea easy to loose track of the row you are on. In my own case i have a fluid width layout, which extends to about 1600px, but even then the one field hard to see is Delete !

I must say one aspect of Glossify that does interest is I have an encyclopedia on one of my sites where I may be able to use it as a simple wiki for linking purposes, which is one thing alinks can not do, or better put, I would not allow it, considering there are 3000+ entries. The Edit page would probably cause a self destruct :)

FYI: One area that has never truly been resolved is self linking, IE linking to the page the link is already on.

Another feature is the ability to ignore specific nodes, though that may be bettter suited to the node form, and may not suit everyone. With larger sites you may also want to have links restricted to specific content types, but then it gets really complex, as in theory you could have two identical terms linking to different locations when they occur in different content types.

Once you have control. It may be a good idea to have a "Features and Bugs" issue so existing users can identify what they know of.