Blocks going empty on multiple saves
Permalink
Hi guys.
Placed 5.7 into play for my new website and has been great so far. But have noticed a small issue which i think is linked back to concrete5 block saving.
After i insert a new block and save it with content - e.g. html and content blocks. - it appears fine, but then if i constantly edit this multiple times there is a risk of the block returning empty after saving it. I could have 500 words of text or html and would all be gone.
The container is still there and i can go back and edit it, but its like it places a new block inside.
Only way around i have found is saving/publishing the page before doing more then 3-5 edits or copying all the content before saving it.
have had more than 15 blocks return empty on me so far.
Below is a list of scripts i use, incase these might be conflicting with the saving process
/js/jquery.min.js"></script>
/bootstrap/3.3.2/js/bootstrap.min.js"></script>
/js/jquery.placeholder.min.js"></script>
/js/jquery.easing.1.3.js"></script>
/js/device.min.js"></script>
/js/jquery.browser.min.js"></script>
/js/snap.min.js"></script>
/js/jquery.appear.js"></script>
/js/waypoints.min.js"></script>
/js/waypoints-sticky.min.js"></script>
/js/main.js"></script>
/js/counter/jquery.countTo.js"></script>
/js/counter/init.js"></script>
Placed 5.7 into play for my new website and has been great so far. But have noticed a small issue which i think is linked back to concrete5 block saving.
After i insert a new block and save it with content - e.g. html and content blocks. - it appears fine, but then if i constantly edit this multiple times there is a risk of the block returning empty after saving it. I could have 500 words of text or html and would all be gone.
The container is still there and i can go back and edit it, but its like it places a new block inside.
Only way around i have found is saving/publishing the page before doing more then 3-5 edits or copying all the content before saving it.
have had more than 15 blocks return empty on me so far.
Below is a list of scripts i use, incase these might be conflicting with the saving process
/js/jquery.min.js"></script>
/bootstrap/3.3.2/js/bootstrap.min.js"></script>
/js/jquery.placeholder.min.js"></script>
/js/jquery.easing.1.3.js"></script>
/js/device.min.js"></script>
/js/jquery.browser.min.js"></script>
/js/snap.min.js"></script>
/js/jquery.appear.js"></script>
/js/waypoints.min.js"></script>
/js/waypoints-sticky.min.js"></script>
/js/main.js"></script>
/js/counter/jquery.countTo.js"></script>
/js/counter/init.js"></script>
I checked my page theme and saw i had put requires instead of provides. that changed. and i shall let you know of any further issue.
Although it seemed to be working fine with no other conflicts while both jquery and jquery.min were running.
Keep you updated
Although it seemed to be working fine with no other conflicts while both jquery and jquery.min were running.
Keep you updated
Nope, the jquery dupe wasnt the issue. Just had a block clear up upon saving it. Seems to be when editing multiple blocks on a page, multiple times.
Additionally it happens in the stacks too. so this would branch outside of theme issues
Additionally it happens in the stacks too. so this would branch outside of theme issues
Is this a from scratch theme?
Does your theme use a page_theme.php and are you registering your assets?
Registering your assets allows you to tell concrete5 what you require from it and what you will provide it. This prevents duplicate loading of assets.
https://www.concrete5.org/documentation/developers/5.7/designing-for...
The first thing that stands out is the inclusion of jQuery. The concrete5 interface loads jQuery, so if your version of jQuery has not been registered, you might be loading it twice.