Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clients keep messing up individual pages by clicking Back to Wordpress editor #5597

Closed
Jaska opened this issue Aug 29, 2018 · 4 comments
Closed

Comments

@Jaska
Copy link
Contributor

@Jaska Jaska commented Aug 29, 2018

Prerequisites

  • [ X ] I have searched for similar features requests in both open and closed tickets and cannot find a duplicate.
  • [ X ] The feature is still missing in the latest stable version of Elementor ( Elementor Pro. )

What problem is your feature request going to solve? Please describe.
Clients keep messing up the site when they click "back to wordpress editor" on a page that has been created with Elementor.

I think the problem is that the "back to the wordpress editor" button text doesn't only change the editor but changes the layout of the page, since it disables elementor.

Describe the solution you'd like
Change "back to wordpress editor" -text to "Remove Elementor layout and go back to Wordpress editor"
After clicking maybe some sort of "Warning - this might break the page"?

Describe alternatives you've considered
In the role manager, the ability to disable "back to wordpress editor" button on pages created with elementor. However, that might cause more problems. (Users could create elementor pages but not transform them back to regular)

@stefanobartoletti
Copy link

@stefanobartoletti stefanobartoletti commented Aug 29, 2018

Use a template and apply it to that particular page, and couple this with dynamic fields, instead of editing the actual page with Elementor; if you have to let the client edit the content this is the best solution.

@Jaska
Copy link
Contributor Author

@Jaska Jaska commented Aug 29, 2018

@Sekhemty Thanks! That's a good idea.

Elementor's dynamic fields seem still to be so much in development that not all content can be edited with them. E.g user selects posts with ACF post filter > but there is no place in the posts -widget to put an array of ID's.

I think a better text might at least alert some clients that by clicking the button they are not only changing the editor but disabling all the Elementor layout stuff.

@srcek
Copy link

@srcek srcek commented Sep 5, 2018

In addition to removing "Back to WordPress editor" button for Editor account and lower it would be very useful to have an option to remove "Edit with Elementor" button for pages and posts that were not created using Elementor (that doesn't include templates in Elementor wp-admin options). I often have a situation that client unnecessarily clicks that button and overrides content in native WordPress editor. That would eliminate the problem of an user creating Elementor page or post without an option to go back. "Edit with Elementor" overlay button would, of course, still be available for content editing on pages and post that were previously created by Admin.

Also, it would be useful if we could remove Elementor wp-admin menu item for non-admin users. I'm worried that clients will mess up the templates. There are plugins for such functionality but it would be nice if such option would be included in Role Manager.

@arielk arielk removed this from the 2.3.0 milestone Nov 2, 2018
@arielk arielk added this to the 2.4.0 milestone Nov 2, 2018
@arielk arielk removed this from the 2.4.0 milestone Dec 30, 2018
@arielk arielk added this to the 2.5.0 milestone Dec 30, 2018
@arielk arielk removed this from the 2.5.0 milestone Jan 1, 2019
@arielk arielk added this to the 2.4.0 milestone Jan 1, 2019
@KingYes
Copy link
Member

@KingYes KingYes commented Jan 1, 2019

Ref: #6588

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants