[TYPO3-core] problems after upgrading from typo3 6.2.16 to 6.2.17

Markus Klein markus.klein at typo3.org
Mon Dec 28 22:43:41 CET 2015

Hi Alex!

First off, do not clear caches manually, but always use the Clear All Cache button from Install Tool.
The caches affected with the issue you have are NOT stored in the filesystem, but in the database!

For 6.2.16:
Can you confirm that flushing caches via Install Tool and showing the page (with no BE user logged in!!) works? Even if you repeat that step multiple times?

For 6.2.17:
If you change the source to 6.2.17 and flush caches via IT right away, does it fail?

The deprecation log should not matter, as bugfix releases do not remove deprecated functionality, only major releases do so (with according breaking change documentation).

Kind regards

Markus Klein
TYPO3 CMS Core Team Member

TYPO3 .... inspiring people to share!
Get involved: typo3.org

> -----Original Message-----
> From: typo3-team-core-bounces at lists.typo3.org [mailto:typo3-team-core-
> bounces at lists.typo3.org] On Behalf Of Alex Tuveri
> Sent: Monday, December 28, 2015 4:13 PM
> To: typo3-team-core at lists.typo3.org
> Subject: Re: [TYPO3-core] problems after upgrading from typo3 6.2.16 to
> 6.2.17
> HI, I made several tests in the last 2 days.
> This is the report:
> 1. the error is very annoying and moreover 'weird', because, to reproduce it i
> switchet my site from 6.2.16 to 6.2.17. Apparently all works until I have
> cleared all cache (frontend/configuration).
> 2. just removed the cache, the site is broken (I can see only the first
> column/area content). It seems that the array to perform more markers
> substitution over the 1st content fails.
> 3. to restore the previous rendering, I clear newly all cache, re-connect to the
> previous source modifying the symlink
> 4. at this point the site do not work more as expected. Turnin back to the v.
> 6.2.16 the site is *always* broken.  So I attempted to clear the cache
> manually (rm -rif typo3temp/Cache/*). Nothing to do.
> 5. at this point the only way to return back is to recover the entire database
> from a previous backup.
> I also activated debug mode, but nothing was printed out (no errors). I
> suspect that the error is some of a logical error.
> However my deprecationlog (located into: typo3conf) shows some errors
> regarding extension that will be not compatible with the newer T3 versione
> 7.x.
> If you need to have some additonal infos (ie. logfiles, screenshots, etc.),
> please contact me privately, I do not want to publish here.
> Thank you very much
> _______________________________________________
> Before posting to this list, please have a look to the posting rules
> on the following websites:
> http://typo3.org/teams/core/core-mailinglist-rules/
> http://typo3.org/development/bug-fixing/diff-and-patch/
> _______________________________________________
> TYPO3-team-core mailing list
> TYPO3-team-core at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core

More information about the TYPO3-team-core mailing list