wpman

Hi Bowo,

That’s a good point !

@pressthemes1
Sorry, maybe I was not clear enough …. I was talking about finding tools inside ASE. For example, I want to change/or make a setting the medias, I type “Media” in the plugin search bar, and it shows me all the ASE tools concerning the media.
Then I can just click on 1 and it brings me to the right ASE’s panel.

Hi,

No, there is nothing there. The only error I saw (that I gave you at first), was the one in the php_error.log file.

While I was waiting for some more ideas to find a solution here, I decided to take a look at some plugins in my website, to test if there could be any conflict. And I found it ! So I’m gonna write it here, so maybe someone won’t loose so much time as I did with that problem.

I use Asset Cleanup Pro, and I can’t tell the problem comes from the plugin, or some settings in the plugin, but if I deactivate it, the backup comes back. That’s it … you can close this conversation.

Hi,
I did what you suggest, but I really doubt that “low number of visitors” is the problem, considering that Updraft has been working fine on my website for years, and that it stopped 2 months ago.

Also, I guess that if my site scheduler would be broken, all the other functions from my website would also fail (I guess), including Backwpup that I installed while waiting for a solution here, and works like a charm !

I’ll keep you posted to tell you if the problem is solved (because of the cron job) or not in the next 24h, but I would really be surprised !

Meanwhile, Would you have another idea or suggestion ?

Thanks

What do you mean by that ? I’m not sure to understand …

Concretely, what I can is that after the backup fails, I see that:

https://share.zight.com/6quwrR4O

And then, in WP Control, the “Database” cron job that I showed you disappear.
Then, if I save my settings again, the cron jobs comes back, and shows what I showed you first, until it fails again … etc

Does this help ?

Hi,

Sure, you can see a screen shot on this link: https://share.zight.com/mXuvpXrr

If this can help, here is the error I get in my php_errolog on my server:

“Task rescheduling event error for updraft_backup_database hook.
Error code: invalid_schedule.
Error message: The scheduled event does not exist.
Data : {“schedule”: “everyhour”, “args”:[], “interval”:3600}”

Done ! ??

Great. Thanks !

I understand !

Thanks again for all those advices and this great plugin ??

Best.

Hi Aaron,

Thanks so much for such a quick and clear answer. With those information on the debug, I can now more understand whats going on.

In fact, this has nothing to do with the CPTs. I think that what happened was that all the simple URLs to guess where already redirected, and what was left was the more complex URLs to guess.

After about 20 different cases, I had to go down to 82, which seems to works in most case, considering the nature of the 404s I have.

Next step:

I have 3353 “Captured 404 URLs”. What should I do ?
Delete them and let you plgin do the work and check from time to time ?
Or is there a way to “push a button” on you plugin, to bulk resubmit them I have them automatically redirected well ? I didn’t find such a setting !

What would you do in such a case ?

I flushed all the caches, but the problem is still there !

I also looked at the plugin on the server, and everything is 4.6.9

So I really don’t know what to say. But anyway, our live site is OK, so that’s fine for me !

Thanks.

We have now two websites:
1 which was our development site
https://wpmanstage.com/jfval
1 which is now our live website.
https://cymbalum-mundi.com

Both where updated to 1.6.9. and surprisingly, the problem only occurs with the development site, which is a good news for us.

But if you want to investigate, you can do it with the development site, for which I already gave you access.

Hi Daniele,

I don’t have much to say… the links terms where showing, but on mouseover, the tooltips was not showing up.
Everything was fine with all other major browsers.
So, I downgraded to 4.6.8 and everything is fine.

Hi, I just made the update and it looks like that your update fixed the bug on Firefox, but created one in Chrome ! ??