Tell us what you are trying to do?
Trying to create a new content template.
Is there any documentation that you are following?
Is there a similar example that we can see?
What is the link to your site?
Brand new site with types and blocks.
When I try to create a new content template for a custom post type, I'm getting an error:
This is the URL that I'm going to when clicking the create content template link:
wp-admin/admin.php?page=ct-creator&action=create&title=Content+template+for+Projects&usage%5Bpost_archives%5D%5B0%5D=project
The page displays this error:
"You have no permission to access this page."
The code shows:
<div class="wpv-setting-container"><p class="toolset-alert toolset-alert-error">You have no permission to access this page.</p></div>
... so this error is definitely coming from Toolset.
I am an administrator. Any idea on how to resolve this error?
I had disabled and deleted ALL plugins except for types and blocks before posting my issue.
I also tried disabling blocks and installing Views -- same result, same error.
This could be a server issue, however I was able to get onto the site.
There is another way you can create the content template. Go to Toolset->Dashboard and from there you can click the create template option on your CPT.
I've already tested this to ensure that it works and it does on my end.
What kind of server issue would cause this error to be thrown by Types? It seems like this would have something to do with Types "User Capabilities" code.
Using your workaround, I was able to click on create template, but then I clicked on use classic editor for template, and now I get the same permission error in the dashboard.
Also, there is no way to create Archive templates from the dashboard, so your solution is not a complete fix.
EDIT: I'm still troubleshooting this, and here's another clue: I am not able to turn on Views debug mode... "Saving Failed. Please reload the page and try again."
Update: I am starting over from scratch. I suspect there may have been an issue with the database caused by a previously installed (but INACTIVE and uninstalled) plugin. I will update this thread when I find out what caused the problem.
Shane,
After re-installing all of my plugins one by one and extensive testing, I have not been able to recreate the issue. I guess we can close this one. I'll be sure to re-open if it re-surfaces in the future.