Libraries tagged by success page

Order Success Page GraphQL is a part of MageINIC Order Success Page extension that adds GraphQL features. This extension extends Order Success Page definitions.

Go to Download

Order Success Page by MageINIC, Order Success Page extension empowers you to create a personalized Thank You Page tailored to your store. It offers a comprehensive order summary, transparent shipping information, and the ability to add custom text. Enhance the post-purchase experience and communicate professionally with your customers.

Go to Download

Hyva Order Success Page by MageINIC, Hyva Order Success Page extension empowers you to create a personalized Thank You Page tailored to your store. It offers a comprehensive order summary, transparent shipping information, and the ability to add custom text. Enhance the post-purchase experience and communicate professionally with your customers.

Go to Download

Bss Order Details Module

Go to Download

Simple counter for landing pages

Go to Download

This extension for Magento >=2.4 implements a billiger.de tracking pixel on checkout success page.

Go to Download

Magento 2 Module for add message in success page

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.43) is used. For example, calling `/info` is the same as calling `/v1.43/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.41) is used. For example, calling `/info` is the same as calling `/v1.41/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

Display notices in WordPress administration panel.

Go to Download

The 'Modehaus Employee' module for Magento enables retail organizations to spotlight their employees, fostering a sense of community and trust among customers. This module provides a dedicated space within the Magento store where businesses can feature profiles of their team members, including their roles, expertise, and personal backgrounds. Key Features: 1. Employee Profiles: Create comprehensive profiles for each team member, including their name, position, bio, and a photo. 2. Role-Based Filtering: Allow customers to filter employees based on their roles or departments within the organization. 3. Customizable Templates: Customize the layout and design of employee profiles to match the branding and aesthetics of your store. 4. Social Integration: Optionally include links to employees' social media profiles to encourage engagement and connection. 5. SEO-Friendly: Ensure that employee profiles are optimized for search engines, helping to improve visibility and attract organic traffic. 6. Easy Management: Easily add, edit, or remove employee profiles through a user-friendly interface within the Magento admin panel. 7. Responsive Design: Ensure a seamless browsing experience for customers on all devices, including desktops, tablets, and smartphones. With the 'Modehaus Employee' module, retailers can humanize their brand and build stronger relationships with customers by highlighting the talented individuals who contribute to their success.

Go to Download

The 'Modehaus Employee' module for Magento enables retail organizations to spotlight their employees, fostering a sense of community and trust among customers. This module provides a dedicated space within the Magento store where businesses can feature profiles of their team members, including their roles, expertise, and personal backgrounds. Key Features: 1. Employee Profiles: Create comprehensive profiles for each team member, including their name, position, bio, and a photo. 2. Role-Based Filtering: Allow customers to filter employees based on their roles or departments within the organization. 3. Customizable Templates: Customize the layout and design of employee profiles to match the branding and aesthetics of your store. 4. Social Integration: Optionally include links to employees' social media profiles to encourage engagement and connection. 5. SEO-Friendly: Ensure that employee profiles are optimized for search engines, helping to improve visibility and attract organic traffic. 6. Easy Management: Easily add, edit, or remove employee profiles through a user-friendly interface within the Magento admin panel. 7. Responsive Design: Ensure a seamless browsing experience for customers on all devices, including desktops, tablets, and smartphones. With the 'Modehaus Employee' module, retailers can humanize their brand and build stronger relationships with customers by highlighting the talented individuals who contribute to their success.

Go to Download

The 'Modehaus Employee' module for Magento enables retail organizations to spotlight their employees, fostering a sense of community and trust among customers. This module provides a dedicated space within the Magento store where businesses can feature profiles of their team members, including their roles, expertise, and personal backgrounds. Key Features: 1. Employee Profiles: Create comprehensive profiles for each team member, including their name, position, bio, and a photo. 2. Role-Based Filtering: Allow customers to filter employees based on their roles or departments within the organization. 3. Customizable Templates: Customize the layout and design of employee profiles to match the branding and aesthetics of your store. 4. Social Integration: Optionally include links to employees' social media profiles to encourage engagement and connection. 5. SEO-Friendly: Ensure that employee profiles are optimized for search engines, helping to improve visibility and attract organic traffic. 6. Easy Management: Easily add, edit, or remove employee profiles through a user-friendly interface within the Magento admin panel. 7. Responsive Design: Ensure a seamless browsing experience for customers on all devices, including desktops, tablets, and smartphones. With the 'Modehaus Employee' module, retailers can humanize their brand and build stronger relationships with customers by highlighting the talented individuals who contribute to their success.

Go to Download