Last post 2 min ago

Posts last week 141

Average response time last week 4 hours 42 min

All time posts 67795

All time tickets 10476

All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#7402 – Purge "Home Page Meta " Only

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Friday, 18 September 2020 22:29 UTC

wreppy

Hi,

Is there any way of purge only "Home Page Meta" ?

Whatever i entered in Home page meta description did not show up in source code, (bug ? ) and the only way to have it updated is to press the purge button, but i loose my all other Sef urls and have to start over again. Please note that everything else entered in the "Home Page Meta" did update immediately, for example, Page title, Keywords tag etc...

Update!

I did som fast digging and found out what was causing this. Disabling the db query cache in the "shlib - Db query cache and programming library" plugin solves the issue. Weird anyway since it only affects the description part and not the others parts.

Monday, 21 September 2020 11:18 UTC

wb_weeblr

Disabling the db query cache in the "shlib - Db query cache and programming library" plugin solves the issue.

Weird indeed, not sure how this can have an effect on that. I'd think that this is not the real source of the problem but instead a side-effect of the db caching being enabled, or a chain of side-effects at work. I'd suggest disabling back the db caching in any case (it's off by default), it's a performance enhancing feature that won't work safely on all sites, due to interference with other extensions mostly and requries extensive testing before being put to use. With modern db servers and enough power, it definitely should not be needed.

Best regards

Yannick Gaultier

weeblr.com / @weeblr

Thursday, 22 October 2020 05:34 UTC

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.