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
6166
Bug reports / Re: SMF bug 4905 (signature length verified before preparsecode)
« on March 10th, 2012, 09:35 PM »
Well if someone complains about that then they have no life.
(does it show that I'm pissed off right now? :P)
(does it show that I'm pissed off right now? :P)
6168
Features / Re: Unfinished, quite raw, would like some feedback
« on March 10th, 2012, 08:25 PM »
If anything, today would have been a bad day to stop for me...
6170
Features / Re: Intrigued by a vB feature
« on March 10th, 2012, 08:21 PM »
Can always be decided upon later.
6171
The Pub / Re: Logo Madness
« on March 10th, 2012, 06:44 PM »
Well at least no one seems to be complaining so far ;)
6172
Off-topic / Re: IT'S OVER 9000!
« on March 10th, 2012, 06:42 PM »
Does it mean you would always beat me in a fistfight?!
6173
Features / Re: Poll mode
« on March 10th, 2012, 12:00 PM »
I'm looking into adding support for multiple polls right now.
A few things.
- I can either add an id_topic to the poll table, or allow for comma-separated poll IDs in the topic table (or both!) What do you like best? The table solution simply requires adding an extra key (on id_topic), seems simple enough. The poll ID list should be okay too, in the sense that when in Display, we can easily query for the poll details by using id_poll IN ({string:poll_ids}).
- I noticed that poll questions are limited in size -- varchar(255). I *think* it might make sense to make that size larger, for specific cases... Maybe even a varchar(65535) would be okay (or just varchar(20000) to account for UTF8, or whatever...)
Heck, if you look into the database structure, there are dozens of varchar(255) that could really benefit from being switched to a larger size, now that we're requiring MySQL > 5.0.3 anyway... Thing is, it's best to do it now. We could still add some sort of converter to the upgrader code when we release new versions, but it's simpler now.
Oh, and while I'm at it... Maybe we could do without the upgrade script? Maybe we could have it inside the admin area... And call it automatically if we find out that the current database version is different from the current Wedge files version. Ask for users to fill in their admin password, and launch the upgrade process... Thus, no files to remove after the upgrade.
A few things.
- I can either add an id_topic to the poll table, or allow for comma-separated poll IDs in the topic table (or both!) What do you like best? The table solution simply requires adding an extra key (on id_topic), seems simple enough. The poll ID list should be okay too, in the sense that when in Display, we can easily query for the poll details by using id_poll IN ({string:poll_ids}).
- I noticed that poll questions are limited in size -- varchar(255). I *think* it might make sense to make that size larger, for specific cases... Maybe even a varchar(65535) would be okay (or just varchar(20000) to account for UTF8, or whatever...)
Heck, if you look into the database structure, there are dozens of varchar(255) that could really benefit from being switched to a larger size, now that we're requiring MySQL > 5.0.3 anyway... Thing is, it's best to do it now. We could still add some sort of converter to the upgrader code when we release new versions, but it's simpler now.
Oh, and while I'm at it... Maybe we could do without the upgrade script? Maybe we could have it inside the admin area... And call it automatically if we find out that the current database version is different from the current Wedge files version. Ask for users to fill in their admin password, and launch the upgrade process... Thus, no files to remove after the upgrade.
6174
Features / Re: New revs
« on March 9th, 2012, 07:23 PM »
rev 1453
(2 files, 2kb)
+ Upon Pete's suggestion, added a few classes to poll results. All bars get a '.bar1', '.bar2' etc class, accessed through '.poll .barX' when styling, and every other bar gets an additional 'alt' class (access through .poll .alt, or just don't use it and use CSS3 to do that, but I suspect no one would). Heck, it's even shorter than the earlier HTML, because I removed the statsbar class which is no longer needed to style these. Also removed some stat styling leftovers from the RTL file. I never test that file anyway... (Display.template.php, index.rtl.css)
(2 files, 2kb)
+ Upon Pete's suggestion, added a few classes to poll results. All bars get a '.bar1', '.bar2' etc class, accessed through '.poll .barX' when styling, and every other bar gets an additional 'alt' class (access through .poll .alt, or just don't use it and use CSS3 to do that, but I suspect no one would). Heck, it's even shorter than the earlier HTML, because I removed the statsbar class which is no longer needed to style these. Also removed some stat styling leftovers from the RTL file. I never test that file anyway... (Display.template.php, index.rtl.css)
6175
Features / Re: New revs
« on March 9th, 2012, 06:57 PM »
rev 1452
(3 files, 2kb)
* Modified $language variable for skins. Now it requires setting up a list of languages accounted for Wedge.org in the <language> tag of a skin.xml file, with the first in the list acting as fallback language. Documented in Warm's skin file as usual (even though I don't make use of it... Maybe I should put it inside comments?) (Subs-Cache.php, index.css, Warm/skin.xml)
(3 files, 2kb)
* Modified $language variable for skins. Now it requires setting up a list of languages accounted for Wedge.org in the <language> tag of a skin.xml file, with the first in the list acting as fallback language. Documented in Warm's skin file as usual (even though I don't make use of it... Maybe I should put it inside comments?) (Subs-Cache.php, index.css, Warm/skin.xml)
6176
Features / Re: Image resizing for non-uploads
« on March 9th, 2012, 06:51 PM »
This is definitely the code in theme.js, as modified for jQuery in Wedge:
Code: [Select]
// Toggles the element height and width styles of an image.
$('img.resized').css('cursor', 'pointer').click(function () {
this.style.width = this.style.height = (this.style.width == 'auto' ? null : 'auto');
});6177
The Pub / Re: Logo Madness
« on March 9th, 2012, 04:13 PM »Lol, in Spanish "con" means "with" =P
Okay, haven't spoken Spanish since 1987 or so. Sue me!
Nice badges though, I like them a lot :)
(Heck, even if it's a comment on the difference between the logo in badges and the logo in signatures, because yes they're slightly different on the left, that would be useful.)
6178
Plugins / Re: Mad idea but it might just work
« on March 9th, 2012, 10:26 AM »Sure, the attachments, avatars,and the gallery folders are at risk from files being overwritten/corrupted, but they're theoretically safe against PHP being dumped in them and executed - because there's an .htaccess ruleset against PHP execution from those folders.
Also, these folders have a redirection through an index.php file, which I can tell you they do execute... :^^;:
Hmm, lemme see... /cache/ doesn't redirect to the root, my bad. It just treats it as a 404 error (i.e. no redirection in the address bar but we do get the homepage.)
The cache is a trickier one but the entire cache folder is marked as inaccessible to outside PHP calling, which means the risk then becomes against the cache files themselves being abused, but since they're regenerated regularly, that's not as much of a deal,
6179
Features / Re: New revs
« on March 9th, 2012, 10:19 AM »
rev 1451
(1 file, 1kb)
! Tweaked installer. It will now disable data compression while installing, and get rid of the uncompressed files after installation. You can now enable data compression by simply choosing the general install setting of compressing data to save bandwidth, which will control both default settings of enableCompressOutput and enableCompressData. You can fine-tune this after installation, of course. (install.php)
+ Added a proper browser language detector for the installer. I've added manually a list of all SMF language packs and their associated language ID, so theoretically you should be able to use an Install.language.php file from SMF into your language folder, and be able to install in your language. Well, this is all only for the glory of Pete, because I doubt we'll be bundling French into the default Wedge package, so the problem of installing Wedge and getting the French version by default is only going to happen in the SVN version... (install.php)
@ Obviously, I'd appreciate it if you guys could confirm that the installer will now default to English for you... ;) It does default to French for me.
(1 file, 1kb)
! Tweaked installer. It will now disable data compression while installing, and get rid of the uncompressed files after installation. You can now enable data compression by simply choosing the general install setting of compressing data to save bandwidth, which will control both default settings of enableCompressOutput and enableCompressData. You can fine-tune this after installation, of course. (install.php)
+ Added a proper browser language detector for the installer. I've added manually a list of all SMF language packs and their associated language ID, so theoretically you should be able to use an Install.language.php file from SMF into your language folder, and be able to install in your language. Well, this is all only for the glory of Pete, because I doubt we'll be bundling French into the default Wedge package, so the problem of installing Wedge and getting the French version by default is only going to happen in the SVN version... (install.php)
@ Obviously, I'd appreciate it if you guys could confirm that the installer will now default to English for you... ;) It does default to French for me.
6180
Plugins / Re: Mad idea but it might just work
« on March 9th, 2012, 09:03 AM »
BTW... We still need to have write access for plenty of folders -- attachments, avatars, media gallery, and obviously the cache folder. Wouldn't this defeat your idea of security entirely...?