Libraries tagged by unpor
unprefix/unprefix-functions
344 Downloads
WordPress Utility Functions
mimmi20/browscap-php-unsorted
87 Downloads
Standalone replacement for php's native get_browser() function
johndwells/dotall-2022
1 Downloads
Active Search Demo as part of my talk for Dot All 2022
blockchaininstitute/jwttools
17 Downloads
This library provides tools for working with JWTs and uPort Decentralized IDs.
onlyongunz/renton-php
4 Downloads
Jadwal Student Portal to JSON Object
unprefix/template-loader
178 Downloads
A simple hookable template loader for WordPress. Allow you to load templates in chain from child to plugin.
unprefix/nonce
6 Downloads
A OOP wrapper for WordPress Nonce
unkorneglosk/flarum-age-check
77 Downloads
Adds a modal that blocks site access until user accepts modal. Used for age verification or critical announcements.
unforgivencl/larachileanlaw
7 Downloads
Provides an wrapper to leychile.cl with Laravel 5.3.
unforgivencl/larachileancongress
9 Downloads
Provides an wrapper to opendata.congreso.cl with Laravel 5.3.
unprefix/bem
447 Downloads
Bem convention as class
zeopix/itinerary-sorter
6 Downloads
A PHP Library that sorts a itinerary given a unordered set of boarding cards — Edit
unamatasanatarai/lara-jungle
31 Downloads
Laravel mish mash of unsorted usable things
px/backend
21 Downloads
pxBackendBundle lets you create administration backends for Symfony applications with unprecedented simplicity.
nodeum-io/nodeum-sdk-php
0 Downloads
The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>