My config:

Apache/2.4.41 
PHP/8.0.21
Drupal 9.4.0

I have two issues:

1.
After click on Generate all boost cacheable pages crawler start generating html pages in public://boost folder.

But in logs I see Retrieve route public://boost/.html can not be done.
And I don't see x-boost header on my pages.

2.
If I paste over 2000 pages in Boost Cacheability Settings in pages textarea I see this error:
Warning: preg_match(): Compilation failed: regular expression is too large at offset 80708 in Drupal\Core\Path\PathMatcher->matchPath()

Comments

kazah created an issue. See original summary.

nonom’s picture

nonom commented
Title: not working » Generate all boost cacheable pages is not working
nonom’s picture

nonom commented

The branch 8.x1.x-dev still in development,

It will be released for ^8 || ^9 || ^10 as soon as possible.

kazah’s picture

kazah commented

Thanks for the answer.

I just wanted to speed up the output of the module as best I can.

I used boost on Drupal 6 and it worked very well despite a bunch of settings.

Now Drupal 9 lacks this module.

Thanks for your work.

nonom’s picture

nonom commented

Hi @kazah we haven't already an alpha release but a dev branch.

We are working testing on huge sites and trying to get the best approach for this, It will be released soon (tm) I guess ;-)

Contributions are always welcome!

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented
Title: Generate all boost cacheable pages is not working » Generate all boost cacheable pages is not working with large path list
Category: Bug report » Support request
Related issues: +#3325126: Boost Cacheability Settings functionality fix

The main problem ist already reported by myself in issue: #3325126: Boost Cacheability Settings functionality fix

But because of the following problem I keep this issue open but currently a support Request:

@kazah
> If I paste over 2000 pages in Boost Cacheability Settings

Oh, this isn't a good idea to use this setting in this way because of many reasons. The idea of this feature (setting) is following the code for block visibility. So we maybe we should add a warning or also add a filed limit.

Background situation:
First of all everything of this field is stored in config and loaded very often in the current code. I'm already thinking of implementing a bypass of this config when not even remove it. Because it's currently used on every page load I think it's already a performance problem even when used with only some path setting. And as your error message shows this setting is used with an regex code on paths.

kazah’s picture

kazah commented

Show warning message is good idea.
Thank you.

nonom’s picture

nonom commented
Component: Apache integration » Code
c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented

> But in logs I see Retrieve route public://boost/.html can not be done.

This is already fixed and available in dev release.

c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented
Related issues: +#3323984: Purge is incomplete because of current suffix strategy
c-logemann’s picture

c-logemann
he/him
Primary language German
Location Frankfurt/M, Germany
commented