37
Arslanbey
Re: Testing Xoops Total 2.0.18 Package.
  • 2007/10/23 8:52

  • Arslanbey

  • Just popping in

  • Posts: 10

  • Since: 2007/10/14


New 2.0.18 Turkish Language

http://www.xoopsturkey.com/dosyalar/XOOPS-2.0.18Tr.rar

36
svaha
Re: Testing Xoops Total 2.0.18 Package.
  • 2007/10/22 15:40

  • svaha

  • Just can't stay away

  • Posts: 896

  • Since: 2003/8/2 2


@Giba :

I'm testing athttp://exm.amevita.eu


Php version : 5.2.3
Mysql version : 5.0.15
GD lib : Bundled (2.0.34 compatible)
What doesn't kill me,
makes me stronger.

http://exm.amevita.eu
http://www.amevita.eu
http://www.alohaspirit.nl

35
InnoSense
Re: Testing Xoops Total 2.0.18 Package.
  • 2007/10/22 5:53

  • InnoSense

  • Just popping in

  • Posts: 25

  • Since: 2006/10/2


script_fu,
Quote:
It is my choice not to support a commercial project based on open source.

If they want to make money with XOOPS go for it. There is nothing wrong with it in alot of peoples eyes.



I think, you are in wrong way of thinking.
Quote: - means commercial support, not commercial product.


By the way, in GNU(2,3) commercial support and commercial product guarantees are allowed , and its normal practice.

34
svaha
Re: Testing Xoops Total 2.0.18 Package.
  • 2007/10/22 0:18

  • svaha

  • Just can't stay away

  • Posts: 896

  • Since: 2003/8/2 2


The function for replacing (text) emailadresses by an image doesn't work well, when I have an emailadres www.mysite.com the image shows www.mysite.co (so it 'forgets' the last character.
What doesn't kill me,
makes me stronger.

http://exm.amevita.eu
http://www.amevita.eu
http://www.alohaspirit.nl

33
script_fu
Re: Testing Xoops Total 2.0.18 Package.

It is my choice not to support a commercial project based on open source.

If they want to make money with XOOPS go for it. There is nothing wrong with it in alot of peoples eyes.

All i said was...

(This is where my support for their work stops.)


Quote:

BlueStocking wrote:

BTW: occasionally, "thanks for what you have taught me" might even be in order.



Huh?

Surely you do not mean me? I thank everyone at every turn.

32
skenow
Re: Testing Xoops Total 2.0.18 Package.
  • 2007/10/21 22:00

  • skenow

  • Home away from home

  • Posts: 993

  • Since: 2004/11/17


Quote:

script_fu wrote:
So the code is secure. What skenow is trying to say is be careful do not give anyone webmaster status thats not trusted.


Bingo! Understand the power of custom blocks before granting access to anyone. (Hint: do a search for 'fork bomb')

Most of this is off-topic, but relevant to the discussion at hand - what features to add to a core distribution and which ones should not be added.

Webmaster access should be reserved for the site administrator only for system administration, not day-to-day access. As a rule, one of the first things I do with a new install is create a new group (call it what you want, and even rename Webmasters, like I do) for day-to-day maintenance and give them access to everything except:

Blocks
Groups
Preferences

I also cautiously add module administration for most modules - but, never for Protector.

Nice to see some interest in testing new release candidates, though

31
script_fu
Re: Testing Xoops Total 2.0.18 Package.

This is one reason im in favor of superadmin options made into the core. There should be 5 groups standard with Xoops.

Super Admin
Webmasters
Moderators
Registered Users
Anonymous Users

30
script_fu
Re: Testing Xoops Total 2.0.18 Package.

So the code is secure. What skenow is trying to say is be careful do not give anyone webmaster status thats not trusted.

29
script_fu
Re: Testing Xoops Total 2.0.18 Package.

Quote:

skenow wrote:
Quote:

script_fu wrote:
Quote:

skenow wrote:
I would caution against allowing editing blocks by anyone except an admin, unless you can restrict by group and disallow HTML and PHP blocks. Nor should the frontend editor allow changing of block types. Please consider the security of such actions.


Huh?

Are you aware of an issue with the edit blocks code? The edit blocks code can only be used by admin no one else.


Only if you set permissions correctly.

From Securing your site

Quote:

13. Never give admin rights to anyone, especially to the XOOPS blocks admin.


Im confused so here is the code.

<?php
/**
 * xos_logos_PageBuilder component class file
 *
 * @copyright    The XOOPS project https://xoops.org/
 * @license      http://www.fsf.org/copyleft/gpl.html GNU public license
 * @package      xos_logos
 * @subpackage   xos_logos_PageBuilder
 * @version        $Id: theme_blocks.php 694 2006-09-04 11:33:22Z skalpa $
 * @author       Skalpa Keo <skalpa@xoops.org>
 * @since        2.3.0
 */
/**
 * This file cannot be requested directly
 */
if ( !defined'XOOPS_ROOT_PATH' ) )    exit();

include_once 
XOOPS_ROOT_PATH '/class/xoopsblock.php';
include_once 
XOOPS_ROOT_PATH '/class/template.php';

/**
 * xos_logos_PageBuilder main class
 *
 * @package     xos_logos
 * @subpackage  xos_logos_PageBuilder
 * @author         Skalpa Keo
 * @since       2.3.0
 */
class xos_logos_PageBuilder {
    
    var 
$theme false;
    
    var 
$blocks = array();    

    function 
xoInit$options = array() ) {
        
$this->retrieveBlocks();
        if ( 
$this->theme ) {
            
$this->theme->template->assign_by_ref'xoBlocks'$this->blocks );
        }
        return 
true;
    }
    
    
/**
     * Called before a specific zone is rendered
     */
    
function preRender$zone '' ) {
    }
    
/**
     * Called after a specific zone is rendered
     */
    
function postRender$zone '' ) {
    }    
    
    function 
retrieveBlocks() {
        global 
$xoopsUser$xoopsModule$xoopsConfig;

        
$startMod = ( $xoopsConfig['startpage'] == '--' ) ? 'system' $xoopsConfig['startpage'];
        if ( @
is_object$xoopsModule ) ) {
            list( 
$mid$dirname ) = array( $xoopsModule->getVar('mid'), $xoopsModule->getVar('dirname') );
            
$isStart = ( substr$_SERVER['PHP_SELF'], -) == 'index.php' && $xoopsConfig['startpage'] == $dirname );
        } else {
            list( 
$mid$dirname ) = array( 0'system' );
            
$isStart = !@empty( $GLOBALS['xoopsOption']['show_cblock'] );
        }
        
        
$groups = @is_object$xoopsUser ) ? $xoopsUser->getGroups() : array( XOOPS_GROUP_ANONYMOUS );
        
        
$oldzones = array(
            
XOOPS_SIDEBLOCK_LEFT                => 'canvas_left',
            
XOOPS_SIDEBLOCK_RIGHT                => 'canvas_right',
            
XOOPS_CENTERBLOCK_LEFT                => 'page_topleft',
            
XOOPS_CENTERBLOCK_CENTER            => 'page_topcenter',
            
XOOPS_CENTERBLOCK_RIGHT                => 'page_topright',
            
XOOPS_CENTERBLOCK_BOTTOMLEFT        => 'page_bottomleft',
            
XOOPS_CENTERBLOCK_BOTTOM            => 'page_bottomcenter',
            
XOOPS_CENTERBLOCK_BOTTOMRIGHT        => 'page_bottomright',
        );
        foreach ( 
$oldzones as $zone ) {
            
$this->blocks[$zone] = array();
        }
        if ( 
$this->theme ) {
            
$template =& $this->theme->template;
            
$backup = array( $template->caching$template->cache_lifetime );
        } else {
            
$template =& new XoopsTpl();
        }
        
$xoopsblock = new XoopsBlock();
        
$block_arr = array();
        
$block_arr $xoopsblock->getAllByGroupModule$groups$mid$isStartXOOPS_BLOCK_VISIBLE);
        foreach ( 
$block_arr as $block ) {
            
$side $oldzones$block->getVar('side') ];
            if ( 
$var $this->buildBlock$block$template ) ) {
                
$this->blocks[$side][] = $var;
            }
        }
        if ( 
$this->theme ) {
            list( 
$template->caching$template->cache_lifetime ) = $backup;
        }
    }
    
    function 
buildBlock$xobject, &$template ) {
        
// The lame type workaround will change
                
global $xoopsUser;
        
$block = array(
            
'module'    => $xobject->getVar'dirname' ),
            
'title'        => ($xoopsUser && $xoopsUser->isAdmin()) ? $xobject->getVar'title' ).
                                                                                                  
"<a href=".XOOPS_URL."/modules/system/admin.php?fct=blocksadmin&op=edit&bid=".$xobject->getVar('bid').
                                                       
"> <img src=".XOOPS_URL."/images/icons/edit1.gif"." title="._EDIT." alt="._EDIT."  /> </a>".
                                                       
"<a href=".XOOPS_URL."/modules/system/admin.php?fct=blocksadmin&op=delete&bid=".$xobject->getVar('bid').
                                                       
"> <img src=".XOOPS_URL."/images/icons/delete1.gif"." title="._DELETE." alt="._DELETE."  /> </a>" $xobject->getVar'title' ) ,
            
//'name'        => strtolower( preg_replace( '/[^0-9a-zA-Z_]/', '', str_replace( ' ', '_', $xobject->getVar( 'name' ) ) ) ),
            
'weight'    => $xobject->getVar'weight' ),
            
'lastmod'    => $xobject->getVar'last_modified' ),
            
'id'        => $xobject->getVar('bid'), // it is not needed and i just add it for those theme designers that want to have a Smarty variable. ( <{$block.id}> ==> block id )
        
);

        
//global $xoopsLogger;
        
        
$xoopsLogger =& XoopsLogger::instance();
        
        
$bcachetime intval$xobject->getVar('bcachetime') );
        
//$template =& new XoopsTpl();
        
if (empty($bcachetime)) {
            
$template->caching 0;
        } else {
            
$template->caching 2;
            
$template->cache_lifetime $bcachetime;
        }
        
$tplName = ( $tplName $xobject->getVar('template') ) ? "db:$tplName"db:system_block_dummy.html";
        
$cacheid 'blk_' $xobject->getVar('bid');

        if ( !
$bcachetime || !$template->is_cached$tplName$cacheid ) ) {
            
$xoopsLogger->addBlock$xobject->getVar('name') );
            if ( ! ( 
$bresult $xobject->buildBlock() ) ) {
                return 
false;
            }
            
$template->assign'block'$bresult );
            
$block['content'] = $template->fetch$tplName$cacheid );
        } else {
            
$xoopsLogger->addBlock$xobject->getVar('name'), true$bcachetime );
            
$block['content'] = $template->fetch$tplName$cacheid );
        }
        return 
$block;
    }
    
    
}


There are no permissions to set its only for admin. You can set permissions inside of XOOPS for edit blocks. The standard is checked yes for webmasters. If you are a webmaster you can edit if your not you can't.

Edit: My Post was backwards. About edit blocks.

28
skenow
Re: Testing Xoops Total 2.0.18 Package.
  • 2007/10/21 12:43

  • skenow

  • Home away from home

  • Posts: 993

  • Since: 2004/11/17


Quote:

script_fu wrote:
Quote:

skenow wrote:
I would caution against allowing editing blocks by anyone except an admin, unless you can restrict by group and disallow HTML and PHP blocks. Nor should the frontend editor allow changing of block types. Please consider the security of such actions.


Huh?

Are you aware of an issue with the edit blocks code? The edit blocks code can only be used by admin no one else.


Only if you set permissions correctly.

From Securing your site

Quote:

13. Never give admin rights to anyone, especially to the XOOPS blocks admin.

Login

Who's Online

209 user(s) are online (155 user(s) are browsing Support Forums)


Members: 0


Guests: 209


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Apr 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits