Hello, I had php 7.2 installed and this meant I had issues with access to the panel. It took me days of frustration to uninstall and reinstall apache and update to php 8.0. I am now not able to access my webpages at all and get this error: This page is currently offline. We are very sorry for the inconvenience and will fix it as soon as possible. I am now being advised to change the PHP version to 7.2, 7.3 or 7.4. Does this mean you do not support php8.0? If this is the case can someone please advise me a less complicated way to change my php version from 8.0 back down to 7.4 with xampp? Thanks.
Kirby 3.5 does support PHP 8. What is your Kirby version?
Not a Xampp user, but looking on their download page, there are different versions with different PHP versions available. So changing the PHP version seems to be a matter of deinstalling the current version and installing a different version.
What is your operating system?
You might want to consider a dev environment where changing the PHP version is easier:
thank you for the reply, if the latest verision of Kirby sypports php8, then I will keep this. How do I check the version of Kirby I am running?
Usually you can see this in the Panel, under settings, but if you cannot access the Panel, then that’s of course not possible.
Other option:
Have a look at the composer.json file in your Kirby project folder. Under “version” you will find the Kirby version.
I’m pretty sure you are not on 3.5.0 if the error message tells you to use 7.2, 7.3 or 7.4, because Kirby 3.5 will say: use 7.3, 7.4 or 8.0 (support for PHP 7.2 was dropped in Kirby 3.5).
Okay Brilliant, yes I am on “version”: “3.4.3”,. Is the best way for me to update this to download a new plainkit from the kirby website and replace the kirby folder with the new one from version 3.5.0?
You can either download the plainkit and replace the Kirby folder, or just download the kirby folder from GitHub
Urika! it worked, thank you. New PHP, new Kirby, New year, lets do this!
1 Like
Hey, I am still not abel to access panel though, I get this issue:
# Object not found!
The requested URL was not found on this server. If you entered the URL manually please check your spelling and try again.
If you think this is a server error, please contact the [webmaster](mailto:you@example.com).
## Error 404
[localhost](http://localhost:8080/)
Apache/2.4.46 (Unix) OpenSSL/1.1.1h PHP/8.0.0 mod_perl/2.0.11 Perl/v5.32.0That’s what you get when you enter http://localhost:8080/panel in the browser?
Hm, is this still a plainkit or have you created any other pages in the frontend? If so, do these work?
I have a feeling that maybe the .htaccess file is either ignored or rewriting is not enabled.
As a first step, add some garbage in .htaccess, if you then get a 500 error, we at least know that the server reads that file. From there we can investigate further.
Yes this is correct when I try to access panel. It is a plainkit and I have created other pages which work fine. It should be an .htaccess issue as I got the 500 error.
Here is the file:
# Kirby .htaccess
# revision 2020-06-15
# rewrite rules
<IfModule mod_rewrite.c>
# enable awesome urls. i.e.:
# http://yourdomain.com/about-us/team
RewriteEngine on
# make sure to set the RewriteBase correctly
# if you are running the site in a subfolder;
# otherwise links or the entire site will break.
#
# If your homepage is http://yourdomain.com/mysite,
# set the RewriteBase to:
#
# RewriteBase /mysite
# In some environments it's necessary to
# set the RewriteBase to:
#
# RewriteBase /
# block files and folders beginning with a dot, such as .git
# except for the .well-known folder, which is used for Let's Encrypt and security.txt
RewriteRule (^|/)\.(?!well-known\/) index.php [L]
# block all files in the content folder from being accessed directly
RewriteRule ^content/(.*) index.php [L]
# block all files in the site folder from being accessed directly
RewriteRule ^site/(.*) index.php [L]
# block direct access to Kirby and the Panel sources
RewriteRule ^kirby/(.*) index.php [L]
# make site links work
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*) index.php [L]
</IfModule>
# pass the Authorization header to PHP
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
# compress text file responses
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/plain
AddOutputFilterByType DEFLATE text/html
AddOutputFilterByType DEFLATE text/css
AddOutputFilterByType DEFLATE text/javascript
AddOutputFilterByType DEFLATE application/json
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript
RewriteBase /jaque/kirby-blank/kirby/blank
</IfModule>Ok, that means that at least Xampp does not ignore that file, that’s good.
If subpages work, then Rewriting should actually also work 
What is your OS?
Thats good. I am running macOS Mojave, version 10.14.6
Ok, and which version of Xampp for OS X? The VM variation or the other one?
I just installed Xampp on Big Sur for testing and the only problem I encountered when trying to access the Panel was permissons to create the media folder, but no “Object not found” error.
So it should actually work sort of out of the box.
Personally, I use Laravel Valet on my Mac without any issues.
I am not exactly sue which version, but it is the newest one with php8 included. I downloaded it this morning.
I tried the plain kit full download, the newst one with the 3.5.0 version. In this one when I go to /panel
I get this error: The Panel assets cannot be installed properly. The directory “/opt/lampp/htdocs/plainkit-master/media/panel” cannot be created
Yes, that’s the same error I got, you have to change the folder rights of the plainkit folder and all encloded ones to make it work.
thank you yes this worked, on mac in terminal to change all files recursively you need to change the file location and paste: ```
chmod -R 777 /Users/Test/Desktop/PATH
Generelly, it’s never a good idea to set permissions to 777. Probably doesn’t matter that much on your device with nobody else being able to access it, but never do this on a remote server.
The state of the art way of doing this would be to change ownership to the Apache user/group, if moving the file location alone didn’t help.
What is the ideal number to set permissions?
755/644
While this is about WP, it also applies to Kirby: