[TYPO3-english] Realurl: Moving of pages
Hi, I guided a bigger client through the update to TYPO3 4.5. Additionally few other things were introduced, e.g. Caching Framework activation + a hand full of performance-related patches (one of them is a back-ported rootline cache from 6.0). They're now experiencing a nasty behaviour, which did not happen with 4.4: * Page A is created and shown in frontend * Page A is renamed to page B * A new page called A is created * Links to that page lead to the old page A (now B) instead of the new one, because the realurl caches are not up to date. I was not able to reproduce the problem in a local installation, but it's not the first time that I see such a behaviour. Does anybody know the reason, why this is happening and how it can be circumvented? Thanks Steffen -- Steffen Gebert TYPO3 v4 Core Team Member TYPO3 Server Administration Team Member TYPO3 inspiring people to share! Get involved: http://typo3.org I work for TYPO3 solely in my spare time. If you think that my work helps you running your business, you are invited to send me a donation via PayPal to this email address. Thanks ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Realurl: Moving of pages
Hi Steffen, You probably should give us some of your configuration details ;) RealURL config .htaccess and the virtual host configuration can sometimes help. Roxanne On 2012-09-27 13:38, Steffen Gebert wrote: Hi, I guided a bigger client through the update to TYPO3 4.5. Additionally few other things were introduced, e.g. Caching Framework activation + a hand full of performance-related patches (one of them is a back-ported rootline cache from 6.0). They're now experiencing a nasty behaviour, which did not happen with 4.4: * Page A is created and shown in frontend * Page A is renamed to page B * A new page called A is created * Links to that page lead to the old page A (now B) instead of the new one, because the realurl caches are not up to date. I was not able to reproduce the problem in a local installation, but it's not the first time that I see such a behaviour. Does anybody know the reason, why this is happening and how it can be circumvented? Thanks Steffen -- Steffen Gebert TYPO3 v4 Core Team Member TYPO3 Server Administration Team Member TYPO3 inspiring people to share! Get involved: http://typo3.org I work for TYPO3 solely in my spare time. If you think that my work helps you running your business, you are invited to send me a donation via PayPal to this email address. Thanks ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Realurl: Moving of pages
hi, 27.9.2012 20:38, Steffen Gebert kirjoitti: * Page A is created and shown in frontend * Page A is renamed to page B * A new page called A is created * Links to that page lead to the old page A (now B) instead of the new one, because the realurl caches are not up to date. Obvious questions: - you have flushed the realurl caches and all caches? - no aliases (called A) created in page header for the old page A (now page B)? Kind regards, Katja ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Realurl: Moving of pages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Katja, > - you have flushed the realurl caches and all caches? after removing the entry from the realurl cache, it works, of course. But that's not feasible, when there are 1700 editors out there. It has to work automatically > - no aliases (called A) created in page header for the old page A (now no, no aliases. Kind regards Steffen - -- Steffen Gebert TYPO3 v4 Core Team Member TYPO3 Server Administration Team Member TYPO3 inspiring people to share! Get involved: http://typo3.org I work for TYPO3 solely in my spare time. If you think that my work helps you running your business, you are invited to send me a donation via PayPal to this email address. Thanks On 9/27/12 10:17 PM, Katja Lampela wrote: > hi, > > 27.9.2012 20:38, Steffen Gebert kirjoitti: >> * Page A is created and shown in frontend >> * Page A is renamed to page B >> * A new page called A is created >> * Links to that page lead to the old page A (now B) instead of the new >> one, because the realurl caches are not up to date. > > Obvious questions: > - you have flushed the realurl caches and all caches? > - no aliases (called A) created in page header for the old page A (now > page B)? > > Kind regards, > Katja -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQZV2GAAoJEIskG/rSlyw4u08IAIR81p5T/LBiKtSHfBTwBR1i djdKGcRvR7DGiuNG8CajJVYsBPKuJ9bEoROT1FaGOstVZ//I0LENwuDumhrUDi+G iElyRIcMQdM4t957MLh0HkB3u4vGGlaQy1/SdD/KgX58KCXUjQvJjySIM/GWbL3L lFi9Rl628SY5f7LTxEJYvWb/SfQogvIoOUygUFskzsK8cZ91kc7Smrl6VO6G/tud MuqmciBaVIhgckChtcNYc/IV8KUD4sBqsC5UrP4CX3KL2AQWn2VJIZ1Tg8t0tvYx PwpsMflHPoPMMmu2a7SWebsnJgmy8Oj7HnV9NKcDPqcf3b8AKORrme8T+e9vpvY= =ti9M -END PGP SIGNATURE- ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Realurl: Moving of pages
Hi! Steffen Gebert wrote: I guided a bigger client through the update to TYPO3 4.5. Additionally few other things were introduced, e.g. Caching Framework activation + a hand full of performance-related patches (one of them is a back-ported rootline cache from 6.0). They're now experiencing a nasty behaviour, which did not happen with 4.4: * Page A is created and shown in frontend * Page A is renamed to page B * A new page called A is created * Links to that page lead to the old page A (now B) instead of the new one, because the realurl caches are not up to date. That's right :) Here is why. When you rename page A to page B, RealURL will know and will update all cached records for page B with path /A to have expiration time. When the user comes to /A, it will redirect it to /B with 302 HTTP code. This is made to be Google-friendly (no rude 404s but polite 302s to the new location). It worked like this for years. Now you create a new page A and expect it to be available at /A. But RealURL has a cache record for path /A, which points to B. Just creating a new A does not add /A to the cache. Thus, when you navigate to /A RealURL looks to the cache, finds a record with /A->/B there and redirects. What can you do? Go to page B in Web>Info and remove all entries that say /A for it. That's all. -- Dmitry Dulepov Simplicity will save the world. ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Realurl: Moving of pages
Hi Dmitry, Dmitry Dulepov wrote: > What can you do? Go to page B in Web>Info and remove all entries that say > /A for it. That's all. Couldn't realurl handle this on its own? Ideally it would warn the editor that the forwarding will be removed.(*) (*) Feature suggestion ;) Best regards -- Philipp Gampe – PGP-Key 0AD96065 – TYPO3 UG Bonn/Köln Documentation – linkvalidator TYPO3 inspiring people to share! ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Realurl: Moving of pages
W dniu 2012-09-27 19:38, Steffen Gebert pisze: Hi, I guided a bigger client through the update to TYPO3 4.5. Additionally few other things were introduced, e.g. Caching Framework activation + a hand full of performance-related patches (one of them is a back-ported rootline cache from 6.0). They're now experiencing a nasty behaviour, which did not happen with 4.4: * Page A is created and shown in frontend * Page A is renamed to page B * A new page called A is created * Links to that page lead to the old page A (now B) instead of the new one, because the realurl caches are not up to date. I was not able to reproduce the problem in a local installation, but it's not the first time that I see such a behaviour. Does anybody know the reason, why this is happening and how it can be circumvented? Thanks Steffen Does this client use config.sendCacheHeaders = 1 and config.cache_period is set to a few days? I mean it may have nothing in common with RealUrl. I use this and from time to time I have explain why changes are not visible straightaway ;-) regards Tomasz ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
Re: [TYPO3-english] Realurl: Moving of pages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for all your feedback. I had a meeting today and we investigated in detail. Result: Once a page is moved/renamed, realurl correctly expires the pathcache entry. However, child pages of a moved page aren't affected and these are the pages (links), which then lead to the wrong page. I located the piece of code responsible for that functionality and will dig into it during the weekend. Kind regards Steffen - -- Steffen Gebert TYPO3 v4 Core Team Member TYPO3 Server Administration Team Member TYPO3 inspiring people to share! Get involved: http://typo3.org I work for TYPO3 solely in my spare time. If you think that my work helps you running your business, you are invited to send me a donation via PayPal to this email address. Thanks On 9/28/12 11:47 AM, Dmitry Dulepov wrote: > Hi! > > Steffen Gebert wrote: >> I guided a bigger client through the update to TYPO3 4.5. Additionally >> few other things were introduced, e.g. Caching Framework activation + a >> hand full of performance-related patches (one of them is a back-ported >> rootline cache from 6.0). >> >> They're now experiencing a nasty behaviour, which did not happen with >> 4.4: >> >> * Page A is created and shown in frontend >> * Page A is renamed to page B >> * A new page called A is created >> * Links to that page lead to the old page A (now B) instead of the new >> one, because the realurl caches are not up to date. > > That's right :) Here is why. > > When you rename page A to page B, RealURL will know and will update all > cached records for page B with path /A to have expiration time. When the > user comes to /A, it will redirect it to /B with 302 HTTP code. This is > made to be Google-friendly (no rude 404s but polite 302s to the new > location). It worked like this for years. > > Now you create a new page A and expect it to be available at /A. But > RealURL has a cache record for path /A, which points to B. Just creating > a new A does not add /A to the cache. Thus, when you navigate to /A > RealURL looks to the cache, finds a record with /A->/B there and redirects. > > What can you do? Go to page B in Web>Info and remove all entries that > say /A for it. That's all. > -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.18 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJQZhhdAAoJEIskG/rSlyw4+cMH/jW/CzKKvp7O/kigAb42EWon C+SsiTGPdxBz3/RUFxwCEd/G/lXphVYN1kYPxFrqgolOPXALFTb8ZShVw3F8DJv1 BhpzLenXaJZf1ZmAx6WSqUDLlZLW04gvmKwoTNXVw4D84Vh4ubJHCTrKBtd4iNYd LnWy7JL4/nW+aXnJGbbEfMf/ibSxSKoqdY2S/8LB5qp+eB8TjzByY72oWJ4npQEv UFnVerVBzVRNk80jTP9uD+M+LrV22zD8ivWzBLP8XH6OlFLqun8j1LTBt6HgzXTK 7U2M6uU6Ea/CjHe+sNG7C8SURSRJlCGUEfnT4QRFY/6KfuNlbYf8iAIFpO3BOI8= =m8cH -END PGP SIGNATURE- ___ TYPO3-english mailing list TYPO3-english@lists.typo3.org http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
