Looking at the network tab, the 2 biggest visuals take up 987 KB – find attached 2 refined versions using ImageOptim, saving 900 KB
Specs: 70% PNG quality (for less color bleed), 60% JPG quality (visual comparison on 1920px width)
Great work and great community approach for refinement!
- I second #75 in linking some sort of public styleguide doc for future reference
- As #144 notes, text wrapping could improve – “Open Source means no vendor lock-in” would wrap as proposed using non-breaking hyphens/spaces as special chars: “Open Source means no
‑in”
Note: the example above replaces the non-breaking spaces (NO-BREAK SPACE / Unicode: U+00A0, UTF-8: C2 A0) with regular spaces but not the non-breaking hyphen (NON-BREAKING HYPHEN / Unicode: U+2011, UTF-8: E2 80 91) – interesting
Hello @gisle – thanks for checking on this – the reason we still saw the message was us using Rules successor ECA which switches users for role operation permissions (as seen in the demo feature) – effectively receiving the message while in a temporary admin state.
We fixed this by applying a local patch that removes the message output.
Strangely, this patch would still show the message to users who definitely weren't being able to access the admin/rebuild page.
stolzenhain → created an issue.
Thanks for this issue and the linking of #3389715 – patch works fine.
this threw some errors by now; should be noted that the linked issue is resolved by now; there is a user/edit route in core →
Thanks to @lind101 for working out a solution to this!
To use this on fresh installation and apply the working patch on #15, we had to
1. refer to the
lenient endpoint package →
allowing to bypass version requirements
2. add the regcode module as an exception
3. successfully requiring the module, after which the
4. the patch file of the drupacode merge could be applied to fix the behaviour
(props to @morenstrat → for pointing to the lenient plugin)
it appears this was fixed with the recent update → .
it appears this was fixed with the recent update → .
> i couldn't find this issue referenced in any of the recent releases notes, which release fixed this issue?
@munchmunch it was fixed in [3.2.3]( https://www.drupal.org/project/multiple_registration/releases/3.2.3 → )
Joachim Namyslo → credited Stolzenhain → .