As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
Could we request a feature in the web console that adds an extra column to the files listing to indicate whether a file is public or not? Even better, allow us to easily flip the status of the public flag?
Also, even public files return an expiresAt property always within a day of the current time. Is this safe to ignore for public files?
Great feedback - we'll definitely incorporate this into the roadmap. When it comes time for us to make improvements to the Files interface, would you be up for chatting further? We love getting direct feedback and uses cases from our customers.
As for the expiresAt property, I will look into that to make sure I get you the right answer.
D
Dave
said
over 9 years ago
Okay, some feedback on the expiresAt property. If you are setting the _public flag to true, then you should not see expiresAt being returned. Is it possible you mixed up _acl read permissions with the _public flag?
_acl permissions determine who can query your file metadata. But the _public flag has nothing to do with _acls. Instead, it only determines whether the file's URL is publicly usable, or private (i.e. must be signed). Even if you set the _acls to fully public (any user can read/write), that doesn't change the _public setting.
Let me know if this isn't the case, and you are still seeing the expiresAt property even though the _public flag is true.
O
OhmzTech
said
over 9 years ago
You are right Dave, some of our files weren't being set to public correctly. Thanks for clarifying the expiresAt property.
OhmzTech
Also, even public files return an expiresAt property always within a day of the current time. Is this safe to ignore for public files?