That made no sense to me at all. So sorry.
I am attaching 2 images. One is our current (pre ES 2, old software) site and one is an exact duplicate on another URL that we upgraded.
This doesn't look like an upgrade to us visually but a mess.
1. The login box was so neat and clean on old style. I do not like how tall the box is now with it's pretty (but not needed) extra background image)
2. The sidebar as you can see worked perfectly pre ES2. I did not need to place it in a "larger" module position. (the one it is in auto sizes, btw)
3. It does not respect layout -- you can see it doesn't resize, it overwrites the boundaries. This is in a "larger module space" so that does not seem to be a solution.
We would like to have the advances in ES 2.0 but not at the cost of the whole site looking and acting poorly.
I am trying to be as clear and detailed as possible. Please don't take this personally - I love ES and the SI team does an amazing job. However, for us, this is not looking like an upgrade at all but a leap off a cliff into a mind numbing mess.
It okay, we will always welcome all the feedback from our customer.
And I also believe 1 sentences is however how we improve the software it surely can't make everyone satisfy but we will try our best to solve each other issue.
The reason why it work correctly in the 1.4 version is because we have implement the auto resize to responsive feature in the pass but the thing is, it will make the site become slower and it will showing some "jumping" effect if the site is extremely slow, you can take a look of my video here (
http://screencast.com/t/G6nk3ciuKk ), this is what i test on my local 1.4 version, imagine if the site load page very slow, at first it will display non-responsive module styling then need to take a little bit time to resize it then only show the nice responsive view.
Most of our customer complain about this in Easysocial 1.4, so we decided to remove this auto resize feature and implement mobile agent detect feature, what this purpose is it will detect those user view on the actual mobile device from the website, then show the responsive view properly.
We did try your is-mobile and it helped a lot but the other issues remain. (not respecting boundaries in our blog titles and the larger than needed login box with a background we don't care for.)
Why is it not responsive and respecting layouts now? Is there a need to change templates with the upgrade?
thanks guys,
Bridgette
To be honest, the login box still looks bad to us. We can live with it, since it is functional but it is not an improvement. The spacing for the two test (header and desc) are too wide between lines and it would look much better without that background.
Hm, I don't think that issue is related when you add
is-mobile module suffix from the module then causing the rest of the issue.
Perhaps you can provide us with your test site Joomla backend and FTP access so we can better have a look?