Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#21 2020-10-12 16:39:52

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 9,832
Website

Re: About override form

It’s not a bad idea, per se. We just need to think about use cases and choose the best UX to support it.

I think maybe what is slightly incongruous is that you get the ‘override’ (a.k.a. reassign) whether you’ve assigned the selected assets to articles or not. Nothing we can do about that, since multi-edit options are built before selections are made.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#22 2020-10-12 16:52:17

etc
Developer
Registered: 2010-11-11
Posts: 3,989
Website

Re: About override form

There are other ways to render override forms invalid: change the article’s section theme to one with missing forms, etc. We are not users nurse, a ‘form in use’ pill is probably enough here.

Offline

#23 2020-10-12 17:04:46

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 9,832
Website

Re: About override form

etc wrote #326340:

There are other ways to render override forms invalid: change the article’s section theme to one with missing forms, etc.

Absolutely.

We are not users nurse

Absolutely again. But if we’re putting in a feature that appears as if we’re nursing them, we need to make sure it actually does :)

a ‘form in use’ pill is probably enough here.

Yep, I like that.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

Board footer

Powered by FluxBB