nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Alfresco Share Document Library button action

sanoojkt

how the "New Folder" button action is triggered within the document library of Alfreso share
and which is the exact action script file?

Find more posts tagged with

Comments

mikeh

"New Folder" is implemented in toolbar.js

Thanks,
Mike

sanoojkt

Yes, it's correct. The action script is there.

The New Folder button definition is given in toolbar.lib.ftl file
as shown below.

<div class="hideable toolbar-hidden DocListTree">
<div class="new-folder"><button id="${el}-newFolder-button" name="newFolder">${msg("button.new-folder")}</button></div>

But it doesn't contain the action call to the script method.

Then how it's happening?

mikeh

That's the Freemarker template, whereas I pointed you to the toolbar.js JavaScript file.

// New Folder button: user needs "create" access
this.widgets.newFolder = Alfresco.util.createYUIButton(this, "newFolder-button", this.onNewFolder,
{
   disabled: true,
   value: "CreateChildren"
});
‍‍‍‍‍‍‍

Thanks,
Mike

sanoojkt

The javascript new folder action is called based on the id
"${el}-newFolder-button" specified in the ftl???

davidcognite

Yes, that's correct. If the full element id isn't explicitly passed in then the createYUIButton method constructs it by joining the scope's id element and the button name together.

In the case of the new folder button it will construct it from:

this.id + "-" + "newFolder-button"‍

('this' is the first parameter in the createYUIButton method call).

which is exactly the same as the form used in the FTL:

${el}-newFolder-button‍

sanoojkt

I have created a Button "Create" in Document Library as shown below.

toolbar.get.html.ftl

<div class="separator hideable DocListTree"> </div>
<div class="file-create hideable DocListTree"><button id="${args.htmlid}-fileCreate-button" name="fileCreate">${msg("button.create")}</button></div>‍‍

—————————————————————————————————————–
toolbar.css

.toolbar .file-create button
{
background: transparent url(images/create-16.png) no-repeat 12px 4px;
padding-left: 32px;
}
.toolbar .file-create .yui-button-disabled button
{
background-image: url(images/create-disabled-16.png);
}‍‍‍‍‍‍‍‍‍

———————————————————————————————————————-
toolbar.js

added a line to instantiate the YUI button named in the toolbar template in the 'onReady' YUI event listener

   // File Create button: user needs  "create" access
   this.widgets.fileCreate = Alfresco.util.createYUIButton(this, "fileCreate-button", this.onFileCreate,
   {
      disabled: true,
      value: "create"
   });
   // done added
‍‍‍‍‍‍‍‍‍

The event is also added in toolbar.js

 /**
 * File Create click handler
 *
 * @method onFileCreate
 * @param e {object} DomEvent
 * @param p_obj {object} Object passed back from addListener method
 */
onFileCreate: function DLTB_onFileCreate(e, p_obj)
{
/*
   var url = YAHOO.lang.substitute(Alfresco.constants.URL_CONTEXT + "page/site/{site}/blog-postedit?container={container}",
   {
      site: this.options.siteId,
      container: this.options.containerId
   });
   window.location = url;
   Event.preventDefault(e);
*/
   var notimpTitle = this._msg("title.notimp");
   var notimpMsg = this._msg("message.notimp", "Create Content");

   Alfresco.util.PopupManager.displayPrompt(
   {
      title: notimpTitle,
      text: Alfresco.util.decodeHTML(notimpMsg),
      noEscape: true,
      modal: true,
      buttons: [
      {
         text: this._msg("button.cancel"),
         handler: function DLTB_onActionDelete_cancel()
         {
            this.destroy();
         }
      }]
   });

},
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

——————————————————————————————————
toobar.get.properties

button.create=Create
title.notimp=Not Implemented
message.notimp = Feature {0} is not implemented yet.‍‍‍‍

———————————————————————————————————

Here the Button is displaying in Document Library.
But can't trigger the button action.
Any other configurations or modifications is needed for triggering the button action???

davidcognite

   // File Create button: user needs  "create" access
   this.widgets.fileCreate = Alfresco.util.createYUIButton(this, "fileCreate-button", this.onFileCreate,
   {
      disabled: true,
      value: "create"
   });
   // done added
‍‍‍‍‍‍‍‍‍

Try using "CreateChildren" in place of "create" for the permission value.

sanoojkt

It's tried. Not working…….

davidcognite

Then you're going to need to step through it with a Javascript debugger.

Three likely scenarios (off the top of my head) are that the button isn't being correctly created, the target function isn't found (check the context of "this") or that the target function is hitting an error: set a break point just after this.widgets.fileCreate is assigned & check the value isn't null - if it is, the problem is that the createYUIButton wrapper method hit a problem. You'll also want to add a break point immediately inside the onFileCreate function to double check that it is being called & then step through it to see if it hits any issues.

tapan_d_thakkar

Hi,

i have created a custom button in my toolbar.
its working fine, but it appears in all folders.

I want to restrict this button for some particular folders only.
Say if user is in "Product" then and then this button should be visible else not.

can you suggest me any way/pointer for doing this ?

Thanks.

mikeh

You'd need to add your logic into the onFilterChanged() function in toolbar.js (or override it and then call the overridden original).

Check that

this.currentFilter.filterId == "path"‍

and then inspect the new path in the

this.currentFilter.filterData‍

variable. You'd then enable or disable the button as appropriate.

Thanks,
Mike

warrior1603

Hello tapan.d.thakkar,
can you please tell me how you made it work, because I've the same problem like sanoojkt;
the button is not clickable and does'nt trigger the appropriate action.
thanks in advance