42
What kind of 'more complicated' do you mean, can you be more specific to what options/designs you reffer? When looking @ the source, you have the basics allright, but there is indeed much more to it.
45
Over complicating things, yes, guess that's just human nature. My comment on your understanding might have been a little harsh and even wrong, but there was just quite some irritation I had to get out. You're not the only one who's stated that everything is easily fixable and telling Xoopsers to 'just do it better....'
I'll just leave it at that
I'll just leave it at that
46
Pretty easy reply don't you think? Don't mean to flame you or anything, but just saying FIX IT shows your complete lack of understanding concerning open source as a whole and XOOPS as a part of it. Even without understanding those things you must at least understand that if it were that simple, it would have al been solved/changed bij now.
Concerning your problems with the forks, it happens, it's unfortunate, but it happens. Bear in mind that most OS CMS' are actually forks. Where do you think XOOPS came from? It sure didn't appear out of nowhere!
When using the argument that when there are 3 Xoops-forks you'll have to check them al out is just ridiculous. That would mean you'd actually have to check OUT every CMS available, because you might just miss something....
Concerning your problems with the forks, it happens, it's unfortunate, but it happens. Bear in mind that most OS CMS' are actually forks. Where do you think XOOPS came from? It sure didn't appear out of nowhere!
When using the argument that when there are 3 Xoops-forks you'll have to check them al out is just ridiculous. That would mean you'd actually have to check OUT every CMS available, because you might just miss something....
47
Is it possible to show the code. Because I assure you the php-option hasn't been put in for future use, it actually works
48
The example posted above is to be used in the main theme file.
A totally different approach to reaching my goal would also be greatly appreciated Oops, is this a bump 
A totally different approach to reaching my goal would also be greatly appreciated
Oops, is this a bump
49
I’m probably just trying to make things harder than necessary, but here’s what I want to achieve: I want to assign a smarty variable that holds the groupid of an user. I need it to be global because it will be used in a dropdown menu which is always displayed. Currently I add extra menus or menuoptions by using these smarty variables: <{if $xoops_isadmin}> and <{if $xoops_isuser}>.
Now I want a variable that will hold groupid so I can use it like this: <{if $groupid == 4}> display newsposters/approvers menu <{/if}>.
I actually thought I could achieve this without hacking, using the smarty php tags. I wanted to create something like this:
Quote:
This is just an impression because I know it can’t work like this. Someone who knows how I can achieve this?
Now I want a variable that will hold groupid so I can use it like this: <{if $groupid == 4}> display newsposters/approvers menu <{/if}>.
I actually thought I could achieve this without hacking, using the smarty php tags. I wanted to create something like this:
Quote:
<{php}>
GLOBAL $xoopsDB;
$userid = $xoopsUser->getVar('uid');
$thegroupid = "SELECT groupid FROM ".$xoopsDB->prefix("groups_users_link")." WHERE uid = userid";
$GLOBALS['xoopsTpl']->assign('group', $sql);
<{/php}>
This is just an impression because I know it can’t work like this. Someone who knows how I can achieve this?
Login
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|