Search for sites, node name is "/Sites"

[Alberto Muñoz Fuertes]

Hi,

On an Spanish OS Alfresco installation, Sites Folder is called "Sitios" on the repository. So, "Sites" default value won't works for searching.

So in "SitesListViewController.m" we found a constant called "kSitesFolderLocation" set to "/Sites" and is not localized, because it's searching for "cm:name". This constant it's used in function "searchBarSearchButtonClicked"

[Mike Hatfield]

Hi Alberto

My understanding of CMIS is that it uses the cmis:path property rather than cmis:name for path queries for this very reason. Just to check, could you let me know what that property is reported as in a CMIS response for your Sitios folder please? It should look something like this:

<cmis:propertyString propertyDefinitionId="cmis:path" displayName="Path" localName="path" queryName="cmis:path">
    <cmis:value>/Sites</cmis:value>
</cmis:propertyString>

Thanks,
Mike

[Alberto Muñoz Fuertes]

Hi Mike,
CMIS response:

Response is "/Sitios" instead of "/Sites"

Thanks in advance,
Alberto

[Mike Hatfield]

Thanks Alberto

I think that's a bug in the Alfresco CMIS implementation, which I'll raise here. Could you let me know which version you're running please?

In the meantime I'll see what we can do to workaround the issue with the iOS and Android apps; it looks like we'll have to enumerate by cmis:objectTypeId instead.

Thanks,
Mike

[Alberto Muñoz Fuertes]

Hi Mike,
Alfresco version 5.0.d. Let me check, but Android app is working fine.

Thanks,
Alberto

[Mike Hatfield]

Thanks Alberto

The Android app doesn't support cross-site search, so there won't be the same issue seen with that version.

Mike

[Mike Hatfield]

Having gone through the CMIS spec just now, it seems the path segments don't need to be localised at all and repository vendors may choose to use cmis:name, as is the case with Alfresco. Therefore this doesn't seem to be a repository bug.

CMIS paths

I'll try to get this addressed in the iOS 2.2 app.

Thanks,
Mike

[Alberto Muñoz Fuertes]

Thank you very much Mike. It's not a critical bug for us, just trace and update iOS code :)

Kind regards,
Alberto