This forum is archived. Posts are preserved for historical reference. For current help, join us on Discord.

4.2.6 Installation Issues

In UserSpice 4.3 and Below · Started by faguss on 2017-05-08 1:33 pm · 9595 views · 3 replies

  • #1 - Setting:File Uploads Recommended:ON Actual:OFF

I'd like to have some information displayed about this because I didn't know what that meant. After some digging I found out that allow_url_fopen is disabled by my host for security reasons. However, there's CURL so I took a function from here:

<pre>
function url_get_contents ($Url) {
	if (!function_exists('curl_init')){ 
        die('CURL is not installed!');
    }
    $ch = curl_init();
    curl_setopt($ch, CURLOPT_URL, $Url);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    $output = curl_exec($ch);
    curl_close($ch);
    return $output;
};
</pre>




And added it to recaptcha.config.php:
$response = url_get_contents($path . $req);

and to check_updates.php:
$remoteVersion=trim(url_get_contents(REMOTE_VERSION));

I find it inconvenient that replacing by usersc requires dependent files so I needed to copy all these:

check_updates.php
init.php
includes/user_spice_ver.php
includes/recaptcha.config.php
login.php

Also added page permission for usersc/check_updates.php in the Admin Dashboard.

Could you automatically detect CURL during installation and use it in place of file_get_contents?
  • #2 - Error performing query '/*!40101 SET NAMES utf8mb4 */; ':

I replaced utf8mb4 with utf8 in the installation sql.

  • #3 - Timezone selection not saved

Timezone is reverted to the first option when you press "Test Settings" button.

  • #4 - Parse error: syntax error in init.php on line 45

My copyright message has an apostrophe. Please add slashes to the user input.
THANK YOU so much for the detailed post.

You can definitely change the paths back to the dependent files when you copy something over to usersc.

Great feedback on the timezone and the copyright. I'm adding that to my "to fix" list. It's crazy busy around here right now, but I will definitely get it.

Would you mind telling me about your hosting provider/server? We haven't had many issues with the utf or the fopen.
Anything specific?

PHP Version 5.6.21
Directive:allow_url_fopen Local Value:Off Master Value:Off

Software: MySQL
Software version: 5.0.91-log - MySQL Community Server (GPL)
Protocol version: 10
Server charset: UTF-8 Unicode (utf8)
That's a pretty old version of mysql and probably explains a lot of your problems. It was released in 2010.