Changes

This is a copy of instructions originally created and published by Calisun: [[User_talk:Calisun|http://wiki.contribs.org/User_talk:Calisun]]

This is a copy of instructions originally created and published by Calisun: [[User_talk:Calisun|http://wiki.contribs.org/User_talk:Calisun]]

{{Note box|msg=(*) If you have followed this How-To prior to April 15 2018, please update your template to the one described in Part 2, Section 2.

{{Note box|msg=(*) If you have followed this How-To prior to April 15 2018, please update your template to the one described in Part 2, Section 2.

=='''Introduction'''==

=='''Introduction'''==

Following Step-by-Step instructions are for installing wordpress in an i-Bay of SME Server.

Following Step-by-Step instructions are for installing wordpress in an i-Bay of SME Server.

Instructions below will show you how to install both single wordpress install and Multisite. All steps build on each other, so if your ultimate goal is step C, Step A and B must be done first.  

Instructions below will show you how to install both Single site and Multisite versions. All steps build on each other, so if your ultimate goal is step C, Step A and B must be done first.  

After following step(s) below you will have a fully functional Wordpress site <u>with the exception of automatic updating</u>. Automatic Updating requires FTP access to the core files. You can manage FTP access to iBays with the contrib located [[FTP Access to Ibays|HERE]]. <u>Alternatively</u>, auto updates can be left off and: Wordpress system, plugins and themes can all be updated manually by following instructions from [https://www.wordfence.com/learn/how-to-manually-upgrade-wordpress-themes-and-plugins/ HERE]

After following step(s) below you will have a fully functional Wordpress site <u>with the exception of automatic updating</u>. Automatic Updating requires FTP access to the core files. You can manage FTP access to iBays with the contrib located [[FTP Access to Ibays|HERE]]. <u>Alternatively</u>, auto updates can be left off and: Wordpress system, plugins and themes can all be updated manually by following instructions from [https://www.wordfence.com/learn/how-to-manually-upgrade-wordpress-themes-and-plugins/ HERE]

*Create an ibay and create a domain using [[SME_Server:Documentation:Administration_Manual:Chapter14|server-manager]]

* Create an ibay and create a domain using [[SME_Server:Documentation:Administration_Manual:Chapter14|server-manager]]

*Upload files to server using FTP. For ease of use I recommend GUI program, like [https://sourceforge.net/projects/filezilla/ Filezilla] or [http://winscp.net/eng/index.php WinSCP]

* Upload files to server using FTP. For ease of use I recommend GUI program, like [https://sourceforge.net/projects/filezilla/ Filezilla] or [http://winscp.net/eng/index.php WinSCP]

*That you know how to issue a command to server using [http://www.putty.org/ PuTTY] or similar program. For ease of use I recommend [[Shellinabox|ShellinaBox]]

* That you know how to issue a command to server using [http://www.putty.org/ PuTTY] or similar program. For ease of use I recommend [[Shellinabox|ShellinaBox]]

*That you know how to create a database and database user. For ease of use I recommend [[PHPMyAdmin]]

* That you know how to create a database and database user. For ease of use I recommend [[PHPMyAdmin]]

   users changing (intentionally or accidentally) files in the application iBay.  

   users changing (intentionally or accidentally) files in the application iBay.  

    

    

   To mitigate the risk, administrators should make use of Groups to only allow authorized users to have access to ibay files via samba/Windows filesharing.

   To mitigate the risk, administrators should make use of Groups to only allow authorized users to have access to ibay files via samba/Windows filesharing.

== '''PART ONE:''' ==

=='''PART ONE:'''==

=== A) Wordpress install in an iBay of SME server: ===

===A) Wordpress install in an iBay of SME server:===

'''<u>A1)</u>''' Create an iBay in which you wish to install wordpress on.

'''<u>A1)</u>''' Create an iBay in which you wish to install wordpress on.

'''<u>A6)</u>''' In the SME server-manager, Create a new domain and point it to the iBay where the wordpress is installed. (Assuming you have already registered a domain with domain registrar and pointed it to your server IP)

'''<u>A6)</u>''' In the SME server-manager, Create a new domain and point it to the iBay where the wordpress is installed. (Assuming you have already registered a domain with domain registrar and pointed it to your server IP)

     * If you want to have a single blog (personal blog) on one domain, you are done.  

     * If you want to have a single blog (personal blog) on one domain, you are done.  

=== B) Enable a Multisite:  (several blogs under one domain) ===

===B) Enable a Multisite:  (several blogs under one domain)===

'''<u>B1)</u>''' Open wp-config.php and add the folowing code:

'''<u>B1)</u>''' Open wp-config.php and add the folowing code:

     * If you are planning to run several blogs under one domain, than you are done.  

     * If you are planning to run several blogs under one domain, than you are done.  

=== C) To run several Domains on one wordpress install: ===

===C) To run several Domains on one wordpress install:===

'''<u>C1)</u>''' You will need to install Wordpress Domain Mapping plugin.

'''<u>C1)</u>''' You will need to install Wordpress Domain Mapping plugin.

SME Server and wordpress use the same folder name "files" for totally different folders in different locations. That conflict is causing problems displaying images inside blogs that use Domain mapping. In order for the images to show up correctly, we need to create a custom template to fix the conflict. Go below to <u>PART TWO #2</u> for instruction on how to create the custom template.

SME Server and wordpress use the same folder name "files" for totally different folders in different locations. That conflict is causing problems displaying images inside blogs that use Domain mapping. In order for the images to show up correctly, we need to create a custom template to fix the conflict. Go below to <u>PART TWO #2</u> for instruction on how to create the custom template.

== '''PART TWO:''' ==

=='''PART TWO:'''==

=== Custom Templates ===

===Custom Templates===

=== 1) Enable Wildcard Subdomains ===

===1) Enable Wildcard Subdomains===

Inside following folder location:

Inside following folder location:

   ServerAlias *.{$virtualHost}

   ServerAlias *.{$virtualHost}

To activate the custom template:

  expand-template /etc/httpd/conf/httpd.conf

=== 2) Fix Image display problem in multisite installation. ===

===2) Fix Image display problem in multisite installation.===

Inside following folder location:

Inside following folder location:

   signal-event post-upgrade; signal-event reboot

   signal-event post-upgrade; signal-event reboot

=== 3) Increase file size limit in PHP. ===

===3) Increase file size limit in PHP.===

This step is not necessary, you can do it if you need to upload files/ pictures larger than the default settings in php.

This step is not necessary, you can do it if you need to upload files/ pictures larger than the default settings in php.

++ This code makes changes to default PHP installation. If you are using [[PHP Software Collections]] (As suggested in step '''A7''') see below.

++ This code makes changes to default PHP installation. If you are using [[PHP Software Collections]] (As suggested in step '''A7''') <u>see below</u>.

   db configuration setprop php MemoryLimit 128M

   db configuration setprop php MemoryLimit 128M

   db configuration setprop php PostMaxSize 112M

   db configuration setprop php PostMaxSize 112M

CaliSun

CaliSun

 

 

 

 

[[Category:Howto]]

[[Category:Howto]]

[[Category:Medium]]

[[Category:Medium]]