The portfolio template is not showing everything in a grid. In this example the last image is in wrong position.
I have tested this on a site with only the latest versions of Beaver Builder and Varnish HTTP Purge active and just with BB active.
The weird thing is that when logged into site it shows correctly. But when viewed in a private window or logged out it shows as above image.
I have tried this in Firefox, Chrome and Safari with the same results.
On another note - The Services template images at bottom still link to Fastline media. Can these links be removed in a future update please. Thanks (image below shows section I’m talking about)
Thanks for getting in touch! I believe the first image you are referring to is using the Photo Portfolio template. I tried the same template on my local dev and it seems to be fine. Anyhow, that template is also using the Collage layout from our Gallery Module so it’s not supposed to show all images in a perfect grid, but instead in varying sizes. If you noticed on that template, the images don’t have the same sizes. We have another layout called Thumbs and that maybe what you’re looking for, it shows everything on a perfect grid, all images having the same sizes.
That link actually redirects to the Beaver Builder site but yes, I’ll tell the other members of the team about it.
Hope this helps!
I am using the default settings. No changes have been made. This is straight from the template. This normally shows in a grid. However if you look at the full page screenshot it doesn’t look right, irrespective of the settings.
This is what it looks like from a private window or not logged in.
this is what it looks like when logged into the site.
BB is the only active plugin
So, as you can see I’m baffled as to why there is a different view between logged in and not logged.
Any suggestions what might be causing this?
I tried again the same template from my end and checked it on Chrome and Firefox, logged in or not and it’s all fine. Everything’s in the grid. Do you want to share the site URL so I can check further?
I’ll have a bug report submitted for this. Since it’s only happening on your server, please leave the admin credentials on so our lead dev can check when he’s available. We’ll get back to you once we have more information.
OK. Thanks Ben. Do you want FTP details also?
Just realized you have 1 Must Use plugin and 1 Drop-in plugin. Would it be possible to disable these and check if the problem is still happening?
Edit: Don’t forget to purge the Varnish Cache as well.
I’ve removed the MU plugin and purged Varnish. The advanced cache is from WP Rocket. Feel free to remove to test (plugin labelled as Speed Boost in plugins page).
You can access everything through SFTP
Sorry, I deleted the WP Rocket plugin but the advanced cache is still there? Would it be possible to just delete the file via FTP or rename it for now? Also, would it be possible to update the BB plugin to the latest version?
I’ve deleted the advance cache and updated plugins. It now looks OK. What do you think was causing this and how can it be fixed. Again not sure if it was the advanced cache or the updates.
Feel free to do anything with this site as it’s only a test site.
It was most likely a caching issue. I’ve used WP Rocket before and they have an option to allow caching for logged in users which is disabled by default. That’s most likely the reason why the problem only occurs when logged out, because then, the cache kicks in. No idea why though when the WP Rocket was disabled.
Allow caching for logged in users in WP Rocket was disabled so it wasn’t this.
Yes, and that is exactly why the problem wasn’t happening when you are logged in. The cache only kicks in when you are logged out and doesn’t when you are logged in.
Hope this makes sense.
It makes perfect sense. Thanks for clarifying. I have contacted the WP Rocket team and created a test site for them, so hopefully they can fix the problem.
Thanks for your support.
Anytime, Dennis! Have fun with The Beaver!
Finally found the problem that was causing the issue. It was the Lazyload Image setting in WP Rocket. Switching this off seemed to fix it. So there is a conflict between the lazyload and BB. Be great if the tech team are able to find a solution for this.