Bug #43676
closedFrontend editing (feedit) does not work
100%
Description
- Extension feedit is loaded
- admPanel is activated
- Checkbox to show edit-icons (pencils) is checked and reloaded page with that option
But no edit-icons show up in the content.
I also checked that it's not just a problem with fluid-templating or so. Happens for me with a plain "page.10 < styles.content.get" for the frontend.
Updated by Stefan Neufeind almost 12 years ago
Heard that it seems to work fine for others. Weird :-(
Updated by Chris topher almost 12 years ago
I have the same problem. In my case I have not set the options to activate the edit icons with the mouse (by clicking in the admin panel), but I have set them in the TypoScript Template directly.
In this installation I also added a custom edit panel on each page, which allows to add a new element as topmost element on the page. This edit panel also is not displayed.
It nearly looks like the FE does not recognize that I am logged in in the BE...
Updated by Stefan Neufeind almost 12 years ago
I've also enabled that functionality through UserTS, yes.
The BE-login seems to be recognised (for me) since when you hide that page and reload it you get a "preview"-box in the upper right corner, indicating TYPO3 knows you are a BE-user.
Updated by Gerrit Code Review almost 12 years ago
- Status changed from New to Under Review
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/17001
Updated by Gerrit Code Review almost 12 years ago
Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/17001
Updated by Paul A. Auwehla almost 12 years ago
I applied the two lines of code from the above Under Review #17001.
No change. No feedit icons.
The extension feedit is installed.
But there are no edit-icons in the FrontEnd.
The AdminPanel itself is visible.
But neither
checking "Display edit icons" nor
checking "Display edit panels"
has any effect.
I propose to use a fresh "government package" for testing.
Because in my opinion this is a core question in the new typo3.
Without these things working Neos still is beta.
Updated by Stefan Neufeind almost 12 years ago
Please make sure to properly clear caches. I think deleting the things in typo3temp/Cache/ should help you.
And since you mentioned Neos: This is not about Neos.
Updated by Bernhard Eckl almost 12 years ago
Same problem here. In V 6.0 the edit icons do not appear.
Updated by Bernhard Eckl almost 12 years ago
Stefan Neufeind wrote:
Heard that it seems to work fine for others. Weird :-(
Who got it working and how to get it to work? I never had problems activating feediting, but now in V 6.0.
Updated by Stefan Neufeind almost 12 years ago
Please try the patch which is under review and comment.
https://review.typo3.org/17001
Best would be a comment inside the review-system if possible for you.
Updated by Heinz Scheungrab almost 12 years ago
I had the same problem. I tried the patch > Now it work's fine
Thank you
Updated by Gerrit Code Review almost 12 years ago
Patch set 1 for branch TYPO3_6-0 has been pushed to the review server.
It is available at https://review.typo3.org/17481
Updated by Stefan Neufeind almost 12 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 719f9fec9b95bbf06870b33a49fd171e3b141bb6.
Updated by Stig Kjeldsen almost 12 years ago
Does anyone knows if the problems occurs in TYPO3 4.5.21?
I have the same problems with no edit-icons showed in the content.
AdmPanel is showed, ext. feedit is loaded, config.admPanel=1 is set in TS etc., but no edit-icons for non-admins.
I'm using TemplaVoila 1.7
I usually don't have problems with feedit
Updated by Stefan Neufeind almost 12 years ago
I didn't experience it on 4.5.x yet.
The patch for this issue here definitely only targeted changes that went into TYPO3 for 6.0+. So I expect you must face some other issue, unfortunately.
Can you replicate it on a clean 4.5.x-install (introduction-package maybe)? If you're able to somehow replicate it, please file a (separate) issue for that. Good luck!
Updated by Stig Kjeldsen almost 12 years ago
My mistake. It was a missing settings in the backend group.