[#4688] - Deprecate the P3P plugin and set it to disabled for new installations.
- Closed
- 17 Oct 2014
- Medium
- Build: staging
- # 4688
- Diff
- Bakual:DeprecateP3P
- Success The Travis CI build passed Details
User tests: Successful: Unsuccessful:
Based on discussion in PR #4678 about the obsolte P3P Policy plugin this PR deprecates the plugin and disables it for new installations.
See detailed explanation in the other PR but the gist is that this headers are only supported by IE6 and since we officially only support IE8+ it doesn't make sense to keep the plugin in eternity. Thus it will be removed with Joomla 4.0 according to our current strategy.
Votes
jissues-bot
- | Labels |
Added:
?
|
||
Awesome - Can we do a similar thing in 2.5 - even though I know it's kinda late - better late than never right!?
@wilsonge You want to deprecate the plugin in 2.5 so we can remove it with 3.0? Indeed kinda late 
We could disable it in 2.5 for new installs. But honestly, nobody in their right mind should install a new 2.5 at this time anyway. Those who do that, have bigger problems than an active P3P plugin.
But feel free to propose a PR.
Indeed I more meant disable! I agree with that comment as well. But meh - it's an easy backport
nicksavov
- | Labels |
Added:
?
|
||
brianteeman
- | Category | ⇒ | Plugins |
@test - Installed patch, nothing bad happened. Since there are no test instructions, I'm not sure this is all there is to it ...
(I also disabled the plugin manually - no effect observed)
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/4688.
To see any effect, you'd have to inspect the HTTP headers (using Fiddler or similar software).
There isn't really anything to test. If you apply the patch, nothing should change. Only in new installations, the plugin will not be active anymore.
simple change. Merging
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2014-10-17 09:27:58 |
At least won’t be enabled by default