cache history not working completely
|Priority:||Could have||Due date:|
In my cachehistory table are the following entries:
uid tstamp mpvar workspace rootpid languageid pageid path
11 1248371255 0 1 0 5 test123456
12 1248371369 0 1 0 5 test12345
13 1248371377 0 1 0 5 test1234
14 1248371380 0 1 0 5 test123
17 1248444953 0 1 0 5 second-page/regenerate
All of the history links work fine apart from the last one. I.E I can go to
And the page loads fine. If I go to
http://localhost/v3/second-page/regenerate.html realurl generates an error saying the keyword is missing - i.e it can't find the page.
I can't find enough documentation to say if this is actually a bug but I thought the cachehistory existed so that when you renamed a page old bookmarks would still work? I hope that I have not totally misunderstood its purpose and wasted your time. If it is a bug please let me know what other information you might require to debug.
Fixed bug 3988: /start/Feedback gets not found because of uppercase; searchTitle_searchPid() return does not use "encoded" version in lookup
Updated by Ralph Hardwick almost 4 years ago
I have tested various other url strings and noted whether or not they have a problem.
http://localhost/v3/seven/888.html - WORKS
http://localhost/v3/777/888.html - WORKS
http://localhost/v3/second-page/regenerate.html - FAILS
http://localhost/v3/secondpage/regenerate.html - WORKS
http://localhost/v3/second-page/regenerat.html - FAILS
http://localhost/v3/secondpag-e/reg-enerate.html - WORKS
http://localhost/v3/second-page/888/999.html - FAILS
The last one returns the array of:
Array (  => second-page  => regenerate ) Array (  => second-page  => regenerate )
It appears that the problem is second-page which is a valid path in the main tree. Here is my page tree:
- Homepage for the dummy site
o LEVEL 1 TEST CACHE
o Second Page
+ Third Page # Fourth Page
When I rename "second-page" to "second-page-backup" the urls in the cache history that contain the path "second-page" begin to work.
Sorry if this information is confusing, I'm trying to provide as much error information as I can.
Updated by Tolleiv Nietsch over 3 years ago
- Status changed from New to Needs Feedback
You're right that's what the history is used for - could you please try to reproduce this with the latest SVN-version of the extension?
Updated by Ralph Hardwick over 3 years ago
I will try that. Where can I download the latest version from?
Updated by Daniel Poetzinger about 3 years ago
- Priority changed from Should have to Could have
The behaviour is by intention:
the logic checks for matches in the non-history table. If there is a path containing "second-page" this is threated as a hit and there is no lookup in the history table anymore.
Problem is the last pathparts could also be postvars.
Another modi of detection would be useful in this case, but still wont work with postvars in the history
1) check cache for full path
2) check history for full path
3) check cache with decreasing path