Closed kenmanheimer closed 1 year ago
I should add that I've tested and affirmed that the unavailability of the HTML block happens whenever I build with the kitkat frontend addon, with any of the following conditions:
@kenmanheimer HTML block is indeed disabled with volto-eea-kitkat add-on due to GDPR. See:
You can re-enable them via your policy add-on or directly within your project:
src/addons/volto-custom-policy-addon/src/index.js
const applyConfig = (config) => {
// Re-enable non-GDPR compliant blocks
config.blocks.blocksConfig.video.restricted = false;
config.blocks.blocksConfig.maps.restricted = false;
config.blocks.blocksConfig.html.restricted = false;
};
export default applyConfig;
Ah, I see!
Thanks!
The HTML block became unavailable for inclusion on a page in recent builds that include volto-eea-kitkat.
Strangely, the HTML block is available if I include all the addons that kitkat contains, but not the kitkat collection itself.
Here is the Plone+frontend build versions:
Here are the addons that are included with kitkat, but don't inhibit availability of the html block if I add them specifying each rather than via kitkat: