TYPO3 Core

In fact these sysexts are missing ext_tables.php :-)

./felogin
./css_styled_content

Yes, the update "failed" from 6.2.3, the backend was inaccessible until I put the files back into the dir.
Even clearing typo3temp via shell did not help.

Wouter Wolters wrote:

They are not missing but the content is moved into Configuration/TCA/Overrides/

Do you have any problem because of this?

Same problem here. Neither FE nor BE are accessible. Deleting the Cache-dir from shell solved the problem: $ rm -rf typo3temp/Cache

How did you upgraded your installation?

Inside the Install Tool is a clear all cache button which can be used. Install Tool should be accesible even if the backend isn't.

I upgraded my installation by manually placing the zip-file content. I had to use the Clear Cache function in the install tool as well.

Maybe in my case this was some local thing - neither BE nor Install Tool was accessible after upgrade.
Just upgraded another install and it went fine. Install-Tool was accessible. Clearing Cache made everything work as expected.

From my side, this ticket can be closed, as clearing cache after upgrade is mendatory anyways.

Markus Klein wrote:

I upgraded my installation by manually placing the zip-file content. I had to use the Clear Cache function in the install tool as well.

Clearing the cache is mandatory, yes. But in the past updating from one patch version to the next didn't break the frontend and backend. TYPO3 even worked if you didn't clear the cache. If you have a setup where you create a typo3_src-6.2.current symlink which is used by multiple TYPO3 instances on the same server, then you can't just change typo3_src-6.2.current to link to typo3_src-6.2.4, because all TYPO3 instances using typo3_src-6.2.current will stop working until you clear the cache of every instance. So in terms of software development it probably isn't a bug, but in terms of usability (for the admins) it is - in my opinion.

This is absolutely right!
We switched to the following mode since 6.2 was released: We have typosrc6_cur and typosrc6_test where _test always points to the newest release and we switch only a single instance at first - for testing ;-)

As stated above: The interesting point is it worked on another instance without any flaws, FE was working just fine, just BE was inaccessible. So I believe it is the sum of things which at the end causes this problem.
In terms of software development: I have some understanding for this type of "inconvenience" since this 6.2 is a young release and a lot of refactoring was done. Most of it for the better - some not.

C. Weilguny wrote:

Clearing the cache is mandatory, yes. But in the past updating from one patch version to the next didn't break the frontend and backend. TYPO3 even worked if you didn't clear the cache. If you have a setup where you create a typo3_src-6.2.current symlink which is used by multiple TYPO3 instances on the same server, then you can't just change typo3_src-6.2.current to link to typo3_src-6.2.4, because all TYPO3 instances using typo3_src-6.2.current will stop working until you clear the cache of every instance. So in terms of software development it probably isn't a bug, but in terms of usability (for the admins) it is - in my opinion.

Anything we need to fix or can this issue be closed?

From my side this can be closed