tamar
Forum Replies Created
-
Forum: Plugins
In reply to: [Selection Sharer by Hans van Gent] LinkedIn support?no problem, thanks! Glad you have an environment upon which to test.
Forum: Plugins
In reply to: [Selection Sharer by Hans van Gent] LinkedIn support?Oh you’re right, sorry! Thanks.
Admins aren’t included on the list but they are listed.
I like the idea of a new update to address the hiding of the titles.
I’ll do “hide from team list.” That works. Thanks 🙂 But yes, looks like that’s a bug.
Solved. It was an issue with my ftp server and passive settings. But no FS_METHOD was able to fix it. Either way, if anyone cares to know the details, I was using vsftpd and I had to add pasv_promiscuous=YES to the conf file.
So… I’m still stuck here.
And I had someone take a look at this and thinks it may actually be a WordPress issue, not user error. He thinks WordPress may not work with PHP 5.6.4.
Here’s my revised question: does anyone here use PHP 5.6.4?
My guess: none of you do.
Based on PHP statistics on web servers to date, with only 0.4% of users actually using PHP 5.6.4 (see http://w3techs.com/technologies/details/pl-php/5/all), my guess is that WordPress hasn’t been tested on this environment yet.
So … friends: If you have your own server, don’t upgrade to PHP 5.6.4. Or do upgrade, and let me know if you encounter the same issue.
Hey Daniel, are you still around to answer these questions?
eh I’m not rolling back PHP to a previous version. Hope Daniel can fix.
I’ve been getting this “could not generate WordPress export file” for as long as I can remember.
WordPress 3.9.1
PHP 5.4.28Here’s what it looks like:
[06-Jun-2014 03:00:09] Database backup done!
[06-Jun-2014 03:00:09] 1. Trying to create a WordPress export to XML file …
[06-Jun-2014 03:00:15] ERROR: Could not generate a WordPress export file.
[06-Jun-2014 03:00:15] 2. Trying to create a WordPress export to XML file …
[06-Jun-2014 03:00:15] 3. Trying to create a WordPress export to XML file …
[06-Jun-2014 03:00:23] Check WP Export file …
[06-Jun-2014 03:00:23] WARNING: XML ERROR (1): internal error: Huge input lookup
[06-Jun-2014 03:00:23] WARNING: XML ERROR (5): Extra content at the end of the documentForum: Fixing WordPress
In reply to: wp-cron not running; no idea why@esmi – yes, I do that often. But it doesn’t kick wp-cron into play, if that’s what you’re asking …
I also see I’ve had 253 visits today alone.
Or what did you mean?
Forum: Fixing WordPress
In reply to: wp-cron not running; no idea whyJust restarted the server and scheduled a post. It missed schedule. No mention of cron in any of my wp error_logs…
Forum: Fixing WordPress
In reply to: wp-cron not running; no idea why(I’ll restart the server and see if I can find out.)
Forum: Fixing WordPress
In reply to: wp-cron not running; no idea whyIt hasn’t been running for a really long time, so I don’t even see any references of it in any of my error logs 🙁
I get a decent amount of traffic; sometimes the spikes take the server down. So I don’t think it’s lack of visits… I just don’t understand why it keeps happening. I even had a system cron job that was set up to start the wp_cron to no avail.
Forum: Fixing WordPress
In reply to: wp-cron not running; no idea whyesmi: it’s a 6 year old site but doesn’t get substantial traffic. I don’t think traffic is taking down wp-cron. But I do know that wp-cron isn’t working, and whenever I get it to work temporarily, about 20 minutes later, it dies again.
Forum: Fixing WordPress
In reply to: HTTP Error 500 (Internal Server Error)Higher level answer: you probably edited the code in a way that your web server couldn’t process. If you wanted to know the error, you’d ask your host to tell you what the error_logs said.
But esmi recommends restoring the previous file and getting that working.
If you’re a total beginner, your best bet is not to touch the code. I consider myself more advanced (I understand a bit about PHP too) but I still won’t touch code.
Forum: Fixing WordPress
In reply to: Weird 404s since the upgrade to 3.1BUMPING THIS UP. I miss the days when Otto wasn’t so busy 😉