This may be a Core issue or it may be a d.o issue...

So. If you go to a page like
https://drupal.org/node/1884796
and edit this book, changing its position in the outline, as I just did, it should invalidate the book navigation block. But it doesn't. The book outline shown is not updated.

So this page is currently really under
https://drupal.org/node/2116747 (Drupal 8 APIs)
but the book navigation is showing it under a page that doesn't even exist (see screen shot).

I tried editing the two pages I just moved both with the Edit button and with the Outline button, and neither one properly invalidated the book cache block.

CommentFileSizeAuthor
#9 screen3.png36.63 KBtvn
#9 screen2.png37.38 KBtvn
#9 screen1.png17.7 KBtvn
blockcache.png19.51 KBjhodgdon

Comments

tvn’s picture

tvn commented

Seems this is cache issue, the page is in the proper place now. I can't reproduce this on the dev site as well.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

Does the dev site have the exact same caching settings as the live site? I think the cache settings on the live site may be wrong. Or else there is a core bug that when you edit a Book page it should invalidate the cached Book navigation block.

tvn’s picture

tvn commented

Dev sites are very different. staging will be closer (even though still not completely the same), can you test there?

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

I could do that tomorrow... What is the URL of the staging site, and can I use my own account to log in or is there a special account to use?

tvn’s picture

tvn commented

https://staging.devdrupal.org/, yes your usual drupal.org username/password

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

Staging is apparently down.

Fatal error: Unsupported operand types in /var/www/staging.devdrupal.org/htdocs/sites/all/modules/project_issue/views/project_issue.views.inc on line 192

tvn’s picture

tvn commented

It probably was in the process of rebuilding at that moment.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

I tested on Staging and it appears the block is not cached there. Book outline updates are immediately reflected in the book navigation block.

tvn’s picture

tvn commented
Priority: Normal » Major
Issue tags: +Drupal.org 7.1
StatusFileSize
new screen1.png17.7 KB
new screen2.png37.38 KB
new screen3.png36.63 KB

Something is going on with the caching indeed. Just ran into this with https://drupal.org/stats. First I was changing the weight in the outline, to move the page up, but it wasn't moving in the nav block. Now as a logged in user, I don't see the book navigation block at all:
https://drupal.org/files/issues/screen1_17.png

If I go not to alias /stats but to /node/2183001 I can see the nav block, note the location of the page in it:
https://drupal.org/files/issues/screen2_14.png

As an anonymous user from another browser, I can see the nav block as well, however the page is located in a different place:
https://drupal.org/files/issues/screen3_8.png

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

Yeah, I ran into this again today with
https://drupal.org/documentation/modules/basic_auth
but it seems to be in the correct nav now (at least while I'm logged in).

It's hard to make a reproducible report of this because by the time someone gets back to check, the cache has usually been cleared out.

tvn’s picture

tvn commented
Project: [Archive] Drupal.org D7 upgrade QA » Drupal.org infrastructure
Component: User interface » Other

Can anyone please take a look what's going on with the caching here?

dokumori’s picture

dokumori commented
Assigned: Unassigned » dokumori
Issue tags: +drupal.org szeged sprint
dokumori’s picture

dokumori commented
Assigned: dokumori » Unassigned

Had a quick look on local / d.o dev and it works just fine so I believe it is indeed a cache issue. Unassigning.

basic’s picture

basic commented

I think the only difference between dev/staging and production at this point is memcache. This issue may be related: https://drupal.org/node/2027677

basic’s picture

basic commented

I am unable to reproduce on dev with a single memcache bin enabled. This may be a problem with php-fpm, or with multiple memcache bins and separate bins used in production. I'll continue testing.

basic’s picture

basic commented

memcache api has been upgraded to 7.x-1.1-beta5+1-dev in production, but the issue of the block not updating after an outline change persists. I'll continue looking into this.

tvn’s picture

tvn commented
Assigned: Unassigned » basic
Status: Active » Needs work
tvn’s picture

tvn commented
Status: Needs work » Fixed

We switched block cache from memcache to database and this issue is fixed. Rudy is going to open core issue to make this actually work with the memcache.

tvn’s picture

tvn commented
Issue tags: +drupal.org DC Austin sprint

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.