Forum Replies Created
-
AuthorPosts
-
August 7, 2025 at 11:50 am in reply to: Stretch Row Alignment Broken on New Pages in Porto 7.6.1 (WPBakery) #34241
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!
August 5, 2025 at 2:30 pm in reply to: Stretch Row Alignment Broken on New Pages in Porto 7.6.1 (WPBakery) #34105Thank 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”.
August 4, 2025 at 10:53 pm in reply to: Stretch Row Alignment Broken on New Pages in Porto 7.6.1 (WPBakery) #34092Adding 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.
Thanks, I’ll check their forums and see what they say. I just wanted to be sure that it’s not going to affect functionality or cause any other issues. If it’s strictly appearance-related, I’m okay with that.
Hi – thanks for the reply. I wasn’t referring to the overall font not being poppins. I was referring to the WP-Bakery back end font not being in Poppins anymore with the latest WPB update. I thought that was what you were going to investigate. It used to look aligned with the theme, and it does not anymore. (In addition to the changes in the number of columns, etc, which I understand is likely a WPB change you cannot control.) Why does the latest update override the back end font of Poppins? Please refer to attached graphics. One shows the appearance and Poppins font on the back end of WPB version 6, and the other shows how it changed with WPB7. I assumed that because you could override the look before with the font, you’d still be able to do so. Is that not the case?
Attachments:
You must be logged in to view attached files.I think the problem with the temp link is that your interface is cutting off the end of the link so you can’t copy the whole thing. At any rate, it does work – but you probably can’t see the whole link. It’s ok – just use the other login. Thx.
Hi – That’s odd. The temp admin login link should work. I tested it as well, and I go straight to the dashboard under temporary access. Are you sure you copied/pasted the entire link?
I’ll also provide you with a user login instead, but I would appreciate it if you could let me know if you try the temp link again. It should work.
Thanks!
This field is Private Content.
-
This reply was modified 2 years, 1 month ago by
sarah-5068.
Thank you! Will provide a link for login (temporary admin access link) in the private area.
The font change is solely within WPBakery. It’s like it is overriding the settings you previously had, if that helps.
The site I’m giving you access to is brand new – I’ve done nothing to configure it yet other than install the theme and get it set up with a child theme. There’s a sample page you can use to see the issue I’m talking about.
Eager to hear what you can do. Thanks!
This field is Private Content.
Hi! I’d like to request addition of a category dropdown filter feature in the Porto Post Grid widget: Basically, right now, when you toggle to allow a category filter in a Porto post grid element in WP Bakery, it displays categories in an inline horizontal list. It’s ajax – so when you click, the posts below will auto-filter without reloading the page.
However, we have a lot of categories, and it makes it wrap around in an awkwardly long inline horizontal list.
We would prefer a dropdown filter, but with ajax still, so the page does not reload or take me to a category archive page (which is what the standard wordpress category element will do).
Hopefully this is something you can add soon!
Thanks,
SarahI can’t share the login credentials as this is a live site. But here are screenshots.
Basically, when you toggle to allow a category filter in a Porto post grid element in WP Bakery, it displays categories in an inline horizontal list. It’s ajax – so when you click, the posts below will auto-filter without reloading the page.
However, we have a lot of categories, and it makes it wrap around in an awkwardly long inline horizontal list.
We would prefer a dropdown filter, but with ajax still, so the page does not reload or take me to a category archive page (which is what the standard wordpress category element will do).
I thought I had seen an option to select dropdown instead of inline for the Porto post grid, but I can’t find where that is. Does it exist? Can I use a post grid with a dropdown category ajax filter?
Thanks.
I understand. I did have one other question, though. Gutenberg is supposed to have a standard Related Posts block, but it doesn’t show up on your theme. Any idea why?
https://wordpress.com/support/wordpress-editor/blocks/related-posts-block/
Never mind! I converted my WP Bakery template to classic editor, grabbed the Porto shortcode for the element, and plugged that back into Gutenberg via a Shortcode block. All good.
But it would really be nice if you could enable everything for every builder. I have templates I’ve had to do in multiple builders because some functionality isn’t available in one or the other, and it’s kind of annoying.
-
This reply was modified 2 years, 1 month ago by
-
AuthorPosts