Updated December 1, 2019
After months and months of hard work, V2 is finally here! This update has changed the face of Stackable, and together with such a huge update comes the risk of some (minor) kinks that may temporarily affect blocks that were built with Version 1.
We’ve spent a considerable amount of time testing this latest version to make sure that it does not break anything on your published site. However, since some minor hiccups might occur, here are some troubleshooting guides on what to do just in case you do encounter a problem. We will update this post as more and more people upgrade to v2.
1. Everything looks broken in the frontend
If everything looks broken in your frontend after upgrading, please try out these solutions:
The styles being loaded in your frontend may still be the old styles from version 1.
For those who curious about how this works, this option is automatically checked if you upgraded from version 1. There are a lot of changes between version 1 and version 2, and in order to ensure fast loading speeds of your site, all the old styles have been separated into another stylesheet. This stylesheet is only needed if you use version 1 blocks.
2. Reusable blocks that have Stackable blocks look broken
After updating, and you’re using reusable blocks, there’s a chance that you may notice your reusable blocks to look broken.
Unfortunately, this needs to be done because the block editor doesn’t yet handle block updating in reusable blocks well.
3. Space between a Separator Block and another block
After updating, you might see a space between a Stackable Separator block and an adjacent block.
When this happens, you have 2 possible solutions depending on the adjacent block you are using:
4. Some Text Colors Inside Containers might Reset when Editing Existing Pages
While all text colors are maintained in the published view, you might encounter some text colors reverting back to the theme colors. This will not automatically happen and might occur only after you edit your existing page.
5. Block Error Prompt
While this is not expected to happen, in editing mode you might encounter the prompt “This block contains unexpected or invalid content”.
6. Other Errors after Updating to V2
If there are any other errors that you encounter after updating to V2 that cannot be solved by the troubleshooting tips above, please let us know. Our support team is always ready to help you out!
You can also report any bugs on the Stackable Git Hub Repository.