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
1231
Features / Re: New revs
« on March 3rd, 2014, 11:01 PM »
[Commit revision 244cb53]
Author: Nao
Date: Mon, 03 Mar 2014 23:01:20 +0100
Stats: 1 file changed; +0 (insertion), -16 (deletions)
Date: Mon, 03 Mar 2014 23:01:20 +0100
Stats: 1 file changed; +0 (insertion), -16 (deletions)
- Hopefully I'm not breaking anything else by this, but I'm fixing profile options, that were broken a few months ago and were no longer changed when setting them. (Profile-Modify.php)
1232
Archived fixes / Re: Changes to settings won't stick under Member Options->Default Options
« on March 3rd, 2014, 11:00 PM »
'kay, got it...
What was being erased, was the specific per-theme settings of a member apart from the default theme, once a default setting was changed.
It doesn't make a lot of sense. I've always hated theme-specific options, at least the way they're implemented in SMF, I mean... I really, really need to reappropriate that.
Anyway, fixed! (Profile pages.)
What was being erased, was the specific per-theme settings of a member apart from the default theme, once a default setting was changed.
It doesn't make a lot of sense. I've always hated theme-specific options, at least the way they're implemented in SMF, I mean... I really, really need to reappropriate that.
Anyway, fixed! (Profile pages.)
1233
Archived fixes / Re: Changes to settings won't stick under Member Options->Default Options
« on March 3rd, 2014, 10:55 PM »
Oh... Interesting. Indeed, the profile page doesn't allow me to change my settings. I'll look into it.
Surprising that no one reported this in a whole month... :^^;:
Problem is due to variable being updated, THEN being erased entirely from the database immediately after that, ah ah...
I need to remember the difference between id_theme=1 and id_theme!=1 in the theme settings table... -_- It'll come back to me.
Surprising that no one reported this in a whole month... :^^;:
Posted: March 3rd, 2014, 10:47 PM
Problem is due to variable being updated, THEN being erased entirely from the database immediately after that, ah ah...
I need to remember the difference between id_theme=1 and id_theme!=1 in the theme settings table... -_- It'll come back to me.
1234
Archived fixes / Re: Changes to settings won't stick under Member Options->Default Options
« on March 3rd, 2014, 10:42 PM »
Can you reformulate..?
I *did* make several changes to member options, BTW, when I dropped theme support.
I *did* make several changes to member options, BTW, when I dropped theme support.
1235
Archived fixes / Re: Fatal error: Unsupported operand types (Load.php on line 1971)
« on March 3rd, 2014, 10:41 PM »
It may not be related. I mean, the problem may lie in a folder problem within /languages. Waiting for feedback..!
1236
Archived fixes / Re: Notification mails are send twice
« on March 3rd, 2014, 09:38 PM »
I wouldn't consider it fixed. It can only be fixed for now by disabling HTML emails for notifications. Sorry I'm so overwhelmed with bugs to fix! I didn't get to do a tenth of my plans today.
Please move this back to the bug reports topic if posting again here. This board is disabled from my latest topics view and is not intended to communicate with me on a daily basis. ;)
Please move this back to the bug reports topic if posting again here. This board is disabled from my latest topics view and is not intended to communicate with me on a daily basis. ;)
1237
Archived fixes / [Full Editor] Re: Text is empty error
« on March 3rd, 2014, 08:29 PM »
You mean, enabling it by default in your profile, and then doing Switch to Full Editor with text entered?
1238
Archived fixes / Re: Exhausted memory?
« on March 3rd, 2014, 08:26 PM »
Hmm... I'm reaching my limits, here. (As well as debug_backtrace's :P)
So, how can we do that... Do these PHP errors show up regularly? A lot? When did they start? Can you point out a single IP address generating them? Where does this log come from, do you have access to your Apache log? Can you match the times between the PHP and Apache logs, and determine what URLs are called that generate the errors?
So, how can we do that... Do these PHP errors show up regularly? A lot? When did they start? Can you point out a single IP address generating them? Where does this log come from, do you have access to your Apache log? Can you match the times between the PHP and Apache logs, and determine what URLs are called that generate the errors?
1239
Archived fixes / Re: Errors on subscriptions
« on March 3rd, 2014, 07:47 PM »
They need to use your subscription link... Really, they do. Just direct them to their profiles.
That's because Wedge (and SMF) first create a subscription log, then put it in standby until they receive a notification from PayPal. If they receive the notif without having a subscription created in the first place, then Wedge/SMF don't know what to do with it.
It 'could' be fixed, I guess, but I'm not going into that. There's no reason not to use the profile links.
That's because Wedge (and SMF) first create a subscription log, then put it in standby until they receive a notification from PayPal. If they receive the notif without having a subscription created in the first place, then Wedge/SMF don't know what to do with it.
It 'could' be fixed, I guess, but I'm not going into that. There's no reason not to use the profile links.
1240
Features / Re: Language revs
« on March 3rd, 2014, 07:25 PM »
[Commit revision dee9896]
Author: Nao (Signed-off)
Date: Mon, 03 Mar 2014 19:25:03 +0100
Stats: 39 files changed; +0 (insertion), -0 (deletion)
Date: Mon, 03 Mar 2014 19:25:03 +0100
Stats: 39 files changed; +0 (insertion), -0 (deletion)
- Moved French files to their own sub-folder, now that Wedge supports these. It'll be less practical for me to update them, but more practical for everyone else. Worth it. (*.french.php, french/*)
1241
Archived fixes / Re: Fatal error: Unsupported operand types (Load.php on line 1971)
« on March 3rd, 2014, 07:09 PM »
Oh my...
Still, that's no solution. Other people are using LiteSpeed, and I need to make sure that this line of code will be accepted, or rewrite it in an acceptable way. (Its only purpose is to add to an array a list of language sub-folders that should be searched for language items. There are approximately 8742 different ways of doing that, but this one was by far the shortest and coolest. I tend to commit my code only when it's short and cool enough. Cool because I'm vain, and short because it makes for more maintainable code if it's not too cryptic.)
Stupid me!! That's what happens when you're trying to work on several things at the same time.
I just realized that the error wasn't due to glob() (I focused too much on GLOB_ONLYDIR), but on the "+=" item.
Thing is, glob() MAY return false instead of an array, if an error occurred.
I don't know why your error wasn't logged, though...! Who cares that the operand is unsupported. What I want to know is why your code failed in the first place.
Can you re-enable LiteSpeed, and replace the line of code with this?
Code: [Select]
This will force typecasting the result to an array, and avoid this error. Then, maybe it'll finally record the error...
Still, that's no solution. Other people are using LiteSpeed, and I need to make sure that this line of code will be accepted, or rewrite it in an acceptable way. (Its only purpose is to add to an array a list of language sub-folders that should be searched for language items. There are approximately 8742 different ways of doing that, but this one was by far the shortest and coolest. I tend to commit my code only when it's short and cool enough. Cool because I'm vain, and short because it makes for more maintainable code if it's not too cryptic.)
Posted: March 3rd, 2014, 07:02 PM
Stupid me!! That's what happens when you're trying to work on several things at the same time.
I just realized that the error wasn't due to glob() (I focused too much on GLOB_ONLYDIR), but on the "+=" item.
Thing is, glob() MAY return false instead of an array, if an error occurred.
I don't know why your error wasn't logged, though...! Who cares that the operand is unsupported. What I want to know is why your code failed in the first place.
Can you re-enable LiteSpeed, and replace the line of code with this?
$language_directories += (array) glob(LANGUAGES_DIR . '/*', GLOB_ONLYDIR);This will force typecasting the result to an array, and avoid this error. Then, maybe it'll finally record the error...
1242
Archived fixes / Re: Fatal error: Unsupported operand types (Load.php on line 1971)
« on March 3rd, 2014, 06:38 PM »
Hmm, I don't think so... You're not the only one to use it. It doesn't seem like a bad system.
1243
Archived fixes / Re: Fatal error: Unsupported operand types (Load.php on line 1971)
« on March 3rd, 2014, 06:25 PM »
Hmm...
GLOB_ONLYDIR is available on PHP < 5, so it shouldn't be a problem.
I'm not sure why this would be happening. What's your server setup?
GLOB_ONLYDIR is available on PHP < 5, so it shouldn't be a problem.
I'm not sure why this would be happening. What's your server setup?
1244
Archived fixes / Re: Changes to settings won't stick under Member Options->Default Options
« on March 3rd, 2014, 05:25 PM »
Ah, yes (or no), I forgot to deal with this one...
Gimme a sec though, more like an hour, I'm taking a break... Posted a long message somewhere and lost too much time. :P
Gimme a sec though, more like an hour, I'm taking a break... Posted a long message somewhere and lost too much time. :P
1245
Importing into Wedge / Re: SMF 2 to Wedge importer errors
« on March 3rd, 2014, 05:19 PM »
Please keep me posted! :)