Is anyone experiencing odd behavior with Builder over the last 24-48 hours? We have noticed a few things:
Connected data being cached and returned with the wrong page. We have like 30 pages that have connected data and we noticed that when using the target query to fetch data our nextjs app would route to a new page and request for that pages data based on the URL but the builder API would return the response from the previous page request.
This may be related. We’re getting reports from customers that they’re seeing old versions of pages. These old pages are still published but have new versions targeted at the same URL. I’m unable to replicate the issue myself, but have timestamped screenshots from customers showing the old page. It would appear to be a caching issue, but the page they’re receiving should have been overridden many days ago.
It appears that the problem you’re facing may be linked to the uploading of webp images, which could potentially be causing compatibility issues within our platform. We have successfully replicated the issue on our end, and our dedicated team is actively working to investigate and find potential solutions.
At this time, while we are committed to resolving the issue as quickly as possible, we don’t have a specific timeline for when the fix will be deployed. Rest assured, we will keep you updated on our progress.
When you use Builder’s Image Block for your images, Builder serves the correct optimized format for every web browser. Builder performs these optimizations so you don’t have to:
The Image Block ensures you load the smallest possible image.
Builder analyzes your image as it relates to the layout of your page and determines the exact sizing of your image for all device sizes, automatically generating the optimal size for each screen.
Builder uses lazy loading, which loads images only when your users need them. This reduces how much users have to download.
Builder uses responsive page layout analysis to flag which images are below the page fold for each device so they can be lazy loaded.
Builder converts your image to the webp format.
If you’re a developer and are looking for more control over the image that is served by Builder, read the Image API documentation.
I’m also having issues with this page Builder.io: Drag & Drop Headless CMS. I’m unable to edit it. I’m trying to edit the custom component, service detail, but none of the text inputs are changing on the page. Could you take a look?
We’ve discovered a potential solution for the issue you were facing. By enabling the “Proxy Previews” option located in Settings → Advanced Settings → Advanced, it appears that the custom component “Service Details” input fields are now editable.
Could you please verify this and let us know if you encounter any additional questions or concerns?
To address the caching issue, consider including the “cachebust: true” option in your builder’s get call. This will help ensure that your application fetches the most up-to-date content and may resolve any caching-related problems.
I noticed symbols on both pages, but there isn’t a symbol model. I suggest removing these symbols from both pages, publish the changes, and recheck. If the issue persists, consider adding cacheburst: true as recommended by @manish-sharma.
No, it’s not working on our main site. We are trying to migrate our service pages to use a connected data modal as the source instead of the the current hard coded method, but this issue is blocking that. I’m able to reproduce this in multiple builder spaces. Do have you any suggestions on how to fix this?