Still not fixed.

The action you performed has failed.
Reasons(s) returned:
» Version 6 and version 5 folder cache mismatch. System policy was: Use version 6 data if available. (Everything should have worked fine.)


I can't delete messages because of it.

It was fixed and that message was left there for DTBK when he fixed it, but now it is broken again. I believe that since it was working when that message was up, that message has nothing to do with it breaking again. I could be wrong though.

You can either have deletable PMs or removable notices, not both. If I have time I might add a thing to switch modes, but actually fixing this would take a complete overhaul of the core.

Quote from DT_Battlekruser

You can either have deletable PMs or removable notices, not both. If I have time I might add a thing to switch modes, but actually fixing this would take a complete overhaul of the core.

Deletable PMs, thx.

What the hell made this break, anyways? It was perfectly fine when I came to SEN...

IP has been working on and off on SEN v6 for a while. He decided not too long ago that it may be easier to just implement what he had done so far into the existing code. Doing so broke a few things on the site.

http://www.staredit.net/topic/13414/#283345

Since I can't PM you... you have my permission/serious justification/etc. I half deleted it I think so I can't get to it but it didn't actually delete apparently.

What? I have your permission to do what?

Find the PM I'm referring to that I sent to Jack and edit into my OP in that topic.

I can't access it.

I'm not going to do that, sorry.

Broken notices were also causing fatal SQL errors after a time.

The problem is that IP updated about half of the core of SEN to v6, so on some pages and functions the core data follows one paradigm and on others it follows a different paradigm. This wreaks havoc with any function which is called from the core, and despite my best efforts I haven't been able to find a way of determining from within the function which paradigm is correct. The only real solution to this is to fix the core and make it consistent, but I don't have much time to do that.

On the other hand, could we theoretically look for a backup of 5.0 (or 5.1) prior to IP's changes and just revert it? Or would that cause more issues? I believe Devourer may have a backup, unless he got rid of it after he stopped coding.

But I like the speed. D:

There isn't any way to make a cross between the two paradigms?

Could you maybe announce a day when you will switch over to fixing PM counts, so everyone can fix their PM space, and then switch back to the notices setup?

Should be fixed!
Please give me feedback.

Awesome work, Devourer; it's almost working now!

Deleting PMs updates the count, but it still thinks I have more PMs than I do. My inbox only had 32 messages, but said I had 101. I deleted 2 and the count changed to 99.

I have 4 pages for my inbox, but page 2, 3 and 4 are empty because I don't actually have that many messages.

Huge problem is that the count is relative to the count before. It does not recheck the actual count via a sql loop. This causes lag so I will activate that once -> works for everyone, yet I first want to ensure that all is working.

You flipped the switch - messages are fixed but notices are broken again. I hope the SQL errors will be stopped by the die() branch I have in there, but we'll see.

Devourer closed and reopened a topic of mine to test this, and I got the notices for them (and they disappeared). So unless something changed since this morning, they should theoretically work.

I flipped the flipped switch. Messages do not disappear.
IP, seriously...?

I never understood the way he codes some spefici things. Doing weird stuff which could have been done easier.
I dunno whether I will find the solution or the bug in it's origin.