AdminAddArticleCategoryAjaxAction Class Reference
[Action]


Public Member Functions
	AdminAddArticleCategoryAjaxAction ($actionInfo, $request)
	validate ()
	perform ()
Public Attributes
	$_categoryName
	$_categoryUrl
	$_properties
	$_categoryDescription

Detailed Description

Action that adds a new article category to the database.

Definition at line 14 of file adminaddarticlecategoryajaxaction.class.php.

Member Function Documentation

AdminAddArticleCategoryAjaxAction.AdminAddArticleCategoryAjaxAction	(	$	actionInfo,
		$	request
	)

Constructor. If nothing else, it also has to call the constructor of the parent class, BlogAction with the same parameters

Definition at line 26 of file adminaddarticlecategoryajaxaction.class.php.

References $request, and AdminAction.AdminAction().

AdminAddArticleCategoryAjaxAction.perform ( )

Carries out the specified action

Reimplemented from Action.

Definition at line 53 of file adminaddarticlecategoryajaxaction.class.php.

References $categories, $catId, $result, AdminAction.notifyEvent(), and CacheControl.resetBlogCache().

AdminAddArticleCategoryAjaxAction.validate ( )

This method can be used for data validation and is always executed before perform(). If it returns 'true', execution will continue as normal. If it returns 'false', the process will be stopped and the current contents of the view will be returned. If the view is empty, an exception will be thrown.

As of pLog 1.0, it is not necessary to implement data validation code here and it is recommended to use the data validation framework (see methods Action.registerFieldValidator() and related) There is more information about the data validation framework in the wiki: http://wiki.plogworld.net/index.php/PLog_1.0/Forms_and_data_validation.

With the default code provided in the Action.validate() method, the callback method Action.validationErrorProcessing() will be called and after that, the view set via the Action.setValidationErrorView() will be used to generate the contents of the error message.