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.
631
Off-topic / Re: Automagically De-Nesting Quotes
« on May 22nd, 2013, 01:12 AM »
Well, there's already an option in SMF (and has been for some time) to strip nested quotes so you'd only have the outermost quote in the first place. I am not sure if it is buggy or not (it is disabled here but I don't remember if it was just because it's not enabled in SMF by default or because we found a reason to disable it)
I see where you're going but I'm not entirely sure I like the look of it. Would be interested to see what other comments there are.
I see where you're going but I'm not entirely sure I like the look of it. Would be interested to see what other comments there are.
632
Features / Re: New revs
« on May 21st, 2013, 11:33 PM »
(9 modified, 4 deleted, 3KB)
Revision: 2128
Author: arantor
Date: 21 May 2013 22:33:05
Message:
! Meant to commit this deletion yesterday. (PackageGet.php)
! Streamlined the language editing area, there's no need for the settings page when it's all on the main languages page, including now setting which languages are selectable by users. This will need to be set on wedge.org. (Admin.php, Load.php, ManageLanguages.php, Admin and Help language files)
! Removed the 'add language' area. Languages tend to be a one-time thing, so it's OK to not have a super friendly interface. Allows decluttering of a bunch of code that would have needed a total rewrite anyway. (ManageLanguages.php, ManageLanguages.template.php, ManageSettings and Packages language files)
----
Modified : /trunk/Sources/Admin.php
Modified : /trunk/Sources/Load.php
Modified : /trunk/Sources/ManageLanguages.php
Deleted : /trunk/Sources/PackageGet.php
Modified : /trunk/Themes/default/ManageLanguages.template.php
Modified : /trunk/Themes/default/languages/Admin.english.php
Modified : /trunk/Themes/default/languages/Admin.french.php
Modified : /trunk/Themes/default/languages/Help.english.php
Modified : /trunk/Themes/default/languages/ManageSettings.english.php
Modified : /trunk/Themes/default/languages/ManageSettings.french.php
Deleted : /trunk/Themes/default/languages/Packages.english-uk.php
Deleted : /trunk/Themes/default/languages/Packages.english.php
Deleted : /trunk/Themes/default/languages/Packages.french.php
Revision: 2128
Author: arantor
Date: 21 May 2013 22:33:05
Message:
! Meant to commit this deletion yesterday. (PackageGet.php)
! Streamlined the language editing area, there's no need for the settings page when it's all on the main languages page, including now setting which languages are selectable by users. This will need to be set on wedge.org. (Admin.php, Load.php, ManageLanguages.php, Admin and Help language files)
! Removed the 'add language' area. Languages tend to be a one-time thing, so it's OK to not have a super friendly interface. Allows decluttering of a bunch of code that would have needed a total rewrite anyway. (ManageLanguages.php, ManageLanguages.template.php, ManageSettings and Packages language files)
----
Modified : /trunk/Sources/Admin.php
Modified : /trunk/Sources/Load.php
Modified : /trunk/Sources/ManageLanguages.php
Deleted : /trunk/Sources/PackageGet.php
Modified : /trunk/Themes/default/ManageLanguages.template.php
Modified : /trunk/Themes/default/languages/Admin.english.php
Modified : /trunk/Themes/default/languages/Admin.french.php
Modified : /trunk/Themes/default/languages/Help.english.php
Modified : /trunk/Themes/default/languages/ManageSettings.english.php
Modified : /trunk/Themes/default/languages/ManageSettings.french.php
Deleted : /trunk/Themes/default/languages/Packages.english-uk.php
Deleted : /trunk/Themes/default/languages/Packages.english.php
Deleted : /trunk/Themes/default/languages/Packages.french.php
633
Features / Re: Miscellaneous/WIP screenshots
« on May 21st, 2013, 08:36 PM »
So, finally getting round to a few things.
In particular, I'm getting shot of the language 'settings' page (since it only has two settings, one of which was already duplicated)
So, the main language page as shown now lets you select the default, as well as whether users get to play with choosing their own language and on top of that it also sorts out what language choices users can have.
Installing a language pack then becomes the job of dropping files into the languages folder then visiting this page to enable it, and this page to deselect a language pack. (In theory we could just bundle all the translations in a release and just let users enable the ones they want)
In particular, I'm getting shot of the language 'settings' page (since it only has two settings, one of which was already duplicated)
So, the main language page as shown now lets you select the default, as well as whether users get to play with choosing their own language and on top of that it also sorts out what language choices users can have.
Installing a language pack then becomes the job of dropping files into the languages folder then visiting this page to enable it, and this page to deselect a language pack. (In theory we could just bundle all the translations in a release and just let users enable the ones they want)
634
Features / Re: New revs
« on May 21st, 2013, 04:24 AM »
(14 modified, 1 deleted, crap I forgot one as Packages-Get should have died too, I'm blaming the rum, 3KB)
Revision: 2123
Author: arantor
Date: 21 May 2013 03:23:14
Message:
! Unnecessary extra globals. (Subs-Cache.php, Subs-Captcha.php)
! There's no need for the admin inclusion when in short order we proceed to run a hook which can actually *do* something anyway. (Admin.php)
! We have loadSource, let's use it. And just for kicks, since a bunch of array('file', 'function') had the same things, I made it into just array('file'). Could even have gone really mad and made it a string but that seemed like one step too far, you know? After all, I only wanted to get shot of the use of $sourcedir, everything else just sort of 'happened'. (index.php)
! I finally realised that there really was no need to keep the random stuff around for the old package manager, if I wanted it, I had SVN but really there wasn't much I thought I might have found useful, so removed a bunch of stuff. There are still tendrils elsewhere that haven't been cleaned up yet, but I'm getting to it. (Admin.php, PackageGet.php, Security.php, Subs-Package.php, Packages.template.php, language files: Admin, Errors, Packages, Who)
----
Modified : /trunk/Sources/Admin.php
Modified : /trunk/Sources/Security.php
Modified : /trunk/Sources/Subs-Cache.php
Modified : /trunk/Sources/Subs-Captcha.php
Modified : /trunk/Sources/Subs-Package.php
Deleted : /trunk/Themes/default/Packages.template.php
Modified : /trunk/Themes/default/languages/Admin.english.php
Modified : /trunk/Themes/default/languages/Admin.french.php
Modified : /trunk/Themes/default/languages/Errors.english.php
Modified : /trunk/Themes/default/languages/Errors.french.php
Modified : /trunk/Themes/default/languages/Packages.english.php
Modified : /trunk/Themes/default/languages/Packages.french.php
Modified : /trunk/Themes/default/languages/Who.english.php
Modified : /trunk/Themes/default/languages/Who.french.php
Modified : /trunk/index.php
Revision: 2123
Author: arantor
Date: 21 May 2013 03:23:14
Message:
! Unnecessary extra globals. (Subs-Cache.php, Subs-Captcha.php)
! There's no need for the admin inclusion when in short order we proceed to run a hook which can actually *do* something anyway. (Admin.php)
! We have loadSource, let's use it. And just for kicks, since a bunch of array('file', 'function') had the same things, I made it into just array('file'). Could even have gone really mad and made it a string but that seemed like one step too far, you know? After all, I only wanted to get shot of the use of $sourcedir, everything else just sort of 'happened'. (index.php)
! I finally realised that there really was no need to keep the random stuff around for the old package manager, if I wanted it, I had SVN but really there wasn't much I thought I might have found useful, so removed a bunch of stuff. There are still tendrils elsewhere that haven't been cleaned up yet, but I'm getting to it. (Admin.php, PackageGet.php, Security.php, Subs-Package.php, Packages.template.php, language files: Admin, Errors, Packages, Who)
----
Modified : /trunk/Sources/Admin.php
Modified : /trunk/Sources/Security.php
Modified : /trunk/Sources/Subs-Cache.php
Modified : /trunk/Sources/Subs-Captcha.php
Modified : /trunk/Sources/Subs-Package.php
Deleted : /trunk/Themes/default/Packages.template.php
Modified : /trunk/Themes/default/languages/Admin.english.php
Modified : /trunk/Themes/default/languages/Admin.french.php
Modified : /trunk/Themes/default/languages/Errors.english.php
Modified : /trunk/Themes/default/languages/Errors.french.php
Modified : /trunk/Themes/default/languages/Packages.english.php
Modified : /trunk/Themes/default/languages/Packages.french.php
Modified : /trunk/Themes/default/languages/Who.english.php
Modified : /trunk/Themes/default/languages/Who.french.php
Modified : /trunk/index.php
635
Features / Re: Splitting a topic, keeping the origin
« on May 20th, 2013, 11:26 PM »
Yeah, that's something I hadn't quite figured out what to do with.
It's one of those things that will likely be useful to a lot of forums and a pain in the backside to a lot of others - but I think it's useful enough for the bulk that it be a feature included.
It's one of those things that will likely be useful to a lot of forums and a pain in the backside to a lot of others - but I think it's useful enough for the bulk that it be a feature included.
636
Features / Splitting a topic, keeping the origin
« on May 20th, 2013, 08:52 PM »
OK, so this came up on sm.org earlier and a topic that was split ended up losing some context because of it.
I wondered, then, if it would be of use to keep the origin topic in a split. In the newly split topic, keep a reference to the original topic and provide a link back, ideally not as part of the message body itself.
We have per-message data storage, it's no big deal to get that and stuff a link to the old topic inside the first post of the new one.
I figure that if it wasn't part of the message body, there's no way it could be accidentally deleted by a moderator.
Thoughts?
I wondered, then, if it would be of use to keep the origin topic in a split. In the newly split topic, keep a reference to the original topic and provide a link back, ideally not as part of the message body itself.
We have per-message data storage, it's no big deal to get that and stuff a link to the old topic inside the first post of the new one.
I figure that if it wasn't part of the message body, there's no way it could be accidentally deleted by a moderator.
Thoughts?
637
Off-topic / Re: Doctor Who
« on May 20th, 2013, 06:06 AM »
I have a different outlook on it to you. I liked it. But yes, I would agree that it wasn't as epic as it could have been, seemed to me to have a lot of great ideas that were so underutilised.
Colin Baker is only really lamentable in respect of the writing; it isn't him, as such, it's the way he was written, though Trial of a Time Lord did sort of redeem it a little to me.
Actually, what happened in terms of Clara/TARDIS/One isn't inconsistent with canon. It takes a liberty with it, but it doesn't change its substance. But it was a less than brilliant piece of storytelling.
What I will say is that this episode had an awful lot of callbacks for the fans, and it was definitely trying to be too clever for its own good. But I liked it, all in all. There were some interesting ideas never explored before, but some of the best ideas they had do actually violate canon to a point.
(click to show/hide)
As for the aforementioned female character... yes, she was annoying. Yes, given canon she wasn't quite who she was, but that doesn't give her the right to be annoying.
Colin Baker is only really lamentable in respect of the writing; it isn't him, as such, it's the way he was written, though Trial of a Time Lord did sort of redeem it a little to me.
Actually, what happened in terms of Clara/TARDIS/One isn't inconsistent with canon. It takes a liberty with it, but it doesn't change its substance. But it was a less than brilliant piece of storytelling.
What I will say is that this episode had an awful lot of callbacks for the fans, and it was definitely trying to be too clever for its own good. But I liked it, all in all. There were some interesting ideas never explored before, but some of the best ideas they had do actually violate canon to a point.
The idea of the TARDIS dying and leaking the 'bigger on the inside' to the outside does not fit with canon. It's the first time this has ever been mentioned, and contradicts what Nine said to Rose as part of Emergency Program One when it took her off the Dalek craft, that she should just leave the TARDIS there, and no-one will notice it and it'll just become part of the world. I think people would notice.
As for the aforementioned female character... yes, she was annoying. Yes, given canon she wasn't quite who she was, but that doesn't give her the right to be annoying.
638
Off-topic / Re: Excuses for turniing off all Personal Messages
« on May 20th, 2013, 02:13 AM »My reasoning to them was that spammers won't waste time PMing each member because it's very inefficient. Better to get an ad in a signature or post so it can be there for all to reach.
If that's the issue then all I ask is of them is honesty - not some lame excuse that spammers are PMing all the members.
About ~100 spammer membernames who just happened to have a birthday every day. Go figure. I told them about it and they turned it off but I never got any thanks for it.
Do you personally think that a declaration should be in the registration agreement by default that it's possible that personal messages could be read by Admins who have access to Cpanel? I.e., there is no inherent security of member's PMs?
639
Off-topic / Re: Excuses for turniing off all Personal Messages
« on May 20th, 2013, 01:51 AM »
I've had PM spam, on sm.org. I still get people asking for help because they can't read my signature or somehow think it doesn't apply to them, though it's not as bad as it used to be.
I do know that some forums get a lot of PM spam, and that it's actually worse on some platforms than others (phpBB historically had a much higher incidence of PM spam than SMF has, as platforms) but I have no reason as to *why* that should be. Maybe they had a spate of it a while ago and blocked it against future occurrences, which is a valid way to go about things.
More broadly, there is an argument - which is also valid, I'll add - that as the host, they are responsible for content that is on their domain. Businesses are naturally more sensitive to 'liability' and take the view that if they can't see it (like SMF, phpBB frowns on viewing PMs), they could be liable for it if it is illegal, so prevent it. It may be that the spam issue was enough to encourage them to just stop it in all cases.
(Wedge makes it crazy-easy to do so, btw. There's a button to turn off PMs entirely should folks want to do so, but there are reasons why that's there, and they're not for spam.)
I do know that some forums get a lot of PM spam, and that it's actually worse on some platforms than others (phpBB historically had a much higher incidence of PM spam than SMF has, as platforms) but I have no reason as to *why* that should be. Maybe they had a spate of it a while ago and blocked it against future occurrences, which is a valid way to go about things.
More broadly, there is an argument - which is also valid, I'll add - that as the host, they are responsible for content that is on their domain. Businesses are naturally more sensitive to 'liability' and take the view that if they can't see it (like SMF, phpBB frowns on viewing PMs), they could be liable for it if it is illegal, so prevent it. It may be that the spam issue was enough to encourage them to just stop it in all cases.
(Wedge makes it crazy-easy to do so, btw. There's a button to turn off PMs entirely should folks want to do so, but there are reasons why that's there, and they're not for spam.)
641
Features / Re: New revs - Public comments
« on May 18th, 2013, 10:26 PM »I should be able to get a proper list of permissions, global and per board (and per album), for any given member, with a section in their profile area..
It gives you the general permissions and the 'all boards' permissions but lets you select different boards from a dropdown.
In the radio box list, I'd personally use dropdowns with an icon on each (green for enabled or enabled_own, red for disabled, another green or some blue for enabled_any). Sure, it's an extra click to change a permission, but then you can add deny permissions, right..? Unless you want to add deny for _own and _any separately, in which case, err...
If deny permissions weren't an option, I'd do what I did in SimpleDesk which was dropdowns with nice icons.
- I'd like to see the membergroups ajaxified... i.e. when clicking the link to modify their permissions, have it load under the permission name instead, so that you can even load multiple membergroups on one page, and then change them all in a row...
642
Features / Re: New revs - Public comments
« on May 18th, 2013, 07:44 PM »
There are probably other array_intersect calls, sure.
As far as permissions, it's long been on my plan to adjust how permissions were loaded and tested (to use isset rather than in_array) but that was part of the permissions overhaul and until I figure out how to make the UI, I won't be touching that.
As far as permissions, it's long been on my plan to adjust how permissions were loaded and tested (to use isset rather than in_array) but that was part of the permissions overhaul and until I figure out how to make the UI, I won't be touching that.
643
Archived fixes / Re: Error Message Displayed When Replying
« on May 18th, 2013, 07:29 PM »
Thanks :)
I did edit out the full path but I'm sure we'll get into that shortly enough.
I did edit out the full path but I'm sure we'll get into that shortly enough.
644
The Pub / Re: Looking for volunteers to test the Wedge private alpha!
« on May 18th, 2013, 03:24 AM »
It's almost like a self-selecting opt-out for access :niark:
645
The Pub / Re: Looking for volunteers to test the Wedge private alpha!
« on May 18th, 2013, 03:20 AM »
Yup. In fact, the people that will likely be added to the list come the next round of alphas haven't really posted on this topic... funny that. I'm sure I have no idea why that might be.