Search options (Page 28 of 77)

I'm on PgSQL. Not sure if it's implemented the same way as MySQL.

Btw, the lack of an error message for the db error was a self inflicted coding injury.

I backported the prev_url setup to 1.2*, but it is with the same function & column setup as 1.3, in that regard. (I'll just double check to make sure I haven't made any changes to the basic premise, though). The prev_url column is varchar(255). A pagination link or suchlike with more than that length fails to insert due to the 255 max setting.

Just thought to check the SQL logs. It's the new get_current_url function combined with the online table which is causing the problem. The URI is too long to go in the prev_url column. (The error message wasn't displaying).

Edit: Just whilst on the subject, would there be a better way to supply the id's to the script other than in the pagination links?

That's not disagreeing. I just made a poor word choice. To rephrase somewhat. As you mention, it should continue looping. That is what I was meaning when I used the term bypass. To report the error is easy enough. It can easily be added to an anrray and reported after completion. For example, this is the mail looping I used in the email_topic form:

        foreach ($rclist as $recipient)
        {
                $recipient = trim($recipient);

                if (is_valid_email($recipient))
                {
                        $rcptlist[] = $recipient;
                        $recipient = $recipient.' <'.$recipient.'>';

                        if ($pun_config['o_smtp_host'] != '')
                        {
                                smtp_mail($recipient, $subject, $message, $headers);
                        }
                        else
                        {
                                mail($recipient, $subject, $message, $headers);
                        }
                }
                else
                {
                        $failedlist[] = $recipient;
                }
        }

with the recipient failure notice:

                if (isset($failedlist) && $failedlist != null)
                {
                        echo "\t\t\t".'<p>'.$lang['email']['Failed recipients'].' '.pun_htmlspecialchars(implode(', ', $failedlist)).'</p>'."\n";
                }

That type of code, added to the e-mail broadcast plugin inplace of the existing, would most likely, (with a bit of tweaking to explicitly catch the smtp errors too), do the job.

Whichever files where the I.P address is displayed. Off the top of my head, there is viewtopic.php, userlist.php, profile.php, but probably more.

Then the patch hasn't applied correctly, (which will happen if your forums are modified). Manually look at the patch and apply the changes in functions.php for the logout link.

Good to hear.

Create a test group, add a few test accounts to it and modify the db query in the plugin to only pull that and the banned groups info. Then you'll easily be able to tell that it is both doing the ban list bit correctly, and that it is indeed sending the e-mails correctly.

I'd not noticed the hard coded prefix. Thanks for pointing it out. I've updated the original code again accordingly. Is it working okay now, that code?

Btw, not sure on the other failure, offhand. I'll have a peek when I've chance.

Any chance you could post a copy of the code as it was when you modified that code? I'm curious now.

Plus, for the failure bit, changing this line:

pun_mail($mail_to, $mail_subject, $mail_message);

to

@pun_mail($mail_to, $mail_subject, $mail_message);

should, I believe, cause it to ignore/suppress the errors and continue.

Obviously, otherwise you wouldn't have created this thread. Again, post the link to your forum.