Support Forums - All Posts - XOOPS Web Application System

81

Re:Loving Xoops and Learning the Setup

2004/10/11 0:26
Draven
Module Developer
Posts: 337
Since: 2003/5/28

The XOOPS team is certainly aware that more and more people are in need of WorkFlow management in XOOPS as our system creeps closer to being a CMS rather than a portal/community system (which is what XOOPS was/is).

For now, unless the module itself gives the ability to restrict sub levels within the module, it's and all or nothing kind of thing. Either they have access to all of the admin panel for the news module, for example, or none of it. There is always a work around, but some are complicated and not suggested to the novice. Just rest assured that we are working towards these features and your comments are not being ignored. But until these systems are in place, using the group system, and in some cases cloning modules, may be the only option.

Perhaps if you could detail exactly what the level of access you want to give, and to what modules you want to give it to, we can direct you a little better on a possible solution.

82

Re:Altern8News and News

2004/10/10 16:10
Draven
Module Developer
Posts: 337
Since: 2003/5/28

Both cloning of blocks and cloning of modules are on our todo list. I'll be talking on the revamp of the whole block system (cloning being only one of the improvements I hope to add), not sure if cloning modules has been taken on by anyone yet.

83

Re:uploader.php and Notice: Undefined index:

2004/10/10 15:46
Draven
Module Developer
Posts: 337
Since: 2003/5/28

I don't have time to check your code thoroughly as I'm jus about to step out. Here's a few things I'd test to find out what's going on.

First, change the old $HTTP_POST_VARS['partnerlogo'] to the new $_POST['partnerlogo'].

Second, view the source code of the form you are using to upload and double check that the method is set to POST and not GET. Might want to just set your XoopsThemeForm to method POST.


$form       = new XoopsThemeForm(_MD_ADDPARTNER, "addform", "index.php", "POST");

and last I would add a print_r to the begining of that second function so I could review all of the post vars and make sure my vars are there.


function uppImage(){



print_r($_POST);



....



}

should be able to determine what's happening from that.

84

Re:Regarding Newbb

2004/10/10 13:26
Draven
Module Developer
Posts: 337
Since: 2003/5/28

Quote:

Draven wrote:
Look in include/newbb.css for ".head". I believe that is the class you are looking for.

Sorry, it uses the class Head from the styles.css in your theme folder.

85

Re:Regarding Newbb

2004/10/10 13:23
Draven
Module Developer
Posts: 337
Since: 2003/5/28

Look in include/newbb.css for ".head". I believe that is the class you are looking for.

86

Re:uploader.php and Notice: Undefined index:

2004/10/10 13:17
Draven
Module Developer
Posts: 337
Since: 2003/5/28

Undefined index means that the array key you are looking for in the HTTP_POST_VARS doesn't exist. Ensure that that the variable it is looking for is being past via POST and not get GET, or that the var is being passed at all.

It sounds to me as though the Filename of the file you are trying to upload is either not being passed, or is being passed using the wrong variable name.

87

Re:block help...

2004/10/10 13:12
Draven
Module Developer
Posts: 337
Since: 2003/5/28

Have you gone into your prefernces and set the templates to update? If not, then you are using the cached versions and that's why you are not seeing your changes.

88

Re:Rate my site

2004/10/10 12:50
Draven
Module Developer
Posts: 337
Since: 2003/5/28

LMAO, WTF?

89

Re: Loving Xoops and Learning the Setup

2004/10/9 17:45
Draven
Module Developer
Posts: 337
Since: 2003/5/28

Quote:

navanywhere wrote:
Hello. I just setup my XOOPS website. I would like to add two secondary members to the website. Each of these members needs to be given access to publish their own content separate from my content. They are not administrators of the website but I want to give them administrative rights to edit their own content that behave like separate websites within the main website and to access modules that will not be seen by the anonymous users. I also want these members to have modules that are separate from the modules that I use and each other. I need to share modules with these members but customize each module differently for each of these members.

What you are looking for is what is referred to in the CMS community as WorkFlow Managament. Currently, XOOPS does not have true workflow management built in (however it is on the todo list). You can emulate workflow management to some degree using the groups system and some modules such as WF-sections allow you to assign tasks to certain groups. Unfortunately there's no system in place for doing this on a per user basis.

90

Re:wf-sections: layout and sections question

2004/10/7 22:13
Draven
Module Developer
Posts: 337
Since: 2003/5/28

One way I can think of off the top of my head is to make the main section theme a switch. What I mean is, set it up to include a different template based on the section being viewed. Either by using the section id or some other variable set in the sections document to be used in smarty as a switch.

I do this all the time in my themes to allow different templates for different modules. By using the theme.html as a switch, I can include different templates for each module. So when someone is viewing the news module, the news.html theme is included into the theme.html template to beused for layouts specific to the news module.

Here's the code I use in my theme.html to make this happen:


<{php}>

if(is_object($GLOBALS['xoopsTpl'])){

    $mod = $GLOBALS['xoopsModule'];

    $dirname = (isset($mod) ? $mod->getVar('dirname') :'system');

    $GLOBALS['xoopsTpl']->assign( 'xoops_cmod', $dirname );

}

<{/php}>

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="<{$xoops_langcode}>" lang="<{$xoops_langcode}>">

  <head>

          <meta http-equiv="content-type" content="text/html; charset=<{$xoops_charset}>" />

          <meta http-equiv="content-language" content="<{$xoops_langcode}>" />

          <meta name="robots" content="<{$xoops_meta_robots}>" />

          <meta name="keywords" content="<{$xoops_meta_keywords}>" />

      <meta name="description" content="<{$xoops_meta_description}>" />

      <meta name="rating" content="<{$xoops_meta_rating}>" />

          <meta name="author" content="<{$xoops_meta_author}>" />

          <meta name="copyright" content="<{$xoops_meta_copyright}>" />

          <meta name="generator" content="XOOPS" />

          <{$metaextra}>

          <title><{$xoops_sitename}> - <{$xoops_pagetitle}></title>

          <link href="<{$xoops_url}>/favicon.ico" rel="SHORTCUT ICON" />

          <link rel="stylesheet" type="text/css" media="all" href="<{$xoops_themecss}>" />

          <script type='text/javascript' src='/standard.js'></script>

          <!-- RMV: added module header -->

          <{$xoops_module_header}>

          <{$metaextra}>

          <script type="text/javascript">

          <!--

          <{$xoops_js}>

          //-->

          </script>

  </head>

  <body>

    <!-- If we are viewing a module other than the system module, then include the module template -->

    <{if $xoops_cmod != "system" && $xoops_cmod != ""}>

        <{include file="marketing/$xoops_cmod.html"}>

    <{else}>

        <!-- otherwise use the system module-->

        <{include file="marketing/system.html"}>

    <{/if}>

  </body>

</html>

Basically the small section at the top is used to determine what module is currently being viewed:


<{php}>

if(is_object($GLOBALS['xoopsTpl'])){

    $mod = $GLOBALS['xoopsModule'];

    $dirname = (isset($mod) ? $mod->getVar('dirname') :'system');

    $GLOBALS['xoopsTpl']->assign( 'xoops_cmod', $dirname );

}

<{/php}>

Then in the body of the theme I invlude the appropriate theme for the module.


<!-- If we are viewing a module other than the system module, then include the module template -->

    <{if $xoops_cmod != "system" && $xoops_cmod != ""}>

        <{include file="marketing/$xoops_cmod.html"}>

    <{else}>

        <!-- otherwise use the system module-->

        <{include file="marketing/system.html"}>

    <{/if}>

The way this works is it includes the module theme using Module_name.html. So in my themes folder I have a template for each module (example: news.html or wfsection.html).

If no module is found or the module variable is blank, like for the homepage, I include a default system.html template to be used.

You can get much more complex then this, but I won't get into that as it usualy has a limited application.

This ystem is nice for things like making the forum module 100%, while having the rest of the site in a fixed width.

Stats
Goal:	$100.00
Due Date:	May 31
Gross Amount:	$0.00
Net Balance:	$0.00
Left to go:	$100.00

Forum Index

Re:Loving Xoops and Learning the Setup

Re:Altern8News and News

Re:uploader.php and Notice: Undefined index:

Re:Regarding Newbb

Re:Regarding Newbb

Re:uploader.php and Notice: Undefined index:

Re:block help...

Re:Rate my site

Re: Loving Xoops and Learning the Setup

Re:wf-sections: layout and sections question

Login

Search

Recent Posts

Re: Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Rebuilding and Updating a 20 years old Xoops Website from 2.0.18? to 2.5.11

Re: NewBB v 5.1.0 b 6

Re: NewBB v 5.1.0 b 6

NewBB v 5.1.0 b 6

Re: XOOPS 2.5.11 search user is not working

Re: oledrion

Re: oledrion

Re: oledrion

Re: oledrion

Who's Online

Donat-O-Meter

Latest GitHub Commits

{{ record.sha.slice(0, 7) }} - {{ record.commit.message | truncate }}