WebHub Object Pascal Components

CDATA tag stripped from WHTEKO files v2.039

You may now include the CDATA tag within a WHTEKO file (in order to make that file xml compliant). WebHub will strip the beginning and ending of the CDATA tag when loading the file; it will leave the contents of the tag intact.

Legend for WebHub Command Expansion rules

• "Never": the string is never expanded prior to evaluation
• "Implicit": the string is always expanded, as if it had surrounding parentils; you must not enter parentils.
• "Explicit": the string is only expanded if it is surrounded by parentils.
• "Always": the string is expanded regardless
• Note: Parentils means whichever pair of macro-start/stop characters you are using, %=...=% or (~...~).

The following WebHub Commands have been changed as indicated. v2.039

• ANCHOR renamed to ANCHOR plus ANCHORMODIFY
  • ANCHOR: Remember a position within the output document by name.
  • ANCHORMODIFY: Substitute content into a remembered ANCHOR position.
• APPDEFAULT, APPSETTING, PAGEDEFAULT, PAGESETTING
  • Both parameters: changed from Never to Explicit expansion.
• ASSERTPROTOCOL
  • Fixed to work as documented, including the case where cgiUseHTTP and cgiUseFilter are both True.
• ASSIGNED, NOTASSIGNED
  • First parameter (sessionVariableName): changed from Implicit to Explicit expansion.
  • This means: the first parameter must be the name of a literal, or it must be an explicit expression which expands to the name of a literal.
  • Example: ASSIGNED|x|text will display "text" as long as x is the name of a literal. ASSIGNED|(~y~)|text will display "text" as long as y contains the name of a literal.
  • Example: %=assigned|edt%=zrecno=%MEMB2ID|text=% no longer works.... the parentils would need to be on the outside of the expression, not nested within the literal name.
  • You can check whether textareas are assigned by using the textarea. prefix, example: ASSIGNED|textarea.txtSample|phraseWhenTrue||phraseWhenFalse (This textarea feature was documented as working but did not work previously.
  • There is no longer any expansion of misc expressions containing a dot (e.g. APPSETTING.x had been allowed to automatically expand)
• BOUNCE[R]
  • Each parameter: changed from Never to Explicit expansion.
• BRANDJUMP
  • Note: contrary to earlier webhub.hlp documentation, this command never accepted a filename as the second parameter.
  • No changes to functionality, only to documentation.
• CGIHTTP renamed to SETCGIHTTP
  • Syntax clarified: first parameter determines value of pWebApp.cgiUseHTTP and second parameter determines value of pWebApp.cgiHttp
  • First parameter can be blank, in which case pWebApp.cgiUseHTTP is unchanged.
  • Each parameter: changed from Implicit to Explicit expansion.
• CMD
  • "asChunk" keyword changed to "asExpanded"
• COM
  • Second parameter: changed from Implicit to Explicit expansion.
• COOKIE
  • Fixed bug which had meant that the rootpath parameter had been ignored in prior versions.
  • Value and RootPath parameters: changed from Implicit to Explicit expansion.
  • Rootpath now defaults to blank instead of /
  • Regardless of the country and locale of the web server machine, the expiration string must be set as dd-mm-yyyy hh:nn:ss. If the string is invalid, the expiration date will default to 0.
  • The COOKIE macro now calls the AddCookie method on pWebApp.
  • In AddCookie, an expiration date of 0 leads to no expiration date being set.
  • In whConst.pas, set ShortCookieDateFormat='ddd, dd-mmm-yyyy hh:nn:ss' which impacts the format of the outgoing Set-Cookie header as sent by AddCookie. (This previously had day of week as dddd, and minutes as mm.
  • Note: do not set the domain to localhost (browsers do not support it). Use an IP# such as 192.168.0.10 for local testing.
  • Reference: cookie specification
• DYNCHUNK - unchanged
• EXPIRES
  • Datetime format is now: dd-mm-yyyy hh:nn:ss rather than based on the locale where the WebHub application happens to be running. e.g. change 12/31/2005 2:15 PM to 31-12-2005 14:15
  • This command no longer sends a #pragma: no-cache header. (In prior versions of WebHub, this header was sent depending on rules in WebBrowserInfo, which is obsolete.)
  • There are no longer any special rules for when the User Agent contains MSIE.
  • A datetime of -1 is no longer sent as -1; rather it is sent as (now - 1) (i.e. yesterday) formatted as a proper datetime value.
• FLUSH
  • "body" is no longer supported as a parameter. Use "out" or blank instead.
• GO, GOR, HIDE, HIDER
  • The initial parameters ([appID:][pageID][(serverID)]): changed from Implicit (as a group) to Never
• HEADER
  • Given the syntax HEADER|a: b "a" and "b" will be expanded if surrounded by parentils. However if there are nested expressions inside a or b, without a or b itself being inside parentils, then those embedded expressions will NOT be expanded. This latter fact is a new restriction as of v2.039.
• IF, IFNOT
  • First parameter: changed from Implicit to Explicit expansion.
  • This means: the first parameter must be the name of a boolean Checked variable, or the first parameter must be an explicit expression which expands to such a name.
• IFINACTIVEFORSEC
  • No longer accepts optional "sec,hr,hrs,min tags after the number of "seconds".
  • Parameter: changed from Implicit to Explicit expansion.
• INCLUDE
  • The filename parameter will be run through CompareTo a maximum of 1 times, and only if surrounded by macro-start and macro-end markers.
• INPUTSELECT
  • isMultiple parameter changed from Implicit to Never
• LIT
  • Fixed to work as documented.
• MATCH, NOMATCH
  • String1 and String2: changed from Implicit to Explicit.
  • There is no longer any automatic treatment of "string1" as a checkbox.
  • As of WebHub v2.043, you have the option of using the pre-v2.039 syntax of MATCH. To do so, set the global variable isMatchTechniqueNew (in htWebApp.pas) to FALSE.
• PAGE
  • Each parameter: changed from Implicit to Explicit.
• PROLOGUE renamed to SETPROLOGUETYPE
  • second parameter: changed from Implicit to Explicit.
• REQUIRES vs REQUIRESMATCH
  • If you were using a match operator with REQUIRES, change REQUIRES to REQUIRESMATCH
  • REQUIRES: Bounce the surfer to another page if a named SessionLiteral is blank or a named SessionBoolean is false.
  • REQUIRESMATCH: Bounce the surfer to another page if a specified SessionLiteral does not satisfy the match comparison.
  • Each parameter: changed from Implicit to Explicit expansion.
• SENDFILE
  • Parameter 1 + 2: changed from Never to Explicit
  • Note: Parameter 3 is Never expanded.
• SESSION vs SESSIONHOUSECLEAN
  • SESSIONHOUSECLEAN: Compact the memory used by all sessions and expire old sessions from memory.
  • SESSION: Control aspects of the the session savestate including the session file's date/time stamp.
  • On Session, datetime parameter: changed from Never to Explicit
• SHELL, START
  • Each parameter will be run through CompareTo if surrounded by macro-start and macro-end markers.
• SUMMARY
  • Changed from "never expand" to "explicit expand"

The following WebHub Commands have been deleted. v2.039

• ABORTMACRO (webapp.pas)
• AUTOLOAD (webapp.pas)
• BODYLOAD (webapp.pas)
• EXCEPT (webapp.pas)
• INPUTNUMBER (note: there is no HTML <input type="number" ...> tag anyway)
• MACRO (was allowed for defining macros on the fly. Now use AppSetting instead.)
• NOGO (webapp.pas)
• SUMMARIZEKEYS

If you need those commands in your own application, copy the code from htwebapp.pas in v2.038, or request webapp.pas from tech support.

The following WebHub Commands are deprecated. v2.039

• EMBED, EMBEDR
• FILELINK
• FRAME (replace with HTML FRAME tag)
• HREF (replace with HTML A HREF tag)
• INPUTFORM (replace with HTML FORM tag, using the ACTION or ACTIONR command for the action attribute.) This change is required when editing in Dreamweaver MX 2004, and recommended in all editors.
• JS

Added OnAfterTekero event v2.039

This event fires after OnAfterTranslation, which fires after OnTraceTekero. You could use this event to clear or otherwise manipulate variables local to the current droplet.

Added local string variables v2.039

These variables are local to a droplet, and specific to a surfer.

SETLOCAL|varName=Value (to set varName)

local.varName (to display varName)

CLEARLOCAL|varName (to clear varName, keeping in mind that it will be deleted automatically when the droplet ends)

CLEARLOCAL|* (to clear all local variables associated with the current droplet)

Fixed TWebOutput.SendRedirection method v2.039

There had been a problem when bouncing to URLs using http and a port other than 80. Now, if you set WebServer.HTTP to your desired port, the bounce will use that port number. Likewise, if you want to bounce to https and a port other than 443, set WebServer.HTTPS to that port number.

TWebSock.MessageID property is now "stored false" v2.039

If you are using TWebSock and have a MessageID in your DFM file other than 1152, set that in your OnCreate event instead of in the DFM.

Invalid page handling improved v2.039

WebCommandLineBadPageId in dmWebHub.pas fixed (changed setting of bContinue flag)

TWebCommandLine.ExecutePage in webCall.pas fixed (only regarding the case where the OnInvalidPage event is defined).

If you are using the TWebCommandLine.OnBadPageID event, you should set bContinue to TRUE when you want default handling to take over and to FALSE when you have completely handled the case yourself.

Recommentation: set the application-level default named "InvalidPage" to a PageID which you want displayed when an invalid page is requested, and leave the OnBadPageID event nil.

JPEG webaction component now xhtml compliant v2.039

Instead of generating "dimensions", the JPEG component now generates height and width separately, such that the whtml is xhtml-compliant.

See notes in lib\whJPEG.pas and the "dynamic JPEG" demo on http://demos.href.com

.whteko files may be in UTF-8 format v2.039

Optionally, .whteko files may contain an xml tag in line 1 indicating that the encoding is utf-8, and may have the leading 3-byte marker. Editors such as MacroMedia Dreamweaver MX 2004 may write that marker when they detect utf-8 encoding. WebHub v2.039 ignores the marker. Earlier versions were unable to use the file if it contained the marker.

TWebScan and TWebDataScan: no BRs v2.039

For syntax stage 2.14 and higher only, these two components will no longer generate <br /><br /> between the first/prev/next/last buttons and the prompt for the Rows, Display Set, etc.

The reason for this change is that one can better control the spacing through CSS.

TWebDataSourceIB (for use with Interbase Objects) changed v2.039

TWebDataSourceIB.SetParameters now always returns False. See whibds.pas

What you should do: if you were relying on the component to always rerun the query, you should introduce a webdatasource.close command which should make your overall system faster and more accurate.

Added cgiJumpWithLingvo feature v2.039

Requires StreamCatcher v1.5.2.2, and cgiUseFilter=true

If this feature is set TRUE in [TWebApp.Defaults], then all JUMPs will be generated with a leading lingvo code, e.g. /eng/APPID:PAGEID:etc or /deu/APPID:PAGEID:etc.

Example configuration in application-level INI file:

[TWebApp.Defaults]
cgiJumpWithLingvo=true
cgiJumpWithLingvo.home=false