News:

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

We are using Coppermine as a repository for stock photos we purchased. We have around 9000 images. Most of the photos have been added using FTP and the batch add files feature. When editing files to add keywords it has always taken a long time, but we have started getting "Fatal error: Maximum execution time of 60 seconds exceeded". I was able to stop the errors by extending the max_execution_time value defined in the php.ini to 90 seconds. However, I've just done another import of files and the errors have started again. I was able to extend the max_execution_time value to 120 seconds to allow for editing, but this is obviously not a problem that is going to go away.

I believe that part of the problem somehow lies with the keywords. When the files are imported there have been thousands of keywords automatically loaded into the system.

Does anyone have any insight into why this is happening and what I can do to fix it? As it is, I don't dare add any more images to the gallery.

Turn on DEBUG mode for admin at least (In config - Maintenance settings)Edit files... (has to complete - if you exceed execution time we won't get the data)On the resulting page at the bottom with be an expandable debug section.Look for the SQL statements - each will have a file name, line number, and execution time with it.Looking for LARGE numbers to see where the issue is - and post back here.

I have over 38,000 photos in my largest gallery - I know others have larger - and can edit with no issue... The SQL should point us in the right direction to help you.

I would add that setting the time to 120 is not high by modern standards. I would doubt the number of images is having an effect here and like gmc suggests, it would be good to know what queries are causing the delays. If you are on a shared server, it could even be as simple as your server is sharing too many jobs at once. This results in a slow down or even a pause of running scripts taking them past the limits.

Logged

It is a mistake to think you can solve any major problems just with potatoes.

I would suspect something else happening on the server - or a resource limitation (especially if this is a shared host - some are much better/worse than others...) You may want to discuss with your hosting provider - or consider a different host.

I do agree with Phil that allowing higher times is the norm - but you shouldn't be waiting that long for this type of update... Major batch uploads (with resizing pics) is where I would expect to need that kind of time.

Thank you for your reply. Coppermine is the only thing that is being affected on the server.

This Coppermine gallery sees very little use, probably 3 or 4 people per day, and I am the only one who is adding images to the system. I have one person who is putting in keywords on a regular basis and has been for a long time. He says that the edit feature has always been slow, but has gotten slower over time as I have added more images through the FTP/batch add process. The most recent addition I did was Tuesday and that was when the Fatal Error started showing up again.

I have a feeling that it has something to do with the keywords being added to the system when I do the FTP batch processing. When I look at the keyword manager it practically crashes my browser there are so many words. There is also a weird thing that happens if you look at a gallery's "edit files" option. If there is no keywords listed for a file but there is a description, it will copy all the words from the description into the keywords field when you click apply changes.

Can you think of anything else I might be able to check or help you might offer. I'm really at a loss

I believe that I just solved the problem. The behavior I mentioned about keywords being created from the description field was being caused by a plugin. I uninstalled the plugin and I no longer have the delay. Thanks so much for your help troubleshooting the problem and looking at my log script. It was a big help