inline edit does not work - version 5.1
Does it require a special configuration somewhere? How do I make it work? Watched the video, it does not say that anything has to be configured... Logged in as an admin...
What do you mean by 'does not work' ?
When you click on the Tools icon, and then click on 'Show editing tools', you should see buttons where you can edit content.
I mean that there is no Tools button. I logged into the backend. I clicked on "Edit content directly browsing the site" link on the dashboard. A new window with the site opens, but there is not "Tools" icon in sight. Tried in 4 different browsers, on 3 different machines. None of my multiple content providers see it either. We watched the video about the inline editing, we know that there should be the icon. But it's not there. The Global Permissions settings indicate the following: Use in-line editing given to all Backend users. What else should be done, so it works? Thanks.
Certainly Administrator should have sufficient privs to see it.
Well, as I suspected, there is an additional configuration for the inline editing. Wondering why nobody in this forum knew about it... Here it is:
1. Go to yoursiteurl/.../Advanced
2. click 'Pages'
3. set "Enable in-line editing" to true
So, in ADDITION to the Permission section, the inline editing option should be configured on the pages level as well. Wondering if it's somewhere in those 315 pages of Sitefinity user's manual and if so, why it didn't come up in the search result page when I was searching for the answer all over the sitefinity site...
@Inna,
I think most of us just leave it off... can be a great feature but we're all a tad old fashion
Jochem
Thanks a bunch, Jochem, for showing me how to "unlock" this feature. Still, don't get why it's not in the manual... seems like there was no concern about its length. And the feature has been advertised much. Could be as well taught how to make it available....
@Jochen
"I think most of us just leave it off..."
I can't speak for anyone else, but I just left it ON.
I didn't consider such a setting, because it was enabled by default on my systems.
However, all of mine have been upgraded from 4.x versions.
I wonder, has this changed for 5.x installs ?
@MB,
No you're right, by default / out-of-the-box it is turned 'on'.
Back in the beginning of v4 it had some browser issues and it causes some extra load. So most people I know turn it off when starting development and then 'just leave it off...'
Given the fact that browsers seem to span new versions faster than we as dev can keep up with, I'd say if turned on, warn your clients that it may affect their browsing experience...