TBS version 3.6.0 Release Candidate
Skrol29
A new version of TinyButStrong should be available soon, with 6 new
features and 5 bug fixes.
You're welcome to test the new features and the compatibility:
http://www.tinybutstrong.com/download/download.php?file=tbs_beta.zip&sid=2
The change-log for TBS version "3.6.0 RC 2010-09-10" is here:
(link http://www.tinybutstrong.com/support.php#changelog_3_6_0 )
New features:
--------------------
* New keyword "htmlconv=utf8": enables you to directly convert the
data item into UTF-8.
* New operator "msk": apply a mask on the current data item. Example;
"ope=msk:prefix_*_suffix"
* New plugin event "OnCacheField", it's triggered when a field is put
in the cache of a block definition.
* New properties "OnLoad" and "OnShow": enable you to prevent the
processing of automatic fields and blocks. May be useful for plug-ins
* New parameter "atttrue" (mean "attribute true"). To be used with
parameter "att". Turn the attribute to have a Boolean behavior, which
becomes true for the given value. Example:
[var.x;att=input#selected;atttrue=29] will add "selected=selected" if
$x=29, otherwise the attribute is omitted.
* TBS can now restrict the PHP functions allowed for parameters
"ondata" and "onformat".
Example: $TBS = new clsTinyButStrong('','','f_allowed_');
Fixed bugs:
-----------------
* Parameter "getbody" without value is not working.
* Parameter "att" doesn't work when placed in inside the target tag
and before the target attribute. http://tinybutstrong.com/forum.php?msg_id=10899
* GetBlockSource() with arguments AsArray=false and DefTags=false does
ignore DefTags=false.
* A sublock with a dynamic queries can display "TinyButStrong Error
when merging block" (with the keyword %p1% in the query) when it
founds parameter "p1=" without value. This can happen for instance
when the main block had a null or empty value for the linked column.
* Parameter "valsep" (to be used with ope=list) doesn't work as
expected if its value is HTML/XML encoded. The final value includes re-
encoded value separators.
Have a nice day,
Skrol29
TomH
Just to report that I am getting this error on one application.
"TinyButStrong Error with plug-in 'TBS_NAVBAR' : no class named 'TBS_NAVBAR' is
found, and no function named 'tbspi_TBS_NAVBAR_OnInstall' is found."
But I cannot yet verify that it is because of v 3.6.0 (error also exists when I
just backed up to v3.5.3 release) - but I cannot be sure yet -- I have to back
up to the release before 3.5.3.
Tom
TomH
I have tested 3.6.0 now on my local server and it works fine with the TBS_NAVBAR
plugin !!!
so I have to conclude it is me, I changed to another server farm ecently and
that migration must be the problem.
But running on local machine has proven that it is not 3.6.0 --- BUT i SHOULD
KNOWN THAT IT WASN'T YOU from the beginning!!!
Sorry for the false alarm,
TomH
the new releases
Skrol29
So all is going good for now :)
---------------------
Skrol29
www.tinybutstrong.com
---------------------
Le 11/09/2010 06:24, TomH a �crit :
TomH
Yes, all is going good, now that my main server is properly configured I can
report that ALL of my TBS apps are running just fine!
Thanks for the new release!
And thanks, really, for TBS every day,
TomH
Skrol29
There is a new beta version that should fix your problem of automatic
subblock having a null value.
http://www.tinybutstrong.com/download/download.php?file=tbs_beta.zip&sid=2
Regards,
Skrol29
-----Message d'origine-----
De : tbs-...@googlegroups.com [mailto:tbs-...@googlegroups.com] De la part
de TomH
Envoyé : samedi 11 septembre 2010 14:23
À : tbs-...@googlegroups.com
Objet : Re: [tbs-next] TBS version 3.6.0 Release Candidate
Yes, all is going good, now that my main server is properly configured I can
report that ALL of my TBS apps are running just fine!
Thanks for the new release!
And thanks, really, for TBS every day,
TomH
Skrol29 wrote:
>
> So all is going good for now :)
>
> ---------------------
> Skrol29
> www.tinybutstrong.com
> ---------------------
>
>
> Le 11/09/2010 06:24, TomH a écrit :
>> Well,
>>
>> I have tested 3.6.0 now on my local server and it works fine with the
>> TBS_NAVBAR plugin !!!
>>
>> so I have to conclude it is me, I changed to another server farm
>> ecently and that migration must be the problem.
>>
>> But running on local machine has proven that it is not 3.6.0 --- BUT
>> i SHOULD KNOWN THAT IT WASN'T YOU from the beginning!!!
>>
>> Sorry for the false alarm,
>> TomH
>>
>>
>> the new releases
>>
>
--
You received this message because you are subscribed to "TinyButStrong next
version".
Post to this group: send email to tbs-...@googlegroups.com
Subscribe: send email to tbs-next+...@googlegroups.com
Unsubscribe: send email to tbs-next+u...@googlegroups.com
More options: http://groups.google.com/group/tbs-next
TomH
First, thanks for this new RC -- I have run all of my apps using it and (no
surprise) everything works as expected - VBG !
Except, about the fix for null value fields in the automatic subblock...
After upgrading to RC 2010-09-15:
(1) I eliminated my workaround which forced the field to be empty...
//RC else{
//RC $result[$k]['offices_array'] ="";
//RC }
(2) Then running the program -- I got the error
"TinyButStrong Error for merging the automatic sub-block [blkcat_sub1]: key
'offices_array' is not found in record #3 of block [blkcat]. This key can
becomes optional if you designate it with parenthesis in the main block, i.e.:
sub1=(offices_array)"
This error repeated for each main record with NULL value in the subblock field.
But, GOOD news, the records which did have field offices_array data (not null)
did display correctly however, so that was a big step forward.
(3) Following the instructions implied in your helpful error message - I made
the change to the main block code like this...
[blkcat.name;block=tr;sub1=(offices_array);htmlconv=no;noerr]
This change did eliminate the error messages!
But the display of the subblock
[blkcat_sub1.region;block=tr;magnet=offices;noerr] Region
does NOT work any longer.
----
So in one case the fix works, but throws error messages, while in the second
case it kills the errors, but does not work.
----
If you need any more info I am at your disposal!
Thanks a lot, and thanks for TBS every day,
TomH
PS
If you have a change log / docs for v 3.6.0 please send or post, thanks.
Skrol29
>But the display of the subblock
>[blkcat_sub1.region;block=tr;magnet=offices;noerr] Region does NOT work any
longer.
Could you send to me a piece of code that reproduce your problem?
> If you have a change log / docs for v 3.6.0 please send or post, thanks.
The change log is already available here:
http://www.tinybutstrong.com/support.php#changelog
The online manual has been updated, but can continue to change :
http://www.tinybutstrong.com/manual.php
Regards,
Skrol29
-----Message d'origine-----
De : tbs-...@googlegroups.com [mailto:tbs-...@googlegroups.com] De la part
de TomH
Envoyé : mercredi 15 septembre 2010 17:06
À : tbs-...@googlegroups.com
Objet : RC 09-15 (was Re: [tbs-next] TBS version 3.6.0 Release Candidate
Hello Skrol29,
--
Skrol29
I've reproduced your bug and fixed it. The name of the subblock's column was
truncated in case of parenthesis usage.
A new version of the beta is available for download:
http://www.tinybutstrong.com/download/download.php?file=tbs_beta.zip&sid=2
Your tests are precious,
Regards,
Skrol29
-----Message d'origine-----
De : tbs-...@googlegroups.com [mailto:tbs-...@googlegroups.com] De la part
de TomH
Envoyé : mercredi 15 septembre 2010 17:06
À : tbs-...@googlegroups.com
Objet : RC 09-15 (was Re: [tbs-next] TBS version 3.6.0 Release Candidate
TomH
New subblock handler works as expected, it solves the problems! Great!
Now, I have some things that have interest for me...
(1) in my particular case (the code I sent you illustrated the PHP processing I
have to do to construct the subblock array) do you think it more efficient for
me to do the small added step of "if null" and make it empty myself - rather
than make TBS have to do the processing for optional field ( parentheses usage) ???
(3) again in my code you see that I make an array and then serialize/
unserialize for entering.retrieving from MySQL... is this a proper approach for
storing such arrays in db? Taking in consideration that I would be processing
the results with TBS, is there a better design for such storage/retrieval and
template display?
(2) in the 3.6.0 RC change log, maybe there is a language translation confusion
for me...
For the automatic subblocks: "If the optional column is missing then the
subblock is considered as empty." When you write "is missing" - do you mean
that the value for that field "is null" or do you mean the there is no field
with that name in the array?
As always, thanks for TBS every day, and the great support you provide,
TomH
PS - I am glad to test, I learn so much from you about using TBS
> Hi TomH,
>
> I've reproduced your bug and fixed it. The name of the subblock's column was
> truncated in case of parenthesis usage.
> A new version of the beta is available for download:
>
> http://www.tinybutstrong.com/download/download.php?file=tbs_beta.zip&sid=2
>
> Your tests are precious,
> Regards,
> Skrol29
>
>
> -----Message d'origine-----
> De : tbs-...@googlegroups.com [mailto:tbs-...@googlegroups.com] De la part
> de TomH
> Envoy� : mercredi 15 septembre 2010 17:06
> � : tbs-...@googlegroups.com
Skrol29
Thanks for your fast reply.
(1) I think the TBS option is more efficient because TBS does the check
anyway. And your code will be clearer.
(2) The clean method would be to store those information into a detail table
in MySQL. Nevertheless, serializing is a good solution if your data are
supposed to not be structured as a table's record (column's names may change
or be optional, types of data are not supported by MySQL, data may contain
other hierarchical data, ...) or if your data are very tiny. But you must
keep in mind that serialized data will be useful only through PHP, not
directly with a MySQL query.
(3) TBS will replace the data with an empty array if the column is not
there, or there with a null value, or there if a false value.
Regards,
Skrol29
-----Message d'origine-----
De : tbs-...@googlegroups.com [mailto:tbs-...@googlegroups.com] De la part
de TomH
Envoyé : vendredi 17 septembre 2010 14:02
À : tbs-...@googlegroups.com
Objet : [tbs-next] Re: RC 09-17 (null automatic subblock value
> la part de TomH Envoyé : mercredi 15 septembre 2010 17:06 À :
--
TomH
Thanks for your help about multi-values in a field -- in my historical days I
used the Pick/OS extensively, it had multi-values as native feature of the
database engine and in certain circumstances, like this one, I miss it very much.
I see by your answer that my question (1) was might not have been precise... I
meant to say "compare if the subblock processing is done with the parentheses or
without the parentheses". Are you saying that "without the parentheses" TBS
checks anyway?
Thanks for TBS every day,
TomH
Skrol29 wrote:
> Hi TomH,
>
> Thanks for your fast reply.
>
> (1) I think the TBS option is more efficient because TBS does the check
> anyway. And your code will be clearer.
>
> (2) The clean method would be to store those information into a detail table
> in MySQL. Nevertheless, serializing is a good solution if your data are
> supposed to not be structured as a table's record (column's names may change
> or be optional, types of data are not supported by MySQL, data may contain
> other hierarchical data, ...) or if your data are very tiny. But you must
> keep in mind that serialized data will be useful only through PHP, not
> directly with a MySQL query.
>
> (3) TBS will replace the data with an empty array if the column is not
> there, or there with a null value, or there if a false value.
>
>
> Regards,
> Skrol29
>
>
> -----Message d'origine-----
> De : tbs-...@googlegroups.com [mailto:tbs-...@googlegroups.com] De la part
> de TomH
> Envoy� : vendredi 17 septembre 2010 14:02
> � : tbs-...@googlegroups.com