Custom Manager Pages in 2.1 don't scroll content correctly

Weird stuff.... when I updated my site to 2.1-pl, my CMP’s all kinda broke: the HTML is all there, but I can’t scroll down on the page... so they are working, but I can’t actually see them or save them. I tried just printing a bunch of Lorep Ipsum text in there and I removed all my custom CSS from the CMP (regClientCSS commented out) and the behavior continues.

Anyone got any ideas what might be going on?

JS error - same thing happens, except it happens when I go to System Info

2.1
centos 5.5
php 5.3.6
mysql 5.0.77
Only errors seen through firebug

I’m not seeing any errors in FireBug... but this is becoming a huge problem because we can’t use our custom tools. The most obvious explanation here is that some of the manager CSS changed from 2.0.8 to 2.1.0.

There are now seperate scrollbars for the tree-panel and the content-panel, which is way better than it was before with one scrollbar for all and it solves an issue with positioning and dragging on firefox.
If you need extra scrollbars in your custom-CMP, I think you need to add them where necessary.

Try to add your component using the layout mgr instead of a landing div (coming in the next release : http://bugs.modx.com/issues/4656 )
You should then see a scroller only on the center content.

This problem occurs when you add straight up text... just a bunch of paragraphs for example. I don’t understand why any custom manipulations of ANYTHING are necessary... this is about as basic as it gets, so I’m baffled as to why custom JS or CSS trickery is required.

See this bug I filed:
http://bugs.modx.com/issues/4940

I’ve verified that this did not occur prior to 2.1.

The workaround here is to override the CSS in the output. Here’s my sloppy workaround:

1. Wrap the entire output in a div, e.g. with a class named "cmp_output"
2. Style the div with something like this:




This fixes the immediate problem, but it is seriously janky.

It i snecessary because of the reason mentionned in the issue 4656.
The manager layout use an Ext Viewport with a border Layout, therefore, all resizing should be handled by the Ext layout (that’s why the main manager layout as an option autoScroll set to true).

If you render your text or anything else without using the ext layout manager, ext does not apply the correct resizing (it can be resize event - hence why the grid never resized correctly - , or in this case, no scroller bar).

The real solution would be to not use a border layout in the next manager version and handle positioning with CSS directly. Until then...

Thanks lossendae. So if I make the edits to the various JS files as described in http://bugs.modx.com/issues/4656, that should fix the issue? Sorry, but I’m not immediately seeing what’s causing this and why the changes there would fix it.

Man, I feel like this approach in the MODx manager is completely wrong. It’s already somewhat convoluted, but requiring tweaks along the lines of http://bugs.modx.com/issues/4656 just completely baffles me. I don’t mind that Ext JS allows for really complicated stuff... but it’s really a problem when it forces us to come up with complicated solutions for simple problems.

Quote from: Everett at Jun 01, 2011, 03:57 PM

Thanks lossendae. So if I make the edits to the various JS files as described in http://bugs.modx.com/issues/4656, that should fix the issue? Sorry, but I’m not immediately seeing what’s causing this and why the changes there would fix it.

Man, I feel like this approach in the MODx manager is completely wrong. It’s already somewhat convoluted, but requiring tweaks along the lines of http://bugs.modx.com/issues/4656 just completely baffles me. I don’t mind that Ext JS allows for really complicated stuff... but it’s really a problem when it forces us to come up with complicated solutions for simple problems.

You should just upgrade to 2.1.1.