edtalla / alfresco-bulk-filesystem-import

Automatically exported from code.google.com/p/alfresco-bulk-filesystem-import
GNU Lesser General Public License v3.0
0 stars 0 forks source link

The replacement of "Company Home" to site name is not working perfectly #143

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Open /alfresco/service/bulk/import/filesystem
2. Fill Import directory source
3. Type anything on target space

What is the expected output? What do you see instead?
Its displaying <site name> instead of "Company Home" like in the previous 
version and cause exception due to the <site name> space is not exist. I guess 
the script not replace it back to default "Company Home" during query process.

What version of the product are you using? On what operating system?
Alfresco Enterprise v4.0.2 (.27 @build-number@)

Please provide any additional information below.
To temporarily solve this issue, I have made changes in the file: 
ajaxspace.get.js:

function buildFullPath(theNode)
{
  if (theNode)
  {
    if (theNode.equals(companyhome))  // We hit Company Home, return it
    {
      return("/Company Home");
    }
    else if (theNode.parent)  // We're at a normal folder node, recurse
    {
      var parentPath = buildFullPath(theNode.parent);
      return(parentPath + "/" + theNode.name);
    }
  }

  return(null);  // Shouldn't ever get here, but you never know...
} 

modification on: return("/Company Home");

Original issue reported on code.google.com by iman.suh...@gmail.com on 5 Dec 2013 at 1:04

GoogleCodeExporter commented 8 years ago
I followed your reproduction steps on both 4.2.0 and 4.0.2 but was unable to 
reproduce the issue.  Can you provide more specific reproduction steps, along 
with details on your environment (Community vs Enterprise, OS, app server, 
etc.)?

Original comment by pmo...@gmail.com on 7 Dec 2013 at 12:49

GoogleCodeExporter commented 8 years ago
Also whether you're using Lucene or SOLR.  Both of my tested versions were 
configured with SOLR, and it's possible the issue you're describing only shows 
up with Lucene configured.

Original comment by pmo...@gmail.com on 7 Dec 2013 at 12:51