Bug #22009
closed
PHP Fatal Error: Cannot redeclare class backend_toolbarItem [After Typo3 Upgrade]
0%
Description
Login attempts to the admin backend lead to 500 server errors. Php error log reports:
'Cannot redeclare class backend_toolbarItem in c:\inetpub\wwwroot\typo3_src-4.3.1\typo3\interfaces\interface.backend_toolbaritem.php on line 36'Related/Similar Bugs (ID): 0013237
Windows 2008 with IIS7 using PHP fast cgi.
Migrated servers with Typo3 4.2.x, then successfully upgraded to 4.3.0. However, shortly thereafter when upgrading to 4.3.1 and after updating the symlink to the Typo3 core, the admin backend was inaccessible, leading to 500 internal server errors after entering the login details.
Symlinks were created using the native command 'mklink' which is now available in the newer versions of Windows, (replaces the functionality of 'junctions').
Attempts to revert back to 4.3.0 by updating the symlinks did not help. I have also tried deleting all symlinks and creating them fresh, but the issue still persists.
(issue imported from #M13332)
Updated by Junaid over 14 years ago
It seems that I have managed to resolve the error. Since the Typo3 installation was working once before with the same PHP environment etc and the clue that it was symlink related, I continued troubleshooting and by deleting all 3 symlinks and recreating them using the /D flag, the backend was once again accessible.
In command prompt, I entered the following. First we move to the root of the site and then create the relative symlinks:
#########
C:\Users\Administrator>cd \inetpub\wwwroot
C:\inetpub\wwwroot>
C:\inetpub\wwwroot>mklink /D typo3_src typo3_src-4.3.1
symbolic link created for typo3_src <<===>> typo3_src-4.3.1
C:\inetpub\wwwroot>mklink /D typo3 typo3_src\typo3
symbolic link created for typo3 <<===>> typo3_src\typo3
C:\inetpub\wwwroot>mklink /D t3lib typo3_src\t3lib
symbolic link created for t3lib <<===>> typo3_src\t3lib
#########
I have tried deleting and recreating the symlinks before, without success, so I am assuming that the reason it worked this time, is because I used the relative paths instead of absolute target paths and also using the /D flag (for directory symbolic link) instead of /J (junction). I think when upgrading Typo3 again, the same issue might occur, because previously I used to only delete the typo3_src symlink and recreate it pointing to the latest source files, but maybe that corrupts something and it is better to delete and recreate all 3 symlinks in future.
Hope this clarifies for anyone else in a similar situation.
Updated by Christian Kuhn over 14 years ago
Resolved, no change required.
Thanks for the solution Junaid.
Updated by