cancel
Showing results for 
Search instead for 
Did you mean: 

problems disabling CIFS

stk137
Champ in-the-making
Champ in-the-making
I want to fully disable CIFS
I added to file-servers-custom.xml
   <config evaluator="string-compare" condition="CIFS Server" replace="true">
      <serverEnable enabled="false"/>
   </config>

However, the CIFS network folder icon/link and the "view in CIFS" link still appear

am I missing something?
12 REPLIES 12

kevinr
Star Contributor
Star Contributor
You can change the default 'edit link' action type from CIFS by adding or updating your web-client-config-custom.xml with the following:

<config>
   <client>
     <edit-link-type>http</edit-link-type>
  </client>
</config>

In this case the default edit link type will be changed from CIFS to HTTP, note webdav could also be used.

FYI To avoid possible confusion, this is unrelated to the original issue I raised.  I wasn't using the CIFS edit link type.

I was refering to the "Open Network Folder Icon" next to the space name and the "View in CIFS" on the details page which appears even though CIFS is disabled.  Edit link types  have no effect on these, and they shouldn't, but disabling CIFS should.

This has been fixed in 2.1Enterprise and merged to HEAD (i.e. a nightly build or SVN). If the CIFS server is disabled, the CIFS link in the web-client now disappears from the main browse screens.

Thanks,

Kevin

stk137
Champ in-the-making
Champ in-the-making
This has been fixed in 2.1Enterprise and merged to HEAD (i.e. a nightly build or SVN). If the CIFS server is disabled, the CIFS link in the web-client now disappears from the main browse screens.

Does the also eliminate the startup error?

Also, I am a little confused on the Enterprise vs. Community releases.  Are these not the same code?  Will there be a community 2.1.1 that is the same as 2.1 Ent?

If different, which are the SDKs built on?

kevinr
Star Contributor
Star Contributor
The code streams diverge at major releases, then all changes (fixes and optimzations) made in the Enterprise code are merged back into the community code line. Only Enterprise customers get the minor X.Y.Z versions as a specific release. All code ends up in the community HEAD codeline - just not as controlled as the Enterprise codelines.

Thanks,

Kevin