Not signed in ( Sign In)

Categories

Welcome, Guest

Want to take part in these discussions? Sign in if you have an account, or apply for one below

Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.

    •  
      CommentAuthorPanther
    • CommentTimeAug 17th 2010
     permalink
    If I use search box on my website (warsintheworld.com) it searches only on names of titles (for ex. Puntland).
    There is a plugin or another way to search on text in the articles I've written ?
    I mean, what I search, should be not only on name of article, but in all text in all article.
    Thanks
    •  
      CommentAuthorlaborix
    • CommentTimeAug 17th 2010
     permalink
    Try this:
    Flatpress Forum: | Help: Search full text
    It is a bit older forum entry, but it should also work with FP 0.909.1.
    •  
      CommentAuthorPanther
    • CommentTimeAug 17th 2010
     permalink
    I followed and it works! But the "problem" is that the Search doesn't search on static pages (Admin-Statics-Manage Static).
    If you go on http://www.warsintheworld.com/ and search (Punjab) you can find 3 results, but you don't find the result on static page:

    http://www.warsintheworld.com/?page=static1258254223

    If someone wants search a name of guerrilla group not present on article, he can't find it.
    Do you know how to do ?
    Thank you very much.
    •  
      CommentAuthorNoWhereMan
    • CommentTimeAug 17th 2010
     permalink
    The search function is very barebone, it doesn't even search in static pages (there is a reason: you might not want to make some static pages public, such as those you use in a blockparser widget); if you need more advanced searching capabilities I'd suggest to rather go with a google/bing box embedded in a widget.
    •  
      CommentAuthorStanley
    • CommentTimeAug 17th 2010
     permalink
    @NWM

    On a recent site I created I got around that problem by copying the static which pages I wanted to be searchable into new entries. Duplication, I know, but it was the only way round it I could see. I actually started the site just by using blog entries as pages (as recently suggested by you, hereabouts), and left the statics for blockparsers etc., but the guy I was doing the site for got hugely confused by it all when I was trying to teach him how to write his own pages. So I went back to static pages but continued to keep a duplicate of the page as a blog entry, purely for search purposes.

    That's very long-winded, but I was wondering if there might be a way to add another button (one day!) to the bottom of the static page edit form to publish it and also to create a duplicate of the page as an entry - or some other way - similar to how you can create static pages then later decide to create a blockparser widget out of them, you could later decide to create a duplicate of the page as an entry.
    •  
      CommentAuthorNoWhereMan
    • CommentTimeAug 18th 2010 edited
     permalink
    @Stanley: heh, I don't like it :p

    btw, there is actually one thing I've been thinking about, which is allowing to add a "page name" to a post, which would allow a post to be called "by name", as it was a static page, which would make "real" static pages redundant.

    How would it work: with the FrontPage you could hide[1] a special category (and all of its child-categories), then with plugin similar to the pierovdfn's you could add a name to the page (see my comment on that post).

    Blockparser plugin would probably have to be partially rewritten, though.

    When I was rewriting the back-end, three or four years ago, I considered such a solution, which made sense, but I decided to keep statics on their own, because I could spare a check on an eventual "static" flag: statics just aren't in the index.[2]

    As for the search function, there is a simple reason for which I don't like it: there is no text index, so it is really a full-text search on each post, which means it's very, very slow and cpu intensive! This is why I'd rather go with a google/bing search box; I haven't done it on my blog just because... I'm lazy ;) and anyway the search function is not something your visitors really care about (at least from my very short-sighted point of view ;)).


    [1] better not hide, but rather make default a non-hidden category, and here's why: if you hide a category, when you list the posts you have to check each time if the current post is in the other list, while if you make default a category containing all of the non-hidden posts you just have to list that category :)

    [2] at the time the index was one and only, not one for each category!