Forum Replies Created
-
Posts
-
Hi,
I’m in dev mode with maintenance mode turned on. I know from experience you guys don’t want to deal with that, I can understand why. But I was able to figure out the real issue as I was wrong about the CSS code being the cause.
I tracked it down to avia.js and the code below — the jitter behavior goes away this code is removed.
hide_menu = function()
{
container.removeClass(‘show_mobile_menu’);
container.css({‘height’:”auto”, ‘overflow’:’hidden’});
return false;
},It would be nice if you had boxed-layout mode available on your demo site so as to be able to immediately know if the bug is in your code or due to modifications made by the user.
Cheers
The problem arises when you shrink the window until you get horizontal scrollbars and then scroll over to the right.
The screenshot is on the homepage.
Thanks
I chose this theme specifically because it had a fixed layout option-amongst other things.
I’m very confused here, are you saying that the default behavior of the fixed layout option coupled with the stretch option is to break the layout?
If simple options don’t work together then they shouldn’t be available in order to avoid situations like this.
I’ve spent too many weeks on this project for there not to be a fix. I’ve got to present this site next week so this is potentially a disaster.
I am experiencing the problem in Chrome v29.0.1547.66. And the problem appears when the browser gets resized to less than 910px. You have to horizontal scroll to the right to see it. It’s pretty bad.
OK, that’s cool. I set up a clean install here. Same behavior. http://demo.thelindata.se/demo2/
Thanks for the reply.
I’ve updated to 2.2 and am getting the same behavior. I tried a fresh install on another setup prior to your response and got the same thing too…
You need to modify hosts file to view the site. Need email or private status on thread to send you info.
Thanks
Any news on a general preview functionality? Mayb it could make it on the list :)
One band-aid is to clone a page to be edited then place that page as pending review or whatever and then once finished quickly delete the original and rename the new version and change status. As far as I’m aware there’s no seo penalty for this, can you guys confirm this?
Another way to possibly do it would be to have a caching plugin that didn’t automatically purge updated pages. This way the old static page would still get served up leaving the user free to edit/update a page and see the results before they go live. Unfortunately I can’t find a way for W3 Total Cache to not automatically purge updated pages. Any insights?
Thanks!
