Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V3.6.0/form plugin fixes #501

Merged
merged 6 commits into from
Jun 23, 2022
Merged

Conversation

wesleyboar
Copy link
Member

@wesleyboar wesleyboar commented Jun 21, 2022

Overview

Miscellaneous bug fixes and updates for form plugin.

Related

Changes

See commit messages.

Testing

website status notes
frontera (pprd)
core (dev)
apcd (pprd)
tup (dev) pending FP-1700 to appropriately prevent deploy failure
  1. Load a form.
  2. Verify required fields have red " (required)" (and not an asterisk).
  3. Verify all fields are 100% width except:
    • checkbox
    • radio
    • date
    • time
  4. Verify field height is based on pointer accuracy.
    (Test device with touch control versus without.)
    • touch-controlled device should have tall fields
    • not-touch-controlled device should have short fields

Screenshots

Desktop i.e. No Touch Mobile i.e. Touch
TUP-285 Desktop i e  No Touch TUP-285 Mobile i e  Touch

Notes

The missing space below footer is a known issue. It is solved in v3.7.0 (not deployed) but also has a bug to fix (not started).

@wesleyboar wesleyboar marked this pull request as draft June 21, 2022 19:59
@wesleyboar wesleyboar force-pushed the v3.6.0/form-plugin-fixes branch from 084987d to 5867f21 Compare June 22, 2022 15:33
@wesleyboar wesleyboar changed the base branch from main to release/v3.6.0 June 22, 2022 16:35
@wesleyboar wesleyboar force-pushed the v3.6.0/form-plugin-fixes branch 2 times, most recently from c7ad1c1 to 8623800 Compare June 22, 2022 17:35
Mimicing frontera accent colors, because CMS button design¹ show those:
https://xd.adobe.com/view/b37b291a-7798-4814-90f3-7ac63c48a3e0-e628/screen/d7a72466-4ae8-43fd-9531-44e033245ddb/

Using "Color Button" style² cuz it has more contrast than CMS¹ designs.³

¹ The left two columns ("On Light", "On Dark") are for CMS.
² I.e. .c-button--primary
³ Designer says his CMS designs lack contrast, and he will redesign.

Fixes: https://jira.tacc.utexas.edu/browse/TUP-285
@wesleyboar wesleyboar force-pushed the v3.6.0/form-plugin-fixes branch from 8623800 to 440206b Compare June 22, 2022 17:42
@wesleyboar wesleyboar marked this pull request as ready for review June 22, 2022 17:51
@wesleyboar wesleyboar closed this Jun 22, 2022
@wesleyboar
Copy link
Member Author

Wow. Git, you need to stop being smart. Closing a PR because of a separate repo's commit message… no, sir.

@wesleyboar wesleyboar reopened this Jun 22, 2022
I was gonna use media query ranges, but I found a better media query to use.
@wesleyboar wesleyboar mentioned this pull request Jun 23, 2022
@duckonomy duckonomy self-requested a review June 23, 2022 06:40
Copy link
Contributor

@duckonomy duckonomy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was gonna comment on the footer but saw the notes 👍
Otherwise LGTM!
FOO FIGHTERS & BTS🤘🤣

@wesleyboar wesleyboar merged commit d1dbcab into release/v3.6.0 Jun 23, 2022
@wesleyboar wesleyboar deleted the v3.6.0/form-plugin-fixes branch June 23, 2022 14:13
wesleyboar added a commit that referenced this pull request Jul 6, 2022
wesleyboar added a commit that referenced this pull request Jul 6, 2022
wesleyboar added a commit that referenced this pull request Jul 15, 2022
* feat(tup-230): working form plugin

* docs(tup-230): clarify form submission failure

* feat(tup-230): use jquery version that has ajax

The django-forms(-maintained) plugin expects jquery with ajax features.

Our CMS was using a slim build of jQuery.

The size difference is 17KB, which I consider negligible.

* feat(tup-230): make spam protection available

* feat(tup-230): e-mail template (when e-mail works)

* docs(tup-230): tweak comment in settings

* fix(tup-230): comments & semantic html in template

* fix(tup-230): revert and make some html changes

- less changes form original
- sometimes the original html was better for styling

* feat(tup-230): style form (no design review yet)

Also, no button styling yet.

* chore(tup-230): rename css file, add pointer file

Pointer file mimics what I do for blog CSS, which is also in source.

* chore(settings): tup-308, how to set captcha keys

Ref: TACC/Core-Portal-Deployments@48e6e9c

* noop(settings): tup-308, add new line

* fix(settings): tup-308, use new form css from #500

* fix(settings): tup-308, new form templates by #500

Not a straight clone of #500.

I added a little CSS and a small document to avoid cloning one template.

See:
- default.html.md
- django.cms.forms.css

* noop(settings): tup-308, form settings from #501

* fix(settings): tup-308, css changes from #501

* fix(settings): tup-308, "*" to "(required)"

I use a different solution than #501.

In #501, markup was changed to "(require)":
https://github.com/TACC/Core-CMS/blob/5f63bdf/taccsite_cms/templates/djangocms_forms/form_template/default.html#L27

But here, I do not edit the markup, so no need to clone template:
https://github.com/TACC/Core-CMS/blob/8a46a21/taccsite_cms/templates/djangocms_forms/form_template/default.html.md

* fix(css): tup-308, small form style issues

- bigger gap between single checkbox and input
- add gap between multiple checkbox and input
- align multiple checkbox and input
- simpler, less specific checkbox label selector
- remove undesired label margin*

* This style was ineffectual—good—in 3.6, but "fixed"—bad—when ported.

* fix(css): tup-308, small form style issues

- limit which help text gets margin
- remove ineffectual, unnecessary margin removal
- bigger gap between single checkbox and input
- align single checkbox and input
- add gap between multiple checkbox and input
- align multiple checkbox and input
- remove label margin on last of multiple checkboxes/radios
- simpler, less specific checkbox label selector
- remove undesired label margin*

* This style was ineffectual—good—in 3.6, but "fixed"—bad—when ported.

* docs(styles): typo fix for KSS comment

* fix(form): tup-308 only working export formats

1. Only let users export with supported formats.
2. Update form version to rev. that supports this.

Source: avryhof/djangocms-forms#8

* fix(form): delete unnecessary cloned template

* fix(form): tup-308, clean up templates

- remove unedited cloned template
- update commit in a comment

* fix(form): tup-308, move form export settings

* fix(form): tup-308, remove unused file

I forgot to delete this file earlier.

* fix(form): tup-308, remove redundant script

The removal happens form a merged PR on the plugin:
avryhof/djangocms-forms#12

* chore(core-styles): v0.7.0-beta

* fix(taccsite_custom): get main relevant PRs merged

* docs(form): no commented settings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants