Libraries tagged by user info

Holds information about a SlideShare user.

Go to Download

Holds information about eZ Platform users and content objects.

Go to Download

Hides the Pimcore status bar (version info and warnings) for ordinary users.

Go to Download

Provides css hooks to add to your template BODY element, generated from user state and current page meta information.

Go to Download

Defaults the author/email fields in pages and sys_notes to the info from the currently logged in user.

Go to Download

This Magento 2 modules allows admin users to delete orders with all related information such as invoices, shipments and credit memos.

Go to Download

A lightweight single-user application to securely submit and retrieve information via the web.

Go to Download

The Drupal AI Chatbot module leverages OpenAI's language models to add an intelligent chatbot to your Drupal site. It analyzes user interactions and provides real-time assistance, information retrieval, and interactive experiences for website visitors.

Go to Download

Phergie plugin for providing usage information for available bot commands to users

Go to Download

A basic PHP wrapper for adding IP based user location detection into your application using the IP Info DB API.

Go to Download

# Overview Information and statistics about FIRST Robotics Competition teams and events. # Authentication All endpoints require an Auth Key to be passed in the header `X-TBA-Auth-Key`. If you do not have an auth key yet, you can obtain one from your [Account Page](/account). A `User-Agent` header may need to be set to prevent a 403 Unauthorized error.

Go to Download

The MHinspeya Inspeya Filter ShopBy module is a powerful enhancement for Magento 2, designed to improve the catalog navigation experience on the list page. This module provides advanced layer navigation capabilities, allowing users to filter products seamlessly and efficiently. The Inspeya Filter ShopBy module is fully manageable from the Magento backend, giving store administrators complete control over the filter options and their configurations. Key features include advanced layer navigation, backend manageability, SEO-friendly filter options, flexible filter types, and performance optimization. Required dependencies include mhinspeya/backend-mod, mhinspeya/inspeya-filter-base, mhinspeya/inspeya-filter-shop-by-seo, mhinspeya/inspeya-filter-shop-by-page, mhinspeya/inspeya-filter-shop-by-brand, and mhinspeya/inspeya-filter-shop-by-base. For more information, visit https://inspeya.com.

Go to Download

The Catalog API allows users to search for and locate an eBay catalog product that is a direct match for the product that they wish to sell. Listing against an eBay catalog product helps insure that all listings (based off of that catalog product) have complete and accurate information. In addition to helping to create high-quality listings, another benefit to the seller of using catalog information to create listings is that much of the details of the listing will be prefilled, including the listing title, the listing description, the item specifics, and a stock image for the product (if available). Sellers will not have to enter item specifics themselves, and the overall listing process is a lot faster and easier.

Go to Download

Manages user sessions, allowing you to store and retrieve both persistent and temporary information between requests, such as login data, preferences, and short-term data.

Go to Download

This API describes how API client can obtain a token which is used to access various Parcel Germany APIs. Using this API is often the first step in making your API call. Preconditions You will need: * client ID (aka "API Key", obtained when you create an app in developer.dhl.com) * client secret (obtained when you create an app in developer.dhl.com) * GKP user name (obtained when setting up your business account with Parcel Germany) * GKP password (obtained when setting up your business account with Parcel Germany) Technical Information This uses an implementation of OAuth2 Password Grant (RFC 6749). After successfull usage you will: * have an opaque access token to be used for API calls afterwards * this token will have an expiration time

Go to Download