Mail: [email protected]
Phone: +1(424)231-4091
Documentation
Everything you need to know about NexoPOS.
- Getting Started
- 0. Requirements
- 1. The Environment
- 2. Download And Build
- 3. Installation Wizard
- Components
- Accounting: Incomes & Expenses
- Cash Registers
- Customers
- Customers Group
- Expense History
- Expenses
- Expenses Categories
- Media
- Modules
- Numpad
- Order Types
- Orders
- Payment Types
- Procurements
- Product Categories
- Products
- Providers
- Reward System
- Stock Adjustment
- Table
- Taxes
- Taxes Groups
- Unit Groups
- Units Of Measure
- Base API
- Dashboard Widgets
- Hook System
- Role & Permissions
- NsMultiStore Api
- Make Jobs MultiStore Compatible
- Register Web & API Routes For MultiStore
- Updating Migrations
- Filters
- {namespace}-bulk
- {namespace}-catch-action
- {namespace}-crud-actions
- ns-crud-resource
- ns-dashboard-menus
- ns-dashboard-widgets
- ns-footer-signature
- ns-page-title
- ns-products-crud-form
- ns-products-history-operation
- ns-products-type
- ns-table-name
- ns-views:pages.sign-in
- ns-views:pages.sign-up
- ns-web-receipt-template
- ns.forms
- How To's
- Changing Domain
- Checkout Popup
- Database Configuration
- Email Configuration
- Enable Low Stock Notification
- Installing And Updating A Module
- Installing NexoPOS 4.x On Laragon
- Installing NexoPOS 4.x On Plesk
- Installing NexoPOS 4.x Using The cPanel
- Installing NexoPOS On Hostinger
- Link Nexo Print Server To NexoPOS 4.x
- Local Network Configuration
- Manage Customers On The POS
- Manage Sales Refunds
- Manual Module Installation
- Orders With Instalments
- Rebranding NexoPOS 4.x
- Translating NexoPOS
- Updating NexoPOS 4.x
- Using The Sales Filter
- Javascript API
- nsHttpClient
- nsNotice
- nsSnackBar
- Actions
- ns-crud-footer
- ns-dashboard-footer
- ns-dashboard-pos-footer
- ns-dashboard-settings-footer
- My NexoPOS
- Assign Print Jobs
- Cloud Print Setups
- Creating My NexoPOS Clients
- Deactivating Nexo Print Server 2.6 License
- Linking My NexoPOS To Envato
- Nexo Print Server 2.6.x License Validation
- NexoPOS 3.x License Validation
- Developpers Guides
- Add Create Button On <search-select/>
- Add Crud Entry Custom Action
- Add Crud Header Buttons
- Cart Custom Buttons
- Creating A Sample Hello World Page
- Creating Crud Components
- Creating Custom Pages
- Creating Custom Print Handler
- Creating Settings Page
- Dashboard Theming
- Database Migration
- Generating Modules
- Handle Crud Actions Using JavaScript
- Injecting Vue Component
- Model's Dependency
- Module's config.xml File
- Module's Routing
- Register Dashboard Menus
- Render Field As Vue Component
- Reset User Password With Tinker
- Service Provider
- Troubleshooting
- Broken Media Images
- Common Database Issues
- Conflicting Dashboard
- CSRF Token Mismatch On NexoPOS 4.x
- Disabling Modules Manually
- Environment Misconfiguration
- Gastro Empty Receipts
- Images Not Loading
- No Dashboard
- No Default Customer
- Products Not Appearing For Sale
- Products Not Showing On The POS
- Queues Jobs Are Disabled
- Using Nexo Print Server With SSL
- Gastro Guides
- Managing Modifiers
- Crud API
- Add Crud Entry Custom Action
- Creating Crud Components
- Declare Custom Crud Export Columns
- Handle Crud Actions Using JavaScript
- Header Buttons
- Method: beforeRenderForm
- Method: getView
- Nexo Print Server
- Configuration
- Javascript Actions
- ns-before-mount
- ns-pos-pending-orders-refreshed
- ns-settings-change-tab
- ns-settings-loaded
- Events
- CrudHookEvent
- SettingsSavedEvent
ns-dashboard-settings-footer
This is an action identifier that will be triggered only when a settings page using the SettingPage class is used. This might be used to add further dynamic control on the existing page or change the existing behavior.
The action only uses two parameters which are an App\Classes\Output instance and the second is the identifier of the settings page. This action can be used to inject content at the bottom of a settings page.
Here is how it can be used.
In this example, we're injecting the content of the file located at the path modules/YourModule/Resources/Views/footer.blade.php at the bottom of any settings page.
Making use of the identifier, you can restrict which settings page that view will be injected. For example, if our module "YourModule" has a settings page having the identifier "YourModuleSettings", we can restrict it like so: