Search results

yes I had actually started a thread about this a year or so ago, at the time there was no interest at all. But its quite easy to do, and while not for everyone I think its useful as a plugin.

while bridging with many different products is on the long term todo list, its a big undertaking to integrate different user systems and keep them updated. At this time, this would need to be a custom (paid) job, of course if you know some PHP you can do this yourself :) It really...

Can you explain further, I am not sure I understand what the problem is. facebook, google+ twiiter have absolutley nothing to do with anything in this topic.

I am rebooting the screenshot server now, should be online within 5 minutes and be rendering as normal.

hmm I wish I knew the reason fastCGI was failing for you, seems to be working as expected on my dev box. 45 seconds should be plenty of time to make the round trip: - Send API key - Verify key and domain - Open browser on screenshot server - Wait 5 seconds for site to load - Save screenshot...

not sure what that is to tell me :) please try my above posted solution.

http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html#fcgidmaxrequestlen try setting your FcgidMaxRequestLen value to 13107200 and see if you get farther with it. related reading (thanks Basti)...

I am running some further tests now to see if I can understand what is happening for you

Correct, I cannot explain why your server is timing out after 45 seconds, its is contrary to your settings.

mod_fcgid: read data timeout in 45 seconds, referer: http://xxx.xxx/index.php?a=admin&b=manage your server is timed out in 45 sec

if you cant use these set_time_limit(0); ini_set('max_execution_time',0); then you need to edit your php.ini

your server is timing out. make sure you have this in your screenshots.php file set_time_limit(0); ini_set('max_execution_time',0); and make sure your hosting environment allows you to override these settings like this (may need to ask your host).

well that is a different request altogether :)

haha thats about the best one for me :) sums up the last 10 years of my life working with CSS!

in your root (top level / )

on/off requires yet another DB field be setup, I personally think moving/removing or even styling the template tag is adequate enough. Just my $0.02 :)

as suspected, the problem was a plugin that was not supported was uploaded. I have also added a couple lines to the screenshot file to prevent timeouts, this will be included in 1.0 as well. screenshots.php find: error_reporting(0); add this after: set_time_limit(0)...

I'm 100 % with you Steve :) we are anonymous we are legion lol

You can also send me FTP and your admin password in a private conversation and I can investigate further for you.

absolutely, there are quite a few language definitions we have missed. Anything posted in this thread will be corrected for next release :)