TYPO3 7.6 - Pagebrowser missing in content element “Special Menus”
I am using TYPO3 7.6. I have set up a usergroup which can insert the content element "Special Menus". This group has access to a certain branch of the page tree and also has the right to see and edit every page.
Now a member of this group can insert the content element "Special Menus",
but the page browser to select the pages (Selected Pages) for the menue is missing. What am I doing wrong?
menu typo3 backend
asked Nov 20 '18 at 10:06
RalfRalf
164
add a comment |
I am using TYPO3 7.6. I have set up a usergroup which can insert the content element "Special Menus". This group has access to a certain branch of the page tree and also has the right to see and edit every page.
Now a member of this group can insert the content element "Special Menus",
but the page browser to select the pages (Selected Pages) for the menue is missing. What am I doing wrong?
menu typo3 backend
asked Nov 20 '18 at 10:06
RalfRalf
164
add a comment |
I am using TYPO3 7.6. I have set up a usergroup which can insert the content element "Special Menus". This group has access to a certain branch of the page tree and also has the right to see and edit every page.
Now a member of this group can insert the content element "Special Menus",
but the page browser to select the pages (Selected Pages) for the menue is missing. What am I doing wrong?
menu typo3 backend
asked Nov 20 '18 at 10:06
RalfRalf
164
I am using TYPO3 7.6. I have set up a usergroup which can insert the content element "Special Menus". This group has access to a certain branch of the page tree and also has the right to see and edit every page.
Now a member of this group can insert the content element "Special Menus",
but the page browser to select the pages (Selected Pages) for the menue is missing. What am I doing wrong?
menu typo3 backend
menu typo3 backend
asked Nov 20 '18 at 10:06
RalfRalf
164
asked Nov 20 '18 at 10:06
RalfRalf
164
asked Nov 20 '18 at 10:06
RalfRalf
164
asked Nov 20 '18 at 10:06
RalfRalf
164
asked Nov 20 '18 at 10:06
RalfRalf
164
164
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
A short introduction:
The possibility to configure editing rights in TYPO3 are quite comprehensive. Most of it can be set in the Backend Usergroups (or single Backend users).
On the bottom of the tab Access Lists (in a Backend usergroup record), you can find the section Page Content: Type. Depending on the Install Tool setting [BE][explicitADmode], you have to allow or deny content elements for editors here.
I understand that this was already done in your case.
Your solution:
Above the mentioned section is a larger section with Allowed excludefields. Browse the panel Page content for the following setting:
Startingpoint (pages)
This setting has to be checked. It enables this field for non-admin backend users. It's the same for any other of these listed excludefields.
If enabling this field does not render your missing field, there could be another issue. With TSconfig it's also possible to disable backend fields, like that:
TCEFORM.tt_content.pages.disabled = 1
This configuration would hide the field for all backend users, even administrators (if set globally).
answered Nov 20 '18 at 18:31
sebklnsebkln
6261514
Thanks Sebastian, this was the solution.
– Ralf
Nov 21 '18 at 12:37
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390581%2ftypo3-7-6-pagebrowser-missing-in-content-element-special-menus%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
A short introduction:
The possibility to configure editing rights in TYPO3 are quite comprehensive. Most of it can be set in the Backend Usergroups (or single Backend users).
On the bottom of the tab Access Lists (in a Backend usergroup record), you can find the section Page Content: Type. Depending on the Install Tool setting [BE][explicitADmode], you have to allow or deny content elements for editors here.
I understand that this was already done in your case.
Your solution:
Above the mentioned section is a larger section with Allowed excludefields. Browse the panel Page content for the following setting:
Startingpoint (pages)
This setting has to be checked. It enables this field for non-admin backend users. It's the same for any other of these listed excludefields.
If enabling this field does not render your missing field, there could be another issue. With TSconfig it's also possible to disable backend fields, like that:
TCEFORM.tt_content.pages.disabled = 1
This configuration would hide the field for all backend users, even administrators (if set globally).
answered Nov 20 '18 at 18:31
sebklnsebkln
6261514
Thanks Sebastian, this was the solution.
– Ralf
Nov 21 '18 at 12:37
add a comment |
A short introduction:
The possibility to configure editing rights in TYPO3 are quite comprehensive. Most of it can be set in the Backend Usergroups (or single Backend users).
On the bottom of the tab Access Lists (in a Backend usergroup record), you can find the section Page Content: Type. Depending on the Install Tool setting [BE][explicitADmode], you have to allow or deny content elements for editors here.
I understand that this was already done in your case.
Your solution:
Above the mentioned section is a larger section with Allowed excludefields. Browse the panel Page content for the following setting:
Startingpoint (pages)
This setting has to be checked. It enables this field for non-admin backend users. It's the same for any other of these listed excludefields.
If enabling this field does not render your missing field, there could be another issue. With TSconfig it's also possible to disable backend fields, like that:
TCEFORM.tt_content.pages.disabled = 1
This configuration would hide the field for all backend users, even administrators (if set globally).
answered Nov 20 '18 at 18:31
sebklnsebkln
6261514
Thanks Sebastian, this was the solution.
– Ralf
Nov 21 '18 at 12:37
add a comment |
A short introduction:
The possibility to configure editing rights in TYPO3 are quite comprehensive. Most of it can be set in the Backend Usergroups (or single Backend users).
On the bottom of the tab Access Lists (in a Backend usergroup record), you can find the section Page Content: Type. Depending on the Install Tool setting [BE][explicitADmode], you have to allow or deny content elements for editors here.
I understand that this was already done in your case.
Your solution:
Above the mentioned section is a larger section with Allowed excludefields. Browse the panel Page content for the following setting:
Startingpoint (pages)
This setting has to be checked. It enables this field for non-admin backend users. It's the same for any other of these listed excludefields.
If enabling this field does not render your missing field, there could be another issue. With TSconfig it's also possible to disable backend fields, like that:
TCEFORM.tt_content.pages.disabled = 1
This configuration would hide the field for all backend users, even administrators (if set globally).
answered Nov 20 '18 at 18:31
sebklnsebkln
6261514
A short introduction:
The possibility to configure editing rights in TYPO3 are quite comprehensive. Most of it can be set in the Backend Usergroups (or single Backend users).
On the bottom of the tab Access Lists (in a Backend usergroup record), you can find the section Page Content: Type. Depending on the Install Tool setting [BE][explicitADmode], you have to allow or deny content elements for editors here.
I understand that this was already done in your case.
Your solution:
Above the mentioned section is a larger section with Allowed excludefields. Browse the panel Page content for the following setting:
Startingpoint (pages)
This setting has to be checked. It enables this field for non-admin backend users. It's the same for any other of these listed excludefields.
If enabling this field does not render your missing field, there could be another issue. With TSconfig it's also possible to disable backend fields, like that:
TCEFORM.tt_content.pages.disabled = 1
This configuration would hide the field for all backend users, even administrators (if set globally).
answered Nov 20 '18 at 18:31
sebklnsebkln
6261514
answered Nov 20 '18 at 18:31
sebklnsebkln
6261514
answered Nov 20 '18 at 18:31
sebklnsebkln
6261514
answered Nov 20 '18 at 18:31
sebklnsebkln
6261514
6261514
Thanks Sebastian, this was the solution.
– Ralf
Nov 21 '18 at 12:37
add a comment |
Thanks Sebastian, this was the solution.
– Ralf
Nov 21 '18 at 12:37
Thanks Sebastian, this was the solution.
– Ralf
Nov 21 '18 at 12:37
Thanks Sebastian, this was the solution.
– Ralf
Nov 21 '18 at 12:37
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390581%2ftypo3-7-6-pagebrowser-missing-in-content-element-special-menus%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
