PhrozenByte
commented
6 years ago You basically applied the installation instructions for Pico 1.0 to Pico 2.0. This still works, but has the effects you described above. Starting with Pico 2.0 the main picocms/Pico repository is no longer the "frame" of Pico installations, but rather a dependency of a new separate "frame project" (picocms/pico-composer). It's picocms/pico-composer that installs both the PicoDeprecated plugin and Pico's default theme, picocms/Pico just suggests installing them.
See the "Install" section of Pico 2.0's README.md. If you've read the README.md before and remember that it looked completely different in beta 2, then you're absolutely right. We've updated the installation instructions just recently and after the release of beta 2, so you couldn't know this (i.e. you didn't make anything wrong). Nevertheless I highly recommend re-installing Pico using one of the new official Pico 2.0 installation methods. For a composer-based installation use the following:
composer create-project picocms/pico-composer .The Package … is abandoned messages are caused by development dependencies of Pico when installing Pico with development dependencies (what is the default when using composer install). These packages aren't necessary in a productive environment (try composer install --no-dev). Anyway, the messages don't cause any harm, they can be ignored.
sonst-was
Hi everyone,
I was eager to try the new version of Pico and downloaded the latest version (beta2). After downloading the pre-release and uploading everything to my webspace I was asked to use
composer installfirst. So I let composer do its thing and after a while it was done giving only the following warnings:I thought I'd be good and tried to access my new Pico installation but I only got a HTTP Error code 500. The PHP error log goes a bit more into details:
It looks like the PicoDeprecated plugin isn't loaded - and indeed it isn't in the plugins directory. So while writing this issue I just downloaded the plugin and uploaded it. I still get a HTTP Error code 500 but this time with a different error in the error log:
So apparently there is no default theme, which kinda explains why Pico is unable to display anything. After uploading the default theme it works now.
So... after I solved my issues by myself while writing this issue the only question I have left is: Shoudn't the PicoDeprecated plugin and the default theme included in the Pico installation by default? (I can see both issues not being applicable with the current code, but they are with the beta2 pre-release package)
Kind regards sonst-was