WordPress.org

Ready to get started?Download WordPress

Make WordPress Core

Tagged: search Toggle Comment Threads | Keyboard Shortcuts

  • George Stephanis 9:26 pm on January 15, 2014 Permalink | Log in to leave a Comment
    Tags: , search   

    Due to a lot of stuff in my lap for the next few months, I don’t have the time to keep chasing down things for Search.  If anyone would like to take point, I’d be glad to help in any way possible, I just don’t have the time to wrangle it personally for the foreseeable future.

     
    • utkarshd_42 5:40 pm on March 7, 2014 Permalink | Log in to Reply

      Hi sir,
      I would like to work on the search initiative for the coming GSoC 2014. Can you suggest me as to how to proceed further with the code that has already been completed?
      And what will be my objectives that I have to complete.

      • George Stephanis 5:44 pm on March 7, 2014 Permalink | Log in to Reply

        Have you read the history of posts on this p2 already?

        • Utkarsh Dixit 6:57 pm on March 7, 2014 Permalink | Log in to Reply

          Yes, i’ve already read the entire history of posts. In the ideas page the objectives weren’t specified clearly and i don’t know whether or not you were active on the mailing list, so had to comment here

        • Utkarsh Dixit 7:42 pm on March 7, 2014 Permalink | Log in to Reply

          I’m also going through the codebase of the current plugin available for omnisearch. Hoping to work for the search initiative :)

      • Utkarsh Dixit 4:51 am on March 9, 2014 Permalink | Log in to Reply

        Hi sir,
        Can you suggest me some other improvements that you would like to see in the search initiative. Even the ideas that haven’t yet been planned or thought of completely. Hope that I will be able to complete most of them :)

      • Utkarsh Dixit 5:50 pm on March 9, 2014 Permalink | Log in to Reply

        Hi sir,
        This includes all the patches I have worked on till now, including the patch for asynchronous search. Please look into it. Its my first time contributing to WordPress so my code might not be upto the par or possible full of bugs. Please suggest changes, approaches, ideas anything that you think might help me.

        https://github.com/utkarshd420/omnisearch-patch/

    • Utkarsh Dixit 5:06 am on March 8, 2014 Permalink | Log in to Reply

      “the biggest task at present seems to be unifying all the search forms in the administrative interface to feed into a global search ”

      We could already use the code given for omni search plugin and could probably change the action parameter of each search form in the admin panel with a hidden input of

      <form id="posts-filter" action="” method=”get”>

      Plugin should be activated for this… Therefore we can use the plugin already build to unify all the search fields in the admin panel..
      is this approach feasible? It works well (I’ve tried for the search posts form)..

    • Utkarsh Dixit 2:18 pm on March 8, 2014 Permalink | Log in to Reply

      I’ve also tweaked the codebase ,of the plugin, a little now it shows the the no. of posts (if found).. Not much a change, but now I have the basic understanding of the way this plugin works.. Waiting for some further updates :)

    • Utkarsh Dixit 11:16 am on March 9, 2014 Permalink | Log in to Reply

      Trying to include the suggestions of posts to search in the plugin too, using AJAX to do it… I’ll share the patches one it’s completed. Hoping to complete it soon.

      • George Stephanis 9:56 pm on March 9, 2014 Permalink | Log in to Reply

        Howdy.

        Sorry for the delay getting back to you, just a bit overwhelmed with other stuff this weekend.

        I’ve actually just added you as a committer to the plugin itself — it’s terrific to see someone eager to start working on it.

        I’ll respond in more detail to the above tomorrow! :)

      • George Stephanis 9:57 pm on March 9, 2014 Permalink | Log in to Reply

        I would suggest in the interim, though, to read up on Core’s Coding Standards and Styles — things like including spaces, and always using braces for conditionals as an example.

        http://make.wordpress.org/core/handbook/coding-standards/php/

        • Utkarsh Dixit 7:15 pm on March 10, 2014 Permalink | Log in to Reply

          Thanks for the link. Have gone through all the coding standard. Will use them from the next time. :)

          Sir, will you be attending this?
          http://make.wordpress.org/core/2014/03/10/gsoc-irc-chats/

          • George Stephanis 9:18 pm on March 10, 2014 Permalink | Log in to Reply

            Yup, I’ll be there. :)

            • Utkarsh Dixit 4:49 pm on March 11, 2014 Permalink

              Hi sir,
              Was going across the IRC chat logs when came upon this

              ” often our search acts more like a filter — if I search for “Jaquith” on the posts screen I see a listtable of posts, it doesn’t say what context (or even necessarily what matched if not the title) in the results ”

              I tried making a patch for it… If the search term is in the post or the content of the page it is displayed as

              $title
              …..something something something $search_term something something something….

              In each row.
              I had to tweak the wordpress codebase a little ( WPINC\class-wp-posts-list-table and WPINC\class-wp-list-table)

              Will upload the patch soon and provide the link on this forum :)

            • Utkarsh Dixit 6:15 pm on March 11, 2014 Permalink

              There is a slight mistake in the earlier comment I had made changes in wp-admin/includes/ and not in WPINC. Sorry for the above mistake.

    • Utkarsh Dixit 7:09 pm on March 11, 2014 Permalink | Log in to Reply

      https://github.com/utkarshd420/omnisearch-patch

      Also updated the patch I have explained here:
      http://make.wordpress.org/core/2014/01/15/search-initiative-on-hold/#comment-13044

      Hope you will look into it :)
      Please provide me feedback, bugs and further approaches you would like the search initiative to have. :)

      PS: tried my best to adhere to the coding standards might have some deviations though, as its my first time contributing to WordPress. Hope you don’t mind. :)

    • Utkarsh Dixit 7:54 pm on March 12, 2014 Permalink | Log in to Reply

      Hi sir,
      This is in regards with the gsoc chat session.. will you be available between 11:30 am to 8:00 pm UTC, tomorrow i.e. 13/3/2014?
      I would really like to discuss the current patches that I have provided as well as the new approaches that we can take on improving omnisearch.
      Please mention the timings that you will be available at (If you won’t be able to attend during the above time).
      Thanks :)

      • George Stephanis 8:07 pm on March 12, 2014 Permalink | Log in to Reply

        Just joined the channel now, I should be online around that span. I may be idling, so feel free to poke me there, or on #wordpress if ever needed — `georgestephanis`

    • Utkarsh Dixit 6:08 pm on March 15, 2014 Permalink | Log in to Reply

      Hi, couldn’t find you on the IRC Channels so am posting here, following (utkarshdixit11.wordpress.com) is the link to my proposal. please go through it once and suggest me any necessary changes that might be needed. Thanks :)

  • George Stephanis 4:49 pm on December 9, 2013 Permalink
    Tags: , , search   

    Search Initiative Chat Recap 

    Link: http://irclogs.wordpress.org/chanlog.php?channel=wordpress-core-plugins&day=2013-12-06&sort=asc#m36279

    In Attendance:

    Topics Discussed:

    • The ‘big’ portion of the Search Initiative may have to be delayed unless we get sufficient interest and participation.  A small group with little feedback will have significantly more difficulty building something that will necessarily be attractive to the community at large, and have far less chance of adoption.
    • x-team (Weston and John) have been working on “admin screen search” here, which is very much in line with the Navigation is often tricky to find a menu item (seen time after time in user testing videos). Possibly suggest admin pages as the user is typing their query? auto-suggest item from the original summation post. However, it would need a search field to hook onto to offer the results.  Some questions about how best to cache it were brought up, as that would be expensive to run, but it seemed best to address that after figuring out precisely what it’s going to search and how it’s going to happen.
    • Scott and the Metamorphosis team have been working on how to better structure Post Meta for assorted post types and the like. This would mesh quite well with the Not all relevant information is searched. I may have relevant data stored in a postmeta field, but it’s not indexed for searching item from the original summation post.  If a `include_in_search` flag could be set on specific meta keys, it could provide far more accurate results, as opposed to the status quo, where postmeta is not used in search (leading to rather difficult situations in CPTs where `content` is not supported or is not representative of the item in question)

    We’ll be continuing on December 13 22:00 UTC unless a time that works for more people is suggested in the comments below.

     
    • Scott Kingsley Clark 5:00 pm on December 9, 2013 Permalink | Log in to Reply

      I wonder if exclude_in_search vs include_in_search should be used for interoperability with post type args and the new meta field API we’re working on. What should the default be is the main question here, assume all fields added will get included in searches, or make the default to exclude unless that default is overridden.

      • George Stephanis 5:06 pm on December 9, 2013 Permalink | Log in to Reply

        Possibly instead of having it be a straight boolean, let folks set it explicitly as ‘include’ or ‘exclude’ — and let whatever’s calling them default whichever way it prefers (or to a configurable/filterable value) if not specified?

    • Eric Andrew Lewis 5:34 pm on December 9, 2013 Permalink | Log in to Reply

      Querying post meta data has been a contentious topic. With the current schema and API, querying many meta keys with a search term will not perform well at scale.

      I’ve heard lead developers say that creating complex queries on post meta is doing it wrong (although I can’t find something to cite in that regard), and post meta should exclusively be used for outputting in templates. Although I haven’t heard a top-down recommended alternative to this prickly architectural question. For custom post(/content) types, some projects have invented their own method for dealing with this. BuddyPress uses tables for all of its data objects. Pods creates tables dynamically for custom content types.

      Perhaps a topic to have an IRC summit on, or even its own working group.

    • George Stephanis 1:21 am on December 14, 2013 Permalink | Log in to Reply

      Major apologies, all. I was laid out with a migraine this afternoon and completely lost track of the meeting this afternoon.

  • George Stephanis 9:37 pm on December 4, 2013 Permalink
    Tags: , , search   

    The Search Initiative needs YOU! 

    the-search-initiative

    The Search Initiative needs people!  We’ve (okay, I’ve) had some terrific feedback from folks already, and would love for the actual work to have a plurality of voices coming together to build it!

    What is the Search Initiative?

    Glad you asked! The Search Initiative is a collection of smaller tasks aimed at making searching within the admin panel a more unified, streamlined, simpler experience.  We are not presently looking to change the search experience on the front-end of sites.  Many themes do a variety of display methods for that, and we shouldn’t step on their toes.  Instead, the biggest task at present seems to be unifying all the search forms in the administrative interface to feed into a global search.  Probably offering tabs for each searchable content type, with a count of the number of entries in each.

    There’s also other aspects that can work in parallel, such as client-side suggestions when someone is typing in a search query. So if they begin typing in ‘New P’ — it would autocomplete the links to ‘New Post,’ ‘New Page,’ and ‘New Pachyderm’ (if they’ve got an elephant post type) — and how can we offer more relevant search results on post types by efficiently searching Post Meta as well?  I’d love to get some collaboration with Team Metamorphosis on this aspect.

    If you’re interested, we’ll be having a chat on Friday evening (after the 3.8 code freeze — this is intentional) at December 6 22:00 UTC in #wordpress-core-plugins on Freenode.

    If you’d like to be involved, but either don’t know what IRC or Freenode is, or can’t make it at that time, just drop a comment below and I (we, hopefully) will make sure to loop you in and take your schedule into consideration for future chats.

    The Search Initiative has need of all sorts, from Designers and UX prototypers, to folks able to write and perform user testing, as well as back-end and front-end coders willing to help ensure a tight integration with core.  Most of all, we need you!

     
    • Rouven Hurling 9:58 pm on December 4, 2013 Permalink | Log in to Reply

      Friday or Wednesday evening? think you didn’t write the Shortcode correctly.
      Either way I would love to help with this, but I’m not going to make it on Friday and there seems to be no one in IRC right now, so I guess that means that it’s on Friday.

      • George Stephanis 4:00 pm on December 5, 2013 Permalink | Log in to Reply

        Sorry — I wrote out the [time] shortcode with just the time, and didn’t specify a date, so it seems to keep assuming the current date. Will fix. Yes, I’d meant on Friday.

    • David Radovanovic 10:55 pm on December 4, 2013 Permalink | Log in to Reply

      Please count me in. I would be happy to offer any support.

    • Christian Foellmann 3:38 pm on December 5, 2013 Permalink | Log in to Reply

      I see you are planning on using tabs.

      We already have the assets for horizontal (e.g. network/site-info.php and associated css) and vertical (current help with add_help_tab) tabs but no integration with the Settings API/SomeName API to use it in wp-admin for custom sites.

      How about integrating tabs generation into core to use it in “all these” places?

      • George Stephanis 4:01 pm on December 5, 2013 Permalink | Log in to Reply

        Well, maybe. There’s a lot of ways to do it, and I don’t want to bite off more than we can reasonably chew. I’d love to have you chip in on the implementation if you’d like to tackle the tabs, though.

    • Scott Kingsley Clark 5:46 pm on December 5, 2013 Permalink | Log in to Reply

      I should be around for the meeting, will be representing Metamorphosis since Eric Lewis won’t be able to make it.

  • George Stephanis 10:17 pm on November 11, 2013 Permalink
    Tags: , search   

    The Search Initiative 

    The Search Initiative

    IRC Chat Log

    In Attendance:

    • George Stephanis
    • Ryan Boren
    • Samuel Sidler
    • Mark Jaquith
    • Helen Sandi
    • Sarah Goodling
    • Matt Mullenweg
    • Andrew Nacin

    We opted to begin by reevaluating what pain points we believed there currently were in the WordPress admin around search.

    These are just what we came up with in the chat, please comment afterwards with any additional issues you’d like to see considered. Some of these are pretty big issues, and could easily be spun off into seperate projects. This looks like it is shaping up to be a significantly larger endeavor than was initially run as Omnisearch.

    Current Problems to Solve (The Status Quo) (Because the status is NOT quo)

    1. We have a lot of search forms in the admin, and it’s troublesome to have to find / navigate to the type of thing you want to search before actually searching it. (#)
    2. When searching, often it’s difficult to know / overly vague why a specific result has been included in the result set. (#)
    3. Not all relevant information is searched. I may have relevant data stored in a postmeta field, but it’s not indexed for searching. (#)
    4. When searching, and no results are found, the user hits a ‘dead end’ — no suggestions or path forward is offered. (#)
    5. Navigation is often tricky to find a menu item (seen time after time in user testing videos). Possibly suggest admin pages as the user is typing their query? (#) — Related plugins: Jarvis and WP-Butler
    6. We don’t currently support syntactically-aware search queries. “Comments by [user]“, “Posts in [category]” etc. (#)
    7. There is currently an inconsistency in the adminbar search field. It displays on the front-end of the site, but not on the admin side — due to WordPress not having a unified search results page to send people to on the back-end. (#)

    I feel that 1, 4, and 7 are the most similar and the solution for both would be more a single unit, whereas 2, 3, 5, and 6 are more distinct and could be done in parallel or in subsequent iterations.

    Possible road forward:

    Have a Global Search Page, with some sort of tabbed interface. There would likely need to be an ‘Overview’ tab, and then for each different data type being searched, its own tab. Generic search forms (like the adminbar search) would land on the overview, but if the initial search form designated which bit of content they’d like to search (for example, using the search form on the admin posts page), send them directly to its respective tab, the content of which would be akin to the current search results pages currently dispersed throughout the admin.

    We would be able to add in the adminbar search form to the admin (yay consistency) and even auto-suggest based on links off of the current page (akin to Jarvis or WP-Butler) — or leave that to plugin territory.

    Parallel projects on the rest would be terrific, as I don’t personally see them as interdependent. They could be iterations or new groups could spring up to tackle them.

    That’s what I’ve got, now I’d love to hear your use cases, feedback, and where you’d like to see this headed. Let’s get the feedback in early this time, folks! :)

     
    • Scott Kingsley Clark 1:22 am on November 12, 2013 Permalink | Log in to Reply

      I built the Filters plugin to expand on providing a better UX for searching and filtering on multiple fields and taxonomies at once. It uses Thickbox inline but I plan on integrating the Media Modal possibly instead, for a nicer UI with a less buggy popup.

      http://wordpress.org/plugins/filters/

      I would hope that any solution that is built, can support filtering my fields and taxonomies in a better way than it is now.

      • George Stephanis 3:38 pm on November 12, 2013 Permalink | Log in to Reply

        We’d certainly welcome your input as this develops. As someone with prior experience building an addition to the search experience, it’d be invaluable input.

    • Dwain Maralack 6:09 am on November 12, 2013 Permalink | Log in to Reply

      I love the global Admin search bar and think Ajax search should be built in as the has become the standard.

    • RicaNeaga 2:49 pm on November 12, 2013 Permalink | Log in to Reply

      Please consider if a third-party search api is a viable solution (to be included / implemented alongside wordpress installation).

      For example vbulletin now bundles sphinxsearch.com , and they say for large websites (with large databases) this addition is a ”performance enhancement that will allow you to offload search from your MySQL database”.

      • George Stephanis 3:35 pm on November 12, 2013 Permalink | Log in to Reply

        I don’t believe it’s something that we would bundle with core, but — as I remarked above — the hooks will certainly be in place that a third-party provider could provide a plugin to replace or supplement existing results if desired.

  • Samuel Wood (Otto) 6:20 pm on August 3, 2010 Permalink
    Tags: boolean, filter, search,   

    Theme filter searching now has an all/any selection box, for people who didn’t like it being exclusively boolean AND. See it here: http://wordpress.org/extend/themes/tag-filter/

     
c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel