Bug Lots of Undefined offset: 813xxx errors

[dzeanah]

Seeing lots of these errors:

Server Error Logs
Server Error Logs
Delete...
Undefined offset: 813178
4 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813209
4 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813178
14 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813209
14 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813178
24 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813209
24 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813401
24 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813178
34 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813209
34 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813401
34 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813178
44 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813209
44 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813401
44 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813178
53 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813209
53 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813401
53 minutes ago - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813178
Today at 1:20 AM - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813209
Today at 1:20 AM - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813401
Today at 1:20 AM - library/DBTech/Mail/Newsletter.php:256
Delete...
Undefined offset: 813178
Today at 1:10 AM - library/DBTech/Mail/Newsletter.php:256

 

[Fillip H.]

Added a hotfix for that to v3.2.1

 

[dzeanah]

Awesome. Installing it now.

 

[dzeanah]

And that apparently made the error messages go away, but now every digest test I run kicks out "There are no threads to display. "

Settings unchanged from what was working before, so I've just disabled the digest for now. I created the thread and redid the test to see the same output.

Thoughts?

 

[Fillip H.]

If the user has already received the Digest for this week, it won't correctly generate one again until the next scheduled run. Or am I misunderstanding what exactly you mean?

 

[dzeanah]

Maybe I wasn't clear. I had 186 pages of those error messages, and something like 8 digests actually went out. Now that I've installed the new version, when I test the digest either as a test, or as a test applied to a user I know hasn't logged in for years, instead of a list of threads the content is "There are no threads to display. "

 

[dzeanah]

More information: if I sort by replies then the test digest works correctly. If I choose Advanced Sorting then the output is "There are no threads to display. "

So something about advanced sorting isn't working.

 

[Fillip H.]

Just to be clear, the prediction will only fetch content from the past week, whereas disabling the prediction will fetch all threads since the last time the user received the newsletter.

 

[dzeanah]

Just to be clear, the prediction will only fetch content from the past week, whereas disabling the prediction will fetch all threads since the last time the user received the newsletter.

Maybe it's time for a new thread.

My bug report is that Advanced Sorting results in zero threads, not just those from the past week.

This problem started in the most recent version of the script, downloaded and installed this week. Prior to that the function worked as you explained.

 

[Fillip H.]

After some testing I found that this will only happen if only one thread has been posted in in the past week, and the view counter of that thread has not updated yet. As this is not a critical issue I won't be hotfixing this, the fix will be in a future update

 

[DragonByte Technologies]

Hello dzeanah,

This ticket has now been closed with the status Fixed.

We hope your issue or question has been addressed to your satisfaction. If not, please feel free to re-open it by clicking this link.

If you have any further issues or questions, please feel free to start a new support ticket via the button at the top of every page.

Thank you!