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
1246
Archived fixes / [Full Editor] Re: Text is empty error
« on March 3rd, 2014, 05:19 PM »
I don't see why your firewall would break it, but... Indeed, I can't think of anything else.
1247
Archived fixes / Re: Exhausted memory?
« on March 3rd, 2014, 05:18 PM »
Grmpf...
Okay, are you on PHP 5.4 or better? If yes, you could help with debugging this.
Replace line 636 in /core/app/Class-DB.php with:
Code: [Select]
The only difference is the ", 5" added at the end.
This will set a hard limit on the number of objects returned by debug_backtrace() to 5, which should be enough. This should help your code execute. And by code, I mean "error reporting path". Which means after doing this, you'll see errors show up in your Wedge error log, rather than Apache error log.
At that point, you should be able to see what queries are generating errors for you.
Make sure to enable Query Logging in Admin settings > Admin > Server > Debugging (or Error Log Settings), as I said yesterday.
Keep me posted!
Okay, are you on PHP 5.4 or better? If yes, you could help with debugging this.
Replace line 636 in /core/app/Class-DB.php with:
$trace_log = debug_backtrace(!function_exists('version_compare') || (version_compare('5.3.6', PHP_VERSION) > 0) ? false : DEBUG_BACKTRACE_IGNORE_ARGS, 5);The only difference is the ", 5" added at the end.
This will set a hard limit on the number of objects returned by debug_backtrace() to 5, which should be enough. This should help your code execute. And by code, I mean "error reporting path". Which means after doing this, you'll see errors show up in your Wedge error log, rather than Apache error log.
At that point, you should be able to see what queries are generating errors for you.
Make sure to enable Query Logging in Admin settings > Admin > Server > Debugging (or Error Log Settings), as I said yesterday.
Keep me posted!
1248
Features / Re: Poll: dropping oldIE
« on March 3rd, 2014, 05:10 PM »7 is still supported on Vista but I think it's our responsibility to encourage people off the unsupported 6.
Dropping IE7 compatibility would allow me to get rid of many hacks for display: table.
Interestingly, I've always been very proud of said hack, and actually wrote the entire macro system upon this, but in the end, macros are here to stay, but this particular macro... I don't think so.
1249
Features / Re: New revs
« on March 3rd, 2014, 03:48 PM »
[Commit revision 77b2cd4]
Author: Nao
Date: Mon, 03 Mar 2014 15:21:01 +0100
Stats: 3 files changed; +14 (insertions), -10 (deletions)
[Commit revision 5eee68c]
Author: Nao
Date: Mon, 03 Mar 2014 15:22:22 +0100
Stats: 1 file changed; +5 (insertions), -5 (deletions)
[Commit revision 43738fc]
Author: Nao
Date: Mon, 03 Mar 2014 15:48:02 +0100
Stats: 4 files changed; +12 (insertions), -10 (deletions)
Date: Mon, 03 Mar 2014 15:21:01 +0100
Stats: 3 files changed; +14 (insertions), -10 (deletions)
- Preliminary support for storing language files in sub-folders of the core/languages folder. Yayz. Sub-folder items have priority (and override) similarly named items in the main folder, so you should be able to create an 'english' sub-folder and rewrite index.english.php or whatever to your heart's content. Although there are better ways of doing so, but... That's an alternative, right? (Load.php, ManageLanguages.php, Subs-Cache.php)
- Don't forget to purge your cache when you make any modifications to your language folders.
[Commit revision 5eee68c]
Date: Mon, 03 Mar 2014 15:22:22 +0100
Stats: 1 file changed; +5 (insertions), -5 (deletions)
- Didn't I already commit this file..? Or did I only do it in the languages repo? Silly me... (Help.english.php)
[Commit revision 43738fc]
Date: Mon, 03 Mar 2014 15:48:02 +0100
Stats: 4 files changed; +12 (insertions), -10 (deletions)
- All flags should now point to their proper folders. (TEMPLATES: Boards, ManageBoards, ManagePlugins, MessageIndex)
1250
Archived fixes / [Full Editor] Re: Text is empty error
« on March 3rd, 2014, 02:29 PM »
I don't get it.
Tried in ie10 and chrome mobile. Nothing disappears when switching modes...
Tried in ie10 and chrome mobile. Nothing disappears when switching modes...
1251
The Pub / Re: Wedge translation pt_PT (Git questions)
« on March 3rd, 2014, 12:42 PM »
I'll do that later today then!
1252
Importing into Wedge / Re: SMF 2 to Wedge importer errors
« on March 3rd, 2014, 12:42 PM »
Again, as I said, I got MySQL errors when inserting '1' values through install.sql, but I fixed that by turning them into integers.
So, a proper INSERT would also be
INSERT INTO table SET bit_field = 1;
I could simply test for is_integer() before inserting some imported data, and doing without single quotes in this case...
Or is it that can_collapse accepts more values than 0 or 1? Anything I converted to BIT(1) was thoroughly tested (AFAIK) against this possibility (a lazy habit of earlier SMF developers, I think!)
So, a proper INSERT would also be
INSERT INTO table SET bit_field = 1;
I could simply test for is_integer() before inserting some imported data, and doing without single quotes in this case...
Or is it that can_collapse accepts more values than 0 or 1? Anything I converted to BIT(1) was thoroughly tested (AFAIK) against this possibility (a lazy habit of earlier SMF developers, I think!)
1253
Archived fixes / [Full Editor] Re: Text is empty error
« on March 3rd, 2014, 12:38 PM »
Paste your line again..?
It doesn't delete anything when I click Switch to full editor, so I don't have to paste..?
It doesn't delete anything when I click Switch to full editor, so I don't have to paste..?
1254
Features / Re: Poll: dropping oldIE
« on March 3rd, 2014, 12:38 PM »
1/ http://theie7countdown.com/
2/ IE7 is only support on XP and above, and even XP supports IE8. There is no reason for people not to upgrade to IE8 (which I'm going to keep supporting anyway, until web stats are more favorable.)
3/ I should have specified: not supporting = not giving a damn if it breaks, but also showing for these users a banner explaining that they should get rid of their old browser.
2/ IE7 is only support on XP and above, and even XP supports IE8. There is no reason for people not to upgrade to IE8 (which I'm going to keep supporting anyway, until web stats are more favorable.)
3/ I should have specified: not supporting = not giving a damn if it breaks, but also showing for these users a banner explaining that they should get rid of their old browser.
1255
Features / Poll: changing paths
« on March 3rd, 2014, 12:34 PM »
Advantages of changing paths:
- You can move your source files to a non-accessible path, meaning no one can see their contents, even if you server fails.
Advantages of keeping paths the same across all copies of Wedge:
- Moving your Wedge install to another folder is a no-brainer, because all paths are automatically updated.
- Seriously, even if someone could see your source file contents... Who cares? They can already see them on GitHub anyway!
To me, the only file that MIGHT warrant being moved to a non-web space is Settings.php, and even SMF doesn't support that... If you're not modifying your Settings.php file (i.e. keeping away from the admin area), you could consider turning Settings.php into a file saying "include (__DIR__ . '../../somewhere/Settings.php')", but because Wedge may not have write access to said path, it's not realistic to expect it to handle this kind of redirection easily.
It might be possible to create a hardlink to that file, but I'm not sure it wouldn't simply be shown in the same circumstances at a regular file.
Can anyone think of a GOOD reason to move your folders around..?
PS: media and attachment folders are a special case, though. It's likely that I'll keep the ability to move them around, because of potential disk space concerns.
- You can move your source files to a non-accessible path, meaning no one can see their contents, even if you server fails.
Advantages of keeping paths the same across all copies of Wedge:
- Moving your Wedge install to another folder is a no-brainer, because all paths are automatically updated.
- Seriously, even if someone could see your source file contents... Who cares? They can already see them on GitHub anyway!
To me, the only file that MIGHT warrant being moved to a non-web space is Settings.php, and even SMF doesn't support that... If you're not modifying your Settings.php file (i.e. keeping away from the admin area), you could consider turning Settings.php into a file saying "include (__DIR__ . '../../somewhere/Settings.php')", but because Wedge may not have write access to said path, it's not realistic to expect it to handle this kind of redirection easily.
It might be possible to create a hardlink to that file, but I'm not sure it wouldn't simply be shown in the same circumstances at a regular file.
Can anyone think of a GOOD reason to move your folders around..?
PS: media and attachment folders are a special case, though. It's likely that I'll keep the ability to move them around, because of potential disk space concerns.
1256
Features / Poll: dropping oldIE
« on March 3rd, 2014, 12:21 PM »
I already had a similar poll last year, but want to make sure the new guys have a say in this!
1257
Archived fixes / Re: Errors on subscriptions
« on March 3rd, 2014, 11:34 AM »
It has yet to happen to me.
You should be having errors in your log if this happened...
Or maybe, look for your Apache log and see what connections are made to your subscriptions.php file.
You should be having errors in your log if this happened...
Or maybe, look for your Apache log and see what connections are made to your subscriptions.php file.
1258
The Pub / Re: Wedge translation pt_PT (Git questions)
« on March 3rd, 2014, 11:25 AM »
Support added...
It's only partial, though.
Also, when you add new languages in the language manager -- if you attempt to edit a language's files, if they're in a subfolder, they won't be available. It requires more changes, and I'm not too excited to do this for now...
Still, it's there. You can have the same structure as in the languages repo. I guess I can commit that, with the caveat that language files won't be editable. All right..?
It's only partial, though.
Also, when you add new languages in the language manager -- if you attempt to edit a language's files, if they're in a subfolder, they won't be available. It requires more changes, and I'm not too excited to do this for now...
Still, it's there. You can have the same structure as in the languages repo. I guess I can commit that, with the caveat that language files won't be editable. All right..?
1259
Archived fixes / Re: Errors on subscriptions
« on March 2nd, 2014, 10:49 PM »
Are you sure you still have his money in your PayPal account?
1260
Archived fixes / Re: PHP Fatal error
« on March 2nd, 2014, 10:48 PM »
I don't think I've ever tried this one...