-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
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
Hi Dmitry,
Dmitry Dulepov wrote:
What can you do? Go to page B in WebInfo 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
--
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).
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,
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
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:
