Critical error while trying to access usermgr.php Critical error while trying to access usermgr.php
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Critical error while trying to access usermgr.php

Started by Aleksandra, August 10, 2006, 12:01:09 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Aleksandra

Aww. Alright, so here's the deal. I previously upgraded from 1.3.5 to 1.4.8 (I'm not sure if this should be here or in the "cpg 1.4 upgrading" forum - I apologize if this thread is miscategorized). When I was running 1.3.5 I, out of nowhere ran into a Critical error when trying to access usermgr.php, which is much similar - if not identical - to the one I'm having now. Since upgrading, the error reappeared. However, the fix I applied to CPG 1.3.5 no longer seems to work for 1.4.8 - I tried it, but there was no apparent change. I also tried searching the boards here, but I couldn't find a solution, and thus I'm posting a support request for this error once more, only this time for 1.4.8 usermgr.php. :)

When enabling debug mode, this is what I get.

QuoteCritical error:

There was an error while processing a database query.

QuoteWhile executing query "SELECT user_id as user_id, user_name as user_name, user_email as user_email, UNIX_TIMESTAMP(user_regdate) as user_regdate, UNIX_TIMESTAMP(user_lastvisit) as user_lastvisit, user_active as user_active, COUNT(pid) as pic_count, ROUND(SUM(total_filesize)/1024) as disk_usage, group_name, group_quota FROM `web16-gallery`.cpg135_users AS u INNER JOIN cpg135_usergroups AS g ON u.user_group = g.group_id LEFT JOIN cpg135_pictures AS p ON p.owner_id = u.user_id GROUP BY user_id ORDER BY user_regdate DESC LIMIT 0, 25;" on Resource id #5

mySQL error: The SELECT would examine more than MAX_JOIN_SIZE rows; check your WHERE and use SET SQL_BIG_SELECTS=1 or SET SQL_MAX_JOIN_SIZE=# if the SELECT is okay

QuoteFile: /home/sites/daisymedia.net/public_html/gallery/include/functions.inc.php - Line: 249

I redownloaded the file, in case it was corrupt, but no dice. I still get the same error. Any suggestions? :)

Joachim Müller

This is a mySQL error that shows you're running into restrictions imposed by your webhost - it's not related to Coppermine. Ask your webhost for support.

Aleksandra

^ Ah, thank you. I contacted my host about this, giving her pretty much the same info as I've given in this thread, who contacted her host in return. This is the response she got from the tech guys, but I'm not quite sure what they want me to do - I'm not hugely familiar with MySQL, I'm afraid. Ideas? :)

QuoteYou simply need to edit the scripts that have this error to execute the mysql command SET SQL_BIG_SELECTS=1.

Nibbler

Add the code into usermgr.php

cpg_db_query("SET SQL_BIG_SELECTS=1");

Aleksandra

^ Yay, thank you! :D I put the above strip of coding right under "require('include/init.inc.php');" in usermgr.php and the user manager works like a dream now. Problem solved!

Jasondt2001

I absolutely LOVE this board... I've been pulling my hair out 'trying to do it myself' - Hit the search key and it's already been asked... Another example why this board does NOT operate helping individuals VIA PMs!
Thank you all, so much!
- Jason