Recent content by Neilski

Mmm, I think we're talking at cross purposes here. None of the updates in my example were deleted, just some of the versions, so none of the updates are offering an undelete button. (You can "Release a new version" without choosing "Post an update" of course, and I did so for at least one of the...

This issue is not necessarily a bug in XF, but I'm reporting here because it has clear potential to catch people by surprise*. (See also discussion in the "How to duplicate a live site to use as a test site" thread.) In short, when you disable email with $config['enableMail'] = false; in...

Was sooo confused by this, so went and had another look :) I now see that we're talking about different things. You mention resource updates but I'm unable to undelete resource versions. For example, in the history tab, there's no way I can find to undelete the two older versions:

Sorry, forgot to reply to this. You may have misunderstood me (my point was that if you turn off email temporarily, you could reasonably prefer to keep the bounce handling going, since that might prevent fresh emails being sent to a bouncing address immediately after the email was turned back on...

Did I post this in the wrong place to get a support response?

I can't imagine wanting a cloned test site to handle bounces, ever. For a live site, I struggle to imagine good reasons to turn off email temporarily; best I can come up with is if you have an issue with the mail config and need to update it, you might shut off outgoing emails for a while...

Fair question. I am not actually certain that it should be considered a bug in XF, as such. (It's perhaps more of a bug in this "duplicate your site for testing" guide, if anything :)) It really depends on what one wants/expects to achieve by disabling outgoing emails. On anything other than a...

I may be mixed up, but I thought that 2.3 was going to remove the Cumulative Layout Shift issues that arise from embedded content loading late in the rendering process (including proxied images, media, etc.) but this page is now doing just that. I fear that it's because of the Twitter media...

Finally got around to putting it to the test... In short: the email bounce handler does run even when email is disabled. See pic below... (At first, I manually triggered the job, and then realised that for completeness I should let it run by itself. Both runs fetched a bounce.) I'd rate the...

Ahh, OK yes this would be a drawback of the server-based cron I guess - if you forget to set up a new cron job (or swapping back to activity-based) when cloning the site then the cron jobs never happen at all... (A good reminder, given that I'm considering swapping to server-based on our site.)...

Well, I just re-read the code for the things that happen when $config['enableMail'] = false and I'm unable to see anything that would stop the bounce handler cron job from doing its thing. (I also rechecked XF/EmailBounce/Processor.php and see nothing there either.)

I read below, but am still not clear on the reasons for bumping the minimum version again... What did I miss?

Ahh... Maybe I need to re-read the code then.

A test site has less traffic, thus less likelihood of triggering the cron jobs, thus it's not often going to beat the live site to the bounces. However it could still happen, unless the code actually prevents it; my hasty skim of the code suggests that the bounce handler doesn't check if email...

Ah, that's not what I mean. I already disabled outgoing emails, but (caveat: memory fuzzy, some weeks elapsed now) on one of my test sites, I got an error that suggested the bounce handler had tried to fetch emails from the bounce address. This would interfere with the bounced email system by...