Disable Content Editing

I would like to see an option to disable content editing. To not force it.
If someone needs it then he/she should reconsider not to use CMS.

I do understand attraction to use it for content in columns, quick map and contact form in Page, etc. But there is a Themler for it. Shame they gave in under pressure from Users and implemented it.

All this with custom shortcodes too is a noble ide, but seems as strange implemented.

Now I dont dare to click inside Post content control anymore. I try to avoid it.

Yes, exactly! I have found that even without touching the 'content' of the post Themler starts messing with the post content, for example when moving or restyling the post header on a custom template. It's making it impossible to create anything that I can hand over to clients...!

Really glad to see I'm not the only one with this problem.

It makes one another problem.

Even if CMS Users cannot login to Billiontheme and use Themler because they dont know login credentials, I dont want them to see there is something like Themler there. Even they login as Admins. (You have to give them this Admin login, they are owners of website)

With Themler part when exporting theme ZIP, or without. Better to leave it on live server because they allways have plenty of those small changes they wish. Color here and there, different icon there, etc..

The highest level of access I usually give to a client in WordPress is 'Editor', but they still see the 'Edit in Themler' button which is very irritating, as I don't want them to be able to access Themler or know it was created with it.

I really hope that support respond asap and that a new update with the option to disable content editing is released in the next few days - I need this quickly!

Dont know if it is so easy now.

I had high hopes for shortcodes. As some tool for shortcode generating. But as you cannot put any line of PHP, JS code they are more or less useless for me.

Add this to wp-config.php and it will remove all mention of Themler in backend for Admins. If they by chance hit Themler URL they will get access not allowed error:

define('DISALLOW_FILE_EDIT', true);

Editor button is impossible to remove for now, it has no class attached.
Actually it is maybe possible, but it will leave nasty spacing as it is inline styling.

This removes button, leaves some 15px empty spacing:

add_action('admin_footer','remove_themler_button');
  function remove_themler_button(){
?>
<style>
 #edit-in-themler {display:none;}
</style>
<?php
}

Here is how you remove Themler button right way:

function remove_themler_button() {
   remove_action('edit_form_after_title', 'theme_edit_form_after_title');
}
add_action( 'admin_head', 'remove_themler_button' );

Hi Stagger Lee,

Thanks so much for that. Where is best to put this code? I tried it in 'Additional CMS Code' and it had no effect, and I tried running it as a new plugin and whilst it worked (ie it removed the button), it caused a error 500 message on the website front end.

I have also found that themler adds an option in the WordPress backend to 'insert paragraphs automatically', which it disables if you edit the content in themler, even accidentally. This is irritating, since it's overridding WordPress default behaviour for no reason, but selecting this option on each page resolves the specific issue I mentioned with themler ignoring paragraphs. Still not happy about themler adding [html] shortcodes on WordPress pages, though.

Support team, any word on any of this? Themler is a THEME BUILDING tool, so if content editing is to be available, it should at least be optional.

I have it in custom functions.php in my own plugin, and works there. Just because plugin code is executed before theme code.

Could not get it to work in theme functions.php, or additional.functions.php, (your Themler Settings - Additional CMS Code). No matter what I tried with priority and other tricks.

functions.php "include" export.php file where this function and add_action is, as last line in functions.php.

Maybe developers can help us a bit, I am out of inspiration.

I will check later this error on frontend, have not checked it.

And when we said Goodbye to Artisteer they make something like this. I mean not pitty button, but whole content editing stuff.
How can it work with my Billionthemler login credentials ? Are they so naive they thought all clients and Users will buy a licence just because of this editor button and editing options.

From shortcodes perspective it is wrong too. I never gave any client/user info how to insert shortcodes and meddle with text inside parentheses. It doesnt work this way in real life.

I see now what is problem (error). You probably forgot to delete function from Settings in Themler, so it is called twice from your code.

Thanks Stagger Lee, I will try this and let you know if I get anywhere.

Support team, any comment on this please?

When exporting a theme as a zip from Themler, I make sure the "include Themler for customizing this theme" is NOT checked.
I have no intention of allowing customers to mess with the theme, nor do I want any content from Themler. Content is added in Wordpress. The Themler button does not appear.
My only issue is lack of access to shortcodes in the Wordpress page editor.

Yes, that's certainly one way of getting round it. I do like including Themler so that I can make quick theme edits and fixes if a client needs them without having to work on a localserver and then export the theme and reinstall it, so not an option I'll be using.

How many of you would give clients / Users those shortcodes to work with ?

Any Section shortcode is all way to complicated for any beginner.

Yeah, no way I'd give a client anything that they needed shortcodes to edit. Far too complicated for any sort of beginner, and too much hassle and potential for them to break things...

Shame Shortcake is somehow stranded. First enthusiasm is gone seems so.
For any serious work it has to support mutliple attachments and repeatable fields.

When Shortcakes can be implemented with Themler shortcodes than you can give beginenrs all you want. It goes alreday now to implement many Themler shortcodes in Shortcake, but docummentation is very difficult to find. Still struggle with everything beyond those simple Shortcake shortcodes i found online.

Hello James,
I apologize for delay in response from support team.
The content editing and theme editing tasks are in fact two different tasks.
If you want your users/customers not to be able to open Themler and thus edit style you may:
-save the theme without 'Include Themler..' option and install this theme to WP site;
-hide the Themler menu button in WP admin menu as was described by Stagger Lee

As for content editing, it is possible to do in WP admin back end and we cannot do anything to prevent end users from editing it.

Please let us know if you have any other specific questions

Regards,
Aileen

Hi Aileen,

I think you have misunderstood. Of course theme and content editing are different tasks - that's obvious.

I wasn't asking for a way to prevent content editing all together - if I wanted that I wouldn't use a CMS. What I want is the ability to disable the content editing in Themler. I don't want themler even attempting to edit the content I or my clients produce in the WordPress backend. Perhaps just a toggle option in Themler to switch off its content editing ability?

The hiding Themler from clients issue was a separate but related topic brought up by Stagger Lee, and this is also true. Again, if you could implement an option to disable Themler's content editing ability, it should also hide the button in the WP Backend as Stagger Lee provided instructions for. We shouldn't have to do this manually, and some of us just want a theme building tool, not a full website builder.

James

... some of us just want a theme building tool, not a full website
builder.

+1. Exactly!

I talked about this many times... need more powerful theme building tool, not just a constructor (website builder).
Themler team, please pay attention for this. Will be very nice if you can correct your plans and roadmap for future.

Just one word.

Developers can have "insert content" in new Blog sections. This is completely different aspect and is welcommen addition for styling and layout. Easy to delete them later.