Skip to content
This repository has been archived by the owner on May 18, 2021. It is now read-only.

Installation - unclickable buttons "next step" #5

Open
ghost opened this issue Mar 12, 2016 · 7 comments
Open

Installation - unclickable buttons "next step" #5

ghost opened this issue Mar 12, 2016 · 7 comments
Labels

Comments

@ghost
Copy link

ghost commented Mar 12, 2016

No description provided.

@ghost ghost changed the title Installation - unclickable buttons Installation - unclickable buttons "next step" Mar 12, 2016
@sdavis-r7
Copy link
Contributor

@ghost please provide more description or screen shot? Best for everyone to understand.

@4loof
Copy link

4loof commented Aug 18, 2016

On installation step one, when I click "next step", there's no changes on the webpage. I captured the network found that the "next step" POST a request to the webserver and response a 302 and jump back to step one. I thought maybe that's the meaning of "unclickable buttons".

@PinkSheep
Copy link

I have the same issue as descibed by sonumine. Can't get past the first installation step (Admin Credentials). Clicking next step simply results in a 302 redirect response and resets the form.

@PierrickV
Copy link

Same error here
screenshot from 2016-11-23 21-07-53

@gmaran23
Copy link

Hello,
I have had the buttons unclickable and unable to move to the next step of the installation wizard or complete it. I installed the latest version version of wamp and did some further changes to fix the error.

Full details here - https://renouncedthoughts.wordpress.com/2017/02/21/getting-hackazon-up-and-running-on-wamp-on-nov-2016/

@TobinShields
Copy link

I also can confirm that I was unable to click on them during the installation. Interestingly, I was able to use tab and enter to move the installation forward--I just assumed it was something wrong on my end.

@dentonk
Copy link

dentonk commented Jul 5, 2018

I was having the issue where I could click the button however it would just refresh the page instead of going to the next step. I was using a non-standard port and as soon as I change it back to port 80 everything worked. Thanks to @gmaran23 for your post which pointed me in the right direction.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

7 participants