API documentation

Table Of Contents

Previous topic

< Role management

Next topic

Menus >

This Page

Dynamic pages

Dynamic pages allow Administrators to chose a layout from 12 pre-defined sets and add content without the need for knowledge of any programming language.

../../_images/pages_1.png

You can see the type of layout for each page in “Layout” column.

Adding and editing pages

To create a new page - navigate to “Create new page”.

../../_images/pages_2.png

Fields description:

Title - will be used as HTML Title of the page as well as to identify page in grid.

Url - identify how your page will be accessible from the internet. It must be a relative Url so it can not start with ‘http’ or ‘/’. Example 1: If you set Url as “test” the page will be available at address: http://yoursite.com/page/test . Example 2: If Url is “some-long-page/with/id/1” a full link to the page will be: http://yoursite.com/page/some-long-page/with/id/1 .

Description - used for metadata of the page <meta name=”description” content=”YOURCONTENT”>

Keywords - used for metadata of the page <meta name=”keywords” content=”YOURCONTENT”>

Controller - Developers can use this feature to forward request to specific MVC controller. Imaging that there is ShopPaypalController which performs Paypal checks before page dispatch and WebmoneyController that also performs some Webmoney checks before dispatch. And you have dynamic page with widgets, that have some resolved logic depending on controller. You can set PaypalController->indexAction to perform Paypal checks at this page. This action (and initialization method) will be performed before page rendering.

Roles - Enables you to set up restrictions for given Roles . By default everyone will be able to access the page, that is, if you select none or all of the Roles. Selecting a single Role will only allow access for users assigned to it.

Header and Footer are two specific “Page areas” in the CMS for whose the above settings can not be edited. These as well as the “Home page” are integrated into the CMS and cannot be removed.

Page management

Pages consist of widgets which are the basic build blocks in PhalconEye that perform a specific function such as displaying Menu or Social Icons. You will find widgets in WordPress, Joomla and Drupal call them modules. Widgets can be easily dragged and dropped into a specific widget area within the layout.

../../_images/pages_3.png

List of available widgets is located on the left of management page. Widgets can be part of modules and be displayed under appropriate module name (eg. Menu and Header widgets belong to Core module). They can also be installed as standalone packages and will be displayed under “Other” (see Recentblogs widget above).

Right next to list of available widget you can see the layout you have chosen for your page - this is the drop area for widgets.

Adding new widget - Simply drag a widget from the left area and drop it onto any part of the layout. It is also possible to re-arrange widgets which have already been dropped by dragging and dropping them elsewhere.

Remove widget - Simply click ‘X’ link from within the widget.

Edit widget - Almost all widgets have their options. To edit them, click ‘Edit’ link within the widget and you will see a form with options:

../../_images/pages_4.png

Once you have done editing widget’s parameters, “Save” button becomes active. Note that you can configure multiple widgets at the same time, but all the changes will take effect only if you save the layout:

../../_images/pages_5.png

Page layout can be changed at any time:

../../_images/pages_6.png

Be careful, though, when doing so! When a newly chosen layout has less columns than current, some of them might be lost permanently with all its widgets and their saved parameters.

To avoid that you can temporarily move elsewhere widgets from the column which is about to be removed.

@TODO: Describe precedence of which columns are removed.