Upgrade Broke Local Site

Hi, I am new to Grav. With all of the current WordPress drama, I'm exploring alternatives and Grav came up as a suggestion. I've been toying with a local install for the past week. I installed a zip file of Grav + Admin version 1.7.46 and have been poking around ever since.

Today, I noticed in the admin a notification for version 1.7.47. I decided to check out the upgrade process and clicked the button to upgrade. It said that the upgrade completed.

When I clicked the Dashboard link, I received a Page Not Found. When I tried browsing to any page in the admin from my browser history, it was the same thing. When I tried to load the homepage, I received a 403 Forbidden error and all other pages were Page Not Found errors.

I backed up my user folder, deleted the site, and then downloaded the zip file for the latest version and the admin. I unzipped the files to my directory and then dropped my backed up user folder into it. All started working again.

As a new user, is there anything I should know for future upgrades?

I did the same just now and also got the same error. Let me download the files manually.

I have updated a Grav version from my computer and have not had any problems. This has never happened to me with the websites I have in production.

I am not en expert but... the first thing I would look at is if any folder or file has changed ownership when updating. On a linux server I would open a terminal in the root folder of the installation and order the command:

(sudo) chown user:user -R *

where user is the user assigned to the other files.

Tell us

I upgraded to version 1.7.48 this evening and the same exact thing happened.

After comparing the upgraded install to a backup, I noticed that my install no longer had an index.php in the root directory. I dropped it in from the backup and both the website and the admin both began working again.

I'm not sure why upgrading on my local machine is resulting in a critical file like index.php being deleted.

I noticed that, too. I have two dev machines and the crash happened in both. Restoring the index.php file resolved the issue.