You are here

Beta 2.1.9 , more about SiteIni Encryption and about REX

SiteIni Encryption, SiteIni types :

Since the introduction of SiteIni encryption with version 2.1.7 , now 2.1.9 , new settings and enhancement have been introduced in WebGrab++. As mentioned in, the types of SiteIni can be grouped as follow:

  • Type 1 : 'Legacy' un-encrypted in clear text. Basically no change, SiteIni can be created and updated by any user, is public and does not require any change in SiteIni or WebGrab++.config.xml. The “site” line works with all the commands that can be included (timezone, language, episode-system, firstshow, etc. etc.)
  • Type 2 : Encrypted without user-key. This type of SiteIni is public. Usually prepared by WGTeam members only, content and methods are hidden. No decrypt userkey and no expiration date will be set. A line to SiteIni header is added indicating the encryption date: * $$encrypted [17/03/2019]
  • Type 3 : Encrypted with user-key. This type of SiteIni is usually prepared by WGTeam members only, SiteIni content and methods are hidden. Requires a “decrypt userkey” and have no expiration date. Some userkeys will be published in the forum’s donator area, some are available on request (see below). A line is added to the SiteIni header indicating the encryption date and the need of a “userkey” :* $$encrypted w/userkey [16/03/2019].
  • Type 4 : Encrypted with user-key and expiry date. Same as Type 3 but with addition of expiration date (default 1 year) after this period SiteIni can be renewed with on request. A warning is issued to advise user that SiteIni expiration is getting close to the expiration period. A line is added to the SiteIni header indicating the encryption date and the need of a “userkey” , expiration date(1 year) since the creation of the SiteIni : * $$encrypted w/userkey/expiry [18/03/2019]

Requests for a userkey or an expiry date extension can be either posted in the forum’s donator area, or by PM to one of the WG++ team members or by Email to In all cases at least a donator status is required.

Note: Encrypted SiteIni's need WG++ version 2.1.9 or higher!!
Note: Type 3 and 4 will have priority in forum user’s requests for revision or help.
Note: It is prohibited to post userkeys in public !!

Warning: Never change anything in the header of an encrypted SiteIni!! Else, it will fail to decrypt!

Configuration files:

Reference link:

A. The effect of SiteIni type / encryption on WebGrab++.config:

    -For type 1 and 2, there is no change in WebGrab++.config.xml. Both will be automatically detected by WG++ and will be processed regularly.
    -For type 3 and 4 a new element has been introduced, this element has to be added to WebGrab++.config.xml to allow WebGrab+Plus to decrypt these types of SiteIni’s. For each SiteIni of type 3 and 4 , a userkey must be specified using this new element:

    <decryptkey site="site_value">userkey_value</decryptkey>"

    Example: <decryptkey site="">0a4Wd</decryptkey>
    Note: site_value must be the same as the site_value in the element , which is the SiteIni name without the .ini extension.

B. New channel update mode “c” :

An enhancement to the channel update mode has also been introduced. The new switch mode is: “c” which stands for channel list mode. With any siteini (whatever type 1 to 4) enabling the lines for the channel list creation in the SiteIni is no longer needed. Instead, this can be done, for individual sites, by changing the value of the update attribute in (at least one of) the c

Note: EPG grabbing is disabled and a warning will be issued in WebGrab++.log.txt to advise the user of the change:
[Warning ] !! SiteIni in channelfile creation mode !!!
Note: This simplified way of creating a channel file works with most siteini’s, whatever the type. For particular siteini’s, which require multiple steps to set region etc., this will not work and the usual method needs to be used.

REX postprocessor:

We have the impression that this postprocessor is not used as much as it should. Maybe because users are simply unaware of what it can do. A few lines to give it a fresh introduction :

SiteIni’s developed and maintained by WG++ group members are constructed to provide as much data as is available on the tvguide website, following the obvious structure of the xmltv file format. For example, you will find the show description in the xmltv element <desc> and actors in <actor> and episode in <episode> etc.
Unfortunately, not all PVR xmltv import utilities follow this xmltv format completely. Some expect most data (description, actors, production date etc.) combined in the <desc> element or subtitle combined with episode in the element <sub-title>. Others support only a limited set of xmltv elements, like start- and stop times, title and description only.
Clearly, if a user imports the ‘full spec’ xmltv data provided by WG++ into PVR’s using these limited functionalities, the result is very meager and disappointing.

WG++ provides two solutions, the 'WRONG' one and the 'RIGHT' one.

  • - The 'WRONG' one. The wg++ siteini script language is capable to place, move or combine any epg data in the xmltv element of choice. This looks like a perfect solution but it has its disadvantages:
    > It results in a special ‘custom’ version of the ‘original’ SiteIni , most probably to be made by the user himself.
    > This ‘custom’ version will not be automatically updated when problems arise. It has to be maintained by the user.
    > If the ‘original’ SiteIni is encrypted, it will be very difficult to accomplish.
  • - The 'RIGHT' one. Use the REX postprocessor. REX stands for Rearrange and Edit Xmltv files. It has been especially made for these kind of xmltv file modifications. As described in the rex.config.xml header:

    The purpose of this post-processor is to re-arrange and edit the xmltv file created by the grabber section of WebGrab+Plus. This can be useful or necessary if the EPG viewer of the PVR/Media-Centre used, or the xmltv importer it uses, does not support all the xmltv elements in the xmltv file created by WG++ or simply because of some users wishes. It can: - Move the content of xmltv elements to other xmltv elements - Merge the content of several xmltv elements - Add comments/prefix/postfix text - Remove or create xmltv elements E.g.: If the PVR doesn't support import of credit elements (actors, directors etc.) it can add the content of them to the description and remove the original credit elements which are useless. Or, it can move the episode data to the beginning or end of the subtitle element etc. ..
    And .. it is fully independent whether to ‘original’ SiteIni is encrypted or not.
    And .. REX is very fast and is an integrated part of WG++ and runs automatically immediately after the standard grabbing if enabled.

Beta 2.1.9 has added some functionality to REX. It is strongly recommended to read the documentation included in the Rex.config.documented.xml. Reference link:

Hope you enjoy!!

Brought to you by Jan van Straaten

Program Development - Jan van Straaten ------- Web design - Francis De Paemeleere
Supported by: