Hi
I appreciate this thread is quite old now and relates to a previous version
of Arches but I'd be interested to know whether anyone managed to implement
this.
Our dataset also has a number of resources that are not intended for public
view - this is controlled by a boolean node.
It was
Hi Mike,
I'm not sure if this answers your question, but we're implementing instance
permissions in v5.1.
Instance permissions allow you to define access (No Access, Read, Create,
Update, Delete) on model instances for groups or individual accounts. For
example: imagine setting "No Access"
Hi Mike,
We are currently in the process of implementing this feature. It will be
available in Arches 5.1.
Cheers,
Cyrus
On Mon, May 4, 2020 at 2:38 AM Mike Arrowsmith wrote:
> Hi
>
> I appreciate this thread is quite old now and relates to a previous
> version of Arches but I'd be
I need help with a headscratcher here, please. My 4.4.2 version of Arches
was fine until I attempted to use ufw to make some port changes. This,
apparently started some processes that interfered with arches loading. The
message in the Apache log was that the import arches statement in
Hi Cyrus,
Thank you so much for your help. I did clear the cache but unfortunately,
it didn't help.
The edit is mainly on core arches then carried out to the project through
*collectstatic
*command. I did trace it and found the same edit in the project files
after.
Thank you again,
Best
