I think we can close this one considering the "edit"?

The solution to this would be to write a check for each of the install steps to confirm that the database operations haven't been conducted yet.. you may also need to check the config.ini.php file for clues too. When you think about it, the 'nav bar' that shows the steps to installation is kind of broken in that you can't click through the links to make it work.

Some of the install steps are in fact simple hyper links which make GET requests rather than POST requests (the best practice for things that make server side changes).

Is there anyway we can get this re-opened? I've been bug tracking for quite a while and would be interested in having my fixes applied to upstream if possible.

Btw, where would I go to look for test coverage for the installation scripts at...

• plugins/Installation/Installation.php
• plugins/Installation/FormFirstWebsiteSetup.php

Hello, please use the latest version 2.16.2 where this should be fixed

Hi @mattab, your name has turned up on my browser more times than I can count over the last week. I know first/third hand that Piwik is a tough project to hack on, excellent open source work! It's nice to meet you.

I'm currently on 2.16.2... it's in a docker container.... I'm still tracking the bug(s?), thought I had it yesterday, but caught a brief case of carpel tunnel and had to switch to read only mode. I've been using curl commands to simulate the install process, and they're all leading up to either this bug or another one where piwik boasts that it needs to upgrade the database, and then fails due to their being missing columns.

#6746

I'm starting to think that the install process may require javascript or perhaps a cookie... or it' needs some sleep commands because the db is getting race conditions. I have a docker repo that isolates the phenomenon if you'd like to take a look at it with my I can upload it, but it's commit history looks like trash atm and is subject to change ><

I got my stuff working! I think it needed a couple GET requests that I didn't think were necessary. I'm going to articulate some code cleanliness issues below and possible move them into a new issue if they can be merged in here:

/index.php?action=firstWebsiteSetup has a post form that's dependent on the URL to it's GET/show page.

If you redirect / to render index.php?action-firstWebsiteSetup you will find that the post button on the form doesn't work. I believe this is due to the javascript layer stepping in and adjusting the POST path or something. I'm not 100% on this, I just know that the app works when JS is disabled. Seems related to angularJS. You can see the work in this dockerfile if interested: https://github.com/thenotary/piwik-dokku

I'm starting to think that the install process may require javascript or perhaps a cookie...

we actually don't test Piwik without JavaScript / without cookie use case. it's most likely not working. It's not really a priority or supported use case for us, ie. we don't test for it manually or via our automated tests suites. However if you find some issue and submit pull request so that Piwik works without javascript / cookies, we would for sure try to review them and merge them, so to make Piwik more usable by people who cannot use JavaScript for some reason.