[plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

plugmas.com · 2007-11-22 21:01:49

What about hide author list admin => users tag?

redbot · 2008-06-29 23:26:36

Hi Yura,
it’s been more than a year since your last appearance here and I’m a little worried, because this is an essential plugin which – together with sed_section_fields and glz_custom_fields – really boosts up txp interface. I’m using it all the time even if it behaves strangely sometimes (see the various posts in this thread) and frankly I don’t think I could still build a site without this plugin installed (apart from hacking directly the txp code).
I hope you are still willing to mantain it, otherwise I wonder if there is somebody who wants to adopt it.
Unfortunately I’m not too familiar with javascript or jquery but if nobody wants to take the task I’ll be forced to code it myself. Which will presumibly take some years (and yes, I know I’m too optimistic).

Last edited by redbot (2008-08-20 14:13:02)

robin746 · 2008-06-30 00:15:19

I agree redbot. In fact I’d like to be able to completely customise the user interface for writers. Such facilities would really boost Textpattern IMO. Making it easy for clients is what it’s all about.

net-carver · 2008-07-06 14:04:02

All

Out of curiosity, what are the fields that you most often hide using this plugin?

renobird · 2008-07-06 15:00:49

I Always Hide:

Excerpt – I use rss_auto_excerpt instead
Use Textile – I use hak_tinyMCE on every install.
Keywords – I’ve just never found the need – and when I did – users never filled it in
URL-only title – I leave it for privs 1,2 – hidden for anyone else.

And depending on the site:

Category 2 – just clutter if there’s only need for 1 category assignment.
Override Form – Override form is great when you need it – but I hide it 75% of the time.
Comments

redbot · 2008-07-06 17:59:43

I Always Hide:

Use Textile – I use hak_tinyMCE on every install.
Override Form
Keywords
URL-only title

And depending on the site:

Both categories – I tend not to use them – I prefer custom fields (obviously with glz_custom _field + sed_section_fields)
Status
Article and link categories in the “categories” tab

I Always keep open:

advanced options
recent articles

edited: moved “override form” to items I always hide

Last edited by redbot (2008-07-06 20:57:35)

mrdale · 2008-07-06 20:04:48

I hide everything but:

URL-only title
Article Image
Custom fields (sed kindly hides all but the pertinent fields)

…except my cocktail of plugins has never allowed this plugin to work, so I add a div with a class="hidden" inside “advanced options” that ends just before “article image” to txp_article.php then display:none that puppy, and let sed show the rest when needed.

Ugly Hack, pretty interface.

Last edited by mrdale (2008-07-06 20:13:08)

redbot · 2008-07-06 20:51:36

mrdale wrote:

…except my cocktail of plugins has never allowed this plugin to work…

Did you set “allow form override” to “no” in your preferences ?
In this case set it to “yes” and then hide it with ied_hide_in_admin. Usually this is the cause for the plugin not working…

renobird · 2008-07-09 02:38:47

Disclaimer: I haven’t done much tweaking to the TXP admin…so I might be talking out of my arse here.

There’s a lot of talk about admin redesign going on. (too lazy to find all the threads right now).
I’ve noticed that issues with with this plugin keep coming up when talking about re-arranging elements in the admin.
It’s pretty much indispensable, and it’s functionality should be in the core – however – short of that happening…

A potential solution
It seems to me that if each element in the admin had/has a unique id or class
then it wouldn’t be to difficult to use jquery to show/hide those elements – no matter how they are arranged.

Take the write status for example:
<fieldset id="write-status">

The required jquery to hide it:
$('#write-status').hide();

With this method you could customize the admin however you want, and still be able to use the same plugin.

See where I’m going with this? I haven’t totally fleshed this out, and probably haven’t done the greatest job explaining myself.
I’ll check into it more tomorrow and post a follow up, just wanted to get the idea out there.

—
Tom

jakob · 2008-07-09 07:37:15

Yes, more #ids as ‘hooks’ in the back-end would help. If I remember rightly, that’s why ied_hide_in_admin doesn’t already use that approach.

redbot · 2008-07-09 08:29:47

renobird wrote:

It seems to me that if each element in the admin had/has a unique id or class
then it wouldn’t be to difficult to use jquery to show/hide those elements – no matter how they are arranged.

FWIW I totally agree.
As a bonus I think this kind of modifications can be made quite easily and – if done wisely (for example prepending a certain prefix to such ids and classes) – it can’t in any manner interfere with existing plugins and core functions

robin746 · 2008-07-09 12:05:17

renobird wrote:

It seems to me that if each element in the admin had/has a unique id or class
then it wouldn’t be to difficult to use jquery to show/hide those elements – no matter how they are arranged.

Yep. It really is that easy. If this could be in the next Textpattern version it would enable some really cool plugins.

daver89 · 2008-10-06 10:14:23

Can anyone help me, i can’t seem to get this plugin working at all. i have tried it on a fresh install but it won’t hide anything. is this plugin still support with 4.06.

if it doesn’t can anyone give me any other suggestions please?

dave.

masa · 2008-10-06 11:16:55

I don’t have any problems under 4.0.6. Sorry if that’s obvious, but if you use it to hide features for someone with less privileges, you need to log in as that user to see the changes.

daver89 · 2008-10-06 11:31:30

This is near enough a fresh install, the only other plugin in tiny_mce. But i have unticked everything on every user and nothing seems to happen.

i am looking at the php and from my basic knowledge i am assume this is adding js to the article tab to hide items. but when i check the source of my write tab nothing has been added.

EDIT: the status section is hidden on any permissions when i untick eveything but all the other fields remain.

Last edited by daver89 (2008-10-06 11:35:46)

Textpattern CMS

Textpattern CMS support forum

#76 2007-11-22 21:01:49

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#77 2008-06-29 23:26:36

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#78 2008-06-30 00:15:19

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#79 2008-07-06 14:04:02

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#80 2008-07-06 15:00:49

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#81 2008-07-06 17:59:43

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#82 2008-07-06 20:04:48

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#83 2008-07-06 20:51:36

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#84 2008-07-09 02:38:47

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#85 2008-07-09 07:37:15

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#86 2008-07-09 08:29:47

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#87 2008-07-09 12:05:17

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#88 2008-10-06 10:14:23

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#89 2008-10-06 11:16:55

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

#90 2008-10-06 11:31:30

Re: [plugin] [ORPHAN] ied_hide_in_admin version 0.1.: Hide Fields in Admin

Board footer