Users with Administration rights will have access to the Settings panel from the top menu. Through the settings panel, the Administrator can configure the application’s main settings.

The settings are currently divided into four sections:

1. Application settings
2. Payment settings
3. Update settings
4. White label

1. Application settings

This tab contains all the general application settings.

• elements_dir
  The directory where all your element HTML files are stored. This value is relative to the directory in which you installed the application. Do not add a trailing “/”.
• images_dir
  This is the main directory for the images used by your elements. The images located in this directory belong to the administrator and can not be deleted by regular users. This directory needs to have full read and write permissions!
• images_uploadDir
  This directory is used to store images uploaded by regular users. Each user will have his/her own directory within this directory. This directory needs to have full read and write permissions!
• upload_allowed_types
  The types of images users are allowed to upload, separated by “|”.
• upload_max_size
  The maximum allowed file size for images uploaded by users. This number is represents the number of kilobytes. Please note that this number of overruled by possible server settings.
• upload_max_width (depreciated!!)
  The maximum allowed width for images uploaded by users.
• upload_max_height (depreciated!!)
  The maximum allowed height for images uploaded by users.
• images_allowedExtensions
  These allowed extensions are used when displaying the image library to the user, only these file types will be visible.
• export_pathToAssets
  The collection of asset paths included in the export function. These paths are relative to the folder in which the application was installed and should have NO trailing “/”. The paths are separated by “|”.
• export_fileName
  The name of the ZIP archive file downloaded when exporting a site. We recommend using the “.zip” file extension (others might work, but have not been tested).
• language
  “english” by default. If you’re changing this to anything else, please be sure to have all required language files translated and located in the correct folder inside “/application/languages/yourlanguage”.
• google_api
  Valid Google Maps API key which will enable the Google Map functionality in the application.
• custom_fonts
  A JSON object containing Google fonts to be used in the application. A sample configuration can be found within the application.

2. Payment settings

This tab contains all the payment related settings.

• paypal_api_username
  PayPal API username, required if you want to charge users for subscriptions using PayPal. For more information on how to retrieve this username, please have a look here.
• paypal_api_password
  PayPal API password, required if you want to charge users for subscriptions using PayPal. For more information on how to retrieve this password, please have a look here.
• paypal_api_signature
  PayPal API signature, required if you want to charge users for subscriptions using PayPal. For more information on how to retrieve this password, please have a look here.
• paypal_test_mode
  Switch allowing Administrators to switch between live and test mode. Test mode can be used to test whether your PayPal payments are setup correctly.
• payment_gateway
  Allows Administrators to switch between Stripe and PayPal.
• stripe_secret_key
  Your Stripe API secret key. For more information about how to retrieve your secret key, please have a look here.
• stripe_publishable_key
  Your Stripe API publishable key. For more information about how to retrieve your publishable key, please have a look here.
• stripe_test_mode
  Switch allowing Administrators to switch between live and test mode. Test mode can be used to test whether your Stripe payments are setup correctly.

3. Update settings

This tab contains all the settings related to automated updates.

• auto_update
  Switch allowing Administrators to turn on/off the auto update functionality. When turned off, the application will not attempt to update whenever there is an update available. For the auto update to be turned on and functioning properly, a valid license key must be provided as well.
• license_key
  A valid license key is required in order for the application to perform automated updates. License keys are provided by email whenever a license is purchased. If you’re not sure what your license key is, if you have lost your license key or if you have never received a license key, please reach out to Bloxby support at [email protected].

4. White label settings

This tab contains settings related to white-labeling your copy of Bloxby; it allows you to modify the logo, colors and add custom css.

• Logo
  Administrators can either upload a logo image or provide logo text. If both are provided, the image logo will be displayed.
• Colors
  This panel allows Administrators to customize a selection of colors which affect the entire application.
• Custom CSS
  Administrators can provide their own custom CSS to override additional default values. Custom CSS is loaded after customized colors are loaded, so custom CSS would override any custom colors.