WebGrab+Plus

This beta is not longer available

fixed : crash when no headers are specified
fixed : logging of exceptions shows meaningful stacktrace
added : different headers sets for subpages, (-needs more testing!)
fixed : crash when no subpage header list is specified
added : header-set log
fixed : converting to other timezone inverted the timespan used to correct the time

added : Boolean operators & (and) | (or) ^ (xor) and ! (not) to be used in RPN style boolean preconditional expressions
added : 'if' operation to enable multiple scrubstrings under the same condition
added : 'else' operation als part of 'if'
added : nesting of 'loop' operation(s) as part of an 'if' operation
added : nesting of 'if' operation(s) within a 'loop' operation

fixed : operation calculate, added inputvalue>> to start of operation string if not there
fixed : removed logging of special operation of config_timespan_days
changed : all (5) projects of WG++ are targeted to .net 4.7.2

- Postprocess 2.08 REX
fixed : operations max_char, max_words not properly implemented

Enjoy Jan van Straaten

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 http://www.webgrabplus.com/content/siteini-encryption-beta-217-and-more, 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...

This beta is no longer available

This beta solves a problem in the Linux distro with beta 2.1.8

!! Beta 2.1.8 is no longer recommended and not available anymore !!

All other changes and additions are the same as they were in beta 2.1.8 :

changed : timespan definitions and implementation --integers are minutes, decimals are hours

added : 'legacy' mode for timespan, if MinSWversion < 2.1.7.1 legacy mode as in V2.1.5

added : special timespan handling of 'config_timespan_days' , converts to days as default

fixed : regex pattern for encrypt message , handles the normal date variants

changed : decryption is based on new init vector, requires re_encryption for encrypted siteini's that run in beta 2.1.7 !!

- Postprocess 2.07 REX :

fixed : elements containing certain string values (used as placeholder for control chars) were 'pruned'

added : <file-name> in rex.config can contain a variable 'source_file' that will take the
value of the xmltv source file name (without .xml) plus text elements e.g. :
<filename>rex_'source_file'_1.xml</filename>

added :...

Dear users of Webgrab+Plus

2019 will be a year of changes !!
First thanks for the countless hours that our support group dedicated to updating and developing SiteIni's and responding to WG++ users questions and requests. Chapeau!! Especially I want to thank Blackbear199 (who is currently only active in the background) , Matt8861 and our new star KVanc. And not to forget all the contributing users! Feel free to join our support team!

The latest Beta, V2.1.7. It includes updates and bug fixes. And .. starting with this beta and all future releases, the way SiteIni files are handled will change...

The main change is SiteIni encryption !

Last year we had to move away from -everything fully free of charge- to demanding a small donation for certain SiteIni's in a donators 'badge' section of the forum. But even that gave rise to unfair situations. Examples of users contributing just a few €'s for a donators badge and making a business with the our program and the siteini's they could access with it. Again, as before, undesired reactions in the forum. Our support group was therefore forced to use an unwanted deviation of our SiteIni database...

This beta is no longer available

- added : handles SiteIni encryption with expiry date set
- improved: title match procedure removes any attributes added to the title value
- fixed : method SOAP
- fixed : method POST_BACK
- added : control elements from site{} line episodesystem, subtitlestype and ratingsystem,
can be expanded to their value by 'site_episodesystem' , 'site_subtitlestype' and 'site:ratingsystem'
- added : SiteIni scrubstrings before site {} are blocked
- added : channellist creation through channel attribute update="c" in config
- added : decryption of encrypted SiteIni's
- added : config element 'decryptkey' to enter userkey for decryption
- fixed : timespan h:m was treated as d:h in some cases
- improved: timespan input value decimal hours will convert to h:m or d:h:m
- fixed : strange timezone parsing issue
- update : new tzdatabase based on tzdata2018i

!! There will be no Beta V2.1.6 in case you wonder ..

Dear users of Webgrab+Plus and visitors of this website

around May 20 this website was attacked by a trojan horse exploiting a backdoor in our web platform Drupal. Too late we were informed about this vulnerability of Drupal. See https://www.drupal.org/docs/develop/security/your-drupal-site-got-hacked... . The consequences were fatal. The trojan was able to invite 16 viruses at the moment we (Paul in fact) started to investigate cause and remedy.

Visitors of this website around and shortly after that date were redirected to obscure and mostly fake websites some of them with click bait buttons or other tricks to lure visitors into malware.
For some time Paul tried to clean the website with a regular virusscanner. It appeared not very effective, the trojan fought back by reinstalling the viruses we just removed and installing new ones. At some point there were 100 or more infected files? Shortly after, on May 22, when it became clear that the site could not be kept online, we decided to shutdown and issue 'website on maintenance'.

That was nearly the final...