Show Likes
This section allows you to view all posts where this member received or gave a like to.
1
[Commit revision 405bed2]
Author: Nao
Date: Sat, 16 Aug 2014 23:39:50 +0200
Stats: 2 files changed; +39 (insertions), -44 (deletions)
[Commit revision 588b05f]
Author: Nao
Date: Sun, 17 Aug 2014 00:00:51 +0200
Stats: 1 file changed; +6 (insertions), -0 (deletion)
[Commit revision 96ea5ec]
Author: Nao
Date: Sun, 17 Aug 2014 00:16:49 +0200
Stats: 1 file changed; +5 (insertions), -1 (deletion)
[Commit revision 903402e]
Author: Nao
Date: Sun, 17 Aug 2014 00:21:41 +0200
Stats: 3 files changed; +90 (insertions), -53 (deletions)
[Commit revision 755ae02]
Author: Nao
Date: Sun, 17 Aug 2014 00:34:54 +0200
Stats: 2 files changed; +55 (insertions), -25 (deletions)
[Commit revision 4ba1ebf]
Author: Nao
Date: Sun, 17 Aug 2014 00:47:11 +0200
Stats: 3 files changed; +188 (insertions), -60 (deletions)
Date: Sat, 16 Aug 2014 23:39:50 +0200
Stats: 2 files changed; +39 (insertions), -44 (deletions)
- Got rid of the privacy icon sprite and all that stuff. Instead of a key, I'm now showing something that takes a lot less CSS, and should work on any device: an inverted 0xb6 (paragraph) character. Plus, flat design! (index.member.css, privacy.png) (privacy.gif got deleted earlier today, should have done it in this one.)
- Some extra CSS for an upcoming commit. (index.member.css)
- Privacy icons are now shown the same way as smileys are, i.e. they align with their current neighbors, but this also implies some HTML changes, which will be coming soon. (index.member.css)
[Commit revision 588b05f]
Date: Sun, 17 Aug 2014 00:00:51 +0200
Stats: 1 file changed; +6 (insertions), -0 (deletion)
- Privacy! (index.english.php)
- Colons! (index.english.php)
[Commit revision 96ea5ec]
Date: Sun, 17 Aug 2014 00:16:49 +0200
Stats: 1 file changed; +5 (insertions), -1 (deletion)
- Wuthering header fix for oldIE. (Wuthering/extra.css)
[Commit revision 903402e]
Date: Sun, 17 Aug 2014 00:21:41 +0200
Stats: 3 files changed; +90 (insertions), -53 (deletions)
- Added $().title() function to allow for HTML tooltips using the mini-menu system. I'm committing it separately mostly because I want to keep my options open: I'm not sure this is such a fantastic feature. Perhaps setting a trigger timer would be best, but it might make the code more complicated. Or, showing the tooltip on the right rather than the top, but... This time, the CSS would be more complicated. (script.js, index.css)
- While I'm at it -- fixing <dl> tags imposing a hidden overflow just so they could clearfix, when I really should have applied the proper clearfix mixin here. (index.css, sections.css)
[Commit revision 755ae02]
Date: Sun, 17 Aug 2014 00:34:54 +0200
Stats: 2 files changed; +55 (insertions), -25 (deletions)
- Now, increasing the select box code by 5%, THAT I can accept, if it allows me to add support for the 'multiple' parameter in dropdowns! Seriously. (sbox.js, index.css)
- An interesting feature that I cooked up and isn't part of the 'official' HTML description of <select multiple>: just add a class named 'single' to any option that you want to be 'exclusive', i.e. clicking it will automatically 'unclick' all other items. I've never used so many 'single quotes' in a sentence before.
- There are still a few rough edges: multiple selected items can be rendered with multiple .selected classes when opening a select box; also, there is currently no keyboard support for a 'multiple' dropdown, you can only open and close it without a pointer.
[Commit revision 4ba1ebf]
Date: Sun, 17 Aug 2014 00:47:11 +0200
Stats: 3 files changed; +188 (insertions), -60 (deletions)
- And finally, THIS is the BIG ONE, the high point of all my last couple of weeks' commits. Go to your profile summary, click any heading that has a privacy icon next to icon, and you get to choose who can view said information. You can choose multiple (yay!) groups and/or lists, or just one of the simplified settings: guests & members, just members, or just yourself. (Profile.php, Security.php, Profile.template.php)
- Privacy settings are only applied on public profile pages, so any other area that shows that information won't bother. I'm thinking, maybe the search feature allows you to access some of these details, so I may have to find a way to ignore forbidden settings, but as I'm currently storing privacy data into the members table, I'm not sure I can do that easily. Soon I'll be porting privacy data to a new table, I just need to think of its structure or something... I need it to be extendable (extensible?), obviously.
- The tooltip indicates who can see what, but it's still quite limited to the first of all items in a privacy setting, *and* it won't tell you what group or list exactly. Whatever...
- Contact list save button wasn't translated. (Profile.template.php)
- Using the new $txt[':'] system in the Profile template. Must use it everywhere else! (Profile.template.php)
2
[Commit revision 64aeb4c]
Author: Nao
Date: Sun, 06 Jul 2014 13:35:51 +0200
Stats: 1 file changed; +1 (insertion), -0 (deletion)
Date: Sun, 06 Jul 2014 13:35:51 +0200
Stats: 1 file changed; +1 (insertion), -0 (deletion)
- Recent Posts now honor privacy settings. (Recent.php)
- There are still probably many places where I need to do this kind of thing. I never looked much into it because the rest of the privacy system wasn't really ready until recently anyway. Also, I still have about 400KB of Noisen.com patches that I need to go through. All of the original {query_see_topic}'s are in there, but I was so conservative that I added it in way too many places.
3
Bug reports / [Topic privacy] Re: Messages are readable by guests
Nao « on July 6th, 2014, 03:05 PM »
Okay, I think I've found the reason for the problem...
- SMF 2.0 has these bits: topic.approved, and message.approved. If topic is not approved, the first message isn't either, IIRC, so in Recent Messages, the query basically checks for whether the message being retrieved is approved. If yes, then it shows it.
- However, in Wedge, we add topic privacy to the mix. Wedge moved it to {query_see_topic}, and I replaced all of the topic approved tests with a {query_see_topic}. BUT, here's the thing, a topic can be approved and its messages are still undesirable to the end user. So, in addition to {query_see_topic} on topic approvals, I should be doing it selectively on message approvals, replacing them with something else that takes topic privacy and message approval into account.
Not easy... So, I guess the safest way would be for me to go through the Noisen patch, and take it upon myself to ensure everything is implemented. I don't like the idea, but... It's better than a useless topic privacy feature, right..? ;)
- SMF 2.0 has these bits: topic.approved, and message.approved. If topic is not approved, the first message isn't either, IIRC, so in Recent Messages, the query basically checks for whether the message being retrieved is approved. If yes, then it shows it.
- However, in Wedge, we add topic privacy to the mix. Wedge moved it to {query_see_topic}, and I replaced all of the topic approved tests with a {query_see_topic}. BUT, here's the thing, a topic can be approved and its messages are still undesirable to the end user. So, in addition to {query_see_topic} on topic approvals, I should be doing it selectively on message approvals, replacing them with something else that takes topic privacy and message approval into account.
Not easy... So, I guess the safest way would be for me to go through the Noisen patch, and take it upon myself to ensure everything is implemented. I don't like the idea, but... It's better than a useless topic privacy feature, right..? ;)
4
Features / Re: Multiple Recycling Bins for different Categories/Boards?
Nao « on February 4th, 2014, 06:45 PM »Bumpcough, just an innocent reminder...
This week (and the next?), I'm trying to fix as many bugs as possible, so that I can release a proper public alpha package. A bunch of new features will hopefully come next, then I'll feature-freeze, go beta, fix bugs and do minor tweaks, go RC, fix bugs, and go stable.
That's my schedule...
This feature will probably get into Wedge before I feature-freeze, no worries, but I still have a lot of features I want to do before beta, so it's... kinda complicated.
5
Possibly a problem with how the file system is handled on your server. Sometimes, a web server has no direct access to the hard drive, it goes through an extra layer, and there's a short delay between the moment you write data, and the moment you can retrieve it.
In Wedge, loadSource will first get a /core/app/ source file, then strip its comments, save it to /gz/ (cache folder), and load that version. If the filesystem doesn't see the file as avaiable even though it was written, this could generate your error. Although, I think it should first generate an error saying the files wasn't found..? Maybe I'm not doing that.
PS: sorry guys, I'm not posting a lot these days. Please keep in mind that I'm working hard on many features of Wedge at the same time, and I just don't feel like discussing them because I don't know what will make it to the final cut.
In Wedge, loadSource will first get a /core/app/ source file, then strip its comments, save it to /gz/ (cache folder), and load that version. If the filesystem doesn't see the file as avaiable even though it was written, this could generate your error. Although, I think it should first generate an error saying the files wasn't found..? Maybe I'm not doing that.
PS: sorry guys, I'm not posting a lot these days. Please keep in mind that I'm working hard on many features of Wedge at the same time, and I just don't feel like discussing them because I don't know what will make it to the final cut.
6
rev 2332 -- phew -- here it is, the bigger part of the admin rewrite. There are still many things to commit, but the bulk is in here.
27 files changed, 509 insertions(+), 687 deletions(-), 9.09 KiB[1]
* Admin overhaul. It's all in a day's job for... (Admin.php, ManageAttachments.php, ManageMail.php, ManageMemberOptions.php, ManagePlugins.php, ManageServer.php, ManageSettings.php, Admin.template.php, index.template.php, ManageMembers.template.php, Admin.language.php, ManageSettings.language.php, Profile.language.php, likes.png, contributors.txt)
* Got rid of prepareServerSettingsContext, everything in the admin panel now uses the prepareDBSettingContext format.
* Updated comment that serves as documentation for the DB setting format in ManageServer.
* Moved Likes settings and generic Member settings to General Settings. Moved PM and Paid Subscriptions to the first menu. Moved Embeds back to Media (nostalgia!). Moved Search Engine options to Maintenance.
* Various fixes/simplifications to internal search.
- More unneeded globals.
- Removed forum_width setting; it's easy enough to do in skins: create a custom.css anywhere, add a '#wedge' line, hit Return, Tab, then type 'max-width: 80%' for instance. Save. Upload via FTP. Done, and it doesn't add clutter to your HTML.
+ Added support for big icons in setting titles. Added icons for Member settings and Likes settings; replaced ugly Likes logo with a new one.
* Member defaults page now develops all items from the start. I don't like the hover/click process, it's just too slow. Also emphasized Yes/No settings with color codes. Renamed that page from 'Member preferences' to 'Member options', although I'm also trying to stick the word 'defaults' into it, but, hmm...
* Simplified $db_show_debug handling. (Class-DB.php, Errors.php, Subs-Cache.php, Subs-Template.php, Subs.php, ViewQuery.php)
@ Note: have yet to commit files like Load.php, meaning that this commit will definitely break your Wedge. Just wait until I'm done!
27 files changed, 509 insertions(+), 687 deletions(-), 9.09 KiB[1]
* Admin overhaul. It's all in a day's job for... (Admin.php, ManageAttachments.php, ManageMail.php, ManageMemberOptions.php, ManagePlugins.php, ManageServer.php, ManageSettings.php, Admin.template.php, index.template.php, ManageMembers.template.php, Admin.language.php, ManageSettings.language.php, Profile.language.php, likes.png, contributors.txt)
* Got rid of prepareServerSettingsContext, everything in the admin panel now uses the prepareDBSettingContext format.
* Updated comment that serves as documentation for the DB setting format in ManageServer.
* Moved Likes settings and generic Member settings to General Settings. Moved PM and Paid Subscriptions to the first menu. Moved Embeds back to Media (nostalgia!). Moved Search Engine options to Maintenance.
* Various fixes/simplifications to internal search.
- More unneeded globals.
- Removed forum_width setting; it's easy enough to do in skins: create a custom.css anywhere, add a '#wedge' line, hit Return, Tab, then type 'max-width: 80%' for instance. Save. Upload via FTP. Done, and it doesn't add clutter to your HTML.
+ Added support for big icons in setting titles. Added icons for Member settings and Likes settings; replaced ugly Likes logo with a new one.
* Member defaults page now develops all items from the start. I don't like the hover/click process, it's just too slow. Also emphasized Yes/No settings with color codes. Renamed that page from 'Member preferences' to 'Member options', although I'm also trying to stick the word 'defaults' into it, but, hmm...
* Simplified $db_show_debug handling. (Class-DB.php, Errors.php, Subs-Cache.php, Subs-Template.php, Subs.php, ViewQuery.php)
@ Note: have yet to commit files like Load.php, meaning that this commit will definitely break your Wedge. Just wait until I'm done!
| 1. | I need to stop posting patch sizes. They have obviously nothing to do with actual patch sizes. This one is over 10x bigger than rev 2328 which has a bigger file size. |
7
The Pub / Re: Is the admin area in urgent need of an overhaul?
Pandos « on November 22nd, 2013, 07:11 PM »
YouI know I'll like General Settings :)
So for the new look & feel i think that the new Admin-Center should look like this:
General Settings:
All settings that are important to adminstrate the forum. This includes Maintenance, Caching, Timezone, Prettyurl's, Plugins, Themes/Skins, Search Engine-Tracking, News, Likes, Languages, Embedding and Plugins.
Forum:
All related stuff (leave it untouched instead of Antispam, Attachments, Avatars and Embedding).
Media:
Leave as it is. Plus Avatars and Attachments
Permssions:
Including Members, Registration, Infractions, Bans, Antispam, Permissions and Member Options
Server:
Only Server related things as DB, Load Balancing, Proxy Settings and Sessions.
So for the new look & feel i think that the new Admin-Center should look like this:
General Settings:
All settings that are important to adminstrate the forum. This includes Maintenance, Caching, Timezone, Prettyurl's, Plugins, Themes/Skins, Search Engine-Tracking, News, Likes, Languages, Embedding and Plugins.
Forum:
All related stuff (leave it untouched instead of Antispam, Attachments, Avatars and Embedding).
Media:
Leave as it is. Plus Avatars and Attachments
Permssions:
Including Members, Registration, Infractions, Bans, Antispam, Permissions and Member Options
Server:
Only Server related things as DB, Load Balancing, Proxy Settings and Sessions.
8
rev 2325
10 files changed, 36 insertions(+), 50 deletions(-), 2.16 KiB
! Unneeded or malformed params. (Aeva-Embed.php, Aeva-Foxy.php, ManageMedia2.php, Thoughts.php)
! Nao bug: AeMe didn't correctly get the inserted ID on playlists. (Aeva-Foxy.php)
! SMF bug: non-existent variable $type. Note: fixed in Elk, but not SMF 2.1. Also some bracketnazi. (Reports.php)
! Pete bug: search settings were broken by a hasty rewrite. (ManageSearch.php)
! Pete bug: yet another parenthesis problem, this one was in his very first commit for draft saving. Interesting. Just hoping this fix doesn't actually break the feature; in which case, at least I'll know what I need to remove. Also saving a few function calls if the draft is going to fail. (Subs-Post.php)
! Pete bug: $row['issued_by'], not $issued_by. (And yes, if you want to take your infraction code elsewhere, of course you don't have to bother about this bug fix.) (ModerationCenter.php)
! Pete bug: a single use of $db_connection instead of self::$_db_con since his very first commit of that class. I think the most amusing here is the irony of that bug being inside the function called serious_error. (Class-DB.php)
@ As in a few of the last commits, this changeset is mostly sponsored by hhvm-wrapper. A real life-saver, even if it took hours to get it to work...
10 files changed, 36 insertions(+), 50 deletions(-), 2.16 KiB
! Unneeded or malformed params. (Aeva-Embed.php, Aeva-Foxy.php, ManageMedia2.php, Thoughts.php)
! Nao bug: AeMe didn't correctly get the inserted ID on playlists. (Aeva-Foxy.php)
! SMF bug: non-existent variable $type. Note: fixed in Elk, but not SMF 2.1. Also some bracketnazi. (Reports.php)
! Pete bug: search settings were broken by a hasty rewrite. (ManageSearch.php)
! Pete bug: yet another parenthesis problem, this one was in his very first commit for draft saving. Interesting. Just hoping this fix doesn't actually break the feature; in which case, at least I'll know what I need to remove. Also saving a few function calls if the draft is going to fail. (Subs-Post.php)
! Pete bug: $row['issued_by'], not $issued_by. (And yes, if you want to take your infraction code elsewhere, of course you don't have to bother about this bug fix.) (ModerationCenter.php)
! Pete bug: a single use of $db_connection instead of self::$_db_con since his very first commit of that class. I think the most amusing here is the irony of that bug being inside the function called serious_error. (Class-DB.php)
@ As in a few of the last commits, this changeset is mostly sponsored by hhvm-wrapper. A real life-saver, even if it took hours to get it to work...
9
rev 2323 -- what's with the number 23 again?! I love this commit. It has so many fixes for details *important* to me.
8 files changed, 44 insertions(+), 46 deletions(-), 3.12 KiB
! This is my tentative fix for the infamous "quick edit just marked my post as unread, you silly!" bug... I'm pretty sure it's due to a settings caching problem (as I believe it only happens when the post you're editing is the latest in the forum *and* you've finished editing it within a minute of posting it in the first place), but I tried to follow the 'workflow' and it seemed flawless to me, so I'll instead use the message ID as the log date if the maxMsgID value is outdated at that point. (Subs-Post.php)
+ Added support for outputting Secure HTTP links in Aeva embedding. Rendered videos will still be unsecure, but the point is only to prevent https protocols from breaking the whole process. (ManageMedia3.php)
! Select boxes will now take the page height into account if it's shorter than the window height. Meaning, they'll try to avoid showing their dropdowns below them if there's more room above them, than between their bottom and the actual bottom of the body tag (not the window height). I know, it's complicated, but it magically fixes the skin selector in short pages with a responsive sidebar. That one ate at me over a long time, you can't imagine. Uh, no, actually not that much. (sbox.js)
* Instead of having stat bars span from 4px to 104px in size, I'll have them span from 5px to 100px, that's more than enough thank you. (Stats.php, Stats.template.php)
! Macros weren't being parsed if the skin.xml file was missing, even though they're located in the macros.xml file. (Subs-Cache.php)
* Removed flexbox and display: table code paths for Wilde linktrees. Seriously, it was too complicated for its own good. It works better as an inline-block, especially in iPhones. As a fix for broken gradients on multi-line linktrees, I've simply decided to drop all linktree gradients in responsive mode. Looks 80% as good, and doesn't 'break' when over 2 lines or more. (Wilde/extra.css)
* Improved translation. (PersonalMessage.french.php)
@ Re: quick edit bug. Considering that Wedge is using pretty much the same workflow as SMF here, I'd like to invite SMF developers to look into doing the same. Same comment as before: if you're unsure, ask me to do a pull request. I'll wait until I can confirm this is definitely fixed, though.
8 files changed, 44 insertions(+), 46 deletions(-), 3.12 KiB
! This is my tentative fix for the infamous "quick edit just marked my post as unread, you silly!" bug... I'm pretty sure it's due to a settings caching problem (as I believe it only happens when the post you're editing is the latest in the forum *and* you've finished editing it within a minute of posting it in the first place), but I tried to follow the 'workflow' and it seemed flawless to me, so I'll instead use the message ID as the log date if the maxMsgID value is outdated at that point. (Subs-Post.php)
+ Added support for outputting Secure HTTP links in Aeva embedding. Rendered videos will still be unsecure, but the point is only to prevent https protocols from breaking the whole process. (ManageMedia3.php)
! Select boxes will now take the page height into account if it's shorter than the window height. Meaning, they'll try to avoid showing their dropdowns below them if there's more room above them, than between their bottom and the actual bottom of the body tag (not the window height). I know, it's complicated, but it magically fixes the skin selector in short pages with a responsive sidebar. That one ate at me over a long time, you can't imagine. Uh, no, actually not that much. (sbox.js)
* Instead of having stat bars span from 4px to 104px in size, I'll have them span from 5px to 100px, that's more than enough thank you. (Stats.php, Stats.template.php)
! Macros weren't being parsed if the skin.xml file was missing, even though they're located in the macros.xml file. (Subs-Cache.php)
* Removed flexbox and display: table code paths for Wilde linktrees. Seriously, it was too complicated for its own good. It works better as an inline-block, especially in iPhones. As a fix for broken gradients on multi-line linktrees, I've simply decided to drop all linktree gradients in responsive mode. Looks 80% as good, and doesn't 'break' when over 2 lines or more. (Wilde/extra.css)
* Improved translation. (PersonalMessage.french.php)
@ Re: quick edit bug. Considering that Wedge is using pretty much the same workflow as SMF here, I'd like to invite SMF developers to look into doing the same. Same comment as before: if you're unsure, ask me to do a pull request. I'll wait until I can confirm this is definitely fixed, though.
10
rev 2321 -- changed my mind. I'll get rid of as much as possible, before I start moving folders around.
11 files changed, 13 insertions(+), 49 deletions(-), 4.32 KiB
* Moved Forum Width setting from themes to general settings. (ManageSettings.php, Settings.template.php, index.template.php, ManageSettings.language.php, Themes.language.php)
* Moved Random News setting from themes to News Settings. Renamed language string to 'enable_news'. (ManageNews.php, Settings.template.php, ManageSettings.language.php, Themes.language.php, install.sql)
- Removed Show Profile Buttons theme option. Seriously, I could understand that one wouldn't want to know their friends' online status, but... Nope, couldn't understand. (Msg.template.php, Settings.template.php, Themes.language.php, upgrade.php, install.sql)
- Removed Last Modification theme toggle. Again: no crazy reason for disabling that will work on me. If you really want to hide them, set 'ins' styling to display: none. (Msg.template.php, Settings.template.php, Themes.language.php, upgrade.php, install.sql)
- Removed deprecated language strings: enable_single_post, enable_multiple_posts (I have no idea what these are, but they're not used anywhere), inline_desc (this one was probably outdated 8 years ago) and member_list_bar. (Themes.language.php)
@ Yes, I know, I have no reason to keep updating upgrade.php. Don't mind me.
11 files changed, 13 insertions(+), 49 deletions(-), 4.32 KiB
* Moved Forum Width setting from themes to general settings. (ManageSettings.php, Settings.template.php, index.template.php, ManageSettings.language.php, Themes.language.php)
* Moved Random News setting from themes to News Settings. Renamed language string to 'enable_news'. (ManageNews.php, Settings.template.php, ManageSettings.language.php, Themes.language.php, install.sql)
- Removed Show Profile Buttons theme option. Seriously, I could understand that one wouldn't want to know their friends' online status, but... Nope, couldn't understand. (Msg.template.php, Settings.template.php, Themes.language.php, upgrade.php, install.sql)
- Removed Last Modification theme toggle. Again: no crazy reason for disabling that will work on me. If you really want to hide them, set 'ins' styling to display: none. (Msg.template.php, Settings.template.php, Themes.language.php, upgrade.php, install.sql)
- Removed deprecated language strings: enable_single_post, enable_multiple_posts (I have no idea what these are, but they're not used anywhere), inline_desc (this one was probably outdated 8 years ago) and member_list_bar. (Themes.language.php)
@ Yes, I know, I have no reason to keep updating upgrade.php. Don't mind me.