Libraries tagged by Sam User
lucasgiovanny/filament-inline-translate-field
49 Downloads
Create a beautiful key-value field to allow users to enter all possible language values for a field on the same page
canaltp/sam-ecore-user-manager-bundle
8216 Downloads
Symfony SamEcoreUserManagerBundle
samerton/flarum-ext-coloured-usernames
20 Downloads
Set the username colour to the same as the rank colour (only on posts)
ngearing/wp-user-purchase
4 Downloads
Check if user has purchased an item on same site or another
cotechsolution/laravel-access-user-account
5 Downloads
Sometimes, in you Laravel application you need to manually logging in as a different user, then switching back to their own account. This package allows you to do the same thing with the permission of that user.
horde/sam
0 Downloads
Anti-spam user preferences application
phalcana/userguide
27 Downloads
Userguide module for Phalcana project based of the module for Kohana of the same name
xini/silverstripe-userforms-confirmemailfield
120 Downloads
Adds an email confirmation field that forces the value to be the same as another email field.
tarun-singhal/page-lock
11 Downloads
For muti user access of the web-page then lock the same web page irrespective of browser using for a pre-defined time intervel.
sascha-brandhoff/logincontroll
7 Downloads
allows to adjust how often a member can login with the same account.
jroedel/zf2-juser
6 Downloads
A fork of manuakasam/SamUser. Glues together LmcUser, BjyAuthorize, SlmLocale, and GoalioRememberMe
ublaboo/https-redirect-nette-extension
3824 Downloads
Nette extension for simply redirecting user to the same url with different schema
vanthao03596/laravel-password-history
31 Downloads
Keep a password history of your users to prevent them from reusing the same password like Facebook, Google
fwrepae/fwrepae
0 Downloads
The Inter TT REST API is described using OpenAPI 3.0. The descriptor for the api can be downloaded in both [YAML](http://localhost:8080/cyclos/api/openapi.yaml) or [JSON](http://localhost:8080/cyclos/api/openapi.json) formats. These files can be used in tools that support the OpenAPI specification, such as the [OpenAPI Generator](https://openapi-generator.tech). In the API, whenever some data is referenced, for example, a group, or payment type, either id or internal name can be used. When an user is to be referenced, the special word 'self' (sans quotes) always refers to the currently authenticated user, and any identification method (login name, e-mail, mobile phone, account number or custom field) that can be used on keywords search (as configured in the products) can also be used to identify users. Some specific data types have other identification fields, like accounts can have a number and payments can have a transaction number. This all depends on the current configuration. ----------- Most of the operations that return data allow selecting which fields to include in the response. This is useful to avoid calculating data that finally won't be needed and also for reducing the transfer over the network. If nothing is set, all object fields are returned. Fields are handled in 3 modes. Given an example object `{"a": {"x": 1, "y": 2, "z": 3}, "b": 0}`, the modes are: - **Include**: the field is unprefixed or prefixed with `+`. All fields which are not explicitly included are excluded from the result. Examples: - `["a"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["+b"]` results in `{"b": 0}` - `["a.x"]` results in `{"a": {"x": 1}}`. This is a nested include. At root level, includes only `a` then, on `a`'s level, includes only `x`. - **Exclude**: the field is prefixed by `-` (or, for compatibility purposes, `!`). Only explicitly excluded fields are excluded from the result. Examples: - `["-a"]` results in `{"b": 0}` - `["-b"]` results in `{"a": {"x": 1, "y": 2, "z": 3}}` - `["a.-x"]` results in `{"a": {"y": 2, "z": 3}}`. In this example, `a` is actually an include at the root level, hence, excludes `b`. - **Nested only**: when a field is prefixed by `*` and has a nested path, it only affects includes / excludes for the nested fields, without affecting the current level. Only nested fields are configured. Examples: - `["*a.x"]` results in `{"a": {"x": 1}, "b": 0}`. In this example, `a` is configured to include only `x`. `b` is also included because, there is no explicit includes at root level. - `["*a.-x"]` results in `{"a": {"y": 2, "z": 3}, "b": 0}`. In this example, `a` is configured to exclude only `x`. `b` is also included because there is no explicit includes at the root level. For backwards compatibility, this can also be expressed in a special syntax `-a.x`. Also, keep in mind that `-x.y.z` is equivalent to `*x.*y.-z`. You cannot have the same field included and excluded at the same time - a HTTP `422` status will be returned. Also, when mixing nested excludes with explicit includes or excludes, the nested exclude will be ignored. For example, using `["*a.x", "a.y"]` will ignore the `*a.x` definition, resulting in `{"a": {"y": 2}}`. ----------- For details of the deprecated elements (operations and model) please visit the [deprecation notes page](https://documentation.cyclos.org/4.16.3/api-deprecation.html) for this version.
codeblog.pro/laravel-geo-location
52 Downloads
The package allows you to get the location of the user by his IP. The package provides the ability to use several services at the same time to increase accuracy and to increase free limits.