Forum Replies Created

Viewing 15 replies - 1 through 15 (of 51 total)
  • Denis – that’s a great addition!

    A simple fix to improve it slightly is to simply add a leading space to the SQL “LIKE” statement in wp/includes/classes.php around like 357:

    <code style=”white-space: pre;”>
    if (!$q[‘sentence’]) {
    $s_array = explode(‘ ‘,$q[‘s’]);
    $q[‘search_terms’] = $s_array;
    $search .= ‘((post_title LIKE ”.$n.” “.$s_array[0].$n.”) OR (post_content LIKE ”.$n.” “.$s_array[0].$n.”))’;
    for ( $i = 1; $i < count($s_array); $i = $i + 1) {
    $search .= ‘ AND ((post_title LIKE ”.$n.” “.$s_array[$i].$n.”) OR (post_content LIKE ”.$n.” “.$s_array[$i].$n.”))’;
    }
    $search .= ‘ OR (post_title LIKE ”.$n.” “.$q[‘s’].$n.”) OR (post_content LIKE ”.$n.” “.$q[‘s’].$n.”)’;
    $search .= ‘)’;
    } else {
    $search = ‘ AND ((post_title LIKE ”.$n.” “.$q[‘s’].$n.”) OR (post_content LIKE ”.$n.” “.$q[‘s’].$n.”))’;
    }

    It’s not exactly perfect, but it certainly makes the results more like what you would expect.

    the problem is with how WP constructs the search query… it’s bloody awful. It’s basically a glorified substring search.

    If I search for “rdp” I’ll get everything I posted where I mention WordPress because it contains that string (WordPress)

    I’m working on another search for my new theme, but it’s one of those back burner issues…

    Forum: Plugins
    In reply to: Link replacement plugin

    Although it doesn’t do that completely right now Twilight Friend Finder does something similar, and is XFN friendly too ??

    So its just compress between quotes like “compress” or any instance of the word…

    actually I guess this post will test that on the forums.

    Something this wierd I chalk up to regular expressions, when something wierd happens its usually their fault. You can’t get wierder than regex.

    Forum: Plugins
    In reply to: WordPress: Touched
    Thread Starter darkcryst

    (@darkcryst)

    The answer is somewhere inbetween.

    Quicktags (and any dynamic content) are rather hard because the uick tags load when the page is called. The page is called NOT when it is displayed but, because of the way AJAX works, before that. Therefore the quicktags JS doesn’t execute in the page.

    There are ways of working around that though.. however its on the bottom of the list.

    It’s not designed to be a replacement for the edit page, so I’m not going to try and duplicate everything. The Custom Field area is one that is also waaaaay at the bottom of the list – mostly because of the way WP handles and outputs the custom fields in the post form make them a real pain in the ass to work with in JavaScript.

    Publish to Draft would be easy to do, but rather pointless – you’ve already published the post! Changing it back to draft probably means you want the added functionality of the edit screen.

    However I plan to modularise it so, if someone REALLY wants that, they can have it ??

    Forum: Plugins
    In reply to: WordPress: Touched
    Thread Starter darkcryst

    (@darkcryst)

    LOL

    No that is me. I’m on Fnet. Actually I don’t think I’ve ever seen a DarkCryst that isn’t me turn up. What’s your nick on Fnet?

    Yes there is.. many many ways.

    Google for “Opentype converter” or similar. Almost any modern font tool will convert it.

    The problem with php using opentype is that the bundled GD library that creates the images with php doesn’t support OpenType (only truetype).. therefore no chance of WP or any PHP app using it.

    Fontlab works for this, as do many other products.

    well you’d need to have a style.css for the Theme details to be read, but there’s no reason why one PHP file couldn’t be used. it would be an ugly nasty way of doing it I would think, and slower and fraught with more problems than the CSS route… but there’s no real reason why not I guess…

    could you not jsut add the same spaces when you call that function?

    declare it as a global variable? that should rid the scope issues….

    Thread Starter darkcryst

    (@darkcryst)

    Ok… the permalinks aren’t exactly broken, but they aren’t exactly working.

    Wherever you see “(.+)” replace it with “([_0-9a-z-]+)” in the .htaccess and that “fixes” it, but only if you use english (or the basic 26 char english alphabet for posts anyhow).

    The long and the short of it, after much discussion with Ryan is that unless you have Apache 2, WP does not work out of the box for categories right now.

    I have the same problem – its the rewrite rules somewhere – because an older nightly works FINE.

    Bugged, pure and simple.

    Forum: Fixing WordPress
    In reply to: Why no GD?

    in brief – its not an idea that a)works all the time b) stops it all the time and c) it pisses off users of your site.

    Thread Starter darkcryst

    (@darkcryst)

    lawtai – tried that, as I realised there were some old rules in it.. same problem.

    jpettit – good suggestion, didn’t work, but while doing that I found out my problem! so thanks I guess ??

    It seems to throw a wobbly on my structure – category/year/post_name

    I remove the category and it works FINE.. which sucks because I specifically wanted category. Guess its a bug in the rules generation then…

Viewing 15 replies - 1 through 15 (of 51 total)