# Timeline for PHP8?

**URL:** <https://forum.mautic.org/t/timeline-for-php8/21427>\
**Category:** Development\
**Created:** [October 27, 2021, 1:21pm UTC](https://forum.mautic.org/t/timeline-for-php8/21427 "2021-10-27T13:21:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mkaaaay](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/mkaaaay/32/4707_2.png) [@mkaaaay](https://forum.mautic.org/u/mkaaaay)\
**Post date:** [October 27, 2021, 1:21pm UTC](https://forum.mautic.org/t/timeline-for-php8/21427/1 "2021-10-27T13:21:43Z")

</div>

Just wondering what the time line is for php8 support?

---

<div class="post-metadata">

**Author:** ![EJL](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/ejl/32/12155_2.png) [@EJL](https://forum.mautic.org/u/EJL)\
**Post date:** [October 27, 2021, 2:50pm UTC](https://forum.mautic.org/t/timeline-for-php8/21427/2 "2021-10-27T14:50:59Z")

</div>

> <https://github.com/mautic/mautic/pull/9969>
>
> | Q | A
> | --------------------------------…------ | ---
> | Branch? | features
> | Bug fix? | no
> | New feature? | yes
> | Deprecations? | no
> | BC breaks? | TBD
> | Automated tests included? | no
> | Related user documentation PR URL | mautic/mautic-documentation#... 
> | Related developer documentation PR URL | mautic/developer-documentation#... 
> | Issue(s) addressed | Fixes #... 
> 
> \<!--
> Additionally (see https://contribute.mautic.org/contributing-to-mautic/developer/code/pull-requests#step-5-work-on-your-pull-request):
> - Always add tests and ensure they pass.
> - Bug fixes must be submitted against the lowest maintained branch where they apply
> (lowest branches are regularly merged to upper ones so they get the fixes too.)
> - Features and deprecations must be submitted against the "features" branch.
> \--\>
> 
> \<!--
> Please write a short README for your feature/bugfix. This will help people understand your PR and what it aims to do.
> \--\>
> \#### Description:
> 
> Building further on the work done in https://github.com/mautic/mautic/pull/9833:
> 
> \- \[\] \`friendsofsymfony/oauth2-php\` is not PHP 8.0-ready. Turns out we're lucky and someone just created a PHP 8 PR: https://github.com/FriendsOfSymfony/oauth2-php/pull/125 - looks like no changes are needed on our side apart from just bumping the dependency
> \- \[x\] \`joomla/filter\` already seems to support PHP 8.0 (their test suite runs against it), but it doesn't explicitly declare support in their \`composer.json\`. Created a PR for that: https://github.com/joomla-framework/filter/pull/46
> \- \[\] \`joomla/string\` also needs to explicitly declare support in \`composer.json\` (will create a PR for that later)
> \- \[x\] \`noxlogic/ratelimit-bundle\` has PHP 8.0 support in progress. Looks like no changes from our side are required apart from updating the dependency when it's ready: https://github.com/jaytaph/RateLimitBundle/pull/113
> \- \[x\] \`mautic/transifex\` already works on PHP 8.0, just had to declare explicit support for it: https://github.com/mautic/Transifex-API/pull/3
> \- \[\] \`friendsofsymfony/oauth-server-bundle\` is working on a new major version, but it's not finished yet, so we can't update just yet. However, they have removed PHP templating support in favor of Twig. Since Mautic still heavily relies on PHP templates, we wouldn't be able to update this dependency once we work on PHP 8.0 support. Created a PR to re-add the templating engine: https://github.com/FriendsOfSymfony/FOSOAuthServerBundle/pull/676 - also, @alanhartless created an issue to ask when they will release the new version: https://github.com/FriendsOfSymfony/FOSOAuthServerBundle/issues/682
> \- \[x\] \`plugin-grapesjs-builder\` needs to declare PHP 8 support Done in https://github.com/mautic/mautic/pull/9966
> \- \[\] Update PHPSTAN + Rector in separate PRs (expect that to be quite a pain! Updating PHPSTAN should be OK but Rector will be painful)
> 
> \<!--
> If you are fixing a bug and if there is no linked issue already, please provide steps to reproduce the issue here.
> \--\>
> 
> \#### Steps to test this PR:
> 1. Load up \[this PR\](https://mautibox.com)
> 2. 
> 
> \<!--
> If you have any deprecations, list them here along with the new alternative.
> If you have any backwards compatibility breaks, list them here.
> \--\>