Edgewall Software

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#11836 closed enhancement (fixed)

more intuitive layout for wiki page create form — at Version 7

Reported by: Christian Boos Owned by: Christian Boos
Priority: normal Milestone: 1.1.3
Component: wiki system Version: 1.1dev
Severity: minor Keywords:
Cc: Branch:
Release Notes:

Improved positioning of the Create this page button on the wiki page create form.

API Changes:
Internal Changes:

Description

The existing layout of the form is not optimal when creating a page inside a hierarchy, as it first proposes to create the page elsewhere, then further down has the button Create this page:

the //wiki page creation// form in 1.1.3

The links to "similar names" suggestions are already placed after the Create button, and I think it's better if we would also place the links for the non-existing pages higher in the hierarchy there. That way, users are less likely to follow these links "blindly":

the proposed //wiki page creation// form

Change History (10)

by Christian Boos, 9 years ago

Attachment: create_wiki_form-old.png added

the wiki page creation form in 1.1.3

by Christian Boos, 9 years ago

Attachment: create_wiki_form-new.png added

the proposed wiki page creation form

by Christian Boos, 9 years ago

the proposed changes

comment:1 by Ryan J Ollos, 9 years ago

A suggestion for another minor adjustment to the create page can be found in #11670.

in reply to:  1 comment:2 by Christian Boos, 9 years ago

Replying to rjollos:

A suggestion for another minor adjustment to the create page can be found in #11670.

Ah sorry, I didn't remember that one otherwise I would have followed-up there. Still, I think that changing the order is clearer and makes the notice unnecessary.

Showing the #11670 proposal here for easier comparison:

Or combining the two ideas, we could indeed have "The page Foo/Bar doesn't exist. You can create it here" in a notice message, then the "Create" button and the template selector, followed by the links.

Last edited 9 years ago by Christian Boos (previous) (diff)

comment:3 by Ryan J Ollos, 9 years ago

I think your proposed changes are good. I'd favor committing those, and waiting to see about #11670. Probably #11670 won't be needed.

comment:4 by Christian Boos, 9 years ago

Resolution: fixed
Status: newclosed

Ok, fine, thanks for the review! Patch applied in r13358 (trunk).

comment:5 by Ryan J Ollos, 9 years ago

I fixed a few functional test cases in [13361]. Tests are currently failing though due to issue I introduced in #10984.

in reply to:  5 comment:6 by Christian Boos, 9 years ago

Replying to rjollos:

I fixed a few functional test cases in [13361]. Tests are currently failing though due to issue I introduced in #10984.

Thanks! I thought I had run the test suite, but forgot that if it fails with the unit-tests it won't continue with the functional ones. And I had a few unrelated failures in the unit-tests (possibly due to a messed up version of Python). I'll be more careful next time.

comment:7 by Ryan J Ollos, 9 years ago

Release Notes: modified (diff)
Note: See TracTickets for help on using tickets.