From b2df86054646aac86c6eea6dc103413596bfc514 Mon Sep 17 00:00:00 2001 From: Daniel Willmann Date: Sun, 14 Jun 2020 12:57:36 +0200 Subject: [PATCH 01/16] Add option to set a locale MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit As mentioned in https://www.php.net/manual/en/function.basename.php both basename() and dirname() are locale aware. An incorrect locale can cause the page tree to behave in strange ways. For example the structure /über-uns |-index.md |-impressum.md could lead to the page impressum not being a child of über-uns. --- config/config.yml.template | 1 + lib/Pico.php | 5 +++++ 2 files changed, 6 insertions(+) diff --git a/config/config.yml.template b/config/config.yml.template index 159585b..5500ccb 100644 --- a/config/config.yml.template +++ b/config/config.yml.template @@ -7,6 +7,7 @@ base_url: ~ # Pico will try to guess its base URL, if th rewrite_url: ~ # A boolean (true or false) indicating whether URL rewriting is forced debug: ~ # Set this to true to enable Pico's debug mode timezone: ~ # Your PHP installation might require you to manually specify a timezone +locale: ~ # Your PHP installation might require you to manually specify a locale to use ## # Theme diff --git a/lib/Pico.php b/lib/Pico.php index efb5b33..071e66f 100644 --- a/lib/Pico.php +++ b/lib/Pico.php @@ -936,6 +936,7 @@ class Pico 'rewrite_url' => null, 'debug' => null, 'timezone' => null, + 'locale' => null, 'theme' => 'default', 'theme_config' => null, 'theme_meta' => null, @@ -974,6 +975,10 @@ class Pico } date_default_timezone_set($this->config['timezone']); + if ($this->config['locale'] !== null) { + setlocale(LC_ALL, $this->config['locale']); + } + if (!$this->config['plugins_url']) { $this->config['plugins_url'] = $this->getUrlFromPath($this->getPluginsDir()); } else { From 1345d6ac82909da119d99ec1ddb3bc3b5fe4f485 Mon Sep 17 00:00:00 2001 From: Dimitri Merejkowsky Date: Mon, 29 Jun 2020 21:37:24 +0200 Subject: [PATCH 02/16] More inclusive README Replace 'you guys' by something more gender neutral. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9b9fbc1..bca6f45 100644 --- a/README.md +++ b/README.md @@ -77,7 +77,7 @@ Git is a very powerful distributed version-control system - and it can be used t ### I'm a developer -So, you're one of these amazing folks making all of this possible? We love you guys! As a developer we recommend you to clone [Pico's Git repository][PicoGit] as well as the Git repositories of [Pico's default theme][PicoThemeGit] and the [`PicoDeprecated` plugin][PicoDeprecatedGit]. You can set up your workspace using [Pico's Composer starter project][PicoComposerGit] and include all of Pico's components using local packages. +So, you're one of these amazing people making all of this possible? We love you folks! As a developer we recommend you to clone [Pico's Git repository][PicoGit] as well as the Git repositories of [Pico's default theme][PicoThemeGit] and the [`PicoDeprecated` plugin][PicoDeprecatedGit]. You can set up your workspace using [Pico's Composer starter project][PicoComposerGit] and include all of Pico's components using local packages. Using Pico's Git repositories is different from using one of the installation methods elucidated above. It gives you the current development version of Pico, what is likely *unstable* and *not ready for production use*! @@ -198,7 +198,7 @@ Contributing You want to contribute to Pico? We really appreciate that! You can help make Pico better by [contributing code][PullRequests] or [reporting issues][Issues], but please take note of our [contribution guidelines][ContributionGuidelines]. In general you can contribute in three different areas: -1. Plugins & Themes: You're a plugin developer or theme designer? We love you guys! You can find tons of information about how to develop plugins and themes at http://picocms.org/development/. If you have created a plugin or theme, please add it to our [Wiki][], either on the [plugins][WikiPlugins] or [themes][WikiThemes] page. You may also [Submit][] it to our website, where it'll be displayed on the official [plugin][OfficialPlugins] or [theme][OfficialThemes] pages! +1. Plugins & Themes: You're a plugin developer or theme designer? We love you folks! You can find tons of information about how to develop plugins and themes at http://picocms.org/development/. If you have created a plugin or theme, please add it to our [Wiki][], either on the [plugins][WikiPlugins] or [themes][WikiThemes] page. You may also [Submit][] it to our website, where it'll be displayed on the official [plugin][OfficialPlugins] or [theme][OfficialThemes] pages! 2. Documentation: We always appreciate people improving our documentation. You can either improve the [inline user docs][EditInlineDocs] or the more extensive [user docs on our website][EditUserDocs]. You can also improve the [docs for plugin and theme developers][EditDevDocs]. Simply fork our website's Git repository from https://github.com/picocms/picocms.github.io, change the Markdown files and open a [pull request][PullRequestsWebsite]. From 649feed2f6c1a28c3ed492c8fdae0182dbc7c487 Mon Sep 17 00:00:00 2001 From: Daniel Rudolf Date: Fri, 10 Jul 2020 18:20:59 +0200 Subject: [PATCH 03/16] Update CHANGELOG.md --- CHANGELOG.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index a44f9a4..2676f33 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -16,6 +16,14 @@ Pico Changelog `PicoDeprecated`'s changelog. Please note that BC-breaking changes are only possible with a new major version. +### Version 2.1.3 +Released: 2020-07-10 + +``` +* [New] Add `locale` option to `config/config.yml` +* [Changed] Improve Pico docs +``` + ### Version 2.1.2 Released: 2020-04-10 From 590d467347bce5f23d06068b93370bfaa24d356e Mon Sep 17 00:00:00 2001 From: Daniel Rudolf Date: Fri, 10 Jul 2020 18:51:32 +0200 Subject: [PATCH 04/16] Update Pico::VERSION and Pico::VERSION_ID --- lib/Pico.php | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/Pico.php b/lib/Pico.php index 071e66f..ae53e68 100644 --- a/lib/Pico.php +++ b/lib/Pico.php @@ -49,14 +49,14 @@ class Pico * * @var string */ - const VERSION = '2.1.2'; + const VERSION = '2.1.3'; /** * Pico version ID * * @var int */ - const VERSION_ID = 20102; + const VERSION_ID = 20103; /** * Pico API version From 4be1f6ae90e66c6df23cd6b61911b277df4886fa Mon Sep 17 00:00:00 2001 From: Daniel Rudolf Date: Wed, 9 Sep 2020 17:52:11 +0200 Subject: [PATCH 06/16] Try to proberly encode formatted date strings returned by strftime() Fixes #560 --- composer.json | 1 + lib/Pico.php | 13 +++++++++++-- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/composer.json b/composer.json index 02b45aa..b9ff27c 100644 --- a/composer.json +++ b/composer.json @@ -32,6 +32,7 @@ }, "require": { "php": ">=5.3.6", + "ext-mbstring": "*", "twig/twig": "^1.36", "symfony/yaml" : "^2.8", "erusev/parsedown": "1.8.0-beta-7", diff --git a/lib/Pico.php b/lib/Pico.php index ae53e68..f6384f9 100644 --- a/lib/Pico.php +++ b/lib/Pico.php @@ -1518,8 +1518,17 @@ class Pico } if (empty($meta['date_formatted'])) { - $dateFormat = $this->getConfig('date_format'); - $meta['date_formatted'] = $meta['time'] ? utf8_encode(strftime($dateFormat, $meta['time'])) : ''; + if ($meta['time']) { + $encodingList = mb_detect_order(); + if ($encodingList === array('ASCII', 'UTF-8')) { + $encodingList[] = 'Windows-1252'; + } + + $rawFormattedDate = strftime($this->getConfig('date_format'), $meta['time']); + $meta['date_formatted'] = mb_convert_encoding($rawFormattedDate, 'UTF-8', $encodingList); + } else { + $meta['date_formatted'] = ''; + } } } else { // guarantee array key existance From 1916dc5645bf71d7a6f68f4e46f478b0581370d6 Mon Sep 17 00:00:00 2001 From: Daniel Rudolf Date: Sat, 29 Aug 2020 16:07:10 +0200 Subject: [PATCH 07/16] Silence PHP notices in upstream Parsedown Parsedown is a still unresolved issue in whole, this at least ensures that we don't fill up logfiles with useless errors... --- lib/Pico.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/Pico.php b/lib/Pico.php index f6384f9..26dfb59 100644 --- a/lib/Pico.php +++ b/lib/Pico.php @@ -1673,7 +1673,7 @@ class Pico public function parseFileContent($markdown, $singleLine = false) { $markdownParser = $this->getParsedown(); - return !$singleLine ? $markdownParser->text($markdown) : $markdownParser->line($markdown); + return !$singleLine ? @$markdownParser->text($markdown) : @$markdownParser->line($markdown); } /** From e4741d0fde8b64bd1f93bbee493f71fdbd4105f3 Mon Sep 17 00:00:00 2001 From: Daniel Rudolf Date: Sat, 29 Aug 2020 16:14:52 +0200 Subject: [PATCH 08/16] Update CHANGELOG.md --- CHANGELOG.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 2676f33..bf84f7b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -16,6 +16,15 @@ Pico Changelog `PicoDeprecated`'s changelog. Please note that BC-breaking changes are only possible with a new major version. +### Version 2.1.4 +Released: 2020-08-29 + +``` +* [Changed] Silence PHP errors in Parsedown +* [Fixed] #560: Improve charset guessing for formatted date strings using + `strftime()` (Pico always uses UTF-8, but `strftime()` might not) +``` + ### Version 2.1.3 Released: 2020-07-10 From b95cfe0a0ef5f504dbff76e810cf99db5dcfcc75 Mon Sep 17 00:00:00 2001 From: Daniel Rudolf Date: Sat, 29 Aug 2020 16:15:37 +0200 Subject: [PATCH 09/16] Update Pico::VERSION and Pico::VERSION_ID --- lib/Pico.php | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/Pico.php b/lib/Pico.php index 26dfb59..af68379 100644 --- a/lib/Pico.php +++ b/lib/Pico.php @@ -49,14 +49,14 @@ class Pico * * @var string */ - const VERSION = '2.1.3'; + const VERSION = '2.1.4'; /** * Pico version ID * * @var int */ - const VERSION_ID = 20103; + const VERSION_ID = 20104; /** * Pico API version From 221625efacb726235ed86ad110472539826a608d Mon Sep 17 00:00:00 2001 From: Daniel Rudolf Date: Wed, 11 Nov 2020 16:10:46 +0100 Subject: [PATCH 11/16] CONTRIBUTING.md: Rename 'type: Question' label to 'type: Support' --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9d37588..4eafb00 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -192,7 +192,7 @@ Issues and pull requests labeled with `info: Feedback Needed` indicate that feed - The `type: Release` label is used in the exact same way as `type: Feature` and indicates the primary pull request of a new Pico release (please refer to the *Branching* and *Build & Release process* sections above). -- The `type: Notice`, `type: Question` and `type: Discussion` labels are used to indicate "fyi" issues, issues opened by users or developers asking questions, and issues with disucssions about arbitrary topics related to Pico. They are neither combined with `pri` labels, nor with `status` labels. +- The `type: Notice`, `type: Support` and `type: Discussion` labels are used to indicate "fyi" issues, support-related issues (e.g. issues opened by users or developers asking questions), and issues with disucssions about arbitrary topics related to Pico. They are neither combined with `pri` labels, nor with `status` labels. - The `type: Duplicate` label is used when there is already another issue or pull request related to this problem or feature request. Issues labeled with `type: Duplicate` are immediately closed. @@ -200,7 +200,7 @@ Issues and pull requests labeled with `info: Feedback Needed` indicate that feed The `status: Deferred` label might get added to any open issue or pull request to indicate that it is still unresolved and will be resolved later. This is also true for the `info: Pinned` label: It indicates a important issue or pull request that remains open on purpose. -After resolving a issue, we usually keep it open for about a week to give users some more time for feedback and further questions. This is especially true for issues with the `type: Notice`, `type: Question`, `type: Discussion` and `type: Invalid` labels. After 7 days with no interaction, [Probot](https://probot.github.io/)'s [Stale](https://github.com/apps/stale) bot adds the `info: Stale` label to the issue to ask the participants whether the issue has been resolved. If no more activity occurs, the issue will be automatically closed by Stale bot 2 days later. +After resolving a issue, we usually keep it open for about a week to give users some more time for feedback and further questions. This is especially true for issues with the `type: Notice`, `type: Support`, `type: Discussion` and `type: Invalid` labels. After 7 days with no interaction, [Probot](https://probot.github.io/)'s [Stale](https://github.com/apps/stale) bot adds the `info: Stale` label to the issue to ask the participants whether the issue has been resolved. If no more activity occurs, the issue will be automatically closed by Stale bot 2 days later. Issues and pull requests labeled with `info: Information Needed` indicate that we have asked one of the participants for further information and didn't receive any feedback yet. It is usually added after Stale bot adds the `info: Stale` label to give the participants some more days to give the necessary information. From d8470f9f5cee881390103cab441aed7301dd5e15 Mon Sep 17 00:00:00 2001 From: Daniel Rudolf Date: Tue, 9 Mar 2021 13:40:16 +0100 Subject: [PATCH 12/16] Replace Probot Stale with GitHub Action Looks like Probot Stale is abandoned... Too bad. :unamused: --- .github/stale.yml | 17 ----------------- .github/workflows/stale.yml | 28 ++++++++++++++++++++++++++++ 2 files changed, 28 insertions(+), 17 deletions(-) delete mode 100644 .github/stale.yml create mode 100644 .github/workflows/stale.yml diff --git a/.github/stale.yml b/.github/stale.yml deleted file mode 100644 index c924670..0000000 --- a/.github/stale.yml +++ /dev/null @@ -1,17 +0,0 @@ -daysUntilStale: 7 -daysUntilClose: 2 -exemptLabels: - - "type: Bug" - - "type: Enhancement" - - "type: Feature" - - "type: Idea" - - "type: Release" - - "info: Pinned" -staleLabel: "info: Stale" -markComment: > - This issue has been automatically marked as stale because it has not had - recent activity. It will be closed in two days if no further activity - occurs. Thank you for your contributions! :+1: -unmarkComment: false -closeComment: false -only: issues diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml new file mode 100644 index 0000000..878d942 --- /dev/null +++ b/.github/workflows/stale.yml @@ -0,0 +1,28 @@ +name: "Mark or close stale issues and PRs" +on: + schedule: + - cron: "0 12 * * *" + +jobs: + stale: + runs-on: ubuntu-latest + steps: + - uses: actions/stale@v3 + with: + repo-token: ${{ secrets.GITHUB_TOKEN }} + days-before-stale: 7 + days-before-close: 2 + stale-issue-message: > + This issue has been automatically marked as stale because it has not had + recent activity. It will be closed in two days if no further activity + occurs. Thank you for your contributions! :+1: + stale-pr-message: > + This pull request has been automatically marked as stale because it has not had + recent activity. It will be closed in two days if no further activity + occurs. Thank you for your contributions! :+1: + stale-pr-label: "info: Stale" + stale-issue-label: "info: Stale" + exempt-issue-labels: "type: Bug,type: Enhancement,type: Feature,type: Idea,type: Release,info: Pinned" + exempt-pr-labels: "type: Bug,type: Enhancement,type: Feature,type: Idea,type: Release,info: Pinned" + remove-stale-when-updated: true + From d0f32c0a2b0ac841b0956d599ab7303c81e5fbc4 Mon Sep 17 00:00:00 2001 From: Daniel Rudolf Date: Mon, 21 Jun 2021 20:45:31 +0200 Subject: [PATCH 13/16] Create SECURITY.md --- SECURITY.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..d320d34 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,15 @@ +# Security Policy + +## Supported Versions + +Only the most recent stable version of Pico is supported. + +## Reporting a Vulnerability + +To mitigate the impact of possible security issues we ask you to disclose any security issues with Pico privately first ("responsible disclosure"). To do so please send an email to Pico's lead developer: + +> Daniel Rudolf \ + +You should receive an answer within 48 hours. + +All messages with valid security reports will be puslished on GitHub in full text. From 09fbaaaf3385ccb1326df519e3c84cb2c7d69992 Mon Sep 17 00:00:00 2001 From: Daniel Rudolf Date: Fri, 13 Aug 2021 17:19:24 +0200 Subject: [PATCH 14/16] IRC: Switch from Freenode to Libera.Chat --- README.md | 8 ++++---- content-sample/_meta.md | 4 ++-- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index bca6f45..213f419 100644 --- a/README.md +++ b/README.md @@ -4,7 +4,7 @@ Pico [![License](https://picocms.github.io/badges/pico-license.svg)](https://github.com/picocms/Pico/blob/master/LICENSE.md) [![Version](https://picocms.github.io/badges/pico-version.svg)](https://github.com/picocms/Pico/releases/latest) [![Build Status](https://api.travis-ci.org/picocms/Pico.svg?branch=master)](https://travis-ci.org/picocms/Pico) -[![Freenode IRC Webchat](https://picocms.github.io/badges/pico-chat.svg)](https://webchat.freenode.net/?channels=%23picocms) +[![Libera.Chat](https://picocms.github.io/badges/pico-chat.svg)](https://web.libera.chat/#picocms) [![Open Bounties on Bountysource](https://www.bountysource.com/badge/team?team_id=198139&style=bounties_received)](https://www.bountysource.com/teams/picocms) Pico is a stupidly simple, blazing fast, flat file CMS. @@ -189,7 +189,7 @@ If you're a developer, please refer to the "Contributing" section below and our #### You still need help or experience a problem with Pico? -When the docs can't answer your question, you can get help by joining us on [#picocms on Freenode IRC][Freenode] ([logs][FreenodeLogs]). When you're experiencing problems with Pico, please don't hesitate to create a new [Issue][Issues] on GitHub. Concerning problems with plugins or themes, please refer to the website of the developer of this plugin or theme. +When the docs can't answer your question, you can get help by joining us on [#picocms on Libera.Chat][LiberaChat] ([logs][LiberaChatLogs]). When you're experiencing problems with Pico, please don't hesitate to create a new [Issue][Issues] on GitHub. Concerning problems with plugins or themes, please refer to the website of the developer of this plugin or theme. **Before creating a new Issue,** please make sure the problem wasn't reported yet using [GitHubs search engine][IssuesSearch]. Please describe your issue as clear as possible and always include the *Pico version* you're using. Provided that you're using *plugins*, include a list of them too. We need information about the *actual and expected behavior*, the *steps to reproduce* the problem, and what steps you have taken to resolve the problem by yourself (i.e. *your own troubleshooting*). @@ -245,8 +245,8 @@ Official Pico Contributors won't claim bounties on their own behalf, Pico will n [WikiThemes]: https://github.com/picocms/Pico/wiki/Pico-Themes [Issues]: https://github.com/picocms/Pico/issues [IssuesSearch]: https://github.com/picocms/Pico/search?type=Issues -[Freenode]: https://webchat.freenode.net/?channels=%23picocms -[FreenodeLogs]: http://picocms.org/irc-logs +[LiberaChat]: https://web.libera.chat/#picocms +[LiberaChatLogs]: http://picocms.org/irc-logs [PullRequests]: https://github.com/picocms/Pico/pulls [PullRequestsWebsite]: https://github.com/picocms/picocms.github.io/pulls [ContributionGuidelines]: https://github.com/picocms/Pico/blob/master/CONTRIBUTING.md diff --git a/content-sample/_meta.md b/content-sample/_meta.md index d18f051..11b845e 100644 --- a/content-sample/_meta.md +++ b/content-sample/_meta.md @@ -5,8 +5,8 @@ Social: - title: Visit us on GitHub url: https://github.com/picocms/Pico icon: octocat - - title: Join us on Freenode IRC Webchat - url: https://webchat.freenode.net/?channels=%23picocms + - title: Join us on Libera.Chat + url: https://web.libera.chat/#picocms icon: chat - title: Help us by creating/collecting bounties and pledging to fundraisers url: https://www.bountysource.com/teams/picocms From 2e425dc8ef2d68a58a35fa8953eadc683b245f68 Mon Sep 17 00:00:00 2001 From: dipohl Date: Sun, 15 Aug 2021 11:02:43 +0200 Subject: [PATCH 15/16] Update index.md Checked all web links and updated them where necessary especially eliminating some 404 errors. --- content-sample/index.md | 26 ++++++++++++-------------- 1 file changed, 12 insertions(+), 14 deletions(-) diff --git a/content-sample/index.md b/content-sample/index.md index 341ebec..6e7460e 100644 --- a/content-sample/index.md +++ b/content-sample/index.md @@ -190,8 +190,7 @@ uses [Twig][] for template rendering. You can select your theme by setting the productive website, it's rather a starting point for creating your own theme. If the default theme isn't sufficient for you, and you don't want to create your own theme, you can use one of the great themes third-party developers and -designers created in the past. As with plugins, you can find themes in -[our Wiki][WikiThemes] and on [our website][OfficialThemes]. +designers created in the past. As with plugins, you can find themes on [our website][OfficialThemes]. All themes must include an `index.twig` file to define the HTML structure of the theme, and a `pico-theme.yml` to set the necessary config parameters. Just @@ -486,24 +485,23 @@ url.rewrite-if-not-file = ( ## Documentation -For more help have a look at the Pico documentation at http://picocms.org/docs. +For more help have a look at the Pico documentation at https://picocms.org/docs/. -[Pico]: http://picocms.org/ +[Pico]: https://picocms.org/ [PicoTheme]: https://github.com/picocms/pico-theme [SampleContents]: https://github.com/picocms/Pico/tree/master/content-sample -[Markdown]: http://daringfireball.net/projects/markdown/syntax +[Markdown]: https://daringfireball.net/projects/markdown/syntax [MarkdownExtra]: https://michelf.ca/projects/php-markdown/extra/ [YAML]: https://en.wikipedia.org/wiki/YAML -[Twig]: http://twig.sensiolabs.org/documentation -[UnixTimestamp]: https://en.wikipedia.org/wiki/Unix_timestamp +[Twig]: https://twig.symfony.com/doc/ +[UnixTimestamp]: https://en.wikipedia.org/wiki/Unix_time [Composer]: https://getcomposer.org/ -[FeaturesHttpParams]: http://picocms.org/in-depth/features/http-params/ -[FeaturesPageTree]: http://picocms.org/in-depth/features/page-tree/ -[FeaturesPagesFunction]: http://picocms.org/in-depth/features/pages-function/ -[WikiThemes]: https://github.com/picocms/Pico/wiki/Pico-Themes +[FeaturesHttpParams]: https://picocms.org/in-depth/features/http-params/ +[FeaturesPageTree]: https://picocms.org/in-depth/features/page-tree/ +[FeaturesPagesFunction]: https://picocms.org/in-depth/features/pages-function/ [WikiPlugins]: https://github.com/picocms/Pico/wiki/Pico-Plugins -[OfficialThemes]: http://picocms.org/themes/ -[PluginUpgrade]: http://picocms.org/development/#upgrade +[OfficialThemes]: https://picocms.org/themes/ +[PluginUpgrade]: https://picocms.org/development/#migrating-plugins [ModRewrite]: https://httpd.apache.org/docs/current/mod/mod_rewrite.html [AllowOverride]: https://httpd.apache.org/docs/current/mod/core.html#allowoverride -[NginxConfig]: http://picocms.org/in-depth/nginx/ +[NginxConfig]: https://picocms.org/in-depth/nginx/ From ff5e345e58f6ccdb2683ea33a2fde3337853ca0c Mon Sep 17 00:00:00 2001 From: Maya McDougall <12779160+mayamcdougall@users.noreply.github.com> Date: Sun, 6 Feb 2022 16:34:18 -0500 Subject: [PATCH 16/16] Added Temporary PHP 8.0 Notice --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index 213f419..d1db6b9 100644 --- a/README.md +++ b/README.md @@ -11,6 +11,22 @@ Pico is a stupidly simple, blazing fast, flat file CMS. Visit us at http://picocms.org/ and see http://picocms.org/about/ for more info. +--- + +### PHP 8.0+ Users + +Seeing an `Unparenthesized a ? b : c ? d : e is not supported.` error? + +Pico currently has issues with PHP versions newer than 8.0. This is due to Pico's dependencies, and not Pico itself. There's currently an "alpha" build of Pico you can download as a [Pre-Bundled Release](https://github.com/picocms/Pico/releases/tag/v3.0.0-alpha.2) that solves this issue. + +This "alpha" is **perfectly safe** to use in production, as the *only* changes are **updated dependencies and version number strings**. If you're curious, you can confirm this by [comparing the changes](https://github.com/picocms/Pico/compare/pico-3.0-alpha) between branches. + +More work was intended to be done on this branch, hence the "3.0" label, but it hasn't happened yet. There's an [on-going discussion](https://github.com/picocms/Pico/issues/608) about getting just these updated dependencies merged in as an official update (either Pico 2.2 or 3.0) as soon as possible. + +Sorry for the inconvenience, and thanks to all Pico users for your patience on the matter. ❤️ + +--- + Screenshot ----------