Oh, the irony...
You must be using a very recent version of PHP. Recently they started deprecating mysql() functions.
It's an old importer script, and it was never converted to use mysqli(), unlike the rest of Wedge. Problem is the same on openimporter.
Either TE will fix it by tomorrow, or I'll look into it. In the meantime, you can always try to downgrade your PHP to 5.3, and retry importing.
Wedge repo -- installation feedback
MultiformeIngegno
-
-
- Posts: 1,337
Powerbob
-
-
- Posts: 151
Re: Wedge repo -- installation feedback
« Reply #121, on January 28th, 2014, 09:30 AM »Last edited on January 28th, 2014, 09:49 AM
To test the new installer. Remove all folders except for assets and core. Upload /assets/icons/media. Upload /install. Remove Settings.php. run index.php (NOT install/install.php!) Done.Posted: January 27th, 2014, 10:21 PM
Also, upload the /core/app/OriginalFiles.php file.
I'm sorry, I forgot to add it to the repo. I'd indeed add it to the index, but forgot to hit F5 to refresh my file list, and thus it wasn't added to the changeset.
This should now work for everyone...
On a side note, mass upload is still not working in this install.
My Alpha test site; http://www.pplb.net/wedge/index.php
Nao
- Dadman with a boy
-
-
- Posts: 16,082
Can you be more specific when you say something doesn't work...? Because it works perfectly for me now...
It was only broken due to a last-minute change long ago where I removed a test for the upcook query string, and replaced it for an AJAX test... Which was wrong on two levels: (1) I did the reverse of the test I was thinking about, (2) Flash-based uploads never use Ajax, they just use a regular request, so I had to actually force Ajax status in QueryString.php, which was a waste of time, (3) it also disrupted the template flow, and made it impossible to issue a proper response. Not my most glorious change in the codebase, indeed, but if there's one thing I can be proud of, it's that I don't have any problems recognizing my errors. In this case, it was a human error, and I'm happy it got a human solution. :P
Oooooh, new bug! Inline me's! Yay! :lol:
It was only broken due to a last-minute change long ago where I removed a test for the upcook query string, and replaced it for an AJAX test... Which was wrong on two levels: (1) I did the reverse of the test I was thinking about, (2) Flash-based uploads never use Ajax, they just use a regular request, so I had to actually force Ajax status in QueryString.php, which was a waste of time, (3) it also disrupted the template flow, and made it impossible to issue a proper response. Not my most glorious change in the codebase, indeed, but if there's one thing I can be proud of, it's that I don't have any problems recognizing my errors. In this case, it was a human error, and I'm happy it got a human solution. :P
* Nao thinks he just wrote a Like-magnet.
* Nao likes Like-magnets.
* Nao likes Likes.
Oooooh, new bug! Inline me's! Yay! :lol:
Powerbob
-
-
- Posts: 151
Nope sorry, I get this error;
📎 massupload new error.JPG - 32.21 kB, 412x345, viewed 332 times.
Nao
- Dadman with a boy
-
-
- Posts: 16,082
Lol... It's a typical mass upload error that's been here since the SMF days. It's not related to Wedge at all.
Just search for Aeva Media error 2038 on Google. :P
To be more specific, most of these 2038's can be fixed by adding a crossdomain.xml file to your forum's root, with this content:
Code: [Select]
Replace myforum with your actual URL, of course.
It might be another problem, but it's always about domains and subdomains, to my knowledge.
Rewriting mass upload to use Ajax is one of my next projects. But not a very priority, I'm afraid.
Just search for Aeva Media error 2038 on Google. :P
Posted: January 28th, 2014, 01:34 PM
To be more specific, most of these 2038's can be fixed by adding a crossdomain.xml file to your forum's root, with this content:
<?xml version="1.0"?>
<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
<allow-access-from domain="*.myforum.com" />
<allow-access-from domain="myforum.com" />
</cross-domain-policy>Replace myforum with your actual URL, of course.
It might be another problem, but it's always about domains and subdomains, to my knowledge.
Rewriting mass upload to use Ajax is one of my next projects. But not a very priority, I'm afraid.
Powerbob
-
-
- Posts: 151
Nope sorry no change :whistle:
Nao
- Dadman with a boy
-
-
- Posts: 16,082
Read more docs. There are multiple solutions.
I won't commit to a 'fix' because this feature is only temp.
I won't commit to a 'fix' because this feature is only temp.
Powerbob
-
-
- Posts: 151
Ok Nao, no problem I can wait :cool:
Tried to install the new files from the repo with the new install on a new account on the same host and get this!
Parse error: syntax error, unexpected T_CONST in /home/sfellows/public_html/wedge/index.php on line 14
and the install stops there?
Tried to install the new files from the repo with the new install on a new account on the same host and get this!
Parse error: syntax error, unexpected T_CONST in /home/sfellows/public_html/wedge/index.php on line 14
and the install stops there?
Nao
- Dadman with a boy
-
-
- Posts: 16,082
Oh bugger, I forgot that the new install process, since it goes through index.php first, should ensure pre-install.php executions don't run into PHP 5.3-only calls.
I'll fix that ASAP.
Just replace lines 14 and 15 of index.php with:
Code: [Select]
And yes, it won't help you much... This all means that you're using PHP 5.2 or less, and you need to upgrade/fix your server, or switch to a more competent host.
I'll fix that ASAP.
Just replace lines 14 and 15 of index.php with:
define('WEDGE_VERSION', '0.1');
define('WEDGE', 1); // We are go.And yes, it won't help you much... This all means that you're using PHP 5.2 or less, and you need to upgrade/fix your server, or switch to a more competent host.
Did the Install Yesterday On a sub-domain/ created DB > uploaded all files via ftp > had all DB info ready, typed in the url and let the install process begin, Install went well no issues, well done!
Note the redirect to install worked great, installed my information > was done in a few!
For those who no not > the info in the form fields during install are on example, you must enter you DB name User db name and passwords you created for that DB, "local host" is the only one you will use! > don't forget to remove the Install.php at the finish of the install, then I would go a head and down load the settings.php to you local disk for back up purposes.
Thanks!
regards,
Maxx
Note the redirect to install worked great, installed my information > was done in a few!
For those who no not > the info in the form fields during install are on example, you must enter you DB name User db name and passwords you created for that DB, "local host" is the only one you will use! > don't forget to remove the Install.php at the finish of the install, then I would go a head and down load the settings.php to you local disk for back up purposes.
Thanks!
regards,
Maxx
Nao
- Dadman with a boy
-
-
- Posts: 16,082
Did the Install Yesterday On a sub-domain/ created DB > uploaded all files via ftp > had all DB info ready, typed in the url and let the install process begin, Install went well no issues, well done!
Note the redirect to install worked great, installed my information > was done in a few!
But yeah, this technique was never used in an SMF codebase before, AFAIK, and it makes it much easier to install Wedge from the same package, because then you get to decide whether or not you wish to reinstall (ie, remove Settings.php from the root folder), and it doesn't depend on the package you're using. Also, security-wise, you no longer need to get rid of the install.php file after installing, because it can't do anything by itself. I'd still recommend removing it (I haven't made a full security evaluation on this, and I'm sure there are more people who are more knowledgeable about security than I am), but I'm also tempted to remove the admin warning when it isn't.
For those who no not > the info in the form fields during install are on example, you must enter you DB name User db name and passwords you created for that DB, "local host" is the only one you will use!
> don't forget to remove the Install.php at the finish of the install, then I would go a head and down load the settings.php to you local disk for back up purposes.
MultiformeIngegno
-
-
- Posts: 1,337
@Maxx localhost is just when you have your mysql server running in the same "environment" of your webserver..
Thanks!
Just wanted say it went well!
And also want to direct some of my friends here to check this out, The backup is just in case, I change my mind about where to put, it don't for get, if I have an accident ... getting old LOL! :)
:)
Maxx
Just wanted say it went well!
And also want to direct some of my friends here to check this out, The backup is just in case, I change my mind about where to put, it don't for get, if I have an accident ... getting old LOL! :)
:)
Maxx
havok
-
- Posts: 29
did a reinstall with the new guidelines. went well
Farjo
- "a valuable asset to the community"
-
-
- Posts: 492
I get this message on a fresh install, just after creating the admin account. The message lies across the top of the next screen (i.e. the "Congratulations, the installation process is complete!" step=5 screen). It doesn't stop the installation and is fairly unnoticeable, so it may have been happening a while.