Task description: Document the asset module and its different components. Download the newest dev version and create a documentation page in the drupal.org handbooks for each component:
- Basic assets: integration with textarea's, showcase the asset wizard
- WYSIWYG assets: integration with TinyMCE
- CCK assets: single and multiple value cck field
- Asset Bonus: installation of the module with the external zip. Showcase .swf, .flv and .mp3
- Asset YouTube: enter your YouTube developer's ID and embed one of your YouTube movies
- Asset Embed: enter the object code of a YouTube movie, or any other provider, and see how it embeds
- Asset Import: put a bunch of files of different types somewhere on your installation, point the asset_import module's settings to it, and import them
- Asset Panels: Create a node with a cck multiple-value field an attach 10 assets. Create a panels, attach this node as an asset gallery and show 4 assets per page. Then document how a block is automatically created as a preview
- Views integration: Create a views which selects some nodes that have assets attached and display them
Each handbook page should contain a detailed explanation of how the section is set up (for instance by enabling a module), how it is configured and a step-by-step example of how to get it actually workin (by creating a node, a panels or a views for instance). Include pictures on the configuration and the example and a screenshot of how it eventually looks.
Resources:
Primary contact: Wim Mostrey
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | asset-images.zip | 179.1 KB | philipw |
Comments
Comment #1
aclight commented1. I suspect that you don't want the student to go through detailed steps of how to enable modules on each handbook page, but if that's the case I don't think it's crystal clear, and I would hate for a student to waste his time doing that 9 times at the beginning of the task.
2. I would point them to the location of the parent page in the handbook under which you wish the pages the student generates to go, so that somebody doesn't have to go back later and change the parents for a bunch of pages.
3. There is no deliverables section. It's pretty obvious from the description section, but the deliverables section allows us GHOP admins to quickly scan an issue and see what it is that the student needs to do so we can quickly check to see if the student is making appropriate progress.
The above comments are all pretty minor, so once you've addressed them feel free to add this as a task.
Comment #2
wmostrey commentedThanks for your input. The task has been created: GHOP task #117.
You can make this node the DrupalIssue for the task.
Comment #3
aclight commentedComment #4
webchickLet's stick this in the Asset module queue.
Comment #5
philipw commentedI'm having issues integrating assets with tinymce. One of the few places I found it explained was here: http://drupal.org/node/149582, when I added the code listed (took away the php opening and closing tags, wouldn't of made sense in the plugin_reg.php) it added a drupalassest check box in the tinymce buttons section, but when checked it doesn't do anything. I also found this article: http://drupal.org/node/204622, which said to move the tinymce files from the assest folder to the tinymce's plugins folder, but that didn't do anything either. So I'm not quite sure what to do.
Comment #6
wmostrey commentedPhilipw, you're posting this on a GHOP Documentation task. There article you're mentioning (http://drupal.org/node/204622) is in fact the issue report where you should post this.
Also note that there are two plugin folders for tinymce:
tinymce/pluginsandtinymce/tinymce/jscripts/tiny_mce/plugins/. You should copy it to the second directory.If you need more help on this, please post it in the correct issue.
Comment #7
aclight commented@wmostrey: I don't quite understand your comment above. philipw is the student (I think) who has claimed this GHOP task, so shouldn't he be posting here if he is having problems with the task?
Comment #8
wmostrey commentedAh my bad, I didn't see it was Philip that claimed it, sorry about that. Thanks for doing this Philip, it is highly appreciated!
The first thing I can come up with is that TinyMCE has 2 plugin directories, of which only one should be used for 3rd party integration (like this one): instead of using
tinymce/plugins, trytinymce/tinymce/jscripts/tiny_mce/plugins/.Let me know if this doesn't solve your issue.
Comment #9
philipw commentedTried moving the drupal asset folder, didn't work. The only thing it changed was I got 2 javascript errors, before I moved it from the first plugin directory I only got one. These are the errors I'm getting:
tinyMCE.importPluginLanguagePack is not a functionfrom file '/sites/all/modules/tinymce/tinymce/jscripts/tiny_mce/plugins/drupalasset/editor_plugin.js'
tinyMCE.getEditorId is not a functionfrom file '/sites/all/modules/asset/tinymce/asset_tinymce_helper.js'
Comment #10
wmostrey commentedSo you have the following:
tinymce/tinymce/jscripts/tiny_mce/plugins/drupalassetdirectorytinymce/plugin_reg.phpwith the following code (at the end of the file, before "return $plugins;"):Correct?
Comment #11
philipw commentedThat is exactly correct.
Also what exactly is supposed to be the parent when I write the handbook pages? Is the last 9 supposed to have the first one as their parent? I see there is already an 'asset' handbook page, but I guess I'm supposed to create a new one since that one belongs to the asset maintainer.
Comment #12
wmostrey commentedThat page is just a placeholder. You can create a new one and I'll replace the placeholder and the link on the asset project once all documentation is done. This page is the parent and all other pages are children of this one parent.
I'd suggest you continue the documentation on the other segments and I'll continue looking why you're running into this bug.
Comment #13
wmostrey commentedIt's really odd the TinyMCE plug-in doesn't work for you. I got confirmation at http://drupal.org/node/204622 that those simple 2 steps are really all that's needed to get it working. Did you try clearing cache for instance?
Comment #14
philipw commentedThanks for the help, I'll try just doing a drupal reinstall and start from scratch and see if that works.
Comment #15
philipw commentedI added the first page: http://drupal.org/node/208258
I have some screen shots that I think would be helpful can I put them in or does someone else have to do it for me. They are attached.
Comment #16
wmostrey commentedThe images look great. Perhaps you could save them in a slightly higher resolution or as .png's. You could also try putting a red circle around the area of importance, especially on the configuration pages because it is not always clear what the important bits are.
Comment #17
aclight commented@philipw: It would probably be easiest for you if you apply to be a documentation maintainer (if you aren't already) by creating such an issue at http://drupal.org/project/issues/documentation. Make sure to include your drupal user id (the number, not the name). Once you have documentation maintainer status, you can upload images to handbook pages and use
<img></img>tags within handbook pages by changing the input format of the node to Documentation.Comment #18
philipw commentedI still can't get tinymce plugin working. I tried a fresh installation, even on a different machine and it still didn't work, so I don't know. What do you think about my new pages:
http://drupal.org/node/209387
http://drupal.org/node/209404
Comment #19
philipw commentedAdded another one:
http://drupal.org/node/210530
Comment #20
wmostrey commentedHey Philip, this is perfect! The screenshots look really great as well, this is exactly what I had in mind. Could you tell me what you do on a fresh install to get asset integration?
Comment #21
philipw commentedFirst I install drupal. Then I install the asset module and the tinymce module. I move those files from the asset folder to the tinymce folder, and also add the lines of code to the plugin_reg.php. Then I go and activate the modules on the Administer>Site building>Modules page. Then I configure Tinymce and select the asset button in its button options. Then I go to create some content and the tinymce bar shows up but not the asset button. Since others say this work I think I might just do up a handbook page as best I can.
P.S. I can't get the asset embed module or the asset youtube module to work either.
Comment #22
philipw commentedI was trying to do panels integration and I ended up with this error after creating a new panel as specified:
and when I try to bring up the view:
Fatal error: Call to undefined function i18n_get_lang() in W:\www\drupal ghop\sites\all\modules\asset\asset_panels.module on line 21Comment #23
wmostrey commentedThanks for bringing this up Philip, I'm fixing the asset_panels error asap.
About the warnings: did you put a correct node id or title in the asset field for the panel, using the autocomplete function?
Comment #24
yched commentedphilipw : is your drupal install in a subfolder of your webroot ?
Maybe your difficulties could be related : http://drupal.org/node/207976
Comment #25
philipw commented@wmostrey: yes I used the autocomplete function, so I know it was right
@yched: no it's not in the root so I'll try the patch or try moving it to the root, thanks
Comment #26
aclight commentedphilipw has indicated that he has finished all of the pages in the ghop task tracker, so I'll set the status as CNR here.
Comment #27
jmlane commentedNot sure if this is the place to comment, but it is related to the Asset documentation.
The page relating to CCK Assets (http://drupal.org/node/209387) doesn't explain how to get the "Download this audio file" link to appear on a node with an asset field. It isn't clear if these links are part of the module, generated automatically for certain file formats, or if they are manual, such as when you pick between embedding an image or just providing a link to it.
Comment #28
wmostrey commentedI'm marking this GHOP task as fixed, thanks a lot for your great work Philip!
Jonathan, the link is automatic. If you are experiencing further issues on this, you can open a new issue for it.
Comment #29
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.