At my company we are experiencing the same problem renanf mentions. But in our case ASP.NET localization is not really an option. We have multiple clients running within the same environment and we give them the ability at runtime to customize certain business terms like "Supplier" to match their internal usage. Rather than ever directly use the term Supplier, we use a token [$Supplier$], then each client can customize that token to match what they use internally: Supplier, Vendor, Distributor, Partner, etc. These tokens are used throughout the application: in aspx pages, in c# code, inside text stored in the database. Replacement terms are stored in the database and are modifiable through the web interface at runtime by the clients themselves. The solution we came up with to allow dynamic on the fly replacement of tokens regardless of where they came from was a Response filter. Essentially we just run a regex on the response, swapping out tokens for the replacements configured by the client that the current user is associated with. Localization doesn't help us because the clients want the ability to change the tokens at runtime via the frontend.
In the previous version of atlas that we were using the response filter caused us no problem. After upgrading to the release version of atlas however, we must either disable partial rendering in the script manager tag (basically stop using update panels) or disable the token replacement filter (not an option).
Do you have any recommendations or workarounds? Will this limitation where update panels do not work with Response filters be addressed in a future version of atlas?