We have successfully created a new asset called Frequently Asked Questions. The name is the question and an attribute (editable in the wysiwyg) called answer contains the answer.
We can add and edit the new asset fine in the back end but want to add it to the EES. We've got as far as creating the asset in the Wizard (name[Question] and shortname) but want to
be able to edit it in the contents screen much the same as the news asset. The problem is that there's no Contents screen for it! Anyone got any ideas how to fix this?
We did a similar thing with the Wizard creating an external link asset but that was easier as there was no need for a wysiwyg so the link_url field was just simply added to the details screen and saved accordingly.
I cannot help, I also cannot understand what for You build such asset.
Wouldn't be easier to use just "Standard Page" or even "Data Record" asset with applied metadata?
Sorry for OOT
Not knowing much about your custom asset I couldn't say exactly how to create the appropriate JS for Easy Edit, but I could point you to some example files that might help you along (in the non minified source code):
<system_root>/data/public/ees/Libs/components/screens/assets/EasyEditScreenNewsItem.js
<system_root>/data/public/ees/Libs/components/screens/assets/EasyEditScreenPageStandard.js
Both of those files contain the code that we used to deal with the wysiwyg editor for these asset types. You would have to define your custom asset similarly in the EasyEditScreens.assetTypes namespace. Anything added to that namespace is automatically recognised by Easy Edit and allows you to write your own js for asset screens without affecting any of the core code.
[quote]
Not knowing much about your custom asset I couldn't say exactly how to create the appropriate JS for Easy Edit, but I could point you to some example files that might help you along (in the non minified source code):
<system_root>/data/public/ees/Libs/components/screens/assets/EasyEditScreenNewsItem.js
<system_root>/data/public/ees/Libs/components/screens/assets/EasyEditScreenPageStandard.js
Both of those files contain the code that we used to deal with the wysiwyg editor for these asset types. You would have to define your custom asset similarly in the EasyEditScreens.assetTypes namespace. Anything added to that namespace is automatically recognised by Easy Edit and allows you to write your own js for asset screens without affecting any of the core code.
[/quote]
Thanks Anthony…I see it's your code I'm editing! I had made a EasyEditScreenFaq.js based on your EasyEditScreenPageStandard.js but hadn't defined the new asset in the namespace. It's working fine now…thanks