Once the Edit+ and Viper file are available in data/public/ees dir, you can update the WYSIWYG Content Type Preference in Global Preferences to use Edit+ editor for Matrix admin mode.
Note that this is a system wide setting and will apply to all the places using WYSIWYG Content Type not just for Asset Builder’s bodycopy.
Is there any documentation to assist in getting up and running with using viper in an asset builder?
This is something that will need to be supported in the Matrix natively. The Viper files are already there in your Matrix instance, its just that currently they don’t work in frontend output due some of lib files required for Viper does not gets loaded in the frontend by Matrix.
Agreed, I’m currently trying to build a central news hub so we can push stories across different areas of our website but am disappointed with the WYSIWIG editor within an asset builder as well. Apparently Viper can be embedded (you’ll have to get squiz to do it for you and depends on what version of Matrix you’e on) but me thinks we’re being forced to use Edit+?
You should be able to get it working by using the standalone version of Viper if you are downloading and using it from GitHub, or you can just link to the same CSS and JS files that are used in Edit+.
To use it on an Asset Builder that is already using the classic WYSIWYG, you might have to do some trickery where you manually output the hidden field that normally would get printed using a keyword, and then initiate Viper manually against it.
We are planning on making this easier once we deprecate the classic WYSIWYG and bring Viper into core for Matrix which is scheduled for later this year, but you should be able to work around it with some manual minor frontend dev.
Hi Bart, is there an update please on when Viper might be available by default on WYSIWYG areas on an Asset Builder page? It kinda works in the Edit Form layout, but when activated is fixed to the top of the screen rather than positioned to the WYSIWYG area. Would be handy for a number of projects we have lined up rather than having to train Edit+ users for manage only a few pages in the CMS. Thanks.
Ok. We may continue efforts to restore some Viper functionality that was added in a past development by Squiz in our 5.5.6 or move the WYSIWYG editing of that content to the post creation stage with our asset builder process.