Closed
Bug 510542
Opened 15 years ago
Closed 15 years ago
Add-on name autocomplete field on Collection build page doesn't return results
Categories
(addons.mozilla.org Graveyard :: Collections, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
5.0.9
People
(Reporter: rbango, Assigned: jbalogh)
References
Details
Attachments
(1 file)
304.89 KB,
image/png
|
Details |
On the following page: https://addons.mozilla.org/en-US/firefox/collections/add it seems that the add-on name field's autocomplete function isn't working. Rdoherty mentioned that it could be related to the jQuery autocomplete plugin. Reproduced by TomCat as well.
Comment 2•15 years ago
|
||
What add-on names have you tried? It works for me.
Adblock Plus was the one I tried and it wouldn't appear. The indicator just kept going with no result.
Comment 4•15 years ago
|
||
OK, I can confirm with Adblock Plus. It seems to work for the others I've tried. Fred, can you take a look?
Assignee: nobody → fwenzel
Assignee | ||
Comment 5•15 years ago
|
||
Predictably, I'm seeing an OOM error on the return. Also unsurprising, PHP is a freaking godsend in figuring out the error: <b>Fatal error</b>: Allowed memory size of 33554432 bytes exhausted (tried to allocate 47 bytes) in <b>/home/jbalogh/public_html/amo/site/cake/libs/model/dbo/dbo_mysql.php</b> on line <b>411</b><br />
Assignee | ||
Comment 6•15 years ago
|
||
r49199
Assignee: fwenzel → jbalogh
Status: NEW → RESOLVED
Closed: 15 years ago
Keywords: push-needed
Resolution: --- → FIXED
Comment 7•15 years ago
|
||
Thanks
Comment 8•15 years ago
|
||
Comment 9•15 years ago
|
||
(Took the screenshot at the wrong time; AdBlock Plus autocompleted for me and was added successfully.) Verified FIXED on https://preview.addons.mozilla.org/en-US/firefox/collections/add; see https://preview.addons.mozilla.org/en-US/firefox/collection/db73c1ae-235d-2697-98f5-0a5a2e84d4f7.
Status: RESOLVED → VERIFIED
Updated•15 years ago
|
Keywords: push-needed
Updated•8 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•