Recently Browsing 0 members
- No registered users viewing this page.
AppApiFile adds the /file endpoint to the AppApi routes definition. Makes it possible to query files via the api.
This module relies on the base module AppApi, which must be installed before AppApiFile can do its work.
You can access all files that are uploaded at any ProcessWire page. Call api/file/route/in/pagetree?file=test.jpg to access a page via its route in the page tree. Alternatively you can call api/file/4242?file=test.jpg (e.g.,) to access a page by its id. The module will make sure that the page is accessible by the active user.
The GET-param "file" defines the basename of the file which you want to get.
The following GET-params (optional) can be used to manipulate an image:
width height maxwidth maxheight cropX cropY Use GET-Param format=base64 to receive the file in base64 format.
This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
The API consists of a number of predefined functions, some of which include...
render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for for modifying the stored value by the value (converted as required) in another measurement. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.
A simple length field using Fieldtype Measurement and Inputfield Measurement.
Combination units (e.g. feet and inches) are also supported.
Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.
This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
ACE code editor
This module uses ACE code editor available from: https://github.com/ajaxorg/ace
PHP File Manager
This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
Create an account
Open the module settings
The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.
Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.
The following conditions must be met for the module to work properly:
Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.
The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.
ProcessWire module directory