No caching, "Notice: Undefined index: args in boost_deliver_html_page()"

Same for me. Debian squeeze, nginx 7.67, fastcgi-php using socket, php5.3.3, Drupal 7.15. The $_boost['args'] is a global and I am getting other strange errors in watchdog with missing $_SERVER variables as well. Not necessarily a boost problem. Its like php is "losing" these arrays. When I debug print_r($_SERVER) everything is correct.

elBradford, what is your platform and versions??

EDIT just grep'd for $_boost['args'] and there is only one found so its never set! Bug I think.

I commented out the ref to $_boost['args'] and it works great. VERY BAD (non) fix, but I needed to verify that it works.
Line 1396 looks like ... /*&& $_boost['args'][0] != 'admin'*/. Probably should have added a && isset($_boost['args'][0]) before that test for 'admin'.

Did you test on the latest dev?

The args are set in boost_transform_url(), called from boost_init().
They get initialize to empty.

    // Prevent array warnings.
    $args[0] = empty($args[0]) ? '' : $args[0];
    $args[1] = empty($args[1]) ? '' : $args[1];
    $args[2] = empty($args[2]) ? '' : $args[2];
    $parts['args'] = $args;

Can you provide more specifics on where you get the notice?
* page type node/view/other/all?
* as admin/anonymous?
* does the page have an URL alias?

Did not test the latest dev.
Page type node
Logged in as admin
Boost debug ON
URL alias YES

Can someone test on the latest dev?

I have installed latest dev. have the same problem.

I'm experiencing this same issue. And I believe this is causing my entire site to crash, the home page periodically gets stuck in a constant page refresh and fails to load anything and this is the only error in my log. Subscribing to see if there is a patch... thanks

Same error. Page aren't cached. I can see all the page getting crawled in the log but then the error. And the log line just after it is :

Array
(
    [cache_this] => 
)

So it caches nothing...

EDIT : I'm on 7.x-1.0-beta2 though.

Tried with the dev. Not working either...

So is this being looking at ? In my case it makes Boost almost unusable :( .

The initial report was for an older release and there is very little information to work with.

- is there still a "notice", and if yes, please copy-paste the full message.
- is the notice also logged to watchdog when viewing the page as anonymous? (when the cache is generated)
- when logged-in, enable the Boost status block, and see if it mentions a reason why the page is not cached to anonymous users.

For me, this problem still exists. See #5 above, it happens when logged in. So page is not delivered from boost cache. Don't know if its in watchdog. It is a distracting error which may be trivial OR not. There seems to be huge differences between the D6 and D7 versions of boost. Heaps of config options gone, D7 simpler. GZ compression gone? Boost could be fantastic for shared hosting because its just php code and .htaccess rules. If you have your own server, then consider varnish. There is a Drupal varnish module and Lullabot have excellent explanation on varnish configuration.

Thanks for your feedback. Yes, some features are still in development (ex: gzip, see handbook or issue queue), but the general aim is to keep it simpler than in D6. And yes, bigger sites on dedicated servers should use Varnish, especially since D7 makes that easier (no need for Pressflow).

Can you respond to my questions in #12 ?

Happen to me with last dev (7.x-1.0-beta3+1-dev).
In my case, there is no page cached, although there was "accidentally" 2 pages cached today (?!), 2 pages that was never cached again after cache has been flushed...

To give feedback to #12 :
No notice in site pages.
Only php notice in watchdog (same message as initial post).
It happened on boost settings pages but also on running cron or when flushing cache
and also after running the database update page (even with no update performed)
It never happened as Anonymous.
And always same message in boost block :
Generated: not cached yet (either no one has visited the page recently, or something is preventing the cache from being generated).
(... and I visited all the pages as Anonymous dozens of times)

Feel free to ask if you need some other information...

I have a similar problem on 3 sites using 7.x-1.0-beta2 where the log file shows Notice: Undefined index: args in boost_deliver_html_page() (line 1396 of ... ... )
Taxonomy pages never get cached, often some node pages get cached.

I was getting the same log message using 7.x-1.0-beta2, but oddly only when testing anonymously in Chrome. Viewing in Firefox and Safari resulted in boost creating the cache files.

The problem seemed to be in boost_exit() where drupal_page_is_cacheable() is called (line 275) - this was returning false resulting in no caching.

Clearing all cookies from Chrome resulted in boost working again, but I've not been able to reproduce the problem again.

-edit-

could be related to #1807818: Pages are not cached / not cacheable / caching won't work - except when cookies are disabled?

Same error here.

This might be better as a separate issue? Please advise.

For me cache files are created (but not served) for pages visited by the anonymous user. But no generation when running cron (web crawler).
I consistently get the 'undefined args' message after running cron. Even with crawler (and expire and httprl) disabled.

However, as mentioned the cached html pages do not seems to get served. Anonymously viewed pages do not have the 'Page cached by Boost' comment in the source. There is no noticable speed increase. Furthermore the cache file for the page is updated on every visit. Strangely enough the boost status block correctly reports the pages' cache status ('flush page'button also works).

@Philip_Clarke :
Dont know if this is relevant (as the cache seem to get written for my setup) but I am using a multilingual site with path prefixing. Node dirs (both for the one in root as the ones in subdirectories) have 775, language dirs ( en, de etc.) have 755 and the html cache files have 664.

@bgm :

- is there still a "notice", and if yes, please copy-paste the full message.
In only get them after running cron it seems. Not as a notice, only in dblog. From admin -> reports -> recent :

Notice: Undefined index: args in boost_deliver_html_page() (line 1426 of >MyRoot< /sites/all/modules/boost/boost.module).

- is the notice also logged to watchdog when viewing the page as anonymous? (when the cache is generated)
No errors on cache generation found.

- when logged-in, enable the Boost status block, and see if it mentions a reason why the page is not cached to anonymous users.
All pages visited by anonymous get cached. Non cached pages show the generic 'not cached yet' message.
The pages DO get cached again on every anonymous visit though.

I had this error message in several page views, just when applying a third argument.
Cloning the view and using it under a different name solved the issue.
Example: a view named 'activities' with three taxonomy term ID contextual filters produced the error when passing the third argument in the url. A new view named 'activty' didn't produced the error.
Deleting the initial view and cloning it back to the original name produced the error again.
Both views used an identical template.

I´ve installed latest dev version, and still get this error.
The webpage source code says "Page cached by Boost", but I haven´t noticed any difference in loading speed (I´ve even checked with Google Page Speed Insight).
I´ve checked the Boost Status Block and it says: Generated: not cached yet (either no one has visited the page recently, or something is preventing the cache from being generated).

Any news on what to do? How to ckeck if Boost is working?

Thanks Philip!
Yes, I can see now that Boost is indeed working just fine! :)

firfin,
I was facing same issue.

"Cache files are created (but not served) for pages visited by the anonymous user.

I had configured "Root cache directory" outside webroot. Cache files was created but not served. So when I moved that inside webroot(sites/default/files/*), it worked great. When debug mode is on, still I get that error message. I am using beta2 version.

Notice: Undefined index: args in boost_deliver_html_page()

Yes. Thanks.

Question: Is it a security risk if I plan to place cache files at sites/default/files folder?

i get this error too:
Notice: Undefined index: args in boost_deliver_html_page() (Zeile 1433 von /www/htdocs/w00bbe43/PRODUCT_DISTRI3/sites/all/modules/contrib/boost/boost.module).

i enabled debug and it logs

Array
(
    [scheme] => http
    [host] => www.mydomain.de
    [path] => 
    [query] => 
    [full_path] => 
    [base_path] => /
    [query_array] => Array
        (
        )

    [url_full] => www.mydomain.de/_
    [url] => http://www.mydomain.de/
    [url_decoded] => /_
    [base_dir] => cache/normal/www.mydomain.de/
    [filename] => cache/normal/www.mydomain.de/_
    [directory] => cache/normal/www.mydomain.de
    [normal_path] => node
    [path_alias] => node
    [args] => Array
        (
            [0] => node
            [1] => 
            [2] => 
        )

    [menu_item] => Array
        (
            [page_type] => 
            [page_id] => 
            [path] => node
            [load_functions] => 
            [to_arg_functions] => 
            [access_callback] => 1
            [access_arguments] => a:0:{}
            [page_callback] => empty_page_empty
            [delivery_callback] => 
            [fit] => 1
            [number_parts] => 1
            [context] => 0
            [tab_parent] => 
            [tab_root] => node
            [title] => 
            [title_callback] => t
            [title_arguments] => 
            [theme_callback] => 
            [theme_arguments] => Array
                (
                )

            [type] => 20
            [description] => 
            [position] => 
            [weight] => 0
            [include_file] => 
            [href] => node
            [tab_root_href] => node
            [tab_parent_href] => 
            [options] => Array
                (
                )

            [access] => 1
            [localized_options] => Array
                (
                )

            [original_map] => Array
                (
                    [0] => node
                )

            [status] => 200
            [extra_arguments] => 
        )

    [is_cacheable] => 
)

pretty interesting as its working, generating the files on my local debian, even with this error but not on the webhosters webserver.
i have no permission issues as cache is set to 777