Download the PHP package quarry/customer-uuid without Composer

On this page you can find all versions of the php package quarry/customer-uuid. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of quarry/customer-uuid

Informations about the package customer-uuid

Magento 2 Customer UUID Attribute Extension

Objective

This Magento 2 extension introduces a new read-only attribute, uuid, for customers. The extension ensures the uniqueness of the UUID for each customer and automatically assigns it to existing and new customers. The uuid attribute is exposed through a public GraphQl API for authenticated users and is also be displayed in the customer grid.

Key Features and Implementation Details

  1. The extension uses UUID version 4, in accordance with Magento's best practices. UUID version 4 provides a very high probability of uniqueness due to its reliance on random values.
  2. The extension uses Magento 2's plugin architecture, to intercept customer save and update operations. During this interception, new UUIDs are assigned and existing ones are re-validated.
  3. Upon installation, the extension auto-assigns UUIDs to all the existing customers. This is implemented using Magento's data patches.
  4. After the extension is installed, all new customers created thereafter are auto-assigned a UUID, just before the customer record is committed to the database.
  5. Before any customer (new or existing) is assigned a UUID, the extension ensures that the same UUID is not assinged to another customer.
  6. To enforce data integrity, the extension always re-validates the existing UUID for a customer, whenever changes are made to the customer record, either from admin panel or storefront. If the assigned UUID is invalid, a new one is generated, validated and assigned. A UI notification is also displayed on both admin panel and storefront.
  7. UUIDs are displayed on customer grid, as read-only and are filterable, searchable and sortable.
  8. An authenticated user can read the UUID through the GraphQl API
  9. Extension logs all the UUID transactions to a log file.

Magento Compatability

This extension has been developed and tested on Magento 2 version 2.4.6-p2, with no other third-party extensions installed.

Setting-up Testing Environment

This docker-compose.yml can be used to quickly spin-up a local testing environment, with Magento 2.4.6-p2, mariadb and elastic search installed. Once the docker-compose.yml file is downloaded, docker-compose up -d can be used to download the docker images and setup the containers and volumes.

Recommended Steps Before Extension Installation

  1. Ensure that Magento installation has a few customers created. This will allow the extension to auto-assign UUID during installation.
  2. The extension logs all UUID transations to <magento_root>/var/log/quarry_customeruuid.log. Please ensure this log file has write-permissions enabled. If not, the extension falls back to PHP's system logger.

  3. Enable Magento's developer mode

  4. Disable Magento's cache

Extension Installation Process

  1. Install the extension using composer:

  2. Flush Magento's cache

  3. Clean Magento's cache

  4. Enable the UUID extension

  5. Run Magento setup upgrade:

  6. Run di compile:

Verify the Extension Installation

1. Existing customers are auto-assigned UUID during extension installation.

Expected outcome:

  1. Customer grid, should show a new column labelled UUID, with UUIDs assigned to all the existing customers.
  2. These read-only UUIDs must be filterable, searchable and sortable in the customer grid. customer-grid
  3. Log file should show all the exsiting customer IDs, to whom new UUIDs have been assigned. Log entry message should be in following format:

2. New customers created from admin panel, are auto-assigned UUID

Expected outcome:

  1. The new customer record must show up in the customer grid, with a UUID assigned.
  2. The log file should contain an entry for this transaction. Log entry message should be in following format:

2. New customers created from storefront, are auto-assigned UUID

Expected outcome:

  1. The new customer record should show up in the admin customer grid, with a UUID assigned.
  2. The log file should contain an entry for this transaction. Log entry message should be in following format:

3. UUID is accessible through GraphQl API, for authenticated users.

For authenticated users, UUID is accessible via GraphQL API on the Customer object. Magento's GraphQl endpoint is /graphql and can be accessed at http://<your-domain.com>/graphql. It is recommended to use a GraphQl client like Postman to access this endpoint.

First, a bearer toekn must be obtained by calling GenerateCustomerToken mutation. Example:

Next, this auth token must be passed along with the GraphQl query to retrieve UUID. Sample GraphQl query to retrieve UUID:

Below is a sample response to the above GraphQl query:

Extension Uninstallation Process

  1. Disable the UUID extension

  2. Uninstall the UUID extension

  3. Remove the extension using composer:

  4. Flush Magento's cache

  5. Clean Magento's cache

  6. Run Magento setup upgrade:

  7. Run di compile:

All versions of customer-uuid with dependencies

PHP Build Version
Package Version
Requires php Version ^8.0
ramsey/uuid Version ~4.7.4
magento/module-customer Version ^103.0.6-p2
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package quarry/customer-uuid contains the following files

Loading the files please wait ....