Database Hostname - IP or hostname of your database server (normally "localhost").

Database Name - name of the database where In-Portal will be installed.

Database User Name - name of the user for selected database.

Database User Password - password for selected username.

Database Collation - character set used to store data in text fields (normally "utf8_general_ci").

Prefix for Table Names - specified when multiple scripts will be run in the same database. Prefix can be any text string allowed in table naming by your database engine (normally "inp_").

Use existing In-Portal installation setup in this Database - select "Yes" if you already have In-Portal installed in this database and want to use it. Select "No" in all other cases.

]]> In-Portal is an Open Source object-oriented framework that is developed in PHP and provides a quick and easy way to build websites and web applications.

In-Portal is copyrighted and distributed under GPLv2 license.

GPL / Open Source License - by downloading and installing In-Portal under GPLv2 license you understand and agree to all terms of the GPLv2 license.

Upload License File - if you have obtained Commercial Modules or Support from Intechnic you will be provided with a license file, upload it here.

Use Existing License - if a valid license has been detected on your server, you can choose this option and continue the installation process.

]]> In-Portal is an Open Source object-oriented framework that is developed in PHP and provides a quick and easy way to build websites and web applications.

In-Portal is copyrighted and distributed under GPLv2 license.

GPL / Open Source License - by downloading and installing In-Portal under GPLv2 license you understand and agree to all terms of GPLv2 license.

Download from Intechnic Servers - if you have obtained Commercial Modules or Support from Intechnic you will be provided with a license, specify your Username and Password in order to download the license.

]]> Select the domain you wish to install In-Portal on.

The Other option can be used to install In-Portal other custom domains. Note that your web server should match entered domain name.

]]> The Root Password is initially required to access the Admin Console of In-Portal. The root user can NOT be used to access the Front-end of your In-Portal website.

Once installation is completed it's highly recommented to create additional users with admin privlidges.

]]> Current step lists all In-Portal Modules that were found on your server and can be installed now.

Additional In-Portal Modules can be found and downloaded here.

While In-Portal Community constantly works on improving In-Portal by creating new functionality and releasing new modules we are always looking for new ideas and Your help so we can make In-Portal even better software!

]]> In-Portal Installer checks through the system folders and files that require write permissions (777) to be set in order to run successfully In-Portal on your website.

In case if you see a Failure notice saying that In-Portal Installation cannot continue until all permissions are set correctly please continue reading below.

Permissions can be set by using FTP program or directly in shell running "chmod" command. Please refer to the following guide to learn how to set permissions using your FTP program. In case if you have access to shell in your account you can simply run fix_perms.sh files located in /tools folder or do

   # chmod -R 777 ../system ../themes ../system/config.php

Security reasons you will be asked to change permissions back to 755 on /system/config.php file and root / folder of In-Portal on the last step of this installation process!

]]> Adjust Basic Configuration settings on this step.

Once your In-Portal is installed you can login into Admin Console to change these and other settings. The Configuration section is located in main navigation menu.


Additional Recommendations:

1. Use Cron (UNIX/BSD/Linux) or Task Scheduler (Windows) to run Regular Events in your In-Portal.
It's highly recommended to setup your cron to run every minute so all system events that are enabled will run in the background based on their schedule. These events can be managed in Admin Console via Configuration -> Website -> Scheduled Tasks section.

In-Portal cron file is located in /tools/cron.php folder and can be setup using hosting Control Panel or manually. In Plesk or CPanel interfaces use dialog to add a new cron job and specify the following (use correct paths)
   /absolute/path/to/bin/php -f /absolute/path/to/in-portal/tools/cron.php

2. Adjust Scheduled Tasks
As was explained in the previous recommendation there is a Configuration -> Website -> Scheduled Tasks section where you can control Events triggered by the system. These events do their job to cleanup the data, old image files, check the data integrity, RSS feeds and other processes required for your In-Portal to run efficiently. We do recommend to review and enable/disable these events based on your website needs.

3. Set Mail Server
It's recommended to review and adjust your mail server settings once your In-Portal is up and running. This can be done in Admin Console under Configuration -> Website -> Advanced section.

We strongly recommend carefully reviewing and adjusting all settings under Configuration -> Website section!

]]> These are system advanced settings and must be changed with caution. It's not recommended to change these settings unless you exactly know what you are doing. These settings will be stored in system/config.php file and can be changed manually if needed.


Web Path to Installation - web path to the root of your In-Portal installation. For example, if your In-Portal will be running at http://www.your-website.com, then Web Path to Installation should be left empty since In-Portal is setup in the root of the domain. In case if your In-Portal will be running under http://www.your-website.com/in-portal/, then it should be set to /in-portal (no trailing slash). This setting is auto-detected during the initial installation step, but can be adjusted at Installation Maintenance step.

Path to Writable folder - path to a folder inside your In-Portal installation which can be accessed from the Web and has writable permissions for the web server. This folder will be used to store dynamic content such as uploaded and resized images, cached templates and other types of user files. The default value is /system.

Path to Restricted folder - path to a folder inside or outside your In-Portal installation which will used to store debug files, system logs and other non-public information. This folder must be writable by the web-server and can be located outside of your In-Portal installation if needed. The default value is /system/.restricted .

Path to Admin folder - web path to your In-Portal Admin Console folder. The default value is set to /admin and your Admin Console will be accessible at http://www.your-website.com/admin. In case if you want your Admin Console to be under http://www.your-website.com/secure-admin (or anything else) you'll need to rename original admin folder to secure-admin on your filesystem and then set this path to /secure-admin .

Path to Admin Interface Presets folder - path to a folder inside your In-Portal installation contains Admin Interface Presets. The default value is /admin .

Name of Base Application Class - default value is kApplication and can change very rarely.

Path to Base Application Class file - default value is /core/kernel/application.php and can change very rarely.

Output Caching Engine - provides ability to cache HTML output or other data using various caching engines to lower the database load. The default value is set to None if no available engines detected. Available options are: None (Fake), Memcached (Memcache), XCache (XCache) and Alternative PHP Cache (Apc). Note that only auto-detected caching engines will be available for selection.

Location of Memcache Servers - host or IP address with port where Memcached Server is running. Multiple locations of can be listed separated by semi-colon (;). For example, 192.168.1.1:1121;192.168.1.2:1121;192.168.1.3:1121 .

CSS/JS Compression Engine - provides minification functionality for CSS / Javascript files. The default value is set to PHP-based if no Java is auto-detected on server-side. Available options are: None (empty), YUICompressor (Java) (yui) and PHP-based (php) .

Website Charset - character encoding that will be used across the website. By default this should be set to UTF-8, but can set to other encoding also (see wikipedia.org options). It's highly recommended to have Website Encoding match the Database Encoding (specified on DB step).

Enable "System Log" - "System Log" has capability to record PHP Exceptions, Errors, Warnings, Notices, Database/SQL Errors and Warnings, and User defined messages that happened on your website. It has 3 modes - Enabled (logs everything, including user defined messages), User-only (user defined messages only), and Disabled (don't log anything at all - default setting).

Trust Proxy - whatever to trust information provided by provided by proxy server (if any) located between web server and client browser.


]]> Selected theme will be used as a default in your In-Portal website.

You can manage your themes in Admin Console under Configuration -> Website -> Themes section.

Additional themes are available on Support & Downloads section on In-Portal.com website

]]> In-Portal Installer performs final security checks on this step.

1. Write Permissions Check - checks whether critical In-Portal files are open for the outside world and can be used by hackers to attack your websites. You won't be able to continue until you correctly set these permissions!

2. Ability to Execute PHP in Writable Folders - checks if hackers can save and execute PHP files in your /system folder used for the uploads.While it's recommended to adjust these settings you can continue In-Portal Installation without changing them.

3. Webserver PHP Configuration - additional suggestions how to make your website even more secure. While it's recommended to adjust these settings you can continue In-Portal Installation without changing them.

]]> Thank you for downloading and installing In-Portal Content Management System!

Feel free to visit www.in-portal.com for support, latest news and module updates.

Please make sure to clean your Browser's Cache if you were performing the upgrade.

]]> A Configuration file has been detected on your system and it appears In-Portal is correctly installed. In order to work with the maintenance functions provided to the left you must enter your admin Root password. (Use Username 'root' if using your root password)

Upgrade In-Portal - available when you upload files from new In-Portal release into your current installation. Upgrade scripts will run and upgrade your current In-Portal database to the uploaded version.

Reinstall In-Portal - cleans out your existing In-Portal database and starts with a fresh installation. Note that this operation cannot be undone and no backups are made! Use at your own risk.

Install In-Portal to a New Database - keeps the existing installation and installs In-Portal to a new database. If this option is selected you will be prompted for new database configuration information.

Update License Information - used to update your In-Portal license data. Select this option if you have modified your licensing status with Intechnic (obtained commercial support or module), or you have received new license data via email.

Update Database Configuration - allows you to update your current database configuration variables such as database server host, username, password and others.

Update Installation Paths - should be used when the location of your In-Portal files has changed. For example, if you moved them from one folder to another. It will update all settings and ensure In-Portal is operational at the new location.

]]> Select modules from the list, you need to update to the last downloaded version of In-Portal

]]> Review Administrative Console skin upgrade log.

]]> In-Portal needs to connect to your Database Server. Please provide the database server type*, host name (normally "localhost"), Database user name, and database Password. These fields are required to connect to the database.

If you would like In-Portal to use a table prefix, enter it in the field provided. This prefix can be any text which can be used in the names of tables on your system. The characters entered in this field are placed before the names of the tables used by In-Portal. For example, if you enter "inp_" into the prefix field, the table named Categories will be named inp_Categories.

]]> The System Requirements Check option should be used to ensure proper system behavior in the current environment.

PHP version 5.3.2 or above*
Use this PHP version or better to ensure normal website operation on every day basis.

URL rewriting support
Allows to build nice looking SEO urls without specifying "/index.php" in each of them.

Java template compression
When Java is installed on web server, then it's possible to use YUI Compressor to minify HTML, CSS and JavaScript output of website. This allows to make websites, which opens even faster, then before.

Dependencies via Composer
In-Portal uses Composer to install required 3rd-party libraries. Please ensure, that:

  1. Composer is installed (instructions)
  2. Dependencies are installed (instructions)

Memory caching support
When available use Memcached memory object caching system for data caching. Will severely improve website performance under heavy load and page loading speed in general.

Accessing remote resources (via cURL)
Allows to perform data retrieval from other websites (e.g. rss feeds) in background. Data retrieval internally is done using cURL library, that must be installed on web server.

XML document processing (via SimpleXML)*
In-Portal uses XML files to store module/theme meta data. This library is used keep In-Portal code clean as fast even, when processing XML files.

Standard PHP Library (SPL)*
Usage of this library guarantees memory efficient way to manage files and data structures across In-Portal.

TrueType font support (via Freetype)*
This library allows to use TrueType fonts inside produced images. In particular it's used for Captcha code generation.

GD Graphics Library 1.8 or above*
This library is used to perform various manipulations (e.g. resize, crop, etc.) on user-uploaded images.

JPEG images support*
Support image manipulations on user-uploaded images *.jpg and *.jpeg file extensions.

Database connectivity (via MySQL)*
In-Portal uses MySQL database as it's persistent data storage.

JSON processing support*
JSON data format is used to implement AJAX approach and perform complete page reload only, when necessary.

Memory requirements changing on the fly
In-Portal requires at least 16 megabytes of memory to operate normally. However some resource consuming operations (like link validation) might consume more memory, then usual. To ensure, that such operations never fail In-Portal changes maximally allowed memory limit on the fly. See memory_limit setting for more info.

Prevent script errors in production environment
Prevents any errors to be shown on website, that might happen due incorrect web server configuration. See display_errors setting for more info.

Change error detalization level
Ensures, that all error types are shown in development environment and none in production environment. See error_reporting setting for more info.

Web server timezone is explicitly set*
Web server timezone must be set explicitly to ensure correct date/time calculations and display across the website. See date.timezone setting for more info.

Needed super-global arrays registered
Internally In-Portal relies on super-global array (e.g. $_SERVER, $_POST, etc.) presense inside a script. To make that happen variables_order setting must contain following letters: "G", "P", "C", "S".

Script output buffering enabled*
Output buffering is needed to allow usage of GZIP compression of page output. See output_buffering setting for more info.

Cookies enabled
However In-Portal can work without cookies (by adding ?sid=XXXXXXXX into each page url), but it's strongly advised to use cookies-enabled web browser for better user expirience.

JavaScript enabled
JavaScript might not be required on Front-End (depends on used theme), but it must be enabled in web browser during installation and Admin Console usage.

]]>