I just discovered this bug, and I fixed it (it was a minor hook_menu error), but I thought I should make an issue of it.

Comments

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (works as designed)

That was not actually a bug. The AJAX search was removed from the menu so that it could still be worked on while certain problems are fixed.

1. The AJAX search does not scale well. The entire repository should not be included in the HTML of the page.
2. It was pointed out in another thread that some people would prefer to use text-only browser. Also, it doesn't work on all browsers.
3. It doesn't use the same queue that the rest of the system uses. If something is queued on another page, it doesn't show up on this one. If something is added to the queue on this page, it doesn't appear in the queue from the other pages.

jabapyth’s picture

jabapyth commented

@#3, while it does not check the queue for modules added from other means, it does add its modules to the queue.

Anonymous’s picture

Anonymous (not verified) commented

I know that it is able to queue files, but simply adding something to the queue with the ajax search (without choosing to install) does not add it to the queue from other pages. Or at least it hasn't done so on my machine.

jabapyth’s picture

jabapyth commented
Title: AJAX Search doesnt show up. » AJAX Search revised
Status: Closed (works as designed) » Active

@1: The search no longer loads the whole repository in a page
@2: text-browser users (and people w/o js) can use the regular find/browse pages (as I responded in the other thread)
@3: the search is now queue aware -- it loads the queue to start, and saves to the queue when you click "install".

anything else?

jabapyth’s picture

jabapyth commented

i'll take your silence as a yes.....as I've addressed all the problems you proposed, I will now re-enable the ajax search.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Closed (fixed)