NBH707

I scheduled a published post that had full recipes in it (not roundups) Then I went back and added a roundup item. to the article (for one of the recipes already in the article) and saved it. All of recipes that are full recipes are showing on the manage page as published except the one I added a roundup item for, which is now showing as scheduled.

So it seems that somehow when we add a roundup item, it is getting resaved with the wrong status.

• This reply was modified 3 years, 7 months ago by NBH707.

Actually, a correction, the other posts were not saved as drafts but as scheduled.

No, but I think you are on to something here.

We weren’t originally using separate recipe pages or roundup items. Then we went back and added them to all our existing published posts that had multiple recipes in them. I believe all of those have proper links.

But then we had another article that hadn’t been published yet that we added recipes to and then roundup items BEFORE we published the article. However, I am looking at those recipes on the manage page and they are still showing as drafts.

All of the other posts where this problem is happening also had the roundup items added when they were drafts.

I will try creating a new page, publishing it, and then adding the roundup items after and see what happens.

Here you go: https://staging-genes2teenscom.kinsta.cloud/settings/

I have narrowed down the problem. It started sometime between June 12 and June 15. All recipes whose original parent article was created after June 12 are having the problem.

So let’s say we have ABC recipe and ABC article (the good ones) and XYZ recipe and XYZ article (the bad ones).

If I try to add a roundup item for ABC recipe to either article ABC or XYZ, it works fine. If I try to add a roundup item for XYZ recipe to either article ABC or XYZ, it doesn’t work.

Were there any updates to the plugin during this period?

N/A

• This reply was modified 3 years, 7 months ago by NBH707.

Yes I have cleared caches, restored old versions etc. etc.

I think I have narrowed things down a bit. I’ve identified the first recipe that had the problem and it seems to have affected all recipes saved from that one on. I’m going to check out the exact date in the database for these recipes to see if I can narrow down the possibilites.

Something happened on July 15. Now I know that is the date you released a new version of the plugin but we also added some custom code that could have affected WPRM data on that day as well.

However, I have done some testing that should have eliminated any causes but it is still occurring. I have reverted to a July 15 backup and changed the theme to the WP default. I have disabled all the plugins except WPRM (even the premium version I disabled). I also rolled back to version 7.3.0 instead of 7.4.0. And I also reverted the version of WP.

However, the problem still occurs even with newly created recipes. What I notice is that some recipes have the problem and others do not. We’ve edited a lot of our recipes recently so my feeling is that something is happening when the recipes get resaved.

Where do the slugs get saved in the database when the recipes are saved/resaved? if I can check there it would help me to narrow down when the problem started to occur and perhaps why.

It’s doing it both on the front end and back end. And I see even if the post is already published, it is doing it too. I’m testing a backup of the site from last week on our staging server to see if it looked like that after I created the post but before I published it. There may be some other plugin or code that is causing this.

I see what you are saying, but it was also occurring without me ever visiting a page on the front end (although in theory a site visitor could have done so). However, I repeated this multiple times and got the same results. We have a plugin called CM Answers Pro (it’s a paid plugin). We are disabling it on standard posts as it was causing a conflict. However, when I would reactivate the plugin, it would redirect me to the plugin setting page. Then I would immediately go back to the plugins page, and find things deactivated gain. That this happened multiple times makes me wonder whether something else is going on, because I was moving around so quickly the chances of someone browsing the front end every time to trigger what you describe seems unlikely.

I’ll wait for your fix and if that doesn’t solve the problem, I can also review what other plugins I may have updated around the same time to see if the issue could be coming from any of them.

I have a staging environment. Please share the file and I can test it by making a duplicate of my live site and upgrading again.

The problem was not that FDP was running on all pages, but the fact was that after it was upgraded, the other plugins were showing up as disabled on the plugins page (because they seem to have been disabled). In most cases, I was able to re-enable those plugins, but as soon as I left the plugins page and came back, they were disabled again.

• This reply was modified 3 years, 7 months ago by NBH707.

Hi Jose-Thanks for the quick reply. We are thinking the same way because I already rolled back the version to 1.8.8.6 and the problem is not occurring with that version.

The plugins that I had disabled on some pages on our site that it affected are as follows:
Active Campaign
Add to Any Share Buttons
Contact Form 7
Lazy Load for Videos

There were a few others but they are paid plugins you wouldn’t be able to test with.

Thanks for the information on how this work, both in your comments above and the plugin documentation. Our development team was able to add this functionality to our template.

OK thanks. I’ll do that.

I think I wasn’t really clear here about what we are looking for.

We are not primarily a recipe site, and most of our posts that do feature recipes are on a particular topic such as the best diet for lactating mothers and include one or more recipes related to that topic. Hence, they do not already have their own separate pages.

I’ve changed the settings though so that “Recipe Existence” is set to public. We are going to change all our recipe blocks now to roundup blocks, which according to my testing, with the settings set to public, points to a new page with the recipe on it. What we would like to happen is if possible, automatically display a link on this automatically generated recipe page that points back to the page where that recipe is featured with a recipe roundup block, in case we get people coming to the website landing directly on these recipe pages.