171
toddherrold
Re: Auto-login with xoops sites...???

Excellent hack!!!!
Works great with latest version of IE and Netscape. However, it doesn't seem to work with Firefox : (



172
toddherrold
Re: WebmailFX username password problem

I just discovered something very interesting related to this problem. As earlier noted, it doesn't occur for accounts manually created via "admin email," but only on automatic, user created accounts. What is most interesting is that it also DOES NOT occur when Webmail Debug is turned on. This is why I didn't notice the problem prior to launching it. When running in debug mode, everything works fine, but when debug is turned off, each time a user logs in, the previous account password is denied and a new account is created. . . here's another error message:

Quote:

Openning Connection to: mail.hotdogblog.com
Connection opened
Sending Command: USER rickjames@hotdogblog.com
Result OK:
Sending Command: PASS 123654
Result OK:
Sending Command: NOOP
Result OK:
Sending Command: STAT
Result OK:
Openning Connection to: mail.hotdogblog.com
Connection opened
Sending Command: USER rickjames@hotdogblog.com
Result OK:
Sending Command: PASS 128776
Error: -ERR Username/Password Mismatch perhaps rickjames@yourdomain.com ? Sending Command: NOOP
Error: Sending Command: STAT
Error:



173
toddherrold
WebmailFX username password problem

I recently installed WebmailFX and it works fine if an email account is set using "admin email" in the module admin section. I'm trying to automate account creation for users of my site, using this feature:

Quote:
New Feature in RC2b: Now Cpanel accounts are automaticlly created when the following group permissions are set-
Go to "User Created Webmail Permissions"
1-Check "Allow webmail"
2- Make sure "user create name" is NOT checked.
3- Check "lock xoops".
That's it! Now when a user first opens webmailfx, it will check if that user already has an account. If not it will create one using his XOOPS name for the email and will generate a random password for it.


This results in multiple accounts in the webmail database when a user enters the module page and the following example error message:

Quote:
Error: -ERR Username/Password Mismatch perhaps harry@yourdomain.com ?
Error: Error: Error: -ERR Username/Password Mismatch perhaps
harry@yourdomain.com ? Error: Error: Error: -ERR Username/Password
Mismatch perhaps harry@yourdomain.com ? Error: Error: Error: -ERR
Username/Password Mismatch perhaps harry@yourdomain.com ? Error: Error:
Error: -ERR Username/Password Mismatch perhaps harry@yourdomain.com ?
Error: Error:
Account E-Mails Total Size
harry@hotdogblog.com 1 5 Kbytes
harry@hotdogblog.com 0 Kbytes
harry@hotdogblog.com 0 Kbytes
harry@hotdogblog.com 0 Kbytes
harry@hotdogblog.com 0 Kbytes
harry@hotdogblog.com 0 Kbytes


Only 1 email account in cpanel gets created per user, but multiple instances in the webmail database. this user went into the webmail module 6 times, and hence the 6 accounts plus all the error messages. It seems that webmail isn't sending the username or the password correctly, interprets that no email account exists, and then creates a new one. . . the new one works until the user exits it and comes back, at which point a new one is created. . Interestingly, this doesn not happen for accounts manually created through "admin email." These work fine.

I'm running:
Xoops 2.0.10
CPanel 9
PHP 4.3.10
Apache 1.3.33

Any ideas?



174
toddherrold
Re: My Xoops site crashing host

i have a lot of my blocks cached, but when I run MySQL debug, it shows that nothing is cached. What could be the cause of this?



175
toddherrold
Re: Site Crashes - PLEASE HELP

next time it happens, log into phpMyAdmin or the equivalent on your site and take a look at your SQL database. The error messages you receive on your blank homepage look like the ones i get when my site exceeds the max_questions resource for SQL queries.

If it is the same issue for you, the issue should be periodic, especially when you are installing modules or during heavy traffic on the site, like in chat or forums, and the site should miraculously re-appear usually within one hour.

When you log into your SQL dbase, instead of seeing the database structure, you will see an error message indicating max_questions exceeded. (that is, if it is the same issue, which it may be).



176
toddherrold
Re: XcGallery

works fine for me and has for about 1 year. . you should really give a little more information if you want a useful response.



177
toddherrold
potential max_questions resource solution

I posted this on large thread for max_questions, but thought I would raise it up to a new thread, given my sense that this is the solution that many of us are looking for.

What is needed is this tailored to XOOPS by someone who knows the code better than I do. Can someone look at this and determine how to implement a similar solution for XOOPS. (I tried to delete my other post, but don't have the priviledge, so apologies for duplication. I felt this is a serious issue for many of us and wanted to make sure it got noticed).

Thanks!

Quote:
(host) currently limits users to 72,000 SELECT queries, per hour, per user. Once you have used up your quota, you will begin to receive "max_questions" errors until the end of the hour, and your quota is reset. Please note, this limit only applies to SELECT queries, and not INSERT queries. There has been no official word on whether UPDATE queries are affected.

Most users will never notice this limitation, however there are some programs out there that are very unconservative with their queries. Forums (AKA: bulletin boards, message boards) such as phpbb and CMS's (Content Management Systems) such as phpnuke are typically the greatest offenders due the large number of queries and the rapid click through rate.

To compensate for this limitation, you can set up 2 additional users (for a total of 3 users), and spread out your queries among them. This will give you a total of 216K SELECT queries. To set this up, you must complete 5 steps.

1) Log in to ops and go to packages > MySQL. Add users until you have 3, making sure that each user has the exact same password.

2) Locate where the database information is stored. Often it will be in a file called config.php, base.php, include.php or common.php. You should find the name, the user name, password, and server for your database.

3) Once you have found the file, you will see the variables defined in one of two fashions.
A regular variable will look like this: $db_user = "user_name";
Defined variables will look like this: define("db_user", "user_name");

4) Add the following lines of code immediately after the line you commented out.

$db_user_array[] = ""; //enter 1st user name
$db_user_array[] = ""; //enter 2nd user name
$db_user_array[] = ""; //enter 3rd user name

5) Depending on whether your script uses regular variables, or defined variables, enter one of the following lines after everything else we just added. Make sure you change "db_user" into whatever the correct name should be (see the line that you commented out).

//regular variable
$db_user = $db_user_array[ rand( 0, ( sizeof($db_user_array) -1 ) ) ];

//defined variable
define( "db_user", $db_user_array[ rand( 0, ( sizeof($db_user_array) -1 ) ) ] );

If you end up needing to remove one of your database user names in order to allow someone else to use your database, or if Powweb changes their number of users, updating the rotation script is as simple as adding or removing users from the list (eg: $db_user_array[] = ""



178
toddherrold
Re: max_questions resource problem AND SOLUTION!!

Below is a post from a phpnuke forum. . apparently XOOPS and phpnuke both have problems with running large #s of dbase queries. Anyway, the suggestion below is to add $db_users. I've added these in MySQL.

Can someone more technically savvy than me, please post how we would implement a similar solution in XOOPS? It would be greatly appreciated by many of us!


Quote:
(host) currently limits users to 72,000 SELECT queries, per hour, per user. Once you have used up your quota, you will begin to receive "max_questions" errors until the end of the hour, and your quota is reset. Please note, this limit only applies to SELECT queries, and not INSERT queries. There has been no official word on whether UPDATE queries are affected.

Most users will never notice this limitation, however there are some programs out there that are very unconservative with their queries. Forums (AKA: bulletin boards, message boards) such as phpbb and CMS's (Content Management Systems) such as phpnuke are typically the greatest offenders due the large number of queries and the rapid click through rate.

To compensate for this limitation, you can set up 2 additional users (for a total of 3 users), and spread out your queries among them. This will give you a total of 216K SELECT queries. To set this up, you must complete 5 steps.

1) Log in to ops and go to packages > MySQL. Add users until you have 3, making sure that each user has the exact same password.

2) Locate where the database information is stored. Often it will be in a file called config.php, base.php, include.php or common.php. You should find the name, the user name, password, and server for your database.

3) Once you have found the file, you will see the variables defined in one of two fashions.
A regular variable will look like this: $db_user = "user_name";
Defined variables will look like this: define("db_user", "user_name");

4) Add the following lines of code immediately after the line you commented out.

$db_user_array[] = ""; //enter 1st user name
$db_user_array[] = ""; //enter 2nd user name
$db_user_array[] = ""; //enter 3rd user name

5) Depending on whether your script uses regular variables, or defined variables, enter one of the following lines after everything else we just added. Make sure you change "db_user" into whatever the correct name should be (see the line that you commented out).

//regular variable
$db_user = $db_user_array[ rand( 0, ( sizeof($db_user_array) -1 ) ) ];

//defined variable
define( "db_user", $db_user_array[ rand( 0, ( sizeof($db_user_array) -1 ) ) ] );

If you end up needing to remove one of your database user names in order to allow someone else to use your database, or if Powweb changes their number of users, updating the rotation script is as simple as adding or removing users from the list (eg: $db_user_array[] = ""



179
toddherrold
Re: Can someone tell me how to tell if my XOOPS install closes the database connections automaticall

Thanks!



180
toddherrold
Can someone tell me how to tell if my XOOPS install closes the database connections automatically?

I know that XOOPS is supposed to automatically close database connections, but I think I remember that during a recent re-install I was asked whether I wanted it to be permanently open, and I think I might have selected "yes."

I've been having a lot of problems with exceeding my "max_questions" limit of 50,000 per hour to the database resulting in blank pages until it resets and I wonder whether this could be the problem. My webhost told me that my script is not closing the database connection, but I can't figure out how to tell if it is or isn't. . .

Is this something that would be in "configure.php?"

Thanks.




TopTop
« 1 ... 15 16 17 (18) 19 20 21 ... 23 »



Login

Who's Online

123 user(s) are online (79 user(s) are browsing Support Forums)


Members: 0


Guests: 123


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