Benjamin Intal
Forum Replies Created
-
Hey @mneroni, glad you found the issue! I’m resolving this thread now, please reopen or create another one if you need anything 🙂
Hey @alamiomar, we just released an update with a fix for this. Please update to v3.12.15 and try it out 🙂
Hey @mneroni, if you have updated WordPress, please make sure that you also have the latest Stackable version installed. Aside from that, it would also help to isolate the issue to see whether the issue is coming from Stackable, try deactivating other plugins one by one to see whether that fixes things – there’s a chance that there might be another plugin causing the issue since we haven’t gotten any similar reports to this recently.
We have some troubleshooting docs that might help out:
- https://docs.wpstackable.com/article/379-your-site-doesnt-include-support-for-this-block-error
- https://docs.wpstackable.com/article/383-im-encountering-block-errors
- https://docs.wpstackable.com/category/331-common-issues
We could also help you out if you would be able to send over some login details to our support email support@wpstackable.com so our support team can check things.. seeing the error first hand would make troubleshooting easier.
Hello @silasveta2012, where did you get this warning?
I don’t believe there is much Legacy JavaScript code in there – it’s only the bare essentials for browser compatibility which is added automatically during the build process. The warning also said that you will have 0.0kb savings if you modernize, so I think this should be okay.
Hey @alexshum939, tabs in general hide the content of the other tabs. So while this works for most types of content, there might be scenarios that it show issues especially for more dynamic content or interactive content.
Unfortunately, in these cases you would need to force the interactive content to re-initialize like what you’ve already done with recalculating positions.
- This reply was modified 3 months, 1 week ago by Benjamin Intal.
Hello, thanks for the report. Looks like a bug with the Freemius SDK we’re using, we’ll investigate this.
In the meantime, I found a source that says that it might have something to do with object preloading – are you using something like this in a caching solution? If you are, try disabling it and see if that fixes things.
Thanks!
Forum: Plugins
In reply to: [Stackable - Page Builder Gutenberg Blocks] No block worksHello, I’m resolving this update now due to inactivity, please see our troubleshooting docs here:
Hello, I’m resolving this now since it has been reported that this issue has now been fixed.
Forum: Plugins
In reply to: [Stackable - Page Builder Gutenberg Blocks] PHP Fatal Error issue?Resolving this issue since it has already been reported to have been fixed
Hello, thanks for the report. Both have been fixes in v3.12.8 which has just been released. Let me know how it goes!
Thanks for this @aminvanda, this will be included in the next update. Marking this as resolved.
Forum: Plugins
In reply to: [Stackable - Page Builder Gutenberg Blocks] W3C Validation errorsHello, thanks for posting!
Regarding the CSS parse errors on the optimized CSS, they seem to be false positives because they look to be valid CSS (at least for the CSS which are outputted by Stackable) – I’m not sure about why they are pointed as errors though, but I saw that validation sometimes reports these things, maybe because of CSS optimizations.
Thanks for the report about the incorrect divs, we’ll add this to our list of todos that we will address in a future update. The good thing is that these validation errors don’t have any immediate, critical impact on the website’s functionality or appearance.Thanks!
Hey Alex,
Thanks for the link. We’re able to see the reflow warnings. The difficult thing with these warnings is that it doesn’t exactly say where the source of the issue is.
According to the error, some JavaScript code is causing some slowdown with reflow. Upon further investigation, I do not think these are coming from Stackable. From the link you gave, I removed all JavaScript code that Stackable was adding to the page (so no JavaScript from Stackable can cause reflow), but the warning is still showing up when you scroll. In addition, Stackable isn’t really doing any script calls when you scroll in your page.
I was able to trace though that some the reflow warnings might possibly be coming from a script called sticky.js and main.js which are from Blocksy/Blocksy Compoanion. I would like to recommend contacting their team instead about this warning.
As to why adding a Tabs block makes that warning appear on scroll, my guess is it might have something to do with having more content in the sticky menu.
Forum: Plugins
In reply to: [Stackable - Page Builder Gutenberg Blocks] No block worksHello, please check if you have the Gutenberg plugin active, please deactivate it if it’s there. Did this just start to happen after an update? Can you check if there are any browser console error logs – these can help us see what’s happening.