Libraries tagged by user delete

eZ Publish 4 extension to display or delete notifications for users

Go to Download

A simple Laravel package to log Eloquent model create, update, and delete activities with user tracking.

Go to Download

Very simple package to log user activities. Aim is to capture which object was created / updated / deleted by which user. Package it self has no relation implemented and stores whatever is passed.

Go to Download

Allows users to self-register and self-delete an unite cms user account.

Go to Download

A Laravel package for managing user bookmarks, allowing users to save, view, and delete bookmarks

Go to Download

cms is a very simple and lightweight blogging system that lets you write content as well as delete, update and approve user comments. With admin panel

Go to Download

This is a simple PHP CLI application that performs basic CRUD (Create, Read, Update, Delete) operations on a user table in a MySQL database using PDO (PHP Data Objects). The script interacts with the database through a Command-Line Interface (CLI) and outputs results as JSON in the terminal.

Go to Download

A Filament package is a reusable software library for PHP that provides logging and tracking functionality for CRUD operations and user interactions. It includes a logging class to capture create, read, update, delete actions, as well as user interactions like login and logout.

Go to Download

SystemRoles is a Laravel Role Management package designed to simplify user role and permission management within Laravel applications. It provides a structured approach for defining roles, assigning rights to each role (e.g., edit, delete, approve), linking roles to users, and mapping roles to controllers for precise access control.

Go to Download

This project provides a restful API for managing articles on a news site. It allows users to create, read, update, and delete articles efficiently.

Go to Download

Provides attachment of active user ID to create/update/delete operations.

Go to Download

The Magento 2 Cancel Order By Customer extension allows user to cancel the order from front end. Now customer can easily cancel or delete the order from my account or dashboard page.

Go to Download

Give users with the Editor role the Gravity Forms capabilities to control 'entries' (view, edit, delete, export) and 'entry notes' (view, edit).

Go to Download

**API Version**: 1.7 **Date**: 9th July, 2024 ## 📄 Getting Started This API is based on the REST API architecture, allowing the user to easily manage their data with this resource-based approach. Every API call is established on which specific request type (GET, POST, PUT, DELETE) will be used. The API must not be abused and should be used within acceptable limits. To start using this API, you will need not create or access an existing Segnivo account to obtain your API key ([retrievable from your account settings](https://messaging.segnivo.com/account/api)). - You must use a valid API Key to send requests to the API endpoints. - The API only responds to HTTPS-secured communications. Any requests sent via HTTP return an HTTP 301 redirect to the corresponding HTTPS resources. - The API returns request responses in JSON format. When an API request returns an error, it is sent in the JSON response as an error key or with details in the message key. ### 🔖 **Need some help?** In case you have questions or need clarity with interacting with some endpoints feel free to create a support ticket on your account or you can send an email ([[email protected]](https://mailto:[email protected])) directly and we would be happy to help. --- ## Authentication As noted earlier, this API uses API keys for authentication. You can generate a Segnivo API key in the [API](https://messaging.segnivo.com/account/api) section of your account settings. You must include an API key in each request to this API with the `X-API-KEY` request header. ### Authentication error response If an API key is missing, malformed, or invalid, you will receive an HTTP 401 Unauthorized response code. ## Rate and usage limits API access rate limits apply on a per-API endpoint basis in unit time. The limit is 10k requests per hour for most endpoints and 1m requests per hour for transactional/relay email-sending endpoints. Also, depending on your plan, you may have usage limits. If you exceed either limit, your request will return an HTTP 429 Too Many Requests status code or HTTP 403 if sending credits have been exhausted. ### 503 response An HTTP `503` response from our servers may indicate there is an unexpected spike in API access traffic, while this rarely happens, we ensure the server is usually operational within the next two to five minutes. If the outage persists or you receive any other form of an HTTP `5XX` error, contact support ([[email protected]](https://mailto:[email protected])). ### Request headers To make a successful request, some or all of the following headers must be passed with the request. | **Header** | **Description** | | --- | --- | | Content-Type | Required and should be `application/json` in most cases. | | Accept | Required and should be `application/json` in most cases | | Content-Length | Required for `POST`, `PATCH`, and `PUT` requests containing a request body. The value must be the number of bytes rather than the number of characters in the request body. | | X-API-KEY | Required. Specifies the API key used for authorization. | ##### 🔖 Note with example requests and code snippets If/when you use the code snippets used as example requests, remember to calculate and add the `Content-Length` header. Some request libraries, frameworks, and tools automatically add this header for you while a few do not. Kindly check and ensure yours does or add it yourself.

Go to Download

Package for logging users actions on database and enable to know who has created, updated or delete some line in a table and see data before this action

Go to Download