FMJ Blank View Documentation
FMJ Blank View provides a blank view component for the cases where you only have modules on a page, but need an unexpensive menu item type to display them.
- Several views are available to the user. This means that, you can choose the best view that suits your needs, and still have the most efficient code running it.
- Optimized and efficient code, in order to save CPU cycles and memory consumption. We avoid unnecessary code executions.
- Faster response times, due to code efficiency.
FMJ Blank View is a Component which is instralled the usual Joomla way.
In your Administration console:
1. Click Extensions -> Manage -> Install (or only Manage)
2. Click "Upload Package FIle", browse for the Extension File and click "Upload & Install". Done.
Simply go to the menu editor screen andselect a 'FMJ Blank View' view from in the Menu Item type field. You should start with the Simple Blank View.
3.1. Blank Views
In this section we will go through the available views in the menu item type selection.
3.1.1 Simple Blank View
- This is what you should start with. It processes all menu options and includes whichever are necessary, like: class definitions, page headers and titles, metadata, etc...
- This one is the most expensive of the views, in terms of processing and memory needs. (Still it is a lot cheaper, than doing database calls for other menu types, like "Featured Articles")
3.1.2 Totally Blank View
- This view builds upon the Simple Blank View. In addition to that, it doesn't check / include custom page classes, content titles, headers, etc...
3.1.3 Totally BlankView without Meta Data
- Displays a Totally Blank View without custom metadata - in addition to the Totally Blank View, it does not check / include custom meta data.
3.1.4 Invisible View
- Displays a Totally Blank View but also removes the output of the divs. Essentially it returns nothing from the component. It only checks and includes custom meta data.
3.1.5 Invisible View without Meta Data
- Displays a Totally Blank View without custom metadata - in addition to the Invisible View, it doesn't check / include custom meta data.
- This one is the cheapest, in terms of processing and memory needs.
3.2. Content inclusion
In this section we will go through the content inclusion options. (introduced with version 1.1.0)
Note: Content inclusion is only available on the Simple Blank View, Totally Blank View and Totally Blank View without Meta Data.
- No content will be included.
- HTML from an Editor field will be included
3.2.3 Path to HTML file
- HTML from a file will be included. The root directory for the file is the 'custom' directory inside the component's main directory. In this directory you will also find a sample of an HTML file.
3.2.4 PHP (eval())
- PHP from a textarea field will be included. Note: Use this method only as a last resort. Prefer the use of a PHP file inclusion.
3.2.5 Path to PHP file
- PHP from a file will be included. The root directory for the file is the 'custom' directory inside the component's main directory. In this directory you will also find a sample of a PHP file.