Welcome, Guest. Please Login
IMPORTANT MESSAGE! This forum has now been replaced by a new forum at http://forum.eastgate.com and no further posting or member registration is allowed. The forum is still accessible via read-only access for reference purposes. If you wish to discuss content here, please use the new forum. N.B. - posting in the new forum requires a fresh registration in the new forum (sorry - member data can't be ported).
Pages: 1
Send Topic Print
^file^ and deprecation (Read 2770 times)
Mark Anderson
YaBB Administrator

User - not staff!

Posts: 5689
Southsea, UK
^file^ and deprecation
Aug 15th, 2011, 6:12am
Note: this is something only of note to more advanced users!

I've 'un-deprecated' ^file()^. Why? Currently (v5.9.3) action code can't replicate all the necessary data ($HTMLExportFileName + $HTMLExportExtension). The effect can be seen here. The issue arises, for a reason, due to TB's consideration of file naming collisions on export.

In certain more advanced use of TB it can be useful to construct pointers to other pages where the implicit relative paths of ^linkTo()^ or ^url()^ are not desirable. Thus it is necessary to know the exported file's name pre-export. I would stress this is something the basic user is not going to encounter.

A feature suggestion is to let action evaluation of $HTMLExportFileName return the currently predicted filename. The change can be annotated with a warning to users about possible ambiguity if the value is stored. Those affected will only be export users who'll need to have looked into this aspect before use, so I see now downside to the change plus it allows planned reduction in the number of active export codes.

Sode note: I'll feed this through to the TB Cookbook and other pertinent resources.
Back to top
« Last Edit: Aug 15th, 2011, 6:13am by Mark Anderson »  

Mark Anderson
TB user and Wiki Gardener
aTbRef v6
(TB consulting - email me)
WWW shoantel   IP Logged
Pages: 1
Send Topic Print