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.

'Start Discussion' missing

steel

The "Start Discussion" content action is missing. I am running 1.2 which was upgraded from 1.0 RC2 last month. Everything else is working find including the Create forum, but I cannot get the "Start Discussion" link to appear. The browse.jsp file is identical.

I am looking through all the config files to see if there might be a config error.

What is most likely the culprit for this?

thanks.

Find more posts tagged with

Comments

gavinc

It's most likely to be a permissions problem. The user needs to have CreateChildren permission on the node you are starting the discussion for.

steel

Correction. The original was 1.2 RC1 and now upgraded to 1.2. The permissionDefinition.xml file is exactly the same as the new one. The the "createchildren" permission set specifically somewhere? The uses are able to create home spaces and read/write just fine. Even the system admin login is unable to start discussion.

thanks.

gavinc

Hmmm, the only other reason why this wouldn't show up is if the discussable aspect is already applied to the node or if the node is locked.

If a discussion has already been started on the node the "Discuss" option should appear instead, this will be a small icon under the node title.

Is this what is happening or have both options disappeared?

steel

Hmmm, the only other reason why this wouldn't show up is if the discussable aspect is already applied to the node or if the node is locked.

If a discussion has already been started on the node the "Discuss" option should appear instead, this will be a small icon under the node title.

Is this what is happening or have both options disappeared?

Both icons have disappeared. Not sure why. Does the discussable aspect need to be applied to new nodes?

gavinc

The discussable aspect is applied once you click the "Start Discussion" link and post the inital message.

Does the node in question have the discussable aspect applied? You can browse to the node via the node browser (in the admin console). This will list the aspects applied to the node.

steel

The discussable aspect is applied once you click the "Start Discussion" link and post the inital message.

Does the node in question have the discussable aspect applied? You can browse to the node via the node browser (in the admin console). This will list the aspects applied to the node.

The discussable aspect is not applied to the node. This behavior is really strange.

Question:

<a:booleanEvaluator value="#{r.beingDiscussed == false && r.locked == false}">‍

Where is the "beingDiscussed" property resolver defined? Maybe its implementation has not been updated to the latest version in my deployment.

thanks.

gavinc

Hi,

If i remember rightly it is added in ForumsBean when the list of nodes is built up (in getNodes()).

There should be a custom resolver in ForumsBean that implements the logic.

This is indeed strange, if there is no aspect the option should appear. We also changed the config files around a little in between RC1 and the final release, it may also be worth checking you don't have any old config files still in the classpath.

steel

I'll double check my config files again. The forumsbean is identical to the release one.

steel

This issue has been more of an annoyance than a problem. But I finally found the culprit.

the problems was in web-client-config.xml.

I was missing:

<config evaluator="string-compare" condition="Node Event Listeners">
        <!– Managed beans that wish to be notified of Node events from the BrowseBean –>
        <node-event-listeners>
            <listener>ForumsBean</listener>
        </node-event-listeners>
    </config>‍‍‍‍‍‍

Now to move on with life.

kevinr

Fortunately all this has changed for 1.3 - all actions are now defined externally in config files. This makes for easier customisation/extension and should help with issues like these.

http://wiki.alfresco.com/wiki/Externalised_Client_Actions

Thanks,

Kevin

turgayz

Kevin,
I think that this is excellent work. Modifying the GUI of a software may be considered the most difficult part which can be customized, without touching to the original code. Making this possible in a web project is really excellent job. Also, the wiki entry you are pointing to is very well written. I don't have the time to check it on some actions of my own now, but I'll do soon. Looking forward to the 1.3 release to see all these new additions in action.

Congrats to you and all the Alfresco engineers