resolved
mathrafal
Member
Shame about this, but after upgrading to 2.7.1 and upgrading Photo-Q, I find no options to add photos to the queue. This is quite frustrating! I think it has something to do with a Flash uploader (?), which is something that many have complained about with the Flash uploader in WordPress.
Any suggestions?
Cheers!
sorich87,
thanks for letting us now. i will try to check on that incompatibility you are reporting.
mathrafal,
was your problem finally also due to another plugin? or are you still stuck with single uploads?
sorich87,
so you see them in your queue? the blank page is after you hit "post top of queue"?
hmmm,
any chance you could give me an account to a wordpress install that has this problem? if so you can send me the credentials via email, you'll find my email address on my main website http://www.whoismanu.com/ under contact.
sorich87,
alright, had a look at your blog. kind of weird the whole thing. i also tried on my machine with photoq and post thumb revisited and i don't have the problem with disappearing settings page that you have on your page.
i am thus starting to believe that it might not be a compatibility problem but rather a memory problem (i.e. when both of the plugins are active the memory gets tight and things start to break, same if you post a photo, photoq creates the thumbs which needs a bit of memory). could you try the following things?
define('PHOTOQ_DEBUG_LEVEL', PHOTOQ_LOG_MESSAGES); to define('PHOTOQ_DEBUG_LEVEL', PHOTOQ_SHOW_PHP_ERRORS);if the result is the same or if you get an error hinting at a memory issue, you can try to increase the memory allocated to php via your htaccess file. you can find here under bullet 10.2 how to do this: http://www.whoismanu.com/photoq-wordpress-photoblog-plugin/#troubles
whoismanu,
Thank you for your support.
I changed the debug level but I don't see any error message.
I tried changing the memory allocation in the htaccess file but I get an error message (internal server error). So, I tried to change it (to 128M) by using the ini_set function in the wp-config.php file but the problem in the admin persists.
The default amount of memory allocated is 40M.
Thank you very much.
too bad...looks like we got a tough one here. guess we need to look further to see where your installation differs from others. can you give me some info on your server?
php4 or php5? windows or unix? apache or iis?
one thing that is different from most people is that you are using the french version of wordpress. i'll also install this locally to test but i guess it is pretty unlikely that this is causing the bugs.
thanks. to narrow down the problem, one thing you could try is to setup a second fresh english wordpress install on the same server (remember wordpress installs in just 5min ;-) ), install photoq on this install and check whether it works.
i tried locally and set up two french installs, one on php5 one on php4. both with photoq 1.6.5. both work like a charm...really weird the problem we are having on your server. i'll think about it a bit more.
wrap-up for people with similar problems of what we found was the error:
- it was a memory issue
- the french install used more memory (probably due to the translations performed) than the english one, which in this specific case was just the tiny bit of memory too much
- the server reported a memory-limit of 40M (through php_info/php.ini) but actually only allowed around 12M (!). apparently this can happen (misconfiguration? i don't know). we found out by writing a test script that tries to grab more and more memory until it hits the limit. if you suspect something like this, you can do the same. just copy the following code to a text file and save it under the name memtest.php on your server. then point your browser to the corresponding url (example.com/memtest.php) and you will see where your installation hits the limit. here is the script we used:
<?php
$before = memory_get_usage();
$store = array();
while(true){
//generates approx. 1MB
for ($j = 0; $j<1024; $j++){
//generate approx. 1kB
for ($i = 0; $i<10; $i++)
$store[] = 'abcdefghijklmnopqstuvwxy'; //4*25bytes assuming unicode
}
$after = memory_get_usage();
$script = ($after - $before)/1024/1024;
$total = ($after)/1024/1024;
echo "script: $script, total: $total<br />";
}
?>in our specific case it failed after 10.8M. if you add memory allocated to the system that is not reported this probably translates to a limit near 12M.
- 12M is in general too low for wordpress and even more so if you plan to play around with photos.
- leaves two options in a case like this: 1. negotiate with your host such that they increase your limit; 2. change your host.
You must log in to post.