Asset Builder Wysiwyg

(Chris Horikx) #1

Hi Guys,

 

I'm having a bit of trouble with the asset builder wysiwyg. Its been a long time since I've touched one of these. It seems like the asset builder uses HTMLArea wysiwyg, which I suspect is a version of the classic wysiwyg.

 

I've tested on two separate matrix installations and it seems like the bold and italics button doesn't work. Is there any code out there to get them working?

 

Is there any way to get viper installed on the asset builder wysiwygs instead of HTMLArea? Is Viper perhaps banned from the public front end? I don't think I've seen it on the front end before.

 

Do you guys even use asset builders anywhere anymore? Or do you primarily just use edit+ plugins? Its been ages since I've been asked to make an asset builder.

 

Chris

(Nic Hubbard) #2

When I have needed to have front facing Asset Builder with WYSIWYG I have always used an alternate editor such as CKEditor. You can easily load it up on the textarea that the standard editor uses.

(Chris Horikx) #3

When I have needed to have front facing Asset Builder with WYSIWYG I have always used an alternate editor such as CKEditor. You can easily load it up on the textarea that the standard editor uses.

 

 

Thanks Nic,

 

I've also done this a few times, but it becomes a hassle when you know the client is going to be pasting Microsoft Word into the editor and may also need to insert an image.

 

There is a nice WYSIWYG just there, it would be nice if it was available for all WYSIWYG inclusions not just a select few.

(Bart Banda) #4

Not sure why the bold and italic wouldn't work, but if your system does have Edit+ on it you could always customise the builder and use Viper as the WYSIWYG instead of the Classic one? Has been done before but not that common, shouldn't be hard to do either. 

(Matthew Harding) #5

Bart, could you provide some more information on how to achieve this please? This would be quite helpful.

(Bart Banda) #6

Well if you create an asset builder with a metadata wysiwyg and look at the code, you should see that there is a hidden textarea field that the WYSIWYG pumps the HTML into on submit.

 

Using a custom Simple Edit Interface for the build interface, you should be able to write some custom JS that hides the classic WYSIWYG, and initialises the Viper CSS and JS. Just look at what the Edit+ code does with the Viper files and copy that.