addedValues Plugin

...Powerful Free! Database Expansion for Manila
logoBottle:

(1 or more words)

Home
Feature Overview
FAQ
Reference
Audit Tables
Builtins
Controlpanel Addin
Preferences
Import Extensions
Trigger Actions
Transaction Postprocessors
Timed Task Actions
External Variable Scripts
Ranking Formula Scripts
Custom Renderers Configuration
Database
Export
Forms
Globals
Groups
Import
Installation
Macros
Miscellaneous
Preferences
Queries
Reports
RSS
RPC Handlers
Text Indexing
Timed Tasks
Triggers
Tropes
Updaters
User Transactions
Variables
View Values
WYSIWYG
Primer
Tutorials
Case Studies
Download
Design
Scripting API
Showcase

Get tropes here!
Click to see internals
Report bug


Maennerzeitung

sitepic_maennerzeitung.ch.jpg:
Viewable with Any Browser

Members
Join Now
Login

Custom Renderers Configuration

Placeholder pages

b290 custom renderers now have an admin site/controlpanel addin interface. All custom renderers must be enabled before use. The location of the script for the renderer can be anywhere the system administrator finds convenient; if it is in the #tools subtable of a Manila website, its use will be restricted to that website. The Custom renderers API was inherited from metadata and is unchanged, their purpose is to render a form element for one variable. Custom renderers in the legacy location (a table in the addedValues storage sub-table of each website) , will continue to work as before; however they must be installed anew in each site that uses them, whereas the server wide settings permits shared renderers.