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.
6676
Features / Re: New revs - Public comments
« on August 19th, 2011, 07:17 PM »
Nah, I fixed it by loosening the check in the installer so it doesn't demand the brackets.
6677
I wonder if switching to mysqli will make a difference, I suspect not, because I have a feeling this is ultimately caused by the mysqlnd internal driver, but we'll see.
I'll try it later when I get back from going out.
Oh and just to clarify; it isn't Wedge's fault. SMF does exactly the same on my setup.
I'll try it later when I get back from going out.
Posted: August 19th, 2011, 06:07 PM
Oh and just to clarify; it isn't Wedge's fault. SMF does exactly the same on my setup.
6678
OK, so I've got to play with XDebug, which will really help me (since before I did benchmarking in all kinds of ... interesting ways)
mysql_connect is the culprit for this performance suckage, and I have no idea why that should be, but it is consistently consuming 80%+ of the runtime of the script :/
mysql_connect is the culprit for this performance suckage, and I have no idea why that should be, but it is consistently consuming 80%+ of the runtime of the script :/
6679
Today has been a fuckup, and I'm really confused why things ended the way they did. OK, let me explain.
For the last 8 years, ever since I first dipped my toes into PHP, I've been running Apache, MySQL and PHP as separate components and making them work nicely together. Back then I was building on Linux, and doing it from source because my distro at the time didn't have anything useful to give me, and I guess I just ended up rolling with it.
So, now we make MySQL 5.1 a minimum and I find myself with a problem.
For reasons far too complicated to remember, I used to use MySQL 5.1 with a 5.0 connector. This fails in the installer, because it tests both the connector/client and server versions, because it's possible you'll end up using a stupid old connector with a current DB version - like I was, only it's possible to break more things than I had.
Cue an afternoon of trying to mix and match versions of things to make it all work properly, the best result I had was that PHP wouldn't load the MySQL libraries, and the worst was that PHP would crash if you tried to make a query.
So in the end I went to WampServer. After a little bit of brain ache trying to restore the virtual hosts that I have, because I have specific and weird configurations for things, I finally make it all work.
Then I go through the Wedge installer to verify it works, and it does.
Then I find something I do not understand, and after an afternoon of frustration, I'd like it to stop being a problem. I refer to the footer I encountered... "Page created in 1.10 seconds with 12 queries."
There is absolutely no fucking reason why it should be that slow on my PC. The queries aren't slow, in fact the queries aren't the problem in the slightest... Pulling up the query log shows me that the very first query occurs at in ...\Sources\Load.php line 37, which took 0.00071096 seconds at 1.04372096 into request.
So it's taking over a second before it even gets to actually do anything. :wow: So, I'm really, really confused as to what the hell's going on.
The only comfort is that this might be the first time I play with XDebug (as opposed to other debuggers) to figure out WTF is going on.
For the last 8 years, ever since I first dipped my toes into PHP, I've been running Apache, MySQL and PHP as separate components and making them work nicely together. Back then I was building on Linux, and doing it from source because my distro at the time didn't have anything useful to give me, and I guess I just ended up rolling with it.
So, now we make MySQL 5.1 a minimum and I find myself with a problem.
For reasons far too complicated to remember, I used to use MySQL 5.1 with a 5.0 connector. This fails in the installer, because it tests both the connector/client and server versions, because it's possible you'll end up using a stupid old connector with a current DB version - like I was, only it's possible to break more things than I had.
Cue an afternoon of trying to mix and match versions of things to make it all work properly, the best result I had was that PHP wouldn't load the MySQL libraries, and the worst was that PHP would crash if you tried to make a query.
So in the end I went to WampServer. After a little bit of brain ache trying to restore the virtual hosts that I have, because I have specific and weird configurations for things, I finally make it all work.
Then I go through the Wedge installer to verify it works, and it does.
Then I find something I do not understand, and after an afternoon of frustration, I'd like it to stop being a problem. I refer to the footer I encountered... "Page created in 1.10 seconds with 12 queries."
There is absolutely no fucking reason why it should be that slow on my PC. The queries aren't slow, in fact the queries aren't the problem in the slightest... Pulling up the query log shows me that the very first query occurs at in ...\Sources\Load.php line 37, which took 0.00071096 seconds at 1.04372096 into request.
So it's taking over a second before it even gets to actually do anything. :wow: So, I'm really, really confused as to what the hell's going on.
The only comfort is that this might be the first time I play with XDebug (as opposed to other debuggers) to figure out WTF is going on.
6680
Features / Re: New revs - Public comments
« on August 19th, 2011, 02:21 PM »
Oh, and I figured out what the problem with the installer was.
The stock Settings.php file contains a test to see if install.php exists, and if it does, redirect there. Once the DB settings have been validated, that test is removed from Settings.php.
At least in theory, the test used to check for the if statement, plus there being braces either side of the redirection itself, but since it was a one line if branch, the braces got trimmed in r941 and failed to remove the redirect.
Now, I have to see about upgrading my install or hacking the installer test (since while we require 5.1, there's nothing about the connector that will be broken by what I'm doing, but I might as well fix it rather than leave it quasi-broken as it is now)
The stock Settings.php file contains a test to see if install.php exists, and if it does, redirect there. Once the DB settings have been validated, that test is removed from Settings.php.
At least in theory, the test used to check for the if statement, plus there being braces either side of the redirection itself, but since it was a one line if branch, the braces got trimmed in r941 and failed to remove the redirect.
Now, I have to see about upgrading my install or hacking the installer test (since while we require 5.1, there's nothing about the connector that will be broken by what I'm doing, but I might as well fix it rather than leave it quasi-broken as it is now)
6681
Features / Re: These two bytes may not matter to you...
« on August 18th, 2011, 10:48 PM »
@AngelinaBelle, we wish it had been different, but it isn't like we didn't offer the opportunity for amends to be made.
6682
Other software / Re: Fork discussion at SMF
« on August 18th, 2011, 10:46 PM »I'm going to do this as well in mine and it has little to do with copying, just with agreeing on the fact that it wasn't a very bright idea to include it in the first place. Seriously, how well are the PGSQL and SQLite layers tested in a real-world scenario?Quote from Voldefork on August 18th, 2011, 03:30 PM It's also interesting that vblamer's and JBlaze's forks will both remove support for PGSQL and SQlite. I'll start counting the number of features they're taking verbatim from the Wedge Feature List... :niark:
PostgreSQL is, without doubt, a fine database, in some areas much better than MySQL, but its importance for forum installations is close to zero and I'm unsure about SQLite, which is also a very nice piece of software just not very important as a database for web applications.
I'll also kill support for PHP4, caching support for eAccelerator (doesn't make sense, because eAccel has been stripped from the required functionality) and Turk MMCache (doesn't make sense to support it when you're PHP5+). Furthermore, APC, XCache, memcached and the fallback method with disc caching should be enough options to cover the vast majority of installations.
I'm also considering wiping MySQL fulltext search, because it's pretty much useless when you have custom index (sufficient for most installations) and sphinx (for the big guys).
I hate legacy code that just sits there, making the code harder to read and maintain while doing absolutely nothing for 99% of all installations.
The PGSQL layer is incomplete and has at least one fatal error in it, the SQLite layer is even less tested, but it's also based on SQLite 2.5 while most hosts run SQLite 3. The idea was that at the time, PHP were pushing it as their next generation DB for smaller purposes, like a starter forum could use.
We came to the same conclusions about PHP 4, the caching technologies and also with respect to full text indexes, especially as InnoDB doesn't support them and as of MySQL 5.5, InnoDB is the default engine.
Regarding competition, I'd love to see all the different branches of SMF sit down in a year's time and look at the different directions taken. We took a bold road in some of the changes we're making and it'll be interesting to see if our instincts about them were right, and I know I'd be interested in sharing how we get on in that respect.
6683
Other software / Re: Fork discussion at SMF
« on August 18th, 2011, 05:43 PM »Are they the reason for your forehead scar?
I don't know, depends if you like Timothy Spall... I've loved him since his part in Red Dwarf Back to Reality, where he delivers this excellent line: "Ah ah, that's a classic!" I always quote it
Well, if I were a girl I'd probably be drooling over him as well...
A few minutes ago, the fork board was gone... They had only one topic in it. The rest was gone. I thought, "already the end eh...?" Then it came back a couple of minutes later. Weird!
| 1. | Incidentally, Alan Rickman's in that as well as the bad guy, Johnny Depp as the "good" guy and Sacha Baron Cohen's best performance yet, in my book. Couldn't have happened to a nicer person. I do not like SBC. |
6684
Features / Re: These two bytes may not matter to you...
« on August 18th, 2011, 04:39 PM »
Didn't you already post that, though? *confused*
6685
Features / Re: These two bytes may not matter to you...
« on August 18th, 2011, 04:02 PM »
The change to GPL will occur shortly after the following events all come to pass:
1. GPLv4 is released that isn't hideously virus like in its approach, tainting everything it touches.
2. Richard Stallman steps down from being a hypocritical, misguided zealot.
3. It's the day after the 12th. The 12th of Never.
But it isn't "something like the old SMF licence." It is the old SMF licence with very minor changes, as per http://wedge.org/license/
The irony is that the licence change to a restricted licence is done to protect the code from perceived abuse from other directions.
1. GPLv4 is released that isn't hideously virus like in its approach, tainting everything it touches.
2. Richard Stallman steps down from being a hypocritical, misguided zealot.
3. It's the day after the 12th. The 12th of Never.
But it isn't "something like the old SMF licence." It is the old SMF licence with very minor changes, as per http://wedge.org/license/
The irony is that the licence change to a restricted licence is done to protect the code from perceived abuse from other directions.
6686
Other software / Re: Fork discussion at SMF
« on August 18th, 2011, 03:59 PM »I am a member of the SimpleMachines NPO BOD
His domain name was created in 2002 and has the same expiration date day, which shouldn't have happened if the domain was transferred in the meantime... Usually the expiration date gets reset. Sounds odd to me.
As for JBlaze, I find it odd that you should choose the word 'threatened'...
@Ara Potter> Neither can commit while the other codes! Err...
@DC> With 29 posts, you could be Ron Wedgely's rat.
@AngelinaBelle> Admit it, you have a thing for Snape!
We rewatched HP 5 on TV at the weekend:
Umbridge: So you were unsuccessful at applying for the post of Defence Against the Dark Arts teacher?
Snape: Obviously.
6687
Features / Re: New revs - Public comments
« on August 18th, 2011, 03:54 PM »It had more bugs than that... I remember fixing a few things when I installed v5.3.
Indeed. It's a bit slower probably, though...
Yeah, I'd tend to say that's something that's bound to happen, and it's not going to kill anyone.
If you want to encourage users to become modders, then you have to be ready to accept a few quirks like them not following the MVC model
Does that mean you want to remove the template hooks, or simply not change anything and just discourage people from loading files in template hooks? I'm not sure I'm following you...
For smaller stuff, like the aforementioned, you'll load presentation and logic and execute them. But for anything of any real substance, you'll load the logic separately and pull in a template if you need it, meaning that there's no real harm in leaving the facility for templates to load files but it's a habit that should be discouraged.
Err... I may have forgotten. What were you trying to say?
Oh that would be such a fuuuun job to do....
Yes we do... I can already say the media tables aren't in it
By conflict I meant the program stopped because your version wasn't up to date. (It prints out red text and simply says to update it, but per se there's no actual conflict within the file.)
Ouch... Much be AeMe. I didn't test the installer after I did all of the changes. But OTOH it should be working, I used the rest of the file as a template...
There is a secondary issue that I'm aware of on my configuration (for reasons I won't get into, I'm running 5.1 with a 5.0 connector library) but it shouldn't be failing how it is, it should be failing with an appropriate error.
Come to think of it, I didn't test with the 5.1 version number but have no idea why that should have caused it to fail the way it does.
6688
Features / Re: New revs - Public comments
« on August 18th, 2011, 03:41 PM »
OK, so this is really, really weird.
Whatever happens, it's forcing a 302 redirect back round to the installer >_<
Whatever happens, it's forcing a 302 redirect back round to the installer >_<
6689
Other software / Re: Fork discussion at SMF
« on August 18th, 2011, 03:35 PM »It's also interesting that vblamer's and JBlaze's forks will both remove support for PGSQL and SQlite. I'll start counting the number of features they're taking verbatim from the Wedge Feature List...
I understand that vbgamer's choice was simply about the timing of acquisition of a domain name, i.e. ezforum in the com TLD. As for JBlaze, he has threatened to do something like this for a while...
Posted: August 18th, 2011, 03:34 PM
And if Nao can be Voldefork, I can definitely be Ara Potter.
6690
Features / Re: New revs - Public comments
« on August 18th, 2011, 03:30 PM »Wow, we committed in the same minute! Did you get a conflict? :P
Incidentally, at some point recently we broke the installer somehow, it never gets onto step 2 :/
Posted: August 18th, 2011, 03:25 PM
More specifically, if there's any kind of error that would force it to fall out of DatabaseSettings(), it's just going back to the start rather than actually showing an error :/