1
unlucky
Re: System Admin Rights Problem
  • 2006/5/11 20:30

  • unlucky

  • Just popping in

  • Posts: 26

  • Since: 2005/8/26


Woops, I knew I forgot something... I am normally good about that too. :P

Xoops Version: 2.2.2
System Version: 2.11
MySQL Version: 3.23.58

Hope that helps.



2
unlucky
System Admin Rights Problem
  • 2006/5/11 18:31

  • unlucky

  • Just popping in

  • Posts: 26

  • Since: 2005/8/26


Hello,

So I am having a problem with setting system access rights. Specifically, it is about setting the rights to "Edit Users". I have searched the forums and havent found anything, but I might have missed it. If so, I apologize for wasting your time.

However, here is the problem in more detail.

In System->Groups->Modify Group I have all of the wonderful little check boxes you would expect. And in the "System Admin Rights" row at the top, for the Webmaster group, they are all checked except for "Edit Users". When I click the checkbox and then submit it, it says that the database was successfully updated. However, when I go back to the groups, the "Edit Users" box is still not checked. In viewing the source, this is what it says that particular checkbox is:

<input type='checkbox' id='system_catids[]13' name='system_catids[]' value='XOOPS_SYSTEM_USER' />Edit Users


Any reason why it would be passing the XOOPS_SYSTEM_USER as a value? And any idea how to fix this?



3
unlucky
Re: Modversion Config Problem
  • 2006/5/11 16:20

  • unlucky

  • Just popping in

  • Posts: 26

  • Since: 2005/8/26


Alright, I took out the references to adminIndex and adminMenu, and I uninstalled the module. I then reinstalled the module, and it shows up in preferences, and it has a default value.

Thanks for all your help!



4
unlucky
Re: Modversion Config Problem
  • 2006/5/11 15:58

  • unlucky

  • Just popping in

  • Posts: 26

  • Since: 2005/8/26


Semi-related question... is it possible to have a preferences page (System->Preferences->"Module Name" Preferences) without having an admin page?

I dont have any admin pages, and as of now, I dont have anything that needs them. I just have a few preferences I want set.

I added this:
// Admin things
$modversion['hasAdmin'] = 1;
$modversion['adminindex'] = "admin/index.php";
$modversion['adminmenu'] = "admin/menu.php";


but that didnt help with the preferences thing. I am thinking that since I have no admin section, the admin index and menu arent necessary. But can I still do preferences?



5
unlucky
Modversion Config Problem
  • 2006/5/11 15:22

  • unlucky

  • Just popping in

  • Posts: 26

  • Since: 2005/8/26


Hello,

I have scoured the forums and hopefully I didnt overlook anything that addresses this issue, so I am going to ask it.

I am having problems with a module I am writing. I have tried to add a config section to my xoops_version file. This is what my entry looks like:

$modversion['config'][1]['name']='headshot_dir';
$modversion['config'][1]['title']='_MI_ERUD_HSPATH_TITLE';
$modversion['config'][1]['description']='_MI_ERUD_HSPATH_DESC';
$modversion['config'][1]['formtype']='textbox';
$modversion['config'][1]['valuetype']='text';
$modversion['config'][1]['default'] = 'dir/';


All I want it to do is allow for a way to set a default directory.

Now, there are two problems related to this. First of all, the default value is never there. I have tried all sorts of variations, using double quotes, defining a value in the modinfo.php, etc. But no matter what I do, for some reason, it will not ever set the default option.

And the second problem is that the link to get to this preference file does not show up under System->Preferences like I expect it to. I have to manually change the URL to get to it.

The title and description both show up just fine, and the preferences page looks fine, when I manually type in the URL. But there is no link, and it wont show my default value.

Any ideas?



6
unlucky
Re: Undefined template_c problem
  • 2006/3/1 17:31

  • unlucky

  • Just popping in

  • Posts: 26

  • Since: 2005/8/26


Ok, after two or three days of this crap, I fixed it.

First, I had to hack up recovery.php in order to get the debug to work (stupid PM using the same database key). Then, once I got a bit better understanding of what was going on, I tried playing around with some different themes (as per Juliette's advice) and found that the default one and my custom theme wouldnt work, but the other themes would.

So I figured something about the themes were corrupt, so I uploaded a fresh copy of my custom theme (I dont happen to have a copy of the default one here) and that worked, but some of the modules (specifically the News module) didnt work right.

So I went into the templates and deleted all the ones being used by the afflicted module and regenerated them. Now everything seems to work fine.

Still not sure what caused the problem in the first place, but it works now.



7
unlucky
Re: Undefined template_c problem
  • 2006/3/1 4:25

  • unlucky

  • Just popping in

  • Posts: 26

  • Since: 2005/8/26


When I finally got recovery.php to work, I set everything to default. It showed no difference.

[EDIT] However, if I set the theme to anything other than DEFAULT and my own custom theme, it works but with a lot of warnings (even when I turn off debug). So now it looks like there is a problem with my theme and default... any suggestions from that? [/EDIT]



8
unlucky
Re: Undefined template_c problem
  • 2006/3/1 1:41

  • unlucky

  • Just popping in

  • Posts: 26

  • Since: 2005/8/26


Ok, so I finally got debugging to work. The site is still screwed to all hell, but I can see a little better.

Here is an updated output of the debug:

Quote:

Notice [PHP]: Undefined index: theme in file kernel/object.php line 282
Notice [PHP]: Undefined index: theme in file kernel/object.php line 283
Notice [PHP]: Undefined index: theme in file kernel/object.php line 378
Notice [PHP]: Undefined index: timezone_offset in file kernel/object.php line 282
Notice [PHP]: Undefined index: timezone_offset in file kernel/object.php line 283
Notice [PHP]: Undefined index: timezone_offset in file kernel/object.php line 378


So that is all that is showing, but the SMARTY Debug now pops up too. According to the SMARTY, everything is there. It shows everything loaded into the page, and what not. But all that shows up are these notices.

Anyone got anything to shed some light on this situation? Anyone? Anyone at all?



9
unlucky
Re: Recovery.php
  • 2006/3/1 1:33

  • unlucky

  • Just popping in

  • Posts: 26

  • Since: 2005/8/26


lol, you got my hopes up... here I was thinking someone was going to help me solve this problem. But I appreciate the bump, means I dont have to do it...

But, here is another update.

So I found where that _MI_DEBUG_MODE mode was coming from. When looking for config options, recovery.php looks for anything with the following key:

array('debug_mode''theme_set''theme_set_admin''enable_badips''template_set''session_expire');


The problem is, debug_mode is defined for conf_modid 1 (system), but it is also defined for conf_modid 10 (private messaging). I dont know enough about this code to add into the Criteria() to check for only conf_modid 1, so instead I did a really ugly work around by renaming the debug_mode defined for private messaging to debug_mode1 for now. I know it is an ugly fix, but once I get my site working, I will go back and change it back.

Perhaps someone with some more skill than me can go through and figure out a way to set it up so that recovery.php will only get config options for system stuff and ignore other mods?

And... now back to my original problem (see here) where you will find an update on the problem that lead me into this downward spiral of despair and hatred of all things php.



10
unlucky
Re: Recovery.php
  • 2006/2/28 20:41

  • unlucky

  • Just popping in

  • Posts: 26

  • Since: 2005/8/26


In looking at the code for recovery.php I have outputted some different aspects of it to try to debug the problem. I outputted the config values that recovery.php generated and the list contained two different parts labeled "debug_mode".

The values for the two versions of debug_mode are:

conf_name debug_mode
conf_title _MD_AM_DEBUGMODE
conf_formtype select_multi

conf_name debug_mode
conf_title _MI_DEBUG_MODE
conf_formtype yesno

I dont know why it is drawing on two different versions of debug_mode, but it is preventing me from changing my debug options through recovery.php.

Anyone know anything that can help me fix this problem so that I can get back to the original problem?




TopTop
(1) 2 3 »



Login

Who's Online

259 user(s) are online (178 user(s) are browsing Support Forums)


Members: 0


Guests: 259


more...

Donat-O-Meter

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

Latest GitHub Commits