Search options (Page 45 of 307)

This is like the 5th topic on the subject

I was talking about in its current form, not in the form it was proposed in when Garciat was suggesting that we didn't have the ability to see that information in the first place
If it were switched to comments, it would simply make debugging more tedious. And it wouldn't address any of the other issues.

You can enable PUN_DEBUG if you want to see that information temporarily. It shows up in the footer. However, it's not recommended that you enable it for long periods of time because it also makes more detailed error messages show (in case errors start happening in your forum).

As Bekko pointed out, the behavior is no different. You just never experienced it because a default PunBB does not have any files in a subfolder.

lie: The PM mod would have its own search code, since otherwise it would have to rewrite every bit of backend code in search.php
And you need to be more specific if you're having issues, "it doesn't work" doesn't give me anything to test.

I can't know without knowing how your HTML/CSS was set up before: maybe someone with more CSS experience can

Well, one of the images relies on brdheader2, which doesn't exist.

Line 79 means it couldn't connect to the server: make sure you're passing the correct details (username, password, server address, database name).

Yes, search PunRes

There isn't a hook to output stuff right before

    <div class="main-head">
        <h2><span><?php echo htmlspecialchars($cur_forum['cat_name']) ?></span></h2>
    </div>

which is I assume what you're trying to do.
The stuff you directly edited in to the code is doing exactly what it's supposed to do if you follow how the code works. #1, 2, and 3 are before the block starting with

if ($pun_page['cur_category'] != 0)

so they output before that block outputs. #4 is correctly placed for what you want to do, since it's after that block.
If you think a hook there would be something useful and beneficial to a large number of people, you should request it in the hook request sticky.

Fixed

1. Yes, you could check out a copy of the code from SVN
2. Making SEF URLs. So, instead of going to search.php, you would go to search/. It's just changing how the URLs work.