sifbuilder

Release 1.3.3 of sifbuilder includes the installation package for <span class="bold">PostNuke .763</span>. Having this release installed, these instruction generate the sifbuilder site (http://www.sifbuilder.com/) with that version of PostNuke:

> php sifcmd.php b --sifpacksdir=../sifpacksdir --sifnethost=localhost 
 --sifnetsite=sbpn_at_localhost --siburi=./sibs/sib_PostNuke07_sif_sif.xml -x -f
> php sifcmd.php b --sifpacksdir=../sifpacksdir --sifnethost=localhost 
 --sifnetsite=sbpn_at_localhost --siburi=./sibs/sib_PostNuke07_sifcontent.xml -f

This requires that the <span class="emphasis">localhost</span> host and the <span class="emphasis">sbpn_at_localhost</span> are properly defined in <code class="filename">sifnet_config.php</code> (use the -f and -x options ONLY if you are aware of the implications).

The sip installing that version of PostNuke includes a new version of the <span class="bold">upgrade</span> function intended to support pn .76 sites. Sites having the v4b library installed are also upgraded. By copying pnApi, however, the PostNuke version appears as not increased. To test the update function it is necessary to have a .76 site available. This can be done with

> php sifcmd.php t tca001 -f -v

The command creates the sifbuilder site with the PostNuke .7.6.2 core. then, it updates the site to pn .7.6.3. That test case, defined in <code class="filename">sifnet_usecases.php</code>, relies on the same localhost and sbpn_at_localhost host and site. Run the command without the -v option to see the parameters behind the use case and modify it as necessary. Alternatively, run

 > php sifcmd.php i --sifnethost=localhost --sifnetsite=sbpn_at_localhost 
  --sifpacksdir=../sifpacksdir PostNuke07_core_postnuke_0_7_6_2 -x -f
 > php sifcmd.php file://./sibs/sib_PostNuke07_sif_sif.xml --sifnethost=localhost 
  --sifnetsite=sbpn_at_localhost --sifpacksdir=../sifpacksdir -f
 > php sifcmd.php file://./sibs/sib_PostNuke07_sif_content.xml --sifnethost=localhost 
  --sifnetsite=sbpn_at_localhost --sifpacksdir=../sifpacksdir -f
 > php sifcmd.php file://./sibs/sib_PostNuke07_sif_delta.xml --sifnethost=localhost 
  --sifnetsite=sbpn_at_localhost --sifpacksdir=../sifpacksdir -f
 > php sifcmd.php u --sifnethost=localhost --sifnetsite=sbpn_at_localhost 
  --sifpacksdir=../sifpacksdir PostNuke07_core_postnuke -f
 

The upgrade process copies the resident site to a tmp backup folder. Then a new core site is generated and all the existing files in the modules, themes, includes and images folders that are not found in the new release are copied from the backup. This applies also to <code class="filename">config.php</code> and <code class="filename">config-old.php</code> in the root folder.

To update the sites with v4blib installed, the files <code class="filename">index.php</code>, <code class="filename">personal_config.php</code>, <code class="filename">includes/pnAPI.php</code>, <code class="filename">includes/pnLang.php</code>, <code class="filename">includes/pnMod.php</code>, <code class="filename">includes/pnRender.class.php</code>, <code class="filename">includes/pnSession.php</code> and <code class="filename">images/icons</code> overwrite the new ones. Note that this may create problems in some installations.

sifbuilder 1.3.3 incorporates the installation package for <span class="bold">postnuke 0.8.0.0MS2</span>. This version of the core may be installed with the sourceforge block, the Topics module and sysconfig with

> php sifcmd.php b --sifpacksdir=../sifpacksdir --sifnethost=localhost 
 --sifnetsite=sbpn_at_localhost --siburi=./sibs/sib_PostNuke08_env.xml --dev -x -f

or, just for the core, with

> php sifcmd.php b --sifpacksdir=../sifpacksdir --sifnethost=localhost 
 --sifnetsite=sbpn_at_localhost PostNuke08_core_postnuke --dev -x -f

Note the --dev option that is required for the sips related to development packages. Use the -f and -x options ONLY if you are aware of the implications.

Installation packages for some PostNuke modules are also included.

PostNuke07_mod_mediashare_2_0_0 is the sip for <span class="bold">mediashare 2.0.0</span>. sips are associated to packages -that they be cores, blocks, modules or themes-. A sip normally gets and installs a package. Building a sip may imply creating an entry in the Main Menu, showing a block in a panel or setting a theme as default. sips are not intended to create content, that is inherently independent from packages. This is done with the sibs (the sif beans in the sibs folder) that typically describe the complete target site: core, modules, blocks, theme and content. Content nodes are however limited to text, such as the pagesetter publications in the http://www.sifbuilder.com/ site. The line of development of sifbuilder includes support for tar sibs. It should then be possible publish a sib and have a content rich site automatically generated. This will be dependent, however, on the programmatic interfaces of the media management modules.

PostNuke07_mod_pnFreeChat_1_02 installs <span class="bold"><span class="bold">pnFreeChat</span> 1.02</span> It builds with an entry in Main Many and shows how to install the pnFreeChat block.

PostNuke07_mod_netquery_4_0 installs <span class="bold">Netquery 4.0</span> . We have not seen a way to install this module on PostNuke .7.6.3 without modifying <code class="filename">pnuser.php</code> to have browserinfo -used in <code class="filename">netquery_user_main.htm</code> (380-383)- assigned by Sniffer. The package build includes the activation of the Sniffer module.

Following the experience with the sif site, a few sips are fixed and delivered with a new version.

The stable <span class="bold">PostNuke07_mod_pagesetter_6_2_0</span> and development PostNuke07_mod_pagesetter_6_3_0b5 sips modify the /pntemplates/plugins/function.pagesetter_ezcommentsCount.php function to call EZComments getall with mod param and get the correct number of comments per publication category and item.

The <span class="bold">PostNuke07_mod_v4bPostCalendar_4_03</span> sip modifies the calendar view adding the <code class="filename">PostCalendar/pntemplates/plugins/function.pc_view_select.php</code> from previous releases to the package installation.

This release includes also a few modifications to the sifbuilder and sif libraries and some sips files that determine the modification of the release number.

The <span class="bold">SifFso cp_diff_r</span> function has been changed to behave recursively in all subfolders. This is used in the pn update function, in particular to cover the <code class="filename">includes/blocks</code> and <code class="filename">includes/language</code> subfolders. The flat behavior of the previous code is done by cp_diff_d, in line with cp_d.

The <span class="bold">sif_sip sip_sip_install_site_wrapper</span> function has been set to ignore upgrade of packages in force mode if reinstall is not requested.

In this release, sifbuilder stop on error has been activated in <code class="filename">sifConfigParams.php</code>.