To do so the shipment mailer and payment mailers need to know the @order
Remove the 'callout' class from distributor signoff for uniformity and to keep the callout available for call to actions only
Remaining translation keys for emails will be re-organized in a separate commit
Shared keys are used for greetings, signoffs, order confirmation string (incl. order number), contact distributor note and order edit note
Remaining translation keys for emails will be re-organized in a separate commit
Use wrap style full width background like header
Move 'Powered by...' message to footer and rephrase to suit all recipients (not shoppers only)
Always show link to openfoodnetwork.org instead of email (if present) because email will be available via icon in the row below now
Add social media buttons of instance to email footer
Make footer text and icons dark gray (as instance name in email header)
- this was only used in the enterprise show view
- the above view was deleted here 4f2389e257
- by removing this, we can remove distributor_link_class method
- it will also fix the rubocop error
Once the user accept the cookie, we should not show the cookie banner element. This is handled via `app/helpers/footer_links_helper.rb#cookies_policy_link` and boolean:
```
!Web::CookiesConsent.new(cookies, request.host).exists? && Spree::Config.cookies_consent_banner_toggle
```
Therefor, for the right controllers, simply implements:
```
include WhiteLabel
before_action :hide_ofn_navigation, only: [:show, :edit]
```
This is mort robust, since we're working in a controller level, not parsing URLs...
The old Paperclip configuration was very clever and easy to use but it
was also a complicated implementation building on the complicated Spree
preference system.
I simplified this with Active Storage, storing simple references to blob
ids and default URLs as backup.
- The old method (link to `?locale=#{l.to_s}`) was not functional for path that already has query params in current path (such as `/user/spree_user/password/edit?reset_password_token=`) ;
- This seems that the best way to handle this, is to create a new route, new method that effectively set the lang (not the locale actually...) and then redirect_back (ie. using the HTTP_REFERER, with a fallback to `/`)
s
DRY code and have more consistency. We always use "Terms of service" now
and not "Terms of Service" or "Terms and conditions". The latter is used
for the shop's terms, not the platform terms.
