Problems with Framework and Layout Dimensions

[alexcox6 0]

I am developing the new version of our website and using the 2.2 framework. I have changed the Defaults to Global Width 800 px Sidebar Width 200 px Main Column Width 600 px Once I save and view all the website is still fills the screen. Getting frustrated now with this Regards Alex

[Stefan 6]

Hey Alex, What is your screen resolution set to? I just looked at your website and it doesn't fit the full width of the browser. See here: http://screencast.com/t/yYgdm1CY Also, in the PageLines Settings > Site Options > Layout Editor is the site design set to full-width or fixed-width?

[alexcox6 0]

The Issue is not with the screen resolution. The website you are looking at is the live site on pagelines pro. I am migrating to Framework. I want the new site to have the same look as the old. Below is what i currently see http://www.screencast.com/t/VG8gZVYkdWd http://www.screencast.com/t/7IXblhzhtRor http://www.screencast.com/t/yTaQbMmo

[alexcox6 0]

The development platform is a separate local install

[alexcox6 0]

Pagelines Pro runs with no issue so might just be a framework issue

[alexcox6 0]

Hi All Have done a few tests in various types of Installs and on a single site setup Pagelines Framework Pro is fine and working correctly. Updated to Wordpress 3.4.1 and it works fine. Made wordpress a multisite install and Pagelines Framework Pro no longer works. I will upgrade to the developer version tomorrow and see if it works then. Alex

[Stefan 6]

Hey Alex, Keep us posted! We might have to do some testing ourselves and check the multisite. However, developer is indeed required for multisite so do that and keep us posted! Stefan

[alexcox6 0]

Hi Guys I have updated to Developer and then changed my site to a Multisite install and it breaks!! Layout goes back to how it is in the screen shots above so must me a multisite issue. I guess Developer is not compatable so have wasted $$$ on the upgrade. Hopefully pagelines can issue a fix ASAP Alex

[Danny+ 1,327]

Hi @alexcox6 Am I OK to now resolve this, seeing your issue was a localhost server configuration issue ?