Chris

Hi Jan, thanks for the input here. I just want to add that I am indeed using the premium version of this plugin, not the free version. Given that, I understand this may not have been the best place to post for support on the premium version, but it’s a place to start and I’m not even sure if the issue I had was related to features only found in the premium version or not. I could have used their own contact form though, and might have had I only noticed it first.

As for accessing my installation, I am always hesitant to let anyone touch anything and do prefer giving logs and other data as Jan mentioned. I know most of the developers here have good intentions and are not planning anything malicious when they ask for access (lots of reputable companies do the same thing), but we do need to stay safe.

Thanks for being a great moderator! Thanks to Naweed and Mark for the support too!

I think I’ll pass on the premium support and sharing access – no point now anyway, it seems to be working well enough, and I’ve already manually adjusted the update intervals on each feed.

At this point the only remaining issues are the global Update Interval option not taking affect, but there’s no use in that now, and the cron job being set to hourly instead of daily, which is probably related and again doesn’t matter now that update intervals have been manually set.

I’d hardly say the issue is resolved, but it’s not causing me any problems now so I’ll mark this as resolved.

After installing, the first thing I did was review settings and I’m pretty sure I changed the default Update Interval to 1 day right then. After that, I added a few feeds without overriding the default Update Interval, but they still all said they would update in an hour. Several days later, nothing had changed, and the feeds were still getting checked every hour. I’ve removed and re-added some feeds too, and the default Update Interval was definitely changed to one day at that point, but the feeds were still checking every hour.

I have already changed the update intervals per feed the hard way, so I can not confirm if working with WP Crontrol would make a difference. I suppose I could remove one of the feeds and add it back, but I shouldn’t need to rely on a secondary plugin to fix the scheduling.

I can see in WP Crontrol that wprss_fetch_all_feeds_hook is set to Once Hourly, even though it has been set to Once Daily (1 day) in the settings for a long while now. This site gets plenty of traffic too, so cron jobs should be running regularly.

Okay, if I need additional help I’ll use the support contact form. For now here are my comments.

It does seem that over time they finally pulled in some posts at some point.

There are only seven feeds. However they were getting checked every hour at the same time, even though I had set the default to once a day (so that’s another bug?).

The process to change what time each feed is pulled is not a great process. Why not just use the time that we can enter in when editing the update interval? (I see a time field that is not shown in your screenshots.) I tried setting the times there, but it seems to have no effect. I also see now that I could have disabled them all and set the time to activate the feed, and that would have worked?

I’ve now spent the past couple of days trying to remember to go back to the site every couple of hours, forgetting for four to six hours a couple of times, and toggle one of the feeds off and then back on in order reschedule the feed – luckily there are only seven feeds here. If it had been 20+ feeds, this method to reschedule feeds at different times would be absurd. I’d rather go in to the database and figure out where you are storing the time and just set it there. It can’t be that difficult to just let us specify the the time – please work on this for a future update.

I came across another issue that is probably related. If you have a double quote in a text field’s help text, it does the same thing – everything disappears.

The other issues that got me into all of this mess was the content editor not keeping paragraphs and Custom HTML blocks not keeping simple HTML (headings). I’m assuming both of those issues were related, and those seem to be fixed in the latest version and at least one of them was a known issue. All of this is related to formatting and how the data is being stored though, so maybe the fix for that bug is causing a problem with the button HTML and the double quotes issue too, or is related some other way. I don’t know, just throwing out ideas here.

On another note, and I should probably create a new topic for this, but exporting a single form gives an error saying to select a form. Exporting all seems to work, but when I import, it says it did it, but there’s nothing there. I’ve been trying to save myself some work by doing an export in the middle of the form being redone and still working, but nothing has worked accept the old export from several months ago.

Funny enough, I just checked out your plugin today and had the same question. I’m replacing a premium plugin that we haven’t updated in many years, and you have almost everything we need for free. Thanks!

Are there any plans to update to Font Awesome 5? Is this a Pro feature? I might even be satisfied with the latest version of 4.x. I’m not optimistic though – version 5 came out over a year ago, and 4.1.0 is from 2014. Are the changes that different that it’s difficult to update to 4.7.0?

Ah, I think I understand the purpose of this plugin now too. Thank you for the explanation.

Well I don’t think this is the right fit for me. The posts are published a bit more sporadic – sometimes twice in a day, sometimes twice in a month. I also want them posted to Buffer.com as soon as possible, and I have a detailed schedule on Buffer.com so they go out quickly. I never want it to to re-post an old post either, although that might be a nice “on demand” feature.

Also, I can probably explain the difference on the development server, there’s no traffic to trigger the cron jobs.

Sorry for the confusion, and thanks again!

• This reply was modified 6 years, 1 month ago by Chris.

Yes, there are only two blog posts that have been added in the past week. The problem is not that only those two posts are going to Buffer, it is that those two posts are going to Buffer over and over and over until the queue is full. They should only be sent to buffer once and then wait for a new post to show up.

If I add another post or extend the maximum age, for instance let’s say I go back two weeks which would grab four posts (there are on average two posts per week) and I make a new post right now (making it five posts total), I believe it is going to post those five, and then post them again in a little bit (and then stop because it’s reached the limit of 10).

The development site has many more plugins, but most of them are not active – it’s more of a playground where we can test and demo new features and plugins without affecting the live site. The development site has a few other plugins with similar functionality, but they are all disabled. The live site does not have any other plugins with similar functionality. I’ll spend some time tomorrow comparing the two and see what other differences there are and try to rule out other plugins causing the problem.

Thanks for the quick response!

Ah, well that’s a shame. It’s of no use to me if it can’t simply share a post. Guess I’ll be using “WordPress Buffer – HYPESocial” aka “Buffer My Post”, which does this for free. https://www.ads-software.com/plugins/buffer-my-post/

If it’s already a feature in the Pro version, I would not think that it would take much work or time to copy it to the free version. I’d be interested in getting posted back here (if that’s even possible) if/when this feature makes it to the free version.

Sorry for my absence, this popped up at the end of a large project and I have been really busy ever since.

Switching themes is not an option at this point in time. We are now using WPForms.

Hi everyone, sorry for my absence. This came up at the end of a project and I have been really busy since then.

I did not have time to review the new options before, but I see now that the settings changed and since it now includes abandoned and vulnerable plugins (those were not there before, right?) that not migrating the old setting to the new one was probably intentional.

Actually, although I do not want to know about plugin updates, I do want to know about abandoned and vulnerable plugins. So unchecking that option is not what I want to do and it looks like I have no choice but to read through the notification emails when I get them.

It would be great if that setting could be split out into three individual settings for out of date, abandoned, and vulnerable plugins.

Thanks for the replies!

I’m not sure if my problem is directly related, but it’s the same error as the OP (something about missing the client_id), so I thought I’d share what I found.

I also have BackWPup installed, and many other plugins – none related to SMTP though. I didn’t try deactivating BackWPup though and I’ve already got around the issue so I can’t test that, but I can explain what I did to fix the issue for my particular case – maybe it will help someone.

The issue is that the client id was not being sent to Google when clicking the “Allow plugin to send emails using your Google account” button, and I’m a developer so I looked into the code. Inspecting the button’s link showed me that indeed the client id was not there.

I’m not sure what would cause this (especially how it could be a conflict with another plugin), but my solution was to edit the link (by inspecting it in the browser) and paste the client id where it should have been. Once I did that, I clicked the button, and everything worked as expected.

Well thanks for the quick support Kyle! Problem solved! Well done!

Now to convince my client he still needs to migrate.

Yes, 5.6.31.

EDIT: Disregard that.

I didn’t realize this site was still on PHP 5.3.24. It’s a very old GoDaddy plan. I’ll tell my client he’s out of time and we need to migrate.

Thanks for looking into this Kyle.

• This reply was modified 7 years, 4 months ago by Chris. Reason: wrong PHP version

Ah, what timing. Yes, just applied the update and Pixabay is working again.

Thanks!