Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Arantor
2431
Plugins / Re: Calendar
« on November 13th, 2012, 05:01 PM »
A funny thing happened to me just now, which goes to show how long it's been since I looked at it - the last change predates my rewrite of the theme/member options stuff which was months ago... and it doesn't even let me install it as a result.
2432
Archived fixes / Re: Session writing
« on November 13th, 2012, 02:49 PM »
But not all the time either...
2433
Plugins / Re: Calendar
« on November 13th, 2012, 04:49 AM »
I'd rather be honest than fob you off with some misguided hope. It's a large plugin and it's never been one that I've been interested in, but when I get motivated, I'll go to town and make it work properly, and with some extra features. It's the same reason why it's not substantially changed in SMF in years either, because no-one who actually cares about the functionality uses it.
2434
Bug reports / Re: Double space bug in thoughts + others
« on November 13th, 2012, 01:53 AM »
OK, so I can't seem to reproduce the original main bug.
However, there are a few oddities. Firstly, if you AJAXively add a thought with a smiley, the smiley won't appear in the return, so it'll look like it just got removed, but a refresh shows it to be there. And of course editing works as expected with that smiley.
If a thought is saved with a double space, as mentioned the first space in any pair is converted to an nbsp, and that appears in the resultant thought. Fine, because that's how preparsecode works (so that double spacing after a period is honoured, for example), but it also means that if you edit that thought, it's shown in the editing part, because wherever the Edit button gets it from, it's not decoding that entity. I haven't tried it with other entities, though so it could have all manner of fun. Specifically, the entities that may have odd behaviour are nbsp, amp, lt, gt, apos, quot, and our old friend 039.
However, there are a few oddities. Firstly, if you AJAXively add a thought with a smiley, the smiley won't appear in the return, so it'll look like it just got removed, but a refresh shows it to be there. And of course editing works as expected with that smiley.
If a thought is saved with a double space, as mentioned the first space in any pair is converted to an nbsp, and that appears in the resultant thought. Fine, because that's how preparsecode works (so that double spacing after a period is honoured, for example), but it also means that if you edit that thought, it's shown in the editing part, because wherever the Edit button gets it from, it's not decoding that entity. I haven't tried it with other entities, though so it could have all manner of fun. Specifically, the entities that may have odd behaviour are nbsp, amp, lt, gt, apos, quot, and our old friend 039.
2435
Archived fixes / Re: Modify group does not show correct UI for board access
« on November 13th, 2012, 01:32 AM »
Anyone have any trouble with this?
I think it could be made more usable by putting in category headers and making them have selectors too (which would select all the boards in that category) but it seems to work...
Also, thought of the day: this should mean the old member_groups field could be removed. Except it can't because there's some old stuff related to privacy that this field still drives, though I have no idea if any of it works or what it does if it does work.
I think it could be made more usable by putting in category headers and making them have selectors too (which would select all the boards in that category) but it seems to work...
Posted: November 13th, 2012, 01:29 AM
Also, thought of the day: this should mean the old member_groups field could be removed. Except it can't because there's some old stuff related to privacy that this field still drives, though I have no idea if any of it works or what it does if it does work.
2436
Archived fixes / Re: Modify board: "All groups who can see a board can enter it as well"
« on November 13th, 2012, 01:31 AM »
I want to mark it closed, but I'm still not sure about how the whole thing with per-board visibility rules wording would play out.
The nearest thing I can think of is similar to how it is in the Q&A UI where you can add different language questions... as far as storage goes, it's not a huge deal to take the per board information (provided you don't have way too many languages and way too long messages), serialize it into a TEXT in the boards table, though I can think it might be a performance hit when loading the board index.
The nearest thing I can think of is similar to how it is in the Q&A UI where you can add different language questions... as far as storage goes, it's not a huge deal to take the per board information (provided you don't have way too many languages and way too long messages), serialize it into a TEXT in the boards table, though I can think it might be a performance hit when loading the board index.
2437
Archived fixes / Re: Session writing
« on November 13th, 2012, 01:27 AM »* Arantor merged in one of the other bug reports - it's the same bug. No sense in being untidy.
2438
Archived fixes / Re: Grammatical Typo: Paid Subscriptions
« on November 13th, 2012, 01:19 AM »
Fixed locally, will commit in due course.
2439
Plugins / Re: Calendar
« on November 13th, 2012, 12:33 AM »Well... If I say I don't expect anything, there's a chance you'll never get to work on this. No offence intended.
Good then.
Is IPv6 usable?
And what about the board permission stuff? What if you commit a crappy UI for it, but a UI that actually works..?
2440
Archived fixes / Re: Session writing
« on November 13th, 2012, 12:21 AM »
Yup, I have it in the footer still. But I see no reason why it should be any different in different browsers >_>
2441
Plugins / Re: Calendar
« on November 12th, 2012, 11:43 PM »
:/ That sounds awfully like an expectation.
I'm working on the ban stuff, since while we can go to a private alpha without that, because I already warned everyone before it even got released, we cannot go to a public alpha without that. The ban system as it stands is actually broken, and it's incredibly complicated to design a completely new one, but I'm almost at a point where I can commit something for testing here.
I'm working on the ban stuff, since while we can go to a private alpha without that, because I already warned everyone before it even got released, we cannot go to a public alpha without that. The ban system as it stands is actually broken, and it's incredibly complicated to design a completely new one, but I'm almost at a point where I can commit something for testing here.
2442
Archived fixes / Re: Session writing
« on November 12th, 2012, 11:42 PM »
WTF is wrong with this? If Class-DB is loaded up front with everything, there is no reason for this to be broken.
2443
Plugins / Re: Calendar
« on November 12th, 2012, 03:58 PM »
It'll be finished when I can be bothered to make it work properly.
2444
Archived fixes / Re: RE Home
« on November 11th, 2012, 05:17 AM »
No... you set that in the wedge_settings table...
2445
Archived fixes / Re: Session writing
« on November 10th, 2012, 05:35 PM »
Wait a minute, there's way more issues here. westr_foundation should be declared as well even in a failed state if westr is declared since westr extends (eventually) westr_foundation.
I don't understand why wesql still fails to be loaded in those cases.
I don't understand why wesql still fails to be loaded in those cases.