forum.coppermine-gallery.net
Dev Board => cpg1.4 Testing/Bugs => cpg1.4 Testing/Bugs: FIXED/CLOSED => Topic started by: reallove on July 06, 2005, 10:00:28 am
-
Hello,
My first coppermine install was the 1.3.2 version.I've made succesfuly the upgrade to 1.3.3 when this latest version was released.After a while,I moved the entire gallery to another server,more powerfull. (saved the mysql schema,archived the entire public_html and move them all to the new server).I had no problems,the gallery was running ok.
The problems occured when I wanted to upgrade to 1.4 beta from the new server.After running update.php,it displayed correctly the changes but when clicked to proceed to the gallery main page .. fatal error .I tried then to upgrade to my old server hosting,there I haven't deleted anything.And surprise,all was ok,upgrade was succesfuly.
To see what's the error go to http://reallove.sunbx.net . The 'downgrade' works fine,from this 'fatal error' 1.4 back to 1.3.3.
The server details (the new one who caused trouble) are :
linux 2.6.11.12
httpd -v output : Server version: SBXWS/3.1b (Unix)
PHP 5.0.4 (cli) (built: Apr 6 2005 01:05:54)
I use GD 2 ,ImageMagick is not installed.
If you need any details just let me know.
Thanks!
-
enable debug_mode to see what query actually fails when getting the fatal error.
-
Ok,it's enabled.Seems an error from mysql ? :-o
-
it appears that your mySQL user doesn't have the privileges needed to perform the upgrade (ALTER TABLE). Use a tool like phpMyAdmin to check if the column "player" actually exists in the table "cpg132_filetypes". Try running there the query
ALTER TABLE `cpg132_filetypes` ADD `player` VARCHAR( 5 ) ;there to see if there is an error message. Modify the permissions of the mySQL user if yes.
-
Ok,fixed after talking to the admin and changed my mysql user permissions.
Thanks for the tips !
-
OK, glad this has been fixed. As it wasn't actually a coppermine bug that kept the upgrade from working, but an improper webserver setup, I'm marking this thread as "invalid".
Joachim
-
enable debug_mode to see what query actually fails when getting the fatal error.
How do i actually enable debug_mode if i cant even load the gallery?
-
no need to enable debug mode for you, as you already know what query fails (see your posting on the other thread). Just check the permissions of your mySQL user as suggested in this thread (that's why I refered to it). However, if you want to enable debug mode first, use a tool like phpMyAdmin to directly edit your database, browse coppermine's config table and set debug mode from 0 to 1 there. This has been explained very often already, please search before posting, especially if you're looking for help for an unsupported version, we expect testers of new versions to have above average skills - this includes being able to use the search button.
-
WOW!!!! your so helpfull, but i guess thats what your here for!!!!! I love you GAUGAU!!!!!! ;) ;)
::)
anyways....
-
no need for your sarcasm. I did explain how to enable debug mode "manuall", and I told you what to do to fix your issues. Instead of your above posting, you could have told us what exactly you didn't understand from my explanation and the rest of this thread. We could then look into this particular issue. Just posting "I don't understand" is not very helpfull. I strongly suggest, however, that you don't upgrade to cpg1.4.x, but keep your current cpg1.3.x install - using beta software needs a certain skill level and you have to be ready to put an additional effort into it. That's why it's labelled "beta software" and comes without support - we (the dev team) simply don't have the time to walk newbies through setting up a software package that is a bit harder to set up than the stable one.
-
you dont have to worry about it anymore, i fixed it, go check it out, all i have to do is upload my pics now!!! http://photos.tournashville.net
have a GREAT day gaugau!!!!!! :-*
-
Hmmm so what was wrong?
-
it had nothing to do with the sql settings, it only had to do with an improperly named file in the /include/makers file called .ds_store.
frontpage 2003 will not allow any files that are not named, and in that case, windows recognizes it as an extension only because of the "." in front of it. so, all i had to do was upload it with another program, and it was fine.
that fixed this problem!
-
"improperly named" is relative. ;) In *nix, it is how hidden files are named.
-
do not use MS Frontpage to upload coppermine. In fact, never use Frontpage to upload any php driven app. After thinking about it twice: never use Frontpage at all.
Joachim
-
then what would you recomend people use all knowing gaugau?
-
then what would you recomend people use all knowing gaugau?
http://www.crimsoneditor.com/
-
for editing, any plain text editor is fine, notepad.exe will do. For uploading, use a decent FTP app, like Filezilla, SmartFTP, WsFTP, WinSCP. WYSIWYG editors (like MS Frontpage) are notorious for making "code improvements" that will result in broken files. They touch things they're not meant to touch. MS Frontpage is fine for complete newbies who want to create a static (HTML-only) web page without wanting to learn HTML or other web-related stuff at all. Dynamic pages (pages that are built using server-sided scripting languages like PHP, ASP, Perl) will break when WYSIWYG-editors are being used. This even applies to good products like Dreamweaver as well if you're running them with out-of-the-box settings, but at least good editors have a switch in their config that allows you to specify that the editor mustn't try to "enhance" code. Apps like MS Frontpage don't have such a switch or the switch isn't working well enough.
Joachim
P.S. Why don't you stop posting sarcastic comments like "all knowing gaugau"? I'm trying to do my best to help you as well as others by sharing what I know. I certainly don't know everything about the web, but I do know some things about coppermine (and stuff related to it, like what editor to use or not to use to be out of harms way).
-
hi,
i also have this error.
index.php only displays this:
Fatal error :<br />
the db user has alter rights, but after running update.php the dbs are looking still very different, but update.php said, all is fine.
inserting $CONFIG['debug_mode']='1'; into config.in.php results in no additional messages
so what todo? whats the recommended upgrade path from 1.3.3 to 1.4?
-
Read the thread! There's no support for cpg1.4.1 yet! Replying to a thread that is marked "invalid" is not a good idea. Now I have to lock it.