I created a collection type in the Strapi admin panel and now I want to delete it, but I don't see an option anywhere in the admin panel to do so. I must be missing something obvious, right?
You can do it in Content Type Builder, steps:
Enter Admin panel
Content Type Builder
Click a collection type
Edit (small pen icon next to the name)
Delete
Confirm
Official docs - Deleting content-types
Another way is to use the admin API, make a DELETE call to:
/content-type-builder/content-types/:uid
To use the API you must have permissions enabled for a role under Roles & Permissions
Endpoints docs
At the time of this update Strapi added a caution (Feb 2022):
Deleting a content-type only deletes what was created and available from the Content-type Builder ... All the data ... is however kept in the database.
You need to start the server with npm run develop or yarn run develop
If you started the server with npm run start or yarn run start you will not see these options.
Related
I try to use the PermissionManager (I used UserManager previously). The installation seems to work fine. When I manually add entries to "model_has_permission" and "model_has_role" in the database, the changes are reflected in the UI. But when editing the user I have no options to assign roles and/or permissions like it is visible here:
The installation did not report any errors. What could be wrong or missing?
We have been using old sentry (like 6.*)
We are trying to use the latest onpremise sentry with docker
We don't care about old data, starting fresh is fine.
When I go to the setting page for client-dsn, it has our server's domain name set.
Where did the docker pick this up? and how can I change it?
As far as I have seen th FQDN is taken automatically by Sentry. When doing the first login you are able to set the Root name and there you can change it.
Edit-21.07.2020: As I currently need to do some digging i came across the function:
sentry config set system.url-prefix
or you can set it inside these files:
/etc/sentry/sentry.conf.py
/etc/sentry/config.yml
The below command is deprecated now,
sentry config set system.url-prefix
The better option to edit vim ~/.sentry/config.yml.
Add the below line at the end of vim ~/.sentry/config.yml & restart the sentry.
system.url-prefix: 'https://sentry.example.com'
I've upgraded a 1.5 Joomla to actual verison 3.9.x and I have now a special permission problem.
Users are categorized by standard groups, coming with Joomla, so there are 2 super users and some "Managers". Super users usually create articles, managers are finalizing und publishing them.
So, in System -> Global Configuration -> Articles -> Permissions is set to "Edit - Allow" and "Edit state - allow", which means that on every new created article managers can edit the articles.
Now, the super user clicks on Content -> Articles -> New and check that (not-yet-saved) permission tab. The "Calculated permission" shows a green "Allowed" state in "Manager" tab - as set in the global configuration.
Now, the article will be saved, and re-opened, now the permission tab in manager shows RED "Forbidden" although its saved with explicit "Allowed".
When changing and saving the corrected state again (on the existing article), the permissions are set correctly and the managers can edit the article.
In the actual state, the super user must create an article, close and re-open it and set the right permissions to make it available to other backend users.
How can I fix that?
My guess:
On the first save, the permissions are not set correctly, so Joomla is using "fallback permissions" which means that just super users can edit that article.
Edit:
Here's an interesting comment in joomla core source code, where permissions are saved:
#to do: incorrect info When creating a new item (not saving) it uses the calculated permissions from the component (item <-> component <-> global config).
But if we have a section too (item <-> section(s) <-> component <-> global config) this is not correct.
Also, currently it uses the component permission, but should use the calculated permissions for achild of the component/section.
Try to open and save your superusers. This might at least correct any issue with the actual user, that arised after your wishful upgrade attempt :)
If there are many issues after your upgrade, and your web site is not huge, i would consider doing a fresh install of the latest Joomla, and importing data in a more manual /semi manual way. Else I guess you'll be having issues for a while...
I'm trying to find a list of users for a specific project (by projectKey) who possess the issueadmin permission. I've found a documented API that gets me pretty close:
api/permissions/search_project_permissions
but the response that I get back only has summary information: counts of groups/users for each permission type.
search_project_permissions response
Does anybody know if there's a way to get to the login details for the users?
There is an "internal" web service (meaning it could change without notice!) that does this. You'll use it like so:
http://myserver.myco.com/api/permissions/users?projectId=[project guid]&permission=issueadmin
In Web API interface use the "Show Internal API" checkbox at the top of the left column to see it.
just noticed in Sonarqube v6.7 it works as follows:
https://sonarqube.dhl.com/api/permissions/users?projectKey=<KEY>
https://sonarqube.dhl.com/api/permissions/users?projectKey=<KEY>&permission=issueadmin
https://sonarqube.dhl.com/api/permissions/users?projectKey=<KEY>&permission=issueadmin&permission=scan
All possible permissions are (reg. Browse, See Source Code, Administer Issues, Administer and Execute Analysis):
admin
codeviewer
issueadmin
scan
user
I use the following command to get the latest version of a branch for a specific user (not the one running the process):
tf get $/MyProject/Development /version:WmyPC;otherUser /login:otherUser,otherPassword
Bt I keep getting:
The operation cannot be completed because the user (otherUser) does
not have one or more required permissions (Use) for workspace...
Any ideas?
By default, when you create a workspace it is a 'Private Workspace' - this means that the person who created it is the only person who can "use" it (which is why you get that specific error message).
What you will want to do is change the workspace to a 'Public Workspace' - this updates the permissions and allows multiple people to use the same workspace, but using their own credentials.
For more information, see my blog post TFS2010: Public Workspaces.
You are trying to get the files on your local machine with the credentials of someone else. It is not executing the TF under other credentials.
In other words, you still use the workspace mapping of yourself.
You need to use the RUNAS command to fullfil your task: http://social.msdn.microsoft.com/Forums/en-US/tfsversioncontrol/thread/20b6f678-4657-4b14-a114-5eeb232934e2/