NAMESPACE: Bootstrap/Models
BootstrapModel extends CActiveRecord
$recycleable_objects | ||
$global_recycleable | ||
$recycleable_object_names | ||
$configobj | var | Actions configuration as defined in the web admin. All these can be overriden using $this->rewriteActionConfigField() |
$debugdata | ||
$vars | var | Array of currently loaded user variables in name - id pairs. Should be accessed with the methods declared in the Variables trait, not directly. Declared public for easier debugging for certain cases. |
$varcontent | var | Includes currently loaded user variables in array. Normally you would use $this->getSavedVariable instead of accessing this directly. Declared public for easier debugging for certain cases. |
$session_storage | var | |
$click_parameters_to_save | var | |
$localizationComponent | ||
$submitvariables | var | Array containing the submitted variables for a certain request. Submitting a form using a "submit-form-content" action will allow you to access all of the form variables from this array. Usually retrieved with getAllSubmittedVariables() or getSubmittedVariableByName() methods. Should be used in the model for validation and storing. |
$actionobj | var | Array containing the configuration specified in the web admin. Fields can be rewritten using the rewriteActionField() method |
$playid | var | Currently logged in user id |
$appid | var | Current active application id |
$userid | var | Not to be confused with playid, this is installation specific id - the phone on which the app is installed |
$router | namespace | Router object instance. This is the object that instantiates the controller and wires up the view depending on the called route. |
$action_id | var | Id of the action in the web admin |
$actionid | var | Id of the currently active action |
$playtaskid | ||
$menus | var | Array containing all of the application menus. An application can have multiple menus defined for different purposes and used in different places in the app - side, top, bottom. |
$msgcount | var | |
$bottom_menu_id | var | Id of the application bottom menu |
$branchobj | var | Configuration array for the branch. Includes all configuration fields defined in the web admin. |
$validation_errors | array | This is a general place for storing validation errors. Usually used from the controller for conditional checks and to display errors. |
$permanames | var | Array consisting of action permanames (slugs) - action id pairs |
$rewriteconfigs | var | |
$rewriteactionfield | var | |
$mobilematchingobj | namespace | The model containing the matching related functionality. Matching is used not only in dating applications but in all other apps that have similar business logic i.e. tenants and properties |
$mobilematchingmetaobj | Mobilematching; | Matching meta model |
$access_token | current access token for the user | |
$notifications | NotificationsModel; | This is used for Notifications action, making it very easy to register push & email notifications. Register a new notification like this: $this->mobile_notifications->addNotification(array(to_playid=false,to_email=false,subject = '',$msg='',action_id=false,action_param='',image='',type='invitation' You can show the notifications of the user with Mobile Notificiations action. You can configure additional |
$bottom_menu_config | You can feed following kind of config array for bottom_menu_config $config['flags']['approvals'] = $this->getAdultNotificationCount();$config['flags']['notifications'] = NotificationsModel::getMyNotificationCount($this->playid);$config['background_color'] = '#ffffff';$config['text_color'] = '#000000';$config['hide_text'] = true;$config['flag_color'] = '#3EB439';$config['flag_text_color'] = '#ffffff'; |
|
$mobilesettings | ||
$query | ||
$registered_themes | ||
$bs_log_notices | ||
$bs_log_errors | ||
$bs_log_enabled | ||
$bs_log_name | ||
$force_logout | ||
$var_cache_invalidated |
$className |
This should be used instead of __construct or init()
Returns a configuration parameter as defined in action’s web configuration panel. You can rewrite any configuration parameters in your action using $this->rewriteActionConfigField(‘fieldname’,’newvalue’); Typical parameters you would use are: backarrow, background_color, hide_menubar, subject, share_title, share_description, share_image, hide_scrollbar, pull_to_refresh, transparent_statusbar
$param |
$default |
This will register information about a cache used by the app
$name |
$param | parameter to look for |
$obj | param mixed $obj takes either array or object |
$default | param bool $default default value |
$param |
$obj |
$default |
Get an array of validation errors. Errors are usually filled in from the model upon form validation.
Returns an associative array of the configuration object.
Reloads all variable data and action data
Localize a string
$string |
Get the active action’s permaname (slug) if it is set
Returns mapping between permanent name & action id
$name |
Rewrite configuration field by key
$field | - backarrow - hide_subject - hide_menubar - background_image_portrait |
$field |
$newcontent |
Reconfigure any action property
$field |
$newcontent |
This will get the current item id, as triggered initially by menuid. ie. if you use for example open-action with id, you should define id like this: controller/function/$id this id gets saved to session so it will be remembered even though you would have different menu commands inside the same context. It is tied to action_id
$session_only |
This will extract numeric part separate from the menuid and return parts for the menu string & numeric values separately.
Returns the currently called menuid if set
Current action id (not the play action, but the actual configuration object id)
Return validation error from the array by name The method would handle composite variables as well
$name |
Add error in the errors object
$string |
Return errors object
Remove routes from the session
$actionid |
$actionpermaname |
Used by infinite scrolling content. So if action is refreshed with this id set, you should return the next batch of content.
$string |
This will check whether user should be asked for touch login or not