- echo is now on v4 with major changes including a few breaking changes
- bind() behaviour is now strict. JSON / form etc. unmarshalling of
request data need appropriate `json`, `form` tags. Missing tags for
the public subscription page is added in this commit.
- This also closes#602.
* improved mobile navbar/sidebar
Sidebar is hidden and all menu items moved to hamburger menu on mobile devices
* improvements to menu rendering
-removed redundant code
-fixed an issue with emitting data to App.vue
* Update Navigation.vue
fixed linting errors
* Add minor refactors to the mobile menu PR.
- Fix indentation and line lengths.
- Simplify prop definitions in the Navigation component.
- Remove redundant computed methods and use prop variables directly in
the Navigation compontent.
- Simplify menu rendering logic by:
removing isSidebar, showLogout and using simpler v-if / else
in the parent instead of the Navigation component.
* Update App.vue
removed orphaned isSideBar Boolean
Co-authored-by: Kailash Nadh <kailash@nadh.in>
Every listmonk instance scans the DB periodically to look for
running campaigns to process. This made running multiple instances of
listmonk impractical as they would all pick up the same running
campaign and process them, resulting in duplicate e-mails.
This commit adds a `--passive` flag to the binary that runs listmonk
in a "passive" mode where campaign processing is disabled. This allows
multiple instances of listmonk to be run to handle different kinds of
requests if there is a requirement (scale/traffic?). It is important
to note that there should only be one non-passive instance running at
any given time. If distributed campaign processing is ever considered,
this will change.
If `<!doctype html>` is not found in static/email-templates/base.html,
all system e-mail templates are assumed to be plaintext and go out
as content-type: plaintext e-mails. With this, all HTML tags can
be stripped out of the system e-mail templates (while maintaining
Go template tags and logic) to have plaintext system e-mail templates.
Closes#546
On a successful form submission, error message etc., check if there's
browser history and render a button that takes the user back to
a meaningful origin from the dead-end message page.
Closes#527.
