Re: "multi-language-blog"

Christian Stocker <[email protected]>
Newsgroups gmane.comp.cms.bitflux.general
Message-ID <[email protected]>

On 17.6.2005 13:48 Uhr, Adrian Nussbaum wrote:
> 
> hi
> 
> 
>> No. The actual content is generated before the xsl is called, so you
>> would have to change blog.php. There you could of course try to take
>> only the posts of one language (resp. category). That would be around
>> line 165 in inc/bx/plugins/blog.php
>>
>>             if (isset($cat)  && $cat && $cat != '_all') {
>>                 $lres = $GLOBALS['POOL']->db->query("select l,r from
>> ".$tablePrefix."blogcategories where
>> ".$tablePrefix."blogcategories.fulluri = '$cat' and
>> ".$tablePrefix."blogcategories.status=1 ");
>>
>> There we check, which categories are called.
>>
>> just add your choosen language to $cat and you should be somehow fine
>>
>> chregu
> 
> 
> 
>>> is there a (php-)variable defined for the language, so i could   replace
>>> $cat with it?
>>>
>>
>>  $GLOBALS['POOL']->config->getOutputLanguage();
> 
> 
> i tried to do that, but it didn't work :-(
> 
> but what do i actually have to do? where do i have to put "$GLOBALS
> ['POOL']->config->getOutputLanguage();" instead of "$cat"?
> i tested serveral possibilities but i didn't have a success with it...


$cat = $GLOBALS['POOL']->config->getOutputLanguage() ."/".$cat;

somewhere before line 165 should do it. (not tested by myself,just a guess)

chregu

> 
> adrian
> 
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   xpure - creative services - www.xpure.ch
>   adrian nussbaum | neumattstrasse 107 | ch-3422 ruedtligen
>   mobile: + 41 764 283 913   |    private: + 41 344 456 061
>   [email protected] | http://www.xpure.ch |  www.blogomanie.info
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
bitflux-cms mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.