IMPORTANT ANNOUNCEMENT

These forums were permanently set to read-only mode on July 20, 2022. From that day onwards, no new posting or comment is allowed on the site, but the historical content remains intact and searchable.

A new location for posting questions about PlanetPress Suite is now available:

OL Learn - PlanetPress Classic (opens in new tab)

Topic Options
#23817 - 08/03/05 09:17 AM split "on a word" not imported correctly
stuartg Offline
OL Expert

Registered: 03/06/03
Posts: 713
Loc: Swindon, England
Hi
Whn I import a V4.0.43 config that splits a file "on a word", the config is not imported correctly. The keyword to search for is not imported and shows blank.

The keyword does not appear in the XML and has to be reinput.

Stuart

Top
#23818 - 08/03/05 09:24 AM Re: split "on a word" not imported correctly
stuartg Offline
OL Expert

Registered: 03/06/03
Posts: 713
Loc: Swindon, England
Looking closely at the XML, I see that Keyword has changed to KeyWord.

Top
#23819 - 08/03/05 09:42 AM Re: split "on a word" not imported correctly
stuartg Offline
OL Expert

Registered: 03/06/03
Posts: 713
Loc: Swindon, England
It behaves the same for a splitter on "a word in a stream".
A workaround is to edit the XML before importing to V5.
Stuart

Top
#23820 - 08/03/05 01:00 PM Re: split "on a word" not imported correctly
Yannick Fortin Offline
OL Expert

Registered: 08/25/00
Posts: 354
Loc: Objectif Lune Montréal
This issue is caused by a case-sensitivity problem in the XML code of the configuration file.

Here is the complete list of properties that are incorrectly imported from a Watch 4.0 configuration file:

- Folder output filename (Filename vs FileName)
- Ftp input username (Username vs UserName)
- Splitter keyword (used in multiple splitter types) (Keyword vs KeyWord)
- Output printer page delimiter keyword (Keyword vs KeyWord)
- Ftp output filename and username (Filename vs filename, Username vs UserName)
- Ftp output service retry interval (Interval vs interval)


There are 3 workarounds to this problem.

1. Open each culprit task and click OK using PlanetPress Watch 4.1 or higher before importing it in 5.0.

2. Edit the XML code by hand to set the right tags. See above for the tag names. Please note that this is a serious undertaking as the parser is very picky on the syntax. Tinkering with it by hand may render the file unusable, so back it up before doing anything.

3. Wait for 5.0.1, which will fix this issue.
_________________________
Yannick Fortin, Team OL

Top