[TYPO3-v4] Breaking changes with Card layout

[Kay Strobach]

Hi,

perhaps this does the trick for you:

> API hints:
> 
> JavaScript
> - in old times we used:
> TYPO3.Backend.ContentContainer.setUrl(uri);
> 
> Now please use
> TYPO3.ModuleMenu.App.openInContentFrame(uri, params);
> The "new" function was available before and knows the current
> module. This function uses the correct iframe - if it is allowed to
> load the module.

https://review.typo3.org/#change,3370
https://review.typo3.org/#change,4299
https://review.typo3.org/#change,3947

Perhaps we should change the TYPO3.Backend.ContentContainer as well, but
this was rather hard, as this is a real iframe object :(

Regards
Kay



Am 27.09.2011 22:39, schrieb Lorenz Ulrich:
> Hi everyone
> 
> Now that we approach the release of TYPO3 4.6, I'm doing some testing of
> DAM 1.2 with the new version.
> 
> Unfortunately a lot of stuff seems to be broken, and if I got it right,
> one cause could be the introduction of the Card Layout.
> 
> Does anyone have information if the Card layout will really break older
> JavaScript stuff? DAM uses custom calls for almost everything in the
> backend: Changing folders, mass editing files etc.
> 
> This will cause us some problems because we still should maintain
> version 4.5 as it is a long term support release. And with DAM 2.0 (for
> TYPO3 4.7) coming along maintaining three branches (one for 4.5, one for
> 4.6 and the new one for 4.7) will be quite an time-consuming.
> 
> Thanks for your information and best regards,
> 
> Lorenz


-- 
http://www.kay-strobach.de - Open Source Rocks

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org

Answere was usefull: https://flattr.com/profile/kaystrobach