We are facing a problem with regard to associating documents in Alfresco.
The case:
folder A, has a rule R that triggers only when content is created
a document A is created in folder A and triggers the rule correctly
the document A is being updated and a document B (from folder B) is associated to A ussing a custom aspect/association
document B triggers the folder's A rule!
Folder A and B are completely irrelevant.
Any suggestions?
Associations are stored as children of the file's node.
So if the rule is set to trigger on subfolders, the file with the associations will be handled as a folder and the associated files as its containing files.
Simple solution: uncheck the trigger on subfolders option in the rule's settings
Related
I want to model data in firestore to get items in directories shared by several users (folders are secured with security rules).
My current model is as follows:
/folders/{folder}/folders/{subfolder}
/folders/{folder}/items/{item}
/folders/{folder}/folders/{subfolder}/items/{item}
A user can access several folders and if he accesses the root folder he can also access the subfolders. He can also access subfolders (if he has permission) and his access to the root folder is restricted.
The idea is that the system can list all the items that the user can access.
Is there a way without having to make a query for each folder?
If I make a query for each folder I would have a query for each root and for each subfolder. It would be many queries
Duplicating the access roles of the folders in the items could be an option but with a big problem when the permissions are modified
The directory can only have up to two depth levels (root and
subfolders).
You could have a document per user where you can write every folder id the user can access. Then you could query only these folders.
And if you have a lot of events the users can access i would recommend to show a folder structure to the user like in a file system. So you could save a lot of unnecessary reads for documents the user does not need.
My requirement is to create shortcut of one folder or document into another folder. For example lets say I have a folder called A and in this folder I have many documents. Now I want to create shortcut of this folder into another folder name B. So basically I don't want to store same content in folder B, it's contains link or reference of folder A. Whatever change made in folder A, it has to be reflected to folder B also. So any one please help me how to do it alfresco using apache chemistry.
I'm facing a problem, and don't know if anybody has solved this issue.
I'm using Tridion webdav (Tridion 2011 SP1 HR1) to insert structured content (folders + binary files) into a publication.
All goes well when the folder doesn't exist, but if the folder exist, then an error appear:
You do not have permission to access this Web Folder location
Watching the log files, the problem is that Tridion tries to create a new folder when I drag & drop an existing folder, and rename to the folder title, giving an error:
Name must be unique for items of type: Folder/Virtual Folder within this Folder and its BluePrint context.
I tried using Events to avoid saving the folder when it exists (throwing an exception in the initiated phase), but the permission error appears when updating the content inside the folder.
Has anyone tried to do something alike?
Has anyone any sugestion I can try?
Thank you all in advance.
This has nothing to do with Tridion as you are using Windows Explorer to access WebDAV, so if anything it's the Explorer who is to blame for sending wrong requests, but if you will take a look at WebDAV sprcification here: http://www.webdav.org/specs/rfc4918.html, you can see all the possible calls under chapter 9.
Tridion Folders are treated as collections, so there's a MKCOL call to create a folder, but if you will check 9.7.2 PUT for Collections, you will see:
9.7.2 PUT for Collections
This specification does not define the behavior of the PUT method for existing collections. A PUT > request to an existing collection MAY be treated as an error (405 Method Not Allowed).
The MKCOL method is defined to create collections.
So there's no way to update existing folders, it's create and upload contents, indeed.
You can also check this article if you are interested in WebDAV protocol: http://amarchuk.blogspot.nl/2011/10/heres-c-webdav-client-that-works-with.html
So let's say I have the following setup in Google Reader
Folder One
Engadget
Gizmodo
Folder Two
Engadget
webOSroundup
Using the Google Reader API, I would like to remove engadget from only Folder One...leaving Folder Two untouched.
I know how to pull engadget out of Folder One and leave him ungrouped, but if I unsubscribe it takes it out of both folders.
Any ideas?
To remove a subscription from a folder you'll need to send a POST request to /reader/api/0/subscription/edit with the parameters:
s=feed/http://www.engadget.com/rss.xml: the feed stream ID
ac=edit: the action type (other possible values are subscribe and unsubscribe)
r=user/-/label/Folder One: the folder you wish to remove it from (you can use the a parameter to add it to a folder; you can repeat either one more than once to add/remove it from multiple folders)
T=token: the usual action token used for all state-changing requests
Click on the down-arrow next to Engadget (in either Folder One or Folder Two). Uncheck the option for Folder One.
Alternative: Under the Manage subscriptions >> you can find your subscriptions and remove Folder One from the Engadget folders by clicking on the Change Folders... drop-down.
I used "touch" on a file, updating the file's timestamp but the parent directory's timestamp did not change. However, (as expected) when I created a new file within the parent directory, the directory's timestamp did change.
What criteria do UNIX-like operating systems (specifically AIX) use to determine when to update the timestamp of a directory?
The timestamp is updated when the data that represents the directory changes. A change in a subdirectory of directory D does not change anything in the representation of D because D only points to the subdirectory, not to what's inside it. On the other hand, creating a file in D changes the block of data on disk that represents D.
A directory's timestamp is changed when the Directory itself is changed. The directory contains, among other things, a list of the inodes of the files in the directory so when you change the content of the directory by adding or removing files then the Directories timestamp will be updated.
You can use the stat command to find the modified time, creation time etc of a file/directory.
Refer to https://linux.die.net/man/2/stat
The article states:
st_mtime of a directory is changed by the creation or deletion of files in that directory. The st_mtime field is not changed for changes in owner, group, hard link count, or mode.
A Directory is considered as changed when there is any Addition or Deletion of File/Directory inside it. If existing Files/Directories are just getting update than Parent Directory timestamp will not change.