Project

General

Profile

Actions
Copy link

Bug #25323

closed

Moving a page do not clear page cache of old Neighbors/Parent

Added by Simon Schick about 13 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2011-03-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Hi, all

I'm working with HMENU using the status IFSUB. Now I recogniced the following issue:
If I move a page in the backend like the following (using Drag&Drop):
  • page1
  • page2
  • page3
MOVED TO:
  • page1
    • page2
  • page3

After that I have to clear the whole cache that the link for page1 is rendered using the IFSUB-Settings.

You can try it yourself:
  • set up a clean TYPO3 (or use a test-environment) and create a page-structure like described above.
  • create a HMENU using the states NO and IFSUB. You can also try CUR and CURIFSUB
  • view the frontend to generate the cache-entries in the database for the HMENU
  • move page2 into page1 (so that page2 is a subpage of page1)
  • view the frontend without clearing the cache and you'll see that page1 is rendered using the NO-Settings
  • clear the cache and you'll see that now page1 is rendered using the IFSUB-Settings

TYPO3 v4.5.2
PHP v5.3

Used TypoScript:
http://pastebin.com/4Bd5pt7Z
(issue imported from #M17946)

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #22190: HMENU with IFSUB, CURIFSUB and hidden subpagesClosed2010-02-25

Actions
Actions
Copy link
 #1

Updated by Simon Schick about 13 years ago

Maybe this issue is stronly related to http://bugs.typo3.org/view.php?id=13665...
I found the ticket right now.

Actions
Copy link
 #2

Updated by Stefan Neufeind over 12 years ago

  • Target version deleted (0)

Simon, that would then be #22190. Added a related-link.
Imho it's at least loosely related though not the same issue.

I can confirm similar problems as you mentioned, not being specific to IFSUB for me.

Actions
Copy link
 #3

Updated by Alexander Opitz over 9 years ago

  • Description updated (diff)
  • Status changed from New to Needs Feedback
  • TYPO3 Version set to 4.5
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.4)?

Actions
Copy link
 #4

Updated by Simon Schick over 9 years ago

Hi, Alex

Thanks for answering on this old ticket.

I tried it now again, with a TYPO3 v6.2.x installation and got the following confirmed:

Moving a page in to or out from the menu SOMETIME triggers cache-clearing. To keep the example, I had initially, I tried it again by moving page3 to the following places:

Initial:

  • Startpage (current view)
    • page 1
    • page 2
    • page 3

Moving page 3 to the following places triggers cache-clearing:

Changing the order:
  • Startpage (current view)
    • page 1
    • page 3
    • page 2
Moving the page completely out of the current structure:
  • Startpage (current view)
    • page 1
    • page 2
  • page 3

And now, what doesn't trigger cache-clearing:

Making the page a subpage of one in the current structure:
  • Startpage (current view)
    • page 1
    • page 2
      • page 3

Please write back if you can't confirm it.

Actions
Copy link
 #5

Updated by Alexander Opitz over 9 years ago

I don't have such a setup yet.

Can you please check the page cache on your last test, which pages get cleared?

Actions
Copy link
 #6

Updated by Simon Schick over 9 years ago

Hi, Alex

Yea, there is an entry left there, having the id 1 ... but that doesn't tell me much. I can't look into the binary content. I can just tell you, that the md5-string for the identifier remained the same as for the startpage ;) (confirmed that by clearing the cache and just loading the startpage)

Actions
Copy link
 #7

Updated by Alexander Opitz over 9 years ago

In cf_cache_pages_tags you will find the information which identifier is for which page.

So if you move the page it seams the page cache is cleared for Page2 and Page3 but not for Page1?

As I remember correctly the page is cache is normally cleared for the neighbors and childs of an edited Page record. So it seams this cache clearing doesn't know of the move and do not clear the page cache of the neighbors for his old position.

Does this describes your problem?

Actions
Copy link
 #8

Updated by Simon Schick over 9 years ago

Hi, Alexander

Right. That's exactly the case.

The cache for Page1 is not cleared when moving Page3 into Page2 (see my example yesterday, not the initial one ;)).

But as I see it: This is a matter of compromise ... You, upfront, have to know what the menu is, and clear the cache depending on whether the structure has changed - depending on what kind of menu it is (to make it perfect ;)).

But it's quite usual, that you have a menu, listing all children ;) So therefore, I think, it's quite natural to clear the cache for the parent-page of the old position.

I don't know whose cache to clear else. Depending on the menu (when using an expanded menu) you have to clear the cache of more pages here. But at least the parent of the old position should be in the list of pages to clear the cache for ;)

What's your opinion on that?

Actions
Copy link
 #9

Updated by Alexander Opitz over 9 years ago

  • Subject changed from Menu-Cache is not cleared after moving a page in the backend to Moving a page do not clear page cache of old Neighbors/Parent
  • Category set to Caching
  • Status changed from Needs Feedback to New
Actions
Copy link
 #10

Updated by Mathias Schreiber about 6 years ago

  • Status changed from New to Closed

We'r sorry to say, but Frank and me consider this issue unsolvable.

Actions
Copy link
 #11

Updated by Anonymous over 1 year ago

Mathias Schreiber wrote in #note-10:

We'r sorry to say, but Frank and me consider this issue unsolvable.

I like the spirit of this answer.

Actions
Copy link

Also available in: Atom PDF