Forum Replies Created

Viewing 15 replies - 46 through 60 (of 104 total)
  • Thread Starter poddys

    (@poddys)

    Following up on this problem, I have been investigating another error which appears when WP checks for updates. It seems that if Curl is active, WP assumes that the server has SSL.

    Our server DOES NOT have SSL active, which is possibly why these Curls are giving problems.

    I posted a new thread here wordpress.org/support/topic/wordpress-could-not-establish-a-secure-connection-to-wordpressorg-6 related to the other problem, and I believe if the problem with WP assuming that SSL is active when Curl is active will fix our Curl timeouts as well.

    Points taken Josh (having edited my post and seen your response).
    Will create a new topic.

    Just wanted to add that if many of us are having exactly the same problem, adding your information to a single thread is surely better than creating dozens (or potentially hundreds) of threads all about the same problem. So in that case, adding this post to say that I too have this should be my way of helping to confirm there is a problem, and to hopefully add more information to help resolve it.

    In our case, our server is NOT set up to use SSL at all. I’m not sure if this is relevant to the error being generated, but I added a debug line to wp-content/update.php and the value of $ssl=1. Hoping this will help.

    ———————–

    Edited to add………

    Just saw this thread http://wordpress.org/support/topic/wp_http_supports-array-ssl-yeilds-true-on-a-local-server?replies=3 which shows that even if you do not have SSL enabled, if WP detects Curl as your 1st method of transport (which in our case is true), it assumes that SSL is active.

    I think this is likely to be the root of this problem.

    Thanks Peter.

    I know we have had a few problems setting up the server correctly. This is an in-house site running on IBM iSeries with Zend Server, and WordPress was running painfully slow. A number of tweaks later and installing Hyper-Cache and things are looking a lot better.

    This morning I turned the WP-Cron off and added our own Cron job which runs every 30 minutes, calling WP_cron.php. I’m not sure if turning WP-cron off is relevant to this, but only runnign it every 30 minutes might mean we only connect to Twitter every 30 minutes, in which case I will change the frequency.

    Hopefully if it is a configuration error at our end we can figure it out soon.

    Just been looking at your portfolio of plugins and will recommend our news site designer to take a look. Speed, functionality and ease of use are all important, sounds like you have the right philosophy.

    Best Regards
    Tony

    The Twitter API Log does show these for today:

    13:16:05 – April 16, 2014 1 name lookup timed out
    13:13:07 – April 16, 2014 1 Connection time-out

    and similar for previous days.

    The feed does seem to work though, and we have it set to refresh every 15 minutes, which I assume is optimum since we don’t have a huge number of tweets.

    But this “I believe” is all related to connecting to Twitter, not to your server right?

    Thanks Peter, rapid response too 🙂

    The feed appears to come in ok, but when I click on the Settings link for the plugin in WP Admin I seem to randomly get a Success or Error on connecting. Not sure if it is our problem, but I see nothing in the PHP or Apache logs.

    I just turned on WP_DEBUG and when I go to Settings->Kebo Twitter Feed I see the same error at the top right of the screen:

    API Status
    23.239.13.127 Error
    Your site cannot connect to the Kebo API, this will prevent the plugin from functioning as expected. You are welcome to ask for help on the support forum.

    Since I get the spinner before the error msg is generated, it looks like the connection timed out. The plugin has worked ok previously though.

    I tried again – same error, then a 3rd time and it worked ok. I wonder if your connection is getting overloaded, or it could be at our end too.

    API Status
    23.239.13.127 Success

    I can’t speak for Wordfence, but BackupWordpress is definitely compatible with the BulletProofSecurity (BPS) plugin.

    *post deleted by author*

    Thread Starter poddys

    (@poddys)

    Actually, all my messing around might have got the scheduling working, although I still have the error “mysqldump not found”.
    I set the backups to run hourly, and in the last hour did get a backup run and the warning log updated.

    Where do you add this into the Theme’s functions./php file, at the beginning, end or before the first function definition?

    Our backend is incredibly slow and this is the first real option I have seen that has the potential to make a big difference.

    Our Admin options are incredibly slow too, even though it’s a new site and only 2 developers. What I don’t understand though is why we don’t get the same problems when logged in as an Author, when looking at All Posts for example is almost instant. If logged in as Admin the same option takes 10+ seconds every time.

    Thread Starter poddys

    (@poddys)

    Thanks for the reply Kurt. We aren’t running any accelerators or caching on the site, so I don’t know why the plugin wasn’t working.

    I did find mo-cache (http://wordpress.org/plugins/mo-cache/) which appears to have helped a lot with our performance issues, much of which seems to be caused by WYSIJA which takes forever looping through pomo amd mo when loading.

    Will likely revisit P3 when I have evaluated the results from a couple of other server/site changes.

    ————-
    Aha, I read this (very informative)m post on your site Kurt http://kpayne.me/2013/12/24/write-your-own-code-profiler-in-php/ and we are using Zend Optimiser, which is probably what affected the results.

    @zulfikar Nore I was just looking for the same thing, an easy way to just show extracts on the archive pages. Just installed Fourteen Extended, lots of options to explore and it seems to work really nicely. Great job on this.

    poddys

    (@poddys)

    I am having similar problems on all my sites using Backup WordPress and BPS, and removing “HEAD” seems to be working.

    However, I have been creating the .htaccess in BPS and then manually editing it. Can I specify the code for removing “HEAD” in the Custom Code section? I still have problems with this sometimes, in particular creating the custom .htaccess for SuperCache.

Viewing 15 replies - 46 through 60 (of 104 total)