Information about the Update to 3.6.3: Difference between revisions
From Joomla! Documentation
Marked this version for translation |
No edit summary |
||
| Line 40: | Line 40: | ||
</translate> <!--refers to and other information below --> | </translate> <!--refers to and other information below --> | ||
===3.6.2 | ===3.6.2 {{rarr}} 3.6.3=== | ||
<translate><!--T:15--> | <translate><!--T:15--> | ||
| Line 46: | Line 46: | ||
Just a normal update as you expect. No re-login required</translate> | Just a normal update as you expect. No re-login required</translate> | ||
===3.6.x/3.5.x < 3.6.2 | ===3.6.x/3.5.x < 3.6.2 {{rarr}} 3.6.3=== | ||
<translate><!--T:16--> | <translate><!--T:16--> | ||
| Line 58: | Line 58: | ||
To prevent the security issue we fixed in 3.6.2 you see the relogin screen once (see above) because we need to destroy the session from an older security fix you need relogin twice.</translate> | To prevent the security issue we fixed in 3.6.2 you see the relogin screen once (see above) because we need to destroy the session from an older security fix you need relogin twice.</translate> | ||
===3.2.x/3.1.x/3.0.x | ===3.2.x/3.1.x/3.0.x {{rarr}} 3.6.3=== | ||
<translate><!--T:18--> | <translate><!--T:18--> | ||
| Line 64: | Line 64: | ||
To prevent the security issue we fixed in 3.6.2 you see the relogin screen twice (see above) and because we need to destroy the session from an older security fix you need relogin too.</translate> | To prevent the security issue we fixed in 3.6.2 you see the relogin screen twice (see above) and because we need to destroy the session from an older security fix you need relogin too.</translate> | ||
===2.5.28 | ===2.5.28 {{rarr}} 3.6.3=== | ||
<translate><!--T:19--> | <translate><!--T:19--> | ||
<b>Update Path: 3.5.1 | <b>Update Path: 3.5.1 {{rarr}} 3.6.3</b><br /> | ||
First you need to update to 3.5.1 (nothing special problems are known about that) | First you need to update to 3.5.1 (nothing special problems are known about that) | ||
Than you need to update to 3.6.3 to prevent the security issue we fixed in 3.6.2 you see the relogin screen once (see above) and because we need to destroy the session from an older security fix you need relogin too.</translate> | Than you need to update to 3.6.3 to prevent the security issue we fixed in 3.6.2 you see the relogin screen once (see above) and because we need to destroy the session from an older security fix you need relogin too.</translate> | ||
Revision as of 16:06, 27 September 2016
Since the Securtiy change in com_joomlaupdate with 3.6.2 it was a bit difficult to update to the last version. With 3.6.3 there is a fix in place that make this much more easy.
Fix for that issue
In 3.6.3 we have a fix in place that works like now follows:
If you come from a pre 3.6.1 version you can use the updater as know. But you get a screen like this where you just need to confirm you superadmin login:
| Old Version | via Version | final Version | confirm user/pw |
|---|---|---|---|
| 3.6.2 | none | 3.6.3 | N |
| 2.5.28 | 3.5.1 | 3.6.3 | Y |
| 3.x.x - 3.6.0 | none | 3.6.3 | Y |
Instructions per version
3.6.2 → 3.6.3
Update Path: 3.6.3
Just a normal update as you expect. No re-login required
3.6.x/3.5.x < 3.6.2 → 3.6.3
Update Path: 3.6.3
To prevent the security issue we fixed in 3.6.2 you see the relogin screen once (see above)
3.4.x/3.3.x -> 3.6.3
Update Path: 3.6.3
To prevent the security issue we fixed in 3.6.2 you see the relogin screen once (see above) because we need to destroy the session from an older security fix you need relogin twice.
3.2.x/3.1.x/3.0.x → 3.6.3
Update Path: 3.6.3
To prevent the security issue we fixed in 3.6.2 you see the relogin screen twice (see above) and because we need to destroy the session from an older security fix you need relogin too.
2.5.28 → 3.6.3
Update Path: 3.5.1 → 3.6.3
First you need to update to 3.5.1 (nothing special problems are known about that)
Than you need to update to 3.6.3 to prevent the security issue we fixed in 3.6.2 you see the relogin screen once (see above) and because we need to destroy the session from an older security fix you need relogin too.