Multi-lingual/Multi-skin Blocks

Hello Again,

Stumbled across another issue I thought I'd bring up with the psl
development team.  Last time I talked to you folks about this the
decision was that multilingual functionality just isn't there for the
blocks..  I was looking at this for Back-End and wondered about this
chunk of code from within the storeParsed data function of the
Block.class file:

         $block_options = $this->block_info["block_options"];
         $lang = $this->psl['lang'];
         $skin = $this->psl['skin'];
         $block_options['cache_data'][$lang][$skin]['cache_data'] =
$this->block_info["cache_data"];
         $block_options['cache_data'][$lang][$skin]['last_update'] =
time();
         $serial_options = addslashes(serialize($block_options));
         /* Store in db */
         $query = "UPDATE psl_block
                      SET block_options = '$serial_options'
                    WHERE id = '$id'";

1st question is is this working anywhere?  Are different skins &
languages being effectively cached within the block options?

Wouldn't it just make more sense to move this into a psl_blockCache or
psl_blockText table?

Since most of the mysql is in Block.class it isn't that hard to make the
change..  

Mike
-- 
Mike Gifford, OpenConcept Consulting
Free Software for Social Change -> http://www.openconcept.ca
Site Launch - Make Every Vote Count - http://www.fairvotecanada.org
The cruelest lies are often told in silence. -- Robert L Stevenson




-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01