So what's the resulting output?
« Réponse #435, »
<link rel="stylesheet" href="http://localhost/wedge/css/member-chrome22-1348934260.css">
<!-- Powered by Wedge, © Wedgeward - http://wedge.org -->
<title>Localhost Wedge - Home</title>
<link rel="shortcut icon" href="http://localhost/wedge/favicon.ico" type="image/vnd.microsoft.icon">
<link rel="canonical" href="http://localhost/wedge/index.php">
<link rel="search" href="http://localhost/wedge/index.php?action=search">
<link rel="alternate" type="application/atom+xml" title="Localhost Wedge - Latest Posts Feed" href="http://localhost/wedge/index.php?action=feed">
<meta name="generator" content="Wedge">
I don't have any problems with sbox.js myself. Are you sure you can reproduce this...?
That would be the case if it weren't for the fact I'm talking about two completely different problems.
The problem of the installer crashing and burning is still related to updateSettings. The installer hack gets around that.
The problem of sbox.js being undefined on every single fresh install has been a problem for many months now.
I was attempting to debug it - at which point you asked me what was in <head>, I attempted to do a fresh install to see what the state of play was, only to find it completely broken... but this problem is not resolved.
Not completely, though... updateSettings is called before even WEDGE_INSTALLER is defined, because the language files are loaded first. I worked around that by initializing language strings only after setting the constant, with an $init var to ensure it's only done once (because we're inside a loop at this point.)
The problem doesn't show up at first because the error message(s) (with XDebug) are shown inside an HTML tag, so you can't see them on the HTML rendition.
I don't remember asking you about head, though... Or maybe that was a long time ago?!
Odd, if that were true it should have failed before that - the error in question is that wesql doesn't exist, which is why updateSettings fails.
No, I just got to a screen that only had a gradient and nothing else... ;) I couldn't even press anything to go to the next page.
So, what you're saying is that updateSettings can be called without issues in the installer as long as wesql is loaded..? (I haven't looked into it...)
And the HTML had what...?