Omnisearch User Testing

Welcome!

The WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:

Found a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

Howdy, all!

Sorry for the delay, been a chaotic week or so. Just got the results of some user testing back thanks to the assistance of @lessbloat.

View Results: https://www.usertesting.com/videos/dQBRyueQ9EsMAv1OsQrQmg%3d%3d?back=%2Fdashboard%3Fnew_study_id%3D%23study_905321

Here’s my notes:

User remarks that there is no obvious intermediary way to search things. Seems frustrated about having to go from the current page, to the archive page, to search.
Unrelated Bug: (possibly due to browser extension?) For some odd reason, when the user selects the search box, it jumps below the list table. Really odd behavior in IE 10.
Dislikes native WordPress functionality of the “Search” in the adminbar expanding when selected (native is only on front-end, Omnisearch expands this functionality to adminadmin (and super admin) ui as well) — believes it should be natively expanded. Reiterated several times. Perhaps look at making it drop down a search box on hover (kinda like twentyfourteen does), rather than expanding on click and shifting things about? Unsure.
Found Bug: Reply hoverlink in comments list [in omnisearch] doesn’t function properly (missing JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. hook).
“Overall, I would say that this is a much better tool, much better layout.”

The user seems very positive, seemed to consider it a great win for usability. Pointed out a few bugs (as noted above — only notable one I caught with Omnisearch itself being the hoverlinks in the Comments to reply didn’t work), which I’m about to patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing..

Our weekly meeting will be as usual, Thursday at 22:00 UTC (6pm Eastern)

#omnisearch, #user-testing

deltafactory 5:41 pm on October 8, 2013

I see her point but wonder how an expanded search box would impact layout on narrower screens. Looking good!
- Nico 3:22 am on October 10, 2013
  
  With responsive design there could be both, on smaller screens just the icon and on bigger screens expanded by default.
  
  Btw: Was fun and painful to watch at the same time 😉
  - George Stephanis 3:35 am on October 10, 2013
    
    The difficulty is you can’t make it too big, else when users have plugins that add new items to the adminbar, it will run out of space far too quickly.
TimothyBlynJacobs 9:18 pm on October 8, 2013

What if instead of having it just be an icon, be an icon and the text “search” maybe that will bring it into the forefront more, but not actually have to have a distracting white on black search box the whole time.

Curious, how does this work with custom post types?
- George Stephanis 9:51 pm on October 10, 2013
  
  It works with CPTs, but doesn’t automatically turn itself on for them. A lot of CPTs store arbitrary data that wouldn’t display well (or be easily searchable) via a stock table. They can be turned on as is done here if you like: https://plugins.trac.wordpress.org/browser/jetpack/trunk/modules/omnisearch/omnisearch-core.php#L25 — by doing something like …
  
  https://gist.github.com/georgestephanis/6926206
George Stephanis 9:45 pm on October 10, 2013

r786113-plugins committed, removes reply and quickedit links for comments, as the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. to enable them wasn’t being enqueued and when I tried enqueueing it, it caused issues.

Comments are closed.

Welcome!

Communication

Share this: