kflavin21
Forum Replies Created
-
This was a firewall issue connecting back to the proxy… backend servers could talk to the proxy on 80, but not 443. To resolve this, I scheduled the cron through the OS, rather than rely on WP cron. Additionally, I had to clear out a number of stale wprss_* events. I did this using the wp cli, ie: “wp cron event delete wp_rss_fetch_single_feed_hook”.
Btw, it’s the “wprss_fetch_single_feed_hook” that appears to be “stuck”. There are several of these, I’m assuming one per each feed. Each time I fetch all feeds from the “debugging” tab in the admin, it adds another set of these events to the cron list. They never complete, even after running wp-cron.php as described above.
I’ve noticed if I set the wprss log level to “Error or below” in the general settings, I get some output here:
./wp-content/log/wprss/log_blg-1.txt
However, the output only seems to come from the wprss_fetch_insert_all_feed_items() function. I don’t see anything from the wprss_fetch_insert_single_feed_items() function, even though there are numerous log statements within. As near as I can tell, it isn’t actually being executed.
Hi @erricgunawan,
I checked the Wp-cron status. I have an error saying curl cannot connect to port 443 of my host. There are a number of “wprss_tech_single_feed_hook” items in the “(now)” state.That appears to be part of the problem, so I’ve reached out to my host. In the meantime, I’m trying to manually run wp-cron.php, and the feeds don’t import like that either. I’ve tried to invoke wp-cron.php as follows:
#1
$ php wp-cron.php # Appears to run successfully, but feed items still don’t import.#2
$ curl https://mysite/wp-cron.php # fails to run since my backend server can’t talk to 443 on the public domain#3
Enter https://mysite/wp-cron.php into my browser, loads a blank page, and returns a 200 status. Feed items still don’t import.If Wp-cron runs, it should import the feeds, correct? Do I need to delete the “stuck” items first?
- This reply was modified 8 years, 11 months ago by kflavin21.
Hi Eric,
Yes, I went through the list. No htaccess, curl is enabled, php version above 5.3.9.It had been working for months prior to us switching over the SSL a couple weeks ago. We’re behind an nginx proxy, with SSL terminated at the proxy. I’m wondering if that has something to do with it… wordpress would have been switched over to https, but the backend servers still communicate over standard port 80.
Forum: Developing with WordPress
In reply to: Adding external, dynamically created links to postsGreat, thanks! I’ve been able to get something going – good to know I’m on the right track.
I’ll check out using update_post_meta() as well. I think that makes sense for my situation.
Forum: Developing with WordPress
In reply to: Adding external, dynamically created links to postsI was trying to figure out the best way to store the data, retrieve it, and then display it in the template.
I think I found what I was looking for though:
https://codex.ww.wp.xz.cn/Function_Reference/add_post_metaIt looks like I can just add my URL as metadata for each post, and retrieve it for display on my theme.
One question – when a post is deleted, does all associated metadata get removed, or do I need to handle removing any metadata I add?
Great, thanks!
Forum: Plugins
In reply to: [WordPress Importer] Posts already existThe problem seems to be we added additional pages to the development site, which conflict with the posts we’re trying to import from production. It looks like they (posts and pages) all get stored in the same wp_posts table. So edits to a page generate additional rows in wp_posts with ID’s that conflict with the posts we’re trying to bring in from production. Ugh…