Bug #30582
closed
Update ext_emconf of system extensions with a clean array
Added by Frederic Gaus about 13 years ago.
Updated almost 10 years ago.
Description
The emconf is not up to date in a clean installation of TYPO3 4.5.6 and 4.6 master. The Extension Manager shows several files which seem to differ from the originally installed version. But the files have not been changed.
This also affects saltedpasswords or rsaauth. As these are security relevant features, this should be fixed soon.
Sorry, last sentence should be:
As rsaauth is a security relevant feature this should be fixed soon.
- Subject changed from rsaauth: Clean installation shows changed files in Extension Manager to Update ext_emconf of system extensions with a clean array
This might also be the case in other extensions and it is no security problem.
This should be fixed before each release, but it is nearly always forgotten.
So it might be an idea to just do that now and do it again some time in a few months.
There was a tool, which could fix that in one go for all extensions installed on the sytem - I think it might be the extension extdeveval.
- Priority changed from Must have to Should have
- Target version deleted (
4.5.7)
- Target version set to 4.5.7
Maybe the release managers can put this on their checklist for releases.
I'll send a mail to Xavier.
- Target version deleted (
4.5.7)
Sorry Steffen, our actions overlapped.
Not only the file list is wrong, the dependecies also seem wrong both lang and cms e.g. still depend on 4.4.0.
Just for your info here, I updated the md5 checksums before releasing TYPO3 4.6 RC1 and I'll do it again for 4.6.0 in 2 weeks. Eventually it will be part of the release scripts we have...
What's the status with this one? Can we either close it or move it to the project that deals with the deployment scripts (or at least take care it's going into the release documentation/checklist)?
- Status changed from New to Closed
- Is Regression set to No
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by