Twenty Seventeen: Layout broken and JS error in `wp-activate.php`

[flixos90]

In a Multisite setup with registrations enabled, one can access the wp-activate.php and wp-signup.php pages which use the header and footer as well as stylesheets and scripts of the current themes. It appears that the Twenty Seventeen theme was not optimized for these pages, particularly for wp-activate.php: The layout on that page is broken (no padding at all on the left side of the screen), and there is also a JavaScript error occurring.

I haven't looked into this more closely yet, but I just wanted to open this ticket for now. I can have a closer look probably later next week, if no-one gets there before. :)

[adamsilverstein]

I wasn't able to reproduce the JS error, I do see formatting issues on both pages. In addition top the lack of a left margin on the activate page, both pages forms stretch full width and push the sidebar widgets to the bottom of the page. When submitting signup form with an error, the resulting page shows the splash screen, the form is offscreen, below the visible area.

[afercia]

To reproduce the JS error:

• make sure there's at least one widget in the sidebar
• keep your browser's console closed
• go to the signup or activate page, e.g.: mysite.com/wp-activate.php
• open your browser's console

The JS error disappear after a page refresh.

Screenshot:

[afercia]

Seems the styling issue is not limited to Seventeen, Twenty Fourteen has the same issue. Here's some screenshot for comparison, haven't checked Twenty Thirteen and the previous ones.

Twenty Seventeen:

Twenty Sixteen:

Twenty Fifteen:

Twenty Fourteen:

[SergeyBiryukov]

Related: #25478, #25479.

[xkon]

Fixes the js top error and activate styling

[xkon]

Hello, 40338.diff should solve all the issues.

I added 2 custom css styles for the body when you are viewing the wp-activate.php and wp-signup.php width wp-activate-page and wp-signup-page to address the js issue. It was caused because there is no sidebar rendered on these pages and the script was still trying to set the offsets for it with sidebarPosBottom = sidebarPos.top + ( $sidebar.height() + 28 ); in global.js .

TwentyFourteen is a minor css fix.

All these where tested under a Multisite install so be kind if somebody can to make a test on a single as well to be safe in case of extra errors.

---

Note: the js error is produced ONLY with an embeded developer console because you need to resize the height of it so the window changes height to trigger the offset js.

I had my console on an extra window and was never getting an error as well but I saw afercias screenshot and just had the shiny idea to test it that way! :D

---

Best regards,
Konstantinos

[sabernhardt]

The forms touch the left edge in Twenty Nineteen and newer bundled themes, too. I think the signup and activate pages should have centering for any theme. A patch on #43536 adds the body class and centers the form.

40338.1.diff​ sets the signup form styles on the activate page for Twenty Fourteen and includes the script change for Twenty Seventeen.

If Twenty Seventeen should have the wrap container, that could be added to special header and footer templates (header-wp-activate.php, etc.). Another possibility is assigning the wrap max-width and padding to the signup and activate containers in the Twenty Seventeen stylesheet. Also, with the is_home value corrected on the other ticket, these pages would not have the full-height header image.

[sabernhardt]

(current patch depends on proposed changes in #43536)

[sabernhardt]

Did some change fix the JS error in Twenty Seventeen? I seem unable to reproduce that now. If it still occurs, the script probably could check whether #signup-content exists on the page instead of looking for body classes that are not assigned yet.

For the CSS, setting a width on `.wp-activate-container` added some space around the activation form. The width and/or margin can be better in themes, but I think any further improvements for that can be on a separate ticket (if desired).

[karmatosed]

I also can't seem to replicate the original issue, so for now going to recommend this is closed. We can always reopen if we do find it is still an issue, thank you everyone.

[karmatosed]

Thank you everyone for collaboration here, I am going to follow through and close this.

[flixos90]

@karmatosed @sabernhardt I just checked again, and indeed the bug is gone. I searched a bit more, and found it was fixed by [51257] (see #53512). 🎉

[sabernhardt]

Thanks for testing and finding the commit!