IPS Community Suite 4.1.12.1 + Apps - Nulled By IAF

[saske46 10]

[CENTER][img]http://i.imgur.com/EgL5y6M.png[/img]

[img]http://i.imgur.com/BVLazOr.png[/img]

[img]http://i.imgur.com/08j2OPe.png[/img]

[img]http://i.imgur.com/ptafCrW.png[/img][/CENTER]


[CODE] ___ ____ ____ _____ _ ___ ____
|_ _| _ \| __ )| ___|_ _ _ __ ___(_) |_ _| _ \
| || |_) | _ \| |_ / _` | '__/ __| | | || |_) |
| || __/| |_) | _| (_| | | \__ \ |_ | || _ <
|___|_| |____/|_| \__,_|_| |___/_(_)___|_| \_\

Persian SUPPORT in IPBFARSI.IR [/CODE]

[B][SIZE=4][B]Key Changes:[/B]
[/SIZE][/B]
This is a maintenance release to resolve the following issues:

Permission matrix can show incorrect permissions when using the Member > Group permission tool.
Using Authorize.Net Payment Gateway may result in an error.
A logged in member without a valid timezone set will trigger exceptions any time another members age is checked.
Where the upgrader can result in a fatal error due to an invalid class stored for a Pages record comment.
An upgrade error where reports are loaded for Pages databases that no longer exist.
Orphaned comments trigger an exception when search index is rebuilding.
An exception can occur continued upgrades: DateTime::setTimestamp() expects parameter 1 to be long, object given.
Recursion can occur if the core_log table doesn't exist yet (as happens during auto upgrade).
An issue where importing a theme can break CSS.
MySQL strict mode upgrade to 4.1.12 can fail.
Installing a new plugin via the ACP can fail.
As part of our ongoing internal security audit, this release also improves security in the following areas:

Possible XSS in the "hovercard" system.
Further hardening to the insecure file upload code.

[B][SIZE=5][COLOR="#FFFF00"]Download:[/COLOR][/SIZE][/B]

[ATTACH]11291[/ATTACH]