Manage media doesn't work for 1 gedcom
Brought to you by:
canajun2eh,
yalnifj
Menu
▾
▴
While adding a jpeg, gedview paused. Now the manage media does not display anything. The bottom of the page header is missing? It works fine on all other site gedcoms. I deleted and reinstalled the gedcom, even renaming it but no luck. The media are there and displayed within the gedcom, but I have no means of editing, etc. Version is 4.2.0. I am an admin on all geds.
Something got deleted or overwritten for this gedcom?
Thanks for any fixes or ideas.
Mike
Sometimes media management page problems are caused by the memory limit being too low. This is a configuration setting, also possibly affected by a site-wide php.ini setting. If raising the configuration setting doesn't help check the php.ini setting.
If you can't increase the memory allowed (it should be at least 32 Mb), you can sometimes avoid problems by creating a suitably sized thumbnail outside PGV, and then uploading the main image and the thumbnail at the same time. PGV won't try to create a thumbnail when you supply one.
Thumbnail creation from a main image is done once per image, and uses up LOTS of memory. Incoming JPGs have to be converted to bit mapped images, and then the bit map has to be copied before it can be reduced. After that, the reduced image is converted to JPG. All this has to happen in memory.
Thanks for the help. I changed the memory to 64m. Then I deleted a bunch of larger jpegs. Still no help. The Manage media page does not completely load (display). The footer at the bottom of the page never shows, so it is a memory or corrupt file issue. But what file is corrupt if that is the situation? I don't manage the Server site, so can't change any other settings. The main issue is editing,deleting or adding media to the one site. The rest of the sites (7 others) work fine.
Thanks again
Mike
If a page fails to load or loads incompletely, you can sometimes discover the problem by inspecting the bottom of the page source. You might see an error message that's produced by some "authority" outside PhpGedView.
If you don't know how to get your browser to display the page source, please tell us what browser you're using. We'll be able to guide you, once we know.
Here are some errors (Warnings) from Firefox 3.6:
* is place for my name and webpage
Warning: Empty string passed to getElementById().
Warning: Error in parsing value for 'font-family'. Declaration dropped.
Source File: http://\.com/phpgedview42/themes/xenea/style.css
Line: 995
Warning: Error in parsing value for 'font-family'. Declaration dropped.
Source File: http://\.com/phpgedview42/themes/xenea/print.css
Line: 595
Warning: Use of captureEvents() is deprecated. To upgrade your code, use the DOM 2 addEventListener() method. For more help http://developer.mozilla.org/en/docs/DOM:element.addEventListener
Source File: http://\*.com/phpgedview42/media.php
Line: 0
I get this all when opening manage media on the site that fails.
Same warnings when doing same on working ged.
So I doubt that this will help.
I got this error on my log page in gedview:
Fatal error: Out of memory (allocated 33030144) (tried to allocate 35 bytes) in /homepages/34/d161705931/htdocs/*/phpgedview42/printlog.php on line 66
Mike
canajun2eh :
running the 2 possibilities, The one that fails appears to be in a loop that finally times out without completing the page load. It keeps repeating part of the script. I won't copy the dense text seen in the 2 source views unless you think it will help.
Mike
Your problem is that PGV has run out of memory. It seems to need more than 32 Mb (your current limit) to process one of your images. It's probably trying to create a thumbnail from a very large main image.
You can ignore those warning messages, but I'd advise you to upgrade to version 4.2.3.
If you're brave, you can upgrade to the SVN version. I've been running the SVN version for at least 3 months, and have encountered no problems. The warnings should be gone if you upgrade to the SVN version, but they'll still be there if you just go to 4.2.3
canajun2eh :
Thanks and you are probably correct. I will turn this over to my son-in-law who set all this up on a Linux server.
Appreciate all you gedview gurus taking the time to help us novices out.
Regards,
Mike
You should take a look at the *size* of the images you're expecting PGV to store for you. Please remember that PGV is *not* intended to be a photo archive. Photos that you're uploading with PGV and then linking to persons, families, or sources are intended to provide some interest and colour to the genealogical information.
Do you really need to upload images that are larger than about 800 Px wide or high? How about the colour depth? You you really distinguish a 32 bit colour image from one with a lower colour resolution?
If you reduce the image size and colour depth before PGV sees that uploaded image, you shouldn't have any significant problems when it comes time to create the thumbnails. This shouldn't affect your users' experience of your site.
PROBLEM RESOLVED!
I had to go in and delete all jpgs larger than a certain size (a thumbnail could not be generated for them).
Luckily I had more than one database, so I could choose another database and then choose manage media. Whenever a jpg could not have an automatic thumbnail generated, I deleted it. The process stops each time it reaches the next too-large file. I delete that file and then continue auto generating thumbnails until it stopped again and so on. Eventually all the too-large files were deleted from the media folder and I could once more manage media in the problem database.
Hope this late note helps someone else.
That's a bit drastic, and also very tedious.
You could have created suitable thumbnails for those too-large images and then uploaded these thumbnails to their proper place using something like FTP. The too-large images probably were JPG files with a size larger than about 250 Kb.
When yo use FTP to upload the thumbnails, you still need to ensure that the files have proper read/write/modify permissions. 755 is usually OK, although you might need to set permissions to 777.