Write screen: moving section and category selects to the top

masa · 2008-07-08 12:43:25

redbot wrote:

I agree.
BUT changing the order of some elements (sections, category etc.) will probabli break ied_hide_in_admin cos it is working based on the default order of elements.

That would of course be a real problem.

I agree that having ied_hide_in_admin’s controls in the core would be great.
What’s the status of that plugin? It seems the developer hasn’t been around for quite a while.

redbot · 2008-07-08 13:12:58

masa wrote:

What’s the status of that plugin? It seems the developer hasn’t been around for quite a while.

Some concerns about the status of the plugin have been already expressed in the plugin thread.
I don’t want to be too optimistic but I dare to hope that Steve Net-carver will some day incorporate it in his wonderful sed_section_fields… (probably I’m dreaming)

Last edited by redbot (2008-07-08 13:16:10)

renobird · 2008-07-08 13:41:54

redbot wrote

I didn’t know it could be used to keep open the “more” options. In fact I still think it can’t.

Your right – it can’t. I don’t know what I was thinking.
3 hours of sleep is obviously not enough.

Not to self: Don’t stay up all night with baby and then post false info on the forums.

)

jakob · 2008-07-08 13:48:16

ied_hide_in_admin finds and replaces things using the DOM-structure rather than any jquery-like find and replace so it is prone to ‘breaking’ with the slightest change to the structure of the admin area, but you can rejig by correcting the DOM paths it contains.

I agree that section could be more obvious but arranging them beneath each other is not very economic with space, particularly when you have a truck-load of custom fields…

For what it’s worth, guiguibonbon was even more radical with the section area – see backend2 in this xpattern thread.

masa · 2008-07-08 14:37:21

jakob wrote:

I agree that section could be more obvious but arranging them beneath each other is not very economic with space, particularly when you have a truck-load of custom fields…

But the cfs would stay on the left hand side.

The problem with not stacking the selects is that long category names cause them to grow, so I don’t think placing them on the same line would work too well.

I’m not convinced that mixing them into the central content area (headline, body, excerpt) is a good idea. As it is now things are clearly separated.

jakob · 2008-07-08 15:27:37

But the cfs would stay on the left hand side.

Sorry, my error (I’ve changed my own installations around and have got so used to it I forgot).

The problem with not stacking the selects is that long category names cause them to grow, so I don’t think placing them on the same line would work too well.

You can use css to force the width of the select drop-downs (think it works in most/all browsers). You still see the entire text when the drop-down opens.

masa · 2008-07-08 19:20:37

jakob wrote:

You can use css to force the width of the select drop-downs (think it works in most/all browsers). You still see the entire text when the drop-down opens.

Good point!

Although now that it seems as if it would break ied_hide_in_admin my idea is flawed, unless someone took over development of the plugin and made the necessary changes and of course the devs would consider making the changes in the first place.

It does seem though that there’s enough interest in having the selects organised differently.

Sorry, my error (I’ve changed my own installations around and have got so used to it I forgot).

I can relate to that, since I usually apply some minor modifications to the core, too.

How do you handle this when upgrading?
At the moment I keep a text file with all the modifications and simply apply them again by copy&paste after the upgrade, very tedious.

Last edited by masa (2008-07-08 19:23:48)

jakob · 2008-07-08 20:15:51

How do you handle this when upgrading? … very tedious

Yes, that sums it up, I’m afraid. A little voice in the back of my mind keeps saying there’s got to be a clever way of doing it but for the moment I also note what files I have changed and the basic modifications I have made, just the purpose not the actual code. Where I make a modification to the source I flag it with a searchable comment such as // MOD JR - brief reason for change so that I can at least find them again fairly easily.
You can use a diff program to compare the source code of two files against each other and restore (or adapt) your change to the new source. If you know which files you messed with and why and can discern your own modifications from other changes to the code, that narrows down the work a little.

Although now that it seems as if it would break ied_hide_in_admin my idea is flawed …

ied_hide_in_admin is not impossible to adapt (at least I managed it a while ago) – it’s basically counting out the nodes (sort of like 1 across, three down) and changing the number of steps (e.g. to 1 across, 2 down or whatever) to fit your new arrangement. It’s been a while but think I used the DOM explorer in the IE toolbar to get a better idea of the node structure.

masa · 2008-07-08 20:32:02

Thanks Jakob for your tips – very much appreciated!

Textpattern CMS

Textpattern CMS support forum

#13 2008-07-08 12:43:25

Re: Write screen: moving section and category selects to the top

#14 2008-07-08 13:12:58

Re: Write screen: moving section and category selects to the top

#15 2008-07-08 13:41:54

Re: Write screen: moving section and category selects to the top

#16 2008-07-08 13:48:16

Re: Write screen: moving section and category selects to the top

#17 2008-07-08 14:37:21

Re: Write screen: moving section and category selects to the top

#18 2008-07-08 15:27:37

Re: Write screen: moving section and category selects to the top

#19 2008-07-08 19:20:37

Re: Write screen: moving section and category selects to the top

#20 2008-07-08 20:15:51

Re: Write screen: moving section and category selects to the top

#21 2008-07-08 20:32:02

Re: Write screen: moving section and category selects to the top

Board footer