Excellent stuff seymour, this worked perfectly (and swiftly also) and I got my XOOPS DB successfully on my web host now.

Please note that I did the suggested thing and practised re-installing and migrating it a few times on my local server to make sure I got the gist of the config editing correctly - and all test runs were successful, but.........

Now I have uploaded my XOOPS folder to the root of my www folder on the web host and when I go to the main page I get this error here:

I reuploded it to the web host a few times in case it became corrupted in transit, but still that error.

I went thru all the suggested steps on this page here, but to no avail:

http://wiki.xoops.org/wakka.php?wakka=TroubleshootingBlankPage

Any solutions for this next glitch please?

I just spent 3 weeks building a fanstastic XOOPS site for a local community group and I am unable to migrate the XOOPS SQL DB to my clients webhost.

I sent the SQL #1064 error messages to the hosts tech support and am informed that they are still running an older version of MySQL (version 4.0.24) and that because my XOOPS site was built on my local MySQL server version 4.1.8nt then I will not be able to use it on their hosting space.

They tell me they have no future intentions to upgrade their servers to current version 4.1.x of MySQL and also say this:
Quote:

Now I am in a panic because I need to get this site live for my clients in less than two days and I have no clue how to approach this problem at such short notice.

The specific syntax in the DB which is causing the errors is:


Help please! What can I do???

Quote:
Good scheme jelly bean! Thanks for your input LazyBadger. I just created an extra user group as your suggested called "Expired Members" and gave it the same access permissions as a "Guest User" so they cannot view anything in the private area. This will be a piece of cake to manage by changing group status.

I didn't want to go deleting any pages from the site since I am still new and not confident yet with the things I can and cannot pull to pieces. I did however make backup copies of login templates and edited out the text/link which directed to the registration.php and set the site to not accept any registrations.

Now I have just a few more questions to check out with y'all....

Am I correct in assuming that even tho I have set the site to not accept registrations, I will still be able to overide that from the Admin menu and manually set up new accounts? Can admin directly assign their "first issued" site password, so I can just enter the ht passwords they are already using to access private sub-domain?

Also, I think it would be important for "expired users" to get some kind of notification when they log in to the site. So, is it possible to set up some kind of "redirect" where the users in the expired group are sent to another page that only they can view which notifies them to contact the club treasurer?

And one last question, and it's a bit of a gurly one I know, but this club likes to refer to their "non-members" as "visitors", so to keep congruent to that, is there a way where I could globally (across the entire site) change "guest" to "visitor" so that is what they see in the "who's online" and user groups?

Cheers for reading in
Z

Hiya peeps, I'm just about to embark upon my first XOOPS website. It is a local community website which has been online for about 6 years, written in vanilla HTML, and mostly consists of members content and newsletter archives.

The site has a few pages that are open to the public with information about the club and the rest of it is members-only access, on a sub-domain with access via ht password protection on the directory which contains the sub-domain.

The private area is only available to local members who have paid their annual club fees and I do not want this to be managed from the front end of the site where users can "sign up to register".

I am wanting to implement it somehow that all users (members) must be set up manually by the site admin (currently myself) and with the members name (no nicknames, just real life names) and the club treasurer issues them a new password each year when they have renewed their club fees.

Members accounts that do not renew their fees by the annual date I would want to be able to suspend access, but not actually delete them, because the membership fluctuates each year and some members return after a year or two absence.

Can I remove the public registration access from the site and set it that unpaid members who try to log into suspended accounts would recieve a message to say that their account has been deactivated because they are not a financial member of the club?

The other factor here is that I am only planning to manage this site for another year and so whatever I put in place at this stage of the development would have to be a no-brainer to hand over to whoever takes over from me.

Are their any modules for this kind of thing, or have any XOOPS users here set up anything similar to this and how did they manage it from an access management point-of-view?

I'm interested to hear your ideas and experiences.

Cheers
Z

Quote:
Thanks for your reply Mithrandir, I went thru all the steps of restarting my web/sql servers and rechecking permissions and after a day of driving myself nuts trying to read sql documentation and find out what I was doing wrong with setting my db permissions, it turned out to be the simplest thing of all.....

I needed to set up XOOPS from in my local webserver environment using the username "root" and with "NO password". Tres bizarre, but that's what did the trick.

I've no idea why it would not install using the "new user" account I set up in phpMyAdmin (which had global permissions to everything but my sodding bank account ) but we're running now.

Wow you guys made this CMS a piece of cake to customise. Can't wait to impress my client with what this puppy can do.

Cheers muchly
Z

OK I dumped the Apache2Triad. Took me nearly an hour to manually clean the POS out of the registry so I won't be giving that any rave reviews at any time... ay caramba!

I've installed WAMP5 1.4.3 server now (with PHP downgraded to 4.3.11 and Apache 1.3.33) and got a few steps further down the installation path, but still not all the way yet. It writes to the mainfile.php OK now and everything is in the correct place in the next few install windows, but now I get to this one....

Check Database

Could not connect to the database server.
Please check the database server and its configuration.

Can't find anything in the tutes or docs to explain this error and it's way past my bedtime now, so I'll be back to check in manana.

Anyone can help please?

Cheers
Z

Quote:

Thanks for the offer but I am just not willing to enable stuff like IIS stuff on this box. I'm happy to try other open source webserver options if it turns out that is where the problem lies, but I'm not touching anything "microsoft" with a 20 foot pole.

Maybe I over-explained myself before... what I mean is that I wanted to use XSAS but wasn't able to because of the "Drive W" default setting, and the only other "all-in-one" local websserver solution I was able to find at short notice is Apache2Triad, so this is what I am using....

http://apache2triad.net/

Can somebody suggest a list of possible reasons why mainfile.php cannot be written to other than the obvious ones which I have ruled out already like "read only" file and "NTFS security permissions" ?

Cheers
Z

Hiya peeps! Great forum, great program, great to be onboard with such a fine open source initiative.

I am trying to install a fresh copy of XOOPS v2.0.10 onto my local webserver for testing a new site I'm developing for a local community group. My test server is a vanilla install of Apache2Triad v1.4.1 using following versions:

Apache version 2.0.53
MySQL version 4.0.24
PostgreSQL version 8.0.0
Openssl version 0.9.7e
Slimftpd version 3.16
Xmail version 1.21
Perl version 5.8.6
PHP version 4.3.11
Python version 2.3.4


FWIW I would have preferred to use the XSAS server but it will not give me an option of installing to a different drive letter (W is already in use on my local box) and nobody has responded to my cry for help over on the XSAS forum at sourceforge. But anyhoo, on to the problem.....

I've made all the necessary folders writable and give full access permissions to the database user name account in MySQL panel.


Install confirms:

Checking file and directory permissions...
Directory uploads/ is writable.
Directory cache/ is writable.
Directory templates_c/ is writable.
File mainfile.php is writable.
No errors detected.


Heres's my setup config:

Database mysql
Database Hostname localhost
Database Username (private)
Database Password (private)
Database Name xoops
Table Prefix xoops
Use persistent connection? NO
XOOPS Physical Path D:/WebServer/htdocs/xoops
XOOPS Virtual Pathhttp://localhost/xoops


Two windows later I am getting this error message:

Saving configuration data..
Could not write into mainfile.php. Please check the file permission and try again.


I've read and re-read the installation instructions and followed the very excellent wink tutorial over athttp://www.warpigw2.com/ (big kudos to the bloke who prepared this bunch of flash tutorials) but can't for the life of me figure out what I am doing wrong here.

I read some mumblings in another thread here that somebody was getting this same error after upgrading to Apache2.... is there anything I might need to enable in there which is not enabled in vanilla Apache2Triad setup? Or something I can do to check MySQL has correct permissions to edit the file?

I'm running Win2003 here (hacked to workstation), using Firefox browser to run the install, set my NTFS folder permissions to allow full file access, all my server bits are listening on correct ports and enabled in firewall (Outpost).

Hope that was enough info So, can any of you XOOPS guru's shed some light please?

Cheers m'dears

Z

Please Note: I am only trying to run this on local server for now - it might be a month or so before I get client approval and have it on a web hosted server - so I'm only concerned with this end of things for now and getting this XOOPS test server operational.

[edit: typos]

[re-edit: changed thread title to update status]