The conf/site.php contains all your parameters.
Site Configuration File
All of your settings are normally read from the conf/site.php. But while your site is in production (live), you might want to edit settings “offline” to test new features (not showing these pages to your visitors).
In such cases, you may add “?dev=1” to any of you website's URL in order to use an alternate configuration file. In this case, the configuration file used would be conf/site_dev.php instead of the regular conf/site.php.
All configuration parameters are stored in the $pvw_conf array, like this :
$pvw_conf['site_name'] ="YourCompanyName"; $pvw_conf['baseline'] ="We are the best"; $pvw_conf['navbar_width'] ='2'; $pvw_conf['emails']['support'] ="email@example.com";
if not set or empty, most setting values (except “id”, “site_name” and “baseline”) are automatically filled with predefined default values.
Example: if you set 'navbar_width' to '2', the '2' value will be used. If you ommit this, the default value of '1' will be used.
Check current Values and Descriptions from Private
You may list all parameters and their current values (set by you or by default) from your Private area located in the Web menu and the Hosting Configuration tab at http://private.plugivery.com/web/#tab_web_pvw .
Each parameter effect is clearly explained within that page.
are stored in : $pvw_conf['emails']
If a visitor uses the contact form to reach a certain department on your website such as “customer support” or “general inquiries”, his message will be sent to the corresponding email addresses set as :
$pvw_conf['emails']['general'] ="firstname.lastname@example.org"; $pvw_conf['emails']['support'] ="email@example.com";
Are stored in : $pvw_conf['widgets']
Wigets are snipsets of code (mainly external) that provide extra features for your website. By default, they are all deactivated. Here is the list of all available widgets :
- share : Adds a well known “Share” widget printed on the left or right side of the page.
- share2 : Same as the “Share” widget but it is located inside of the page, near the title.
- share_news : Is an other “share” widget that allows to share news individually instead of the whole News listing page. It is printed near each News title within the News view.
- follow : Adds a “Follow” widget printed on the top of the page.
- fb_like : Is a Facebook “LikeBox” that can be inserted within Boxes.
To activate each widget, set its 'on' parameter value to 1. Set your own parameter values to override the widgets default values.
In example : To active the share widget with 10 icons (instead of the default value of 5), simply add :
$pvw_conf['widgets']['share']['on'] =1; $pvw_conf['widgets']['share']['numPreferredServices'] =10;
Are stored in : $pvw_conf['sections']
The site is organized by sections listed in the navigation's top bar (navbar). Possible sections are :
- home Contains the home page only.
- products Can contain the following pages :
- software : A list of all your software.
- bundles : A list of all your bundles.
- news Can contain the following pages :
- blog : A news blog for posting news, updates, releases, etc.
- videos : All of Your latest YouTube Videos.
- facebook : An external link to your Facebook Page.
- twitter : An external link to your Twitter Page.
- support Can contain the following pages :
- faqs : An FAQ page build from your FAQS configuration file
- forums : An external link to your Forums.
- downloads : A download center with all of your latest product versions.
- about Can contain the following pages :
- company : A description of your company
- press : A page intended for press medias, containing your latest presse releases and media material ready to be downloaded.
- contact : A contact form.
Each sections can be activated (or not) and will be sorted in the order defined in the 'sections_on' array. If this is not set, all sections will be displayed by default. Example :
Each section has its own parameters that, as always, has default values that can be overridden using the site configuration (See your Private page to see their current values). For each section you can set :
- menu_name : The name shown in the Navigation Bar.
- title : The title of the section (visible in the section Index)
- html_title : The browser's window title of the section (visible in the section Index)
- meta_desc : Meta “description” tag content
- meta_keys : Meta “keywords” tag content
$pvw_conf['sections']['about']['menu_name'] ="About MyCompany"; $pvw_conf['sections']['products']['meta_keys']="software,audio,vst,plugins,rtas,music";
Are stored in : $pvw_conf['pages']
Each section can contain one or more pages, defined and sorted according to the 'pages_on' array indexed by sections. By default, all factory pages are shown, but you can limit it to the page you want by setting the pages_on for each section.
Note that if a section contains only ONE page, the section will be replaced by that page
Each page has the following parameters (set by default, or overriden by you) :
- title : The title of the page.
- html_title : The browser's window title.
- intro : A short text displayed within the index section, under the title of the page.
- menu_name : The name of the page displayed in the Navbar menu.
- fa_icon : Another icon to be displayed within various menus.
- meta_desc : Page meta “description” tag content.
- meta_keys : Page meta “keywords” tag content.
$pvw_conf['pages']['about']['contact']['title'] ="Contacting MyCompany"; $pvw_conf['pages']['products']['bundles']['meta_desc']="All bundles made by MyCompany";
If you need to create “custom” pages, you may define these using any HTML content as needed. You simply need to create the page definition in the pages array and enable them from the pages_on array in the corresponding section.
$pvw_conf['pages']['about']['our_jobs']['title'] ="Jobs at MyCompany"; $pvw_conf['pages']['about']['our_jobs']['content'] ="We're hiring a cool developper"; $pvw_conf['pages_on']['about'] =array('company','our_jobs','contact');
In this example we created an our_jobs page, linked from the about section at the url : /about/our_jobs.
Note : The page index name (our_jobs in this example) must NOT be one of the factory default pages as it would be ignored. Moreover, as we will regulary add new factory pages with unique index name, we advice that you choose index names that will never match future factory page names. You may therefore want to Prefix pages using “mycompany” name or use custom_ or our_ as shown in the example above) which would certainly be a good update-safe name to use.