dcell59

Thanks! I noticed this yesterday.

More specifically, if you run /usr/bin/php wp_cron.php from a command line or cron, will it work the same as using wget on the URL.

Well, that turned out to be easy. One of my plugins had a couple of blank lines at the bottom after the php close tag. I removed them and the calendar feed now works.

I looked again, and what I notice is that the feed that works has cr/lf pairs, but the feed that doesn’t begins with a lf (0x0a). I suspect that the parser see the initial 0x0a and decides that the rest of the file should use that same pattern. So, something is generating an extra linefeed at the beginning. Time to start deactivating plugins.

I tried this on another site – same version of A1ec – and it worked fine. I may be running different versions of PHP on the two sites and I do have different plugins, so I suspect a conflict somewhere.

I had the same problem. I got the feed URL and downloaded the file. I tried validating it with an online validator and it failed. I then edited the file and noticed that it had carriage return/newline pairs. I removed the returns and it validated and then imported into Google Calendar.

The reason I asked here is that it’s something that WP seems to handle fine, and because the code will be hosted in a WP page (eventually via a WP plugin).

At this point, we’re going to go with the database. I can still do what I want in the short term, and eventually rewrite all of my bash scripts in php.

Thanks!

Is this more of a php or web site administration question than a WP question?

Yes. Thanks for this article. It helped me get the plugin set up and styled exactly as I needed very quickly.

So you’re trashing me over this? Let’s have some perspective. I got this plugin from this site, which has a forum for this, and this was the topic discussing the issue.

I expected it to improve the editor I use to edit my pages and posts, and then this “experiment” sticks hidden links to an options trading site in the UK and an online gambling site on my pages where the editor doesn’t even reside. I think I had a right to be upset over this. I thought I handled it pretty calmly in the end.

Sorry if you took offense. I’m fairly new to WordPress (but not software development). I do test on a test site, and I do look at changelogs (I didn’t see a mention of this in the log), and everything was working fine. I just happened to be reading the rendered page source and saw this thing I didn’t understand. I’ve heard lots of stories about WordPress sites getting hacked when not kept up to date, so I was worried that this was such a case. Maybe if there had been a comment in the generated code saying where it came from, along with a URL directing me to a post about it, I would have been able to find out what was going on right away and it wouldn’t have bugged me.

I’m sorry that you feel like this has been more trouble than it’s worth.

Well, I guess I’m glad to hear that it’s being taken care of, but it sure scared the heck out of me. I ran across this yesterday and after a sleepless night I was able to figure out what was causing it. Sadly, I just don’t think I can trust this plugin again, and now I’m going to be checking my pages sources every time I add a plugin.