Tokenizer

Send private message

You must be logged in to send a private message.

Friends

No friends yet.

Group membership

Activity

  • Tokenizer replied on the discussion topic Cannot install Elgg 3.3.19 on XAMPP 7.4.20
    I managed to install Elgg. XD I've changed XAMPP ports to the default ones (Apache on 80 and MySQL on 3306). And it installs smooth with no error. Just in case, custom ports were open on the firewall. And other apps work fine on that XAMPP... view reply
  • Tokenizer replied on the discussion topic Cannot install Elgg 3.3.19 on XAMPP 7.4.20
    Does the config file <site-root-folder>/elgg-config/settings.php exist before or after your installation attempt? Not before. After installation attempt it does. Even if the file exists, what is with file permissions? Default... view reply
  • Tokenizer replied on the discussion topic Cannot install Elgg 3.3.19 on XAMPP 7.4.20
    Yes yes. I created the db previously. That's why I find so strange this error. Just in case, I've tried now with a nonexistent database. And the error, as expected, is different. And understandable: ERROR: Exception at time... view reply
  • Tokenizer added a new discussion topic Cannot install Elgg 3.3.19 on XAMPP 7.4.20 in the group Elgg Technical Support
    I'm trying to install a fresh Elgg 3.3.19 over a XAMPP 7.4.20, but it won't install. It seems that the database is not created. I've tried web and CLI. But no luck. c:\xampp7\php\php.exe .\vendor\bin\elgg-cli install Enter admin...
    • I managed to install Elgg. XD

      I've changed XAMPP ports to the default ones (Apache on 80 and MySQL on 3306). And it installs smooth with no error. Just in case, custom ports were open on the firewall. And other apps work fine on that XAMPP installation.

      Maybe a bug. But I don't know if its XAMPP's or Elgg's. Without further testing, I cannot blame anyone. But, indeed, something is trying to make request without considering configured ports.

       

      Thanks for helpping me out, @iionly

    • Would you happen to know if it's only the MySQL port that causes the issue if not using the default 3306? As the installation process itself seems working alright in the browser it might really be only the MySQL port. Could you maybe try if the database connection problem returns if you change the port to be used in elgg-config/settings.php?

      I would say it would be worth testing if there's a problem with using non-default ports and also opening an issue about it at github telling the core developers about it (maybe linking this topic, too). I would do it if you don't want to do it yourself.

    • I found the issue. It had to do with the alternate database port. In the configuration for the database schema the port configuration wasn't provided, so it used the default port (3306).

      This would cause the schema not being implemented on your database.

      FIxed in the next Elgg 3.3 release

      PS: for reference the GitHub issue https://github.com/Elgg/Elgg/issues/13590