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 - Nao
1546
Archived fixes / Re: Reply to Blogs does not work on Blogs main page
« on February 7th, 2014, 05:33 PM »
All right! Looks like that's another Pete bug... :P
The link depends on what setting is enabled for Quick Reply, apparently. I'm guessing the quick reply boxes are open by default, in your regular forum topics..?
The link depends on what setting is enabled for Quick Reply, apparently. I'm guessing the quick reply boxes are open by default, in your regular forum topics..?
1547
Plugins / Re: Plugin suggestion - Prevent ALL CAPS
« on February 7th, 2014, 03:15 PM »
Nope, tested here (5.3) and on local (5.5)...
1548
Plugins / Re: Plugin suggestion - Prevent ALL CAPS
« on February 7th, 2014, 02:37 PM »
I'm having no problems on my side either.
Any posts, body contents, [A-Z]{6,}, case-sensitive, save... Done.
BTW, there really isn't an all-caps filter, out of the box. The one I gave above is really limited. I guess it's plugin material, then... :-/
Any posts, body contents, [A-Z]{6,}, case-sensitive, save... Done.
BTW, there really isn't an all-caps filter, out of the box. The one I gave above is really limited. I guess it's plugin material, then... :-/
1549
Archived fixes / Some thoughts on notifications
« on February 7th, 2014, 11:18 AM »
Just wanted to discuss two things in notifications... The user side has many questions, so get prepared!
- On the code side: yesterday, I was a bit disappointed that it took so long (about an hour) for me to re-figure out how the system worked. I was expected to re-use Like_Notifier for thoughts, but it wasn't possible because thoughts don't have a topic ID. I'm okay with that, as most notifications won't have this problem anyway, but still... Isn't this whole OOP code a TAD too complicated..? I know that Dragooon (who wrote the original code) likes it, but I'm just wondering if there couldn't be a simpler way of doing things. Or, at the very least, ensuring there are LESS files to play with... Seriously, I still can't grasp why there's Class-Notifier, Class-Notification, Notification and Notify PHP files. I'd be willing to accept two files, but four is a bit much for me...
As I'm not planning to add class auto-loading to Wedge (first and foremost because I don't like the idea! Laziness is for users, not developers!), we could at least merge all classes into one file. Like I did for Class-Skeleton.php, which has both the dynamic weSkeleton class, and the wetem static class which is build on it, and renders the whole damn page.
- On the user side: should I make notifications closer to the Facebook system..? Well, I don't know, but if there's one thing that I don't think is questionable in usability over at FB, it's notifications. I'm okay with them. In fact, current notifications in Wedge are closer to FB's than Dragooon's original implementation. But there are things that I want to get opinions on.
a) Is it better to decrease the notification count once you've previewed a notification and it's marked as read, OR to reset it to zero when you've opened the notification popup, like on Facebook..? Notifications would still show as unread and all, and I could even still show the unread count once the popup is opened, but maybe it would be easier to catch your attention when the counter turns orange from gray, rather than increasing from 6 to 7 while staying orange. I tend to remember my latest number of notifications, but... Well, I'm still at 25 unread notifications, and 20 unanswered PMs. (So, if you're wondering why I'm not answering your PM(s)... Please, I prefer forum posts, where it's easier for me to keep track of things, and reply with my phone if needed! The mobile skin has yet to do things about the PM template, it's just not usable on mobile right now.)
b) There's currently a small bug in grouped notifications. Again, this feature was implemented by Dragooon, and I haven't touched it at all (I think), and I think it's a good thing and all, but I'd rather see, in addition to what's already shown, the number of likes I've gotten since last time on a particular post, instead of just the name of the first liker. I think it would be swell. I don't remember if that number is stored, though, but I can always do something about that... However, UI-wise... If more than 1 like, should I show a name at all? Maybe '2 persons liked your post', and then if you click Preview, Wedge shows you a list of all recent likers, and then the preview of the post...? Or just show like now, just one name, and a number next to it? That would need explaining... Or show "Dragooon and 2 others liked your post"? But that one implies additional language strings, and for each of the notification types.
c) Should I add a 'Mark all as read' button at the bottom of the notification popup...?
d) I'm still planning for a 'Mark unread' button to show up below post previews in notifications, to revert an automatic markread. And a 'Mark read' below PM previews, to force a markread, obviously. What else should be there next to these options..?
- On the code side: yesterday, I was a bit disappointed that it took so long (about an hour) for me to re-figure out how the system worked. I was expected to re-use Like_Notifier for thoughts, but it wasn't possible because thoughts don't have a topic ID. I'm okay with that, as most notifications won't have this problem anyway, but still... Isn't this whole OOP code a TAD too complicated..? I know that Dragooon (who wrote the original code) likes it, but I'm just wondering if there couldn't be a simpler way of doing things. Or, at the very least, ensuring there are LESS files to play with... Seriously, I still can't grasp why there's Class-Notifier, Class-Notification, Notification and Notify PHP files. I'd be willing to accept two files, but four is a bit much for me...
As I'm not planning to add class auto-loading to Wedge (first and foremost because I don't like the idea! Laziness is for users, not developers!), we could at least merge all classes into one file. Like I did for Class-Skeleton.php, which has both the dynamic weSkeleton class, and the wetem static class which is build on it, and renders the whole damn page.
- On the user side: should I make notifications closer to the Facebook system..? Well, I don't know, but if there's one thing that I don't think is questionable in usability over at FB, it's notifications. I'm okay with them. In fact, current notifications in Wedge are closer to FB's than Dragooon's original implementation. But there are things that I want to get opinions on.
a) Is it better to decrease the notification count once you've previewed a notification and it's marked as read, OR to reset it to zero when you've opened the notification popup, like on Facebook..? Notifications would still show as unread and all, and I could even still show the unread count once the popup is opened, but maybe it would be easier to catch your attention when the counter turns orange from gray, rather than increasing from 6 to 7 while staying orange. I tend to remember my latest number of notifications, but... Well, I'm still at 25 unread notifications, and 20 unanswered PMs. (So, if you're wondering why I'm not answering your PM(s)... Please, I prefer forum posts, where it's easier for me to keep track of things, and reply with my phone if needed! The mobile skin has yet to do things about the PM template, it's just not usable on mobile right now.)
b) There's currently a small bug in grouped notifications. Again, this feature was implemented by Dragooon, and I haven't touched it at all (I think), and I think it's a good thing and all, but I'd rather see, in addition to what's already shown, the number of likes I've gotten since last time on a particular post, instead of just the name of the first liker. I think it would be swell. I don't remember if that number is stored, though, but I can always do something about that... However, UI-wise... If more than 1 like, should I show a name at all? Maybe '2 persons liked your post', and then if you click Preview, Wedge shows you a list of all recent likers, and then the preview of the post...? Or just show like now, just one name, and a number next to it? That would need explaining... Or show "Dragooon and 2 others liked your post"? But that one implies additional language strings, and for each of the notification types.
c) Should I add a 'Mark all as read' button at the bottom of the notification popup...?
d) I'm still planning for a 'Mark unread' button to show up below post previews in notifications, to revert an automatic markread. And a 'Mark read' below PM previews, to force a markread, obviously. What else should be there next to these options..?
1550
Archived fixes / Re: Reply to Blogs does not work on Blogs main page
« on February 7th, 2014, 10:58 AM »
I'm afraid I'm not seeing any difference between posts without replies and posts with... They're both leading to the proper reply page.
Can't you just post what your link points to, and what shows up in the end..? Blog homepage, or blog post's page..?
Can't you just post what your link points to, and what shows up in the end..? Blog homepage, or blog post's page..?
1551
Plugins / Re: Plugin suggestion - Prevent ALL CAPS
« on February 7th, 2014, 12:31 AM »
Not a very good day for me... But my health has been failing me these last couple of weeks. I should be consulting but my doctor's queue waiting time is usually > 1 hour, and I don't have time to 'waste' on that.
1552
Archived fixes / Re: error 2035 on media player in linked topics
« on February 7th, 2014, 12:29 AM »
It's the Flash stuff... You need to ensure everything's on the same domain, or you provide a crossdomain.xml policy file.
Or it's a firewall problem.
#1 reported bug on Aeva Media (whether it be mass upload or the media player...), since 2009. And the thousand times I got told that, I answered the same.
PS: what a strange illustration of your problem... 'faecal matter can be seen in the bowel'. :lol:
Or it's a firewall problem.
#1 reported bug on Aeva Media (whether it be mass upload or the media player...), since 2009. And the thousand times I got told that, I answered the same.
PS: what a strange illustration of your problem... 'faecal matter can be seen in the bowel'. :lol:
1553
Plugins / Re: Plugin suggestion - Prevent ALL CAPS
« on February 7th, 2014, 12:27 AM »
And of course, that error message is sent on 9 different places in the ManageModeration code... Nice, it'll make it so easy to trace... ::)
1554
Features / Re: New revs
« on February 7th, 2014, 12:23 AM »
[Commit revision 3231132]
Author: Nao
Date: Thu, 06 Feb 2014 23:20:25 +0100
Stats: 6 files changed; +56 (insertions), -16 (deletions)
[Commit revision c0db789]
Author: Nao
Date: Fri, 07 Feb 2014 00:08:19 +0100
Stats: 2 files changed; +1 (insertion), -5 (deletions)
[Commit revision a54e87f]
Author: Nao
Date: Fri, 07 Feb 2014 00:14:22 +0100
Stats: 1 file changed; +2 (insertions), -0 (deletion)
[Commit revision de470ad]
Author: Nao
Date: Fri, 07 Feb 2014 00:23:10 +0100
Stats: 1 file changed; +3 (insertions), -3 (deletions)
Author: NaoDate: Thu, 06 Feb 2014 23:20:25 +0100
Stats: 6 files changed; +56 (insertions), -16 (deletions)
- Added notifications for Thought likes. (Like.php, Notifications.php, notifiers/Likes.php, Notifications.template.php, Notifications.english.php, script.js)
- Seriously, 6 files and lots of code just for a tweak to the Post Like code...? It seems like overkill to me, but I've been unable to find a cleaner way to do it. Meh...
Posted: February 6th, 2014, 11:20 PM
[Commit revision c0db789]
Author: NaoDate: Fri, 07 Feb 2014 00:08:19 +0100
Stats: 2 files changed; +1 (insertion), -5 (deletions)
- Fixed undefined index error. Hopefully. (notifiers/Likes.php)
- Minor revert for a syntax error, and a styling issue. (index.css)
Posted: February 7th, 2014, 12:08 AM
[Commit revision a54e87f]
Author: NaoDate: Fri, 07 Feb 2014 00:14:22 +0100
Stats: 1 file changed; +2 (insertions), -0 (deletion)
- Just because a notification has no preview doesn't mean it shouldn't be harder to dismiss... (script.js)
Posted: February 7th, 2014, 12:15 AM
[Commit revision de470ad]
Author: NaoDate: Fri, 07 Feb 2014 00:23:10 +0100
Stats: 1 file changed; +3 (insertions), -3 (deletions)
- Apologies for the bad fix, I'm very tired. And ill. This one should work better. (script.js)
1555
Plugins / Re: Plugin suggestion - Prevent ALL CAPS
« on February 7th, 2014, 12:04 AM »
Oh, bugger... Any rule?
I have rules on wedge.org... How did I manage to add them, them..? :^^;:
I have rules on wedge.org... How did I manage to add them, them..? :^^;:
1556
Plugins / Re: Plugin suggestion - Prevent ALL CAPS
« on February 6th, 2014, 11:52 PM »
I believe it's already available in the Moderation Filter area... ;)
Not 100% sure, but Pete mentioned working on that at one point.
Not 100% sure, but Pete mentioned working on that at one point.
1557
Features / Language revs
« on February 6th, 2014, 11:22 PM »
[Commit revision eb95cfe]
Author: Nao (Signed-off)
Date: Thu, 06 Feb 2014 23:21:48 +0100
Stats: 2 files changed; +11 (insertions), -3 (deletions)
Author: Nao (Signed-off)Date: Thu, 06 Feb 2014 23:21:48 +0100
Stats: 2 files changed; +11 (insertions), -3 (deletions)
- Thought like notifications. (Notifications)
1558
The Pub / Re: Should Mods be removed before migration?
« on February 6th, 2014, 10:35 PM »
No, it doesn't matter...
Forums aren't migrated. You're effectively creating a second forum, in a different folder, where you then import your SMF data, allowing you to compare both systems and decide which one to keep.
If you want to stay on Wedge, you'll then need to rename your SMF folder to something else, move your Wedge folder over there, and proceed to update your internal URLs to point to the correct positions.
Forums aren't migrated. You're effectively creating a second forum, in a different folder, where you then import your SMF data, allowing you to compare both systems and decide which one to keep.
If you want to stay on Wedge, you'll then need to rename your SMF folder to something else, move your Wedge folder over there, and proceed to update your internal URLs to point to the correct positions.
1559
Features / Language revs
« on February 6th, 2014, 06:42 PM »
[Commit revision 886b0e9]
Author: Nao (Signed-off)
Date: Thu, 06 Feb 2014 18:41:32 +0100
Stats: 3 files changed; +0 (insertion), -3 (deletions)
[Commit revision 860b854]
Author: Nao
Date: Thu, 06 Feb 2014 18:41:47 +0100
Stats: 1 file changed; +1 (insertion), -1 (deletion)
Author: Nao (Signed-off)Date: Thu, 06 Feb 2014 18:41:32 +0100
Stats: 3 files changed; +0 (insertion), -3 (deletions)
- Session-based cache string removed. (ManageSettings)
[Commit revision 860b854]
Author: NaoDate: Thu, 06 Feb 2014 18:41:47 +0100
Stats: 1 file changed; +1 (insertion), -1 (deletion)
- Merge branch 'master' of https://github.com/Wedge/languages
1560
Off-topic / Re: PHP | Learning
« on February 6th, 2014, 06:40 PM »
Err... Well, I don't comment it a lot... In fact, apparently I'm in the 10% worst open source projects when it comes to the comment ratio. Wedge has about 10% of comments versus code, SMF has close to 20%, and Elk has something like 21%. Honestly, I don't know why our numbers are so low, but I suspect it's also due to the fact that out headers are shorter... :P Okay, maybe not that much...
Also, if you don't like PHP, you could stick to JavaScript. You can perfectly run a website using only HTML and JavaScript, even a dynamic one, using Node.js, which is a cool server.
Also, if you don't like PHP, you could stick to JavaScript. You can perfectly run a website using only HTML and JavaScript, even a dynamic one, using Node.js, which is a cool server.