Home › Toolset Professional Support › [Resolved] Toolset Views breaks the default Gutenberg gallery block
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
- | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | - |
- | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | - |
Supporter timezone: Europe/London (GMT+00:00)
Tagged: Views plugin
This topic contains 12 replies, has 2 voices.
Last updated by Nigel 4 years, 8 months ago.
Assisted by: Nigel.
When I add a Gutenberg gallery block to a default page and add more than 35 images and the Toolset Views plug-in is active, the page doesn't show any content.
I have set up a test site:
Theme: Twenty Twenty
Active plug-ins: Views (no other plug-ins active)
Page type: default WP page
When I add a Gutenberg Gallery Block to the page, with 10 images, all is fine. I have added 5 images at a time to the gallery and when I reach 40, the content of the page disappears. The header, title and footer are there, there is just no entry content. Not only the gallery, but no content at all. When I remove 5 images from the gallery, the content reappears.
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
I've just been testing this on my own local site, and I've reached as far as adding 44 (fairly large) images, and haven't hit any limits.
So I conclude there are no hard-coded limits, it is likely a resources issue.
Check your PHP logs and browser console for errors, e.g. out of memory errors.
You may need to increase your server settings, e.g. https://wordpress.org/support/article/editing-wp-config-php/#increasing-memory-allocated-to-php
Thanks. I will look into that. But in the meantime: when I disable the Views plug-in, the issue does not occur. Don't you think that's strange? Because no Toolset view is present at the page at all.
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
If Views is active it is going to be consuming some resources in case a View were to be added to the page, and it sounds like that may be enough to tip you over the edge of the limit of resources available.
Check your logs to see if that is the case.
Thanks. I have checked the logs and see no error. The memory_limit is set to 265M, which I would think would be enough.
Don't you think it's strange that just activating the Views plug-in has such a big impact on the memory, that - even while using all the defaults and no extra plug-ins - it breaks the page with such a small amount of regular content?
Please let me know what we can do to get this issue resolved.
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
Let me take a copy of the site and install it locally to rule out some other issue.
In the meantime you might want to test allocating more memory to see if that does indeed affect the limit on the number of images you can add.
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
I installed the copy of your site—complete with Media Library—locally, disabled other plugins than Views, created a page, inserted a gallery block, added 50 images to the gallery, everything worked as expected when saving the page.
But visiting it on the front-end the result is blank.
I think I had misunderstood your original post to mean that the problem was visible while editing on the back end.
I have now tested again on my own local test site and I found the same: 35 images display okay, 36 is blank.
I don't think that's a coincidence.
I'm escalating this and I'll get back to you when I have some feedback from the developers.
Yes, that is exactly what I meant. Sorry that I wasn't clear in explaining the issue.
Thanks!
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
My second-tier colleague has reproduced this—although he got to a slightly higher number—and is preparing the internal tickets to submit to the developers.
I'll keep you posted.
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
Just to let you know this has been fixed by the developers, though I don't have an ETA for when the next update will be published, but it shouldn't be too long.
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
This should now be fixed with the releases of Blocks and Views today.
Please let me know if you still see any problems after updating (use the Check for Updates button on the registration page if you don't see the updates available).
Hi Nigel,
Are you sure? I am sorry, but I don't see any difference.
I am using:
Toolset Types 3.3.10
Toolset Views 3.1.3
Do you?
Kind regards,
Tim
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
The current version of Views is 3.2.
If you don't see an update notice, click the "Registered" link and then use the Check for Updates button, or download a zip of the latest version from https://toolset.com/account/downloads