WPIntell

Source evidence

[Plugin: HTML Mode Locker] Lock one page not all of them

HTML Mode Locker · support · 2012-01-23T17:07:00+00:00

complaintsentiment
highseverity
1.0relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

7 / 35 rows with source links

20.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
Sheila unresolved
Just installed this. I’m getting this error after installation on every page I switch to: Warning: call_user_func(html_mode_lock_settings) [function.call-user-func]: First argument is expected to be a valid callback in /home/oozandoz/public_html/wp-admin/includes/template.php on line 1102 Screenshot of same: http://awesomescreenshot.com/092smat26 I think that problem is gone now that I’ve selected Pages in the settings. HOWEVER, your plugin says we can lock on a per item basis. As far as I can see it leaves all my pages locked in the mode it was in at the time I installed. I just want to lock one page. Is that possible? HOW? http://wordpress.org/extend/plugins/html-mode-locker/ Hi there, That is not an “error” – it’s just a warning, which means nothing is broken. There are 2 reasons why you seeing this: 1 – you have WordPress debug activated; 2 – PHP error handling set to output warnings (that is not recommended on production servers). I’ll make sure the warning goes away in the next update. Let’s figure out why the locking issue. When you check your specific content type in the Settings => Writing, you should see a Meta Box called “HTML Mode Locker” in the post editor on right right hand side (sidebar). There is only 1 checkbox – to lock the current post in HTML mode. When you click on it and save your post, ONLY THAT particular post will be locked in HTML mode. The rest of your posts and pages will still have both Visual and HTML modes available to them. Let me know if this helpful or not. If it is and the plugin works as intended, then I will release an update to remove the warning message. Thanks! Perfect…thanks so much. I guess I wasn’t looking hard enough. It might be useful to have a little more guidance for newbies. Now that I know where to look I see the check box and it does work. I installed it on another site and got that error again. It’s disconcerting. So getting rid of it next update is a good idea. I’d suggest two brief sentences in the plug-in interface that says something like: Enable in Settings-Writing, then check in top right of any item you’re editing. Thanks for your input. I’ll think of a way to make it more intuitive for others. As for the Warning – have you updated to version 0.2? It should remove all warnings. Please let me know.

Comments

3 shown
Max Chirkov 2012-01-24T19:59:00+00:00

Hi there, That is not an “error” – it’s just a warning, which means nothing is broken. There are 2 reasons why you seeing this: 1 – you have WordPress debug activated; 2 – PHP error handling set to output warnings (that is not recommended on production servers). I’ll make sure the warning goes away in the next update. Let’s figure out why the locking issue. When you check your specific content type in the Settings => Writing, you should see a Meta Box called “HTML Mode Locker” in the post editor on right right hand side (sidebar). There is only 1 checkbox – to lock the current post in HTML mode. When you click on it and save your post, ONLY THAT particular post will be locked in HTML mode. The rest of your posts and pages will still have both Visual and HTML modes available to them. Let me know if this helpful or not. If it is and the plugin works as intended, then I will release an update to remove the warning message. Thanks!

Sheila 2012-01-25T21:55:00+00:00

Perfect…thanks so much. I guess I wasn’t looking hard enough. It might be useful to have a little more guidance for newbies. Now that I know where to look I see the check box and it does work. I installed it on another site and got that error again. It’s disconcerting. So getting rid of it next update is a good idea. I’d suggest two brief sentences in the plug-in interface that says something like: Enable in Settings-Writing, then check in top right of any item you’re editing.

Max Chirkov 2012-01-25T22:02:00+00:00

Thanks for your input. I’ll think of a way to make it more intuitive for others. As for the Warning – have you updated to version 0.2? It should remove all warnings. Please let me know.