Stretch Row Alignment Broken on New Pages in Porto 7.6.1 (WPBakery)

[sarah-5068]

Hi Porto team,

Since updating to Porto 7.6.1, all newly created pages have misaligned stretch rows (rows using stretch_row_css or porto_stretch_css). The row content appears offset to the right instead of stretching full-width.

* ✅ This only happens on **new pages**—older/duplicated pages from pre-7.6.1 render correctly.
* ✅ Happens even with all plugins disabled except WPBakery and Porto Functionality.
* ✅ Affected sites are running Porto child themes or Porto parent directly.
* ✅ The CSS logic references --porto-scroll-w, but this variable appears **unset** on new pages unless specific containers exist in the page structure.
* ❌ The new row/page structure no longer wraps .vc_row inside .porto-wrap-container.container, breaking the variable’s calculation.

Please advise:

1. Has the required page structure for stretch rows changed in 7.6.1?
2. What markup or wrapper should be present to correctly initialize the CSS variables?
3. Will Porto patch this so new pages work out of the box again?

Thanks! I’ve attached pics of both an offset stretch row (on a newly created page since updating to 7.6.1) and a duplicated page stretch row that works (also on 7.6.1 but duplicated from a page created before that version).

Attachments:

You must be logged in to view attached files.

[sarah-5068]

Adding that I’ve determined this only happens when selecting stretch row by CSS. Rows stretch properly when using JS instead. Which is weird and new… but maybe intended? Just wasted 3 hours of my day trying to figure this out.

[Aizaz Awan]

Hello, @sarah-5068,

We didn’t specially changed such code in the 7.6.1 version of the theme, you can check our theme changelog here: https://themeforest.net/item/porto-responsive-wordpress-ecommerce-theme/9207399#item-description__change_logs

But the issue you are facing might be the latest WP Bakery version’s core issue or functionality. Could you please once check here: https://codecanyon.net/item/wpbakery-page-builder-for-wordpress/242431/comments and confirm with their support.

Best Regards,
PThemes Team.

[sarah-5068]

Thank you – I have reached out to the WPB support folks to see what they say. Just flagging this in case someone else runs into the same issue. For now the fix appears to be selecting “Stretch with JS” instead of “Stretch with CSS”.

[Aizaz Awan]

Hello, @sarah-5068,

Thank you for the update! We appreciate you flagging this—it’s definitely helpful in case other users encounter the same issue. Selecting “Stretch with JS” instead of “Stretch with CSS” sounds like a good workaround for now.

Let us know if WPBakery support provides any additional insights—we’re happy to assist further if needed.

Best Regards,
PThemes Team.

[sarah-5068]

The WPBakery folks replied: “Hello, In the 8.5 release, WPBakery introduced updates to row stretching to enhance performance. It appears that the theme may be modifying the row output, which could be affected by this update.”

I have found when I modify your CSS as follows, I get the stretch row by CSS functionality to return to normal – in case this is a fix you want to apply:

.vc_row.porto_stretch_css {
position: relative;
width: calc(100vw – var(–porto-scroll-w, 0px));
width: 100vw !important;
position: relative !important;
left: 50% !important;
transform: translateX(-50%) !important;
margin-left: 0 !important;
margin-right: 0 !important;
box-sizing: border-box !important;
}

It would be nice to have this remedied within the theme, as without the fix, it means I cannot create a new page anymore with the stretch by CSS quality applied – and when using the stretch by JS parameter, while the rows do stretch, it causes pages to jump around a lot when loading.

Thanks!

[Aizaz Awan]

Hello, @sarah-5068,

Thank you for the detailed follow-up and for sharing the response from WPBakery, as well as the CSS adjustment you’ve discovered.

It does appear that the recent WPBakery 8.5 update changed how stretch rows are handled, and this may conflict with how the theme currently manages row output. We appreciate you identifying a workaround using custom CSS—that’s very helpful.

I’ve forwarded this information to our development team for review. We’ll evaluate the compatibility impact of WPBakery’s update and assess whether a theme-level adjustment is appropriate to restore expected behavior for “stretch row by CSS.”

In the meantime, feel free to continue using your CSS fix as a temporary solution. We’ll keep you updated on any theme updates or patches that address this compatibility issue.

Thanks again for your patience and your proactive approach!

Best Regards,
PThemes Team.

[Author]

Posts