not able to purge

[Haresh Shahari]

We had mod_pagespeed enabled via .htaccess

all was good until we upgraded due to the warning email,

we see the below issue;

1) We are not able to purge via the admin, we get
"
Purging not enabled: please add

  ModPagespeedEnableCachePurge on
"

Once we add the above to our .htaccess we get a 500 Internal Server Error

[Joshua Marantz]

Can you try putting directive into your pagespeed.conf file rather than .htaccess?  There are some directives that cannot be used in .htaccess and that is one of them.

The ones that must be in your .conf file are generally indicated as such in the doc.  There ones that control rewriting features like enabling filters and changing image compression settings can be done in .htaccess.  The ones that configure the system caches usually cannot.

Josh

--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/f3cc7d24-d2f8-4608-b755-8e31ba9a6fb6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Haresh Shahari]

Previously we never required :  ModPagespeedEnableCachePurge on

The below filter which used to work on .htaccess gives server error too:
ModPagespeedEnableFilters prioritize_critical_css

These errors show only after we have updated our mod_pagespeed module.

Can we access pagespeed.conf via FTP

Thanks

Harry

--
You received this message because you are subscribed to a topic in the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/mod-pagespeed-discuss/Z1WBp9FtUiM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/CAGKR%2BEAfoZat2x7GU-yjQtv8Dgq9Tzu2jWFoDEFZGw%2BJttV%2BVg%40mail.gmail.com.

[Joshua Marantz]

You still don't need ModPagespeedEnableCachePurge if you want to do full-cache purges by touching cache.flush.  That will still work.

I am not expecting your server to serve 500s in any case.  Can you check the server logs?

I'm not sure about your FTP setup.  You can probably FTP over the conf files if you login to FTP as root, but you'll need to restart the server when you update pagespeed.conf.  Are you talking about a shared hosting setup with FTP access to .htaccess files?  Or do you own the machine?

-Josh

To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/CAAE0kOhMnmooYg_%2BsJhMb%2BCMbacBLb%3Da53CWOqZ2_o%2B3nNeG%3Dg%40mail.gmail.com.

[Haresh Shahari]

I tried to flush cache from the pagespeed console where we get options for individual or entire purge.

However we get the message:

"Purging not enabled: please add

  ModPagespeedEnableCachePurge on

"

Would be great if we can manage pagespeed from.htaccess rather than going to server level, we do use a dedicated server.

If only we could purge via the console , our issues would be solved as of now.

Trying to get somebody check the logs .

To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/CAGKR%2BEDb-u10jYUfum1%2BTgJEn0uGuJ-ycbea-iDPmF7s8vOusQ%40mail.gmail.com.

[Joshua Marantz]

Right.  You can use the legacy 'touch cache.flush' method without adding EnableCachePurge:

  https://developers.google.com/speed/pagespeed/module/system#flush_cache

If you want to use the admin-console purging UI you need to enable it. 

  https://developers.google.com/speed/pagespeed/module/system#purge_cache

We did it this way precisely to make sure that no one with a system built around 'touch cache.flush' would have that break when we added the console-based purging mechanism.

In our system, some of the settings really have to be the same across an entire VirtualHost, and .htaccess files are directory-specific.

-Josh

To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/CAAE0kOj4g0uMq2QFaUfdtSw1uMVuRHY5HTyh6P4kQwr7y6cFPQ%40mail.gmail.com.