1
fireflies
Re: problem with modules
  • 2008/11/2 1:50

  • fireflies

  • Just popping in

  • Posts: 4

  • Since: 2008/10/29


I can click on the system module and it brings up the menu options.. I can reach preferences on that menu and turn on debug.

When I go to the modules page with debug on I get:

Fatal error: Undefined class name 'xoopslocal' in /home/media/public_html/include/functions.php on line 185

All errors (0) queries (6) blocks (0) extra (0) timers (3)
Errors
Queries
SELECT * FROM x_config WHERE (conf_modid = '0' AND conf_catid = '1') ORDER BY conf_order ASC
SELECT sess_data, sess_ip FROM x_session WHERE sess_id = '674d5f42142fcf4e040426aa90596e78'
SELECT * FROM x_users WHERE uid = '1'
SELECT * FROM x_modules WHERE dirname = 'system'
SELECT * FROM x_group_permission WHERE (gperm_name = 'module_admin' AND gperm_modid = '1' AND (gperm_groupid = '1' OR gperm_groupid = '2'))
SELECT * FROM x_modules
Total: 6 queries
Blocks
Total: 0 blocks
Extra
Timers
XOOPS took 0.028 seconds to load.
XOOPS Boot took 0.017 seconds to load.
Module init took 0.011 seconds to load.

(I changed the MySQL prefix/table names and sessionid for security purposes in this post)



2
fireflies
Re: problem with modules
  • 2008/10/31 1:05

  • fireflies

  • Just popping in

  • Posts: 4

  • Since: 2008/10/29


ok still not getting anywhere with this and I don't know what to try next (aside from another CMS) any suggestions before I resort to that anyone? :)



3
fireflies
Re: problem with modules
  • 2008/10/29 11:14

  • fireflies

  • Just popping in

  • Posts: 4

  • Since: 2008/10/29


Ok, I deleted the xcenter directory (I'm 99.9% sure there were no modules listed previously but best to confirm) and I had another look in the modules administration - still just the system module.

I went through Sailjapan's steps - moved and renamed the two folders; moved the two mainfile files (best not to delete just in case!) followed the steps in docs/install.html which said to use the mainfile.dist.php.protector in the extras folder, rename it and shove it in htdocs (ie public_html) - done.

made the two "trust path" folders writable, and the subdirectories to the data folder
moved the original mainfile.php into public_html
moved the install folder back

went through the install process again

back into the modules administration section and there is only the system module listed (does not show any other modules, and no options for the system module such as version, last update, active, order, action) does appear to have an option to rename the system module (I'll leave it as it is though)

any further help gratefully appreciated!






4
fireflies
problem with modules
  • 2008/10/29 2:06

  • fireflies

  • Just popping in

  • Posts: 4

  • Since: 2008/10/29


Hi,

I'm a new user of XOOPS and I have installed it on my site and want to get started installing modules...

currently in my modules directory I have:

pm, profile, protector, system, thadmin and index.html

following instructions I downloaded the xcenter module and copied the xcenter folder into the modules directory. I then logged into XOOPS on my site and clicked on the module administration link, expecting to see a list of modules waiting to be installed..

All I have on the page for modules administration is:

"System"


I cannot see any other modules here, and looking around, I have no idea where to begin.

I looked on the support forums and saw a post with instructions on "Starting a new XOOPS site" which suggested downloading several modules. the "protector" one sounded important (I hadn't seen that there was a folder already in my modules folder with this name) so I thought I would try that and see if that would show up in the list..

I went to the linked site, went to the downloads section, scrolled down a long way to find protector and then got completely baffled by the technical jargon:

It says that they strongly recommend installing it on all XOOPS sites with any versions (ok, sounds very important, where do I start, I think)

installation instructions...(ok good place to start, it will tell me in simple terms what to do, thats a big help)

(this is taken word for word from the first line below INSTALL)

"First, define XOOPS_TRUST_PATH into mainfile.php if you've never done it yet."

as a new user to xoops, and being told this is an important module that everyone should install.. this makes me think I've made the wrong decision somewhere, because clearly I have no idea what an XOOPS_TRUST_PATH is or how to define something..

it says to copy something into the XOOPS root path.. I can guess what it means by that, I'm not entirely stupid and I've been working with websites long enough to know root paths etc.

then it wants me to copy something into the XOOPS trust path.. once again, completely clueless on this..

What I want to know is:

1) Have I made the wrong decision choosing XOOPS for my site?

2) How do I install a module as its not showing in module administration

3) Is protector installed or ready to install already, and if not, where can I find the English version of the instructions (ie for someone who doesn't know XOOPS specific terms, such as a new user like myself)

any help with this would be gratefully appreciated!






TopTop



Login

Who's Online

174 user(s) are online (105 user(s) are browsing Support Forums)


Members: 0


Guests: 174


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