Needs work
Project:
Boost
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Plan
Assigned:
Reporter:
Created:
27 Jun 2022 at 10:47 UTC
Updated:
19 Jan 2025 at 16:41 UTC
Jump to comment: Most recent
Problem/Motivation
The current D8/D9 Code is not feature complete and partially buggy. This issue is for collect missing features and connect them with related issues.
Dependencies
Boost doesn't have any dependencies in 8.x+ it's a pure static file caching system which is going to implement different warming strategies.
Remaining tasks
- #3327723: Plan for 8.x-1.x (D10/D11) unstable release
- #3292909: Drupal 10/11 documentation
#3305014: Language paths are not being cached#3299226: PHP Exception on purging all boost cached pages#3299231: Optimize alias based cache warmer for entity paths#3306459: Services and dependency injection#3306657: Delegate all hook invocations to ModuleHandler for Boost#3323984: Purge is incomplete because of current suffix strategy#3323998: Cache files are created for non existing 404 paths#3323668: Manage CacheGenerate and CachePurge via services, add web auth credentials, improve cache warming, phpcs and drush commands- #3324435: Create cache (file) invalidation logic
- #3500752: TypeError: DrushCommands::logger()
- #3500753: ArgumentCountError: Too few arguments to function Drupal\Core\Form\ConfigFormBase::__construct()
- #3428282: Automated Drupal 11 compatibility fixes for boost
Comments
Comment #2
ressaGreat idea, I have added #3292909: Drupal 10/11 documentation to the list.
Comment #3
nonom commentedComment #4
nonom commentedComment #5
c-logemannComment #6
c-logemannComment #7
nonom commentedComment #8
nonom commentedComment #9
nonom commentedComment #10
nonom commentedComment #11
ressaAdded #3306657: Delegate all hook invocations to ModuleHandler for Boost.
Comment #12
nonom commentedComment #13
nonom commentedComment #14
nonom commentedComment #15
nonom commentedComment #16
c-logemannComment #17
c-logemann@nonom: Better use DEL tag instead of deleting. So we can better show progress :-)
Comment #18
c-logemannComment #19
c-logemannComment #20
c-logemannComment #21
c-logemannComment #22
c-logemannComment #23
c-logemannI think we're coming closer to a stable release. I'd like to avoid a separate issue for this but we can discuss which of the linked issues above are real stable release blockers and which are just "beta release blockers". So we can think and discuss about a beta release.
Comment #24
c-logemannComment #25
nonom commentedMaybe create a ticket for the second release, so we can decide, if needed, what is out from the first one, and maybe create a backlog ticket to take in mind also the community considerations. #23 sounds fine for me.
In my opinion to be stable is to reach the minimal requirements to work with as an anonymous user.
- The module caches the files properly.
- The module has capabilities to clear/prune the current static cached files.
- The settings form works as expected.
- The cache is invalidated successfully.
After that, I could consider releasing a minimal working module and could be good to get more feedback and contributions from the community.
Keep up the good work @C-Logemann!
Comment #26
nonom commentedComment #27
nonom commentedI want to send to the backlog #3292654: Boost Cache operations on entity CRUD because could make an unstable version on a first release.
Comment #28
c-logemannA few weeks ago I started working on #3323668: Manage CacheGenerate and CachePurge via services, add web auth credentials, improve cache warming, phpcs and drush commands. Because there is a big rewrite part I didn't finished yet there is not everything committed and pushed. Meanwhile I needed to work more on customer issues. But now I'm working again on finishing this bigger change where I already spent lot's of development time. Maybe it's currently not so transparent but I think everybody is interested in getting things forward. After merging this big change which will fix several issues I need to sort the leaving issues mentioned here. Nex I will move the most important to a new issue for an "unstable release". When these issues are fixed I will create an unstable release. There is a good chance that this will happen before
$this_year++.Comment #29
c-logemannI finished my work on #3323668: Manage CacheGenerate and CachePurge via services, add web auth credentials, improve cache warming, phpcs and drush commands. Because there are lot's of changes it would be very helpful if somebody does a review.
Comment #30
c-logemannThere is a new issue for a unstable release I like to create on 8.x-1.x branch: #3327723: Plan for 8.x-1.x (D10/D11) unstable release
With the unstable release on branch 8.x-1.x I like to stop work on this branch and will concentrate on a new 2.x branch where we can still change caching logic etc. and maybe do some API breaks if needed. In this case people needs to do a manual branch/release switch and can be aware of changes like this. I just opened an issue where I just think about changing logic which I don't like to just integrate in the current branch: #3327711: Make serving cached content via RequestEvent optional
So this is a first issue I would like to move to the new branch by myself.
Comment #31
c-logemannComment #32
nonom commentedHappy new year! I was out a couple of weeks or so.
I was going to suggest to do a module across 8^ || 9^ || 10^ since our requirements have fully support on these three. But the new tag naming convention is mandatory and drupal 8 will be finally unsupported. Not a big issue maintenance the 8.x-1.x dev branch if needed just left as is on the release list.
Thanks for your work
Comment #33
c-logemannComment #34
c-logemannComment #35
joseph.olstadWow, looks like we're very close to a tagged release of some sort? I am wondering if anyone has had success using the 8.x boost yet. Looking forward to this!
Comment #36
c-logemannComment #37
c-logemannComment #38
joseph.olstadIt appears that every item in the issue summary has been looked after, mostly thanks to @C-Logemann , thanks so much!
I haven't had a chance to test this yet.
Comment #39
joseph.olstad@C-Logemann, absolutely stellar work on this project. I hope to one day be able to use it on one of my projects. Have you started using it? I see usage statistics are still low but have to start somewhere. Right now the 8.x branch is at 11 installs.
With that said, to keep this project moving forward we do need a Drupal 11 release.
Perhaps tag a 2.0-alpha with the D11 merge request.
https://www.drupal.org/project/boost/issues/3428282
Thank you,
Joseph Olstad
Comment #40
c-logemannComment #41
c-logemannComment #42
c-logemann@joseph.olstad
No, it's currently more a hobby project of myself and part of a product idea I have but not started yet. So boost is currently in no website of myself, my company or any of the customer projects we maintain.
If somebody wants to push with money there would be a possibility as a normal contract with Nodegard to bring Boost also to my normal job additionally to my freetime.
Comment #43
c-logemannComment #44
c-logemann