Recent content by Dhekhanur

No problem. Just wanted to report since it was obviously not intended behavior. (And this is me just playing around in my sandbox with "all" addons)

Not sure if I should report this under XF bugs or importer bugs but upon release and upgrade of XF and addons (2.3.0 RC 5) (xfes, xfmg, xfrm, xfi) to latest (2.3.0 and 1.6.0 Alpha 1 respectively) I have an "upgrade loop" to rebuild XFI and I do not have unstable upgrades enabled

To enhance understanding of my rambles (also while I use more strongly worded language is my opinion and not expectations): the absence of third-party hashes (as in the files modified by third parties (=addons), I am in complete agreement with you. Maybe a note if you detect one missing but...

So creating a new thread for this since this is a "different" bug than the file clean-up also removing the hashes.json what I did was this I "deleted" the hashes.json by hand and checked with the file health checker how that changed the results no other actions were taken while this was done...

Just to add to this that while you're unlikely to keep the importers of the forums (XFI) around long-term they also lack the hashes.json files hash included in the hashes.json (did a quick cat grep) this works as expected: php cmd.php xf:file-clean-up XFI (edit: TL;DR of this thread only the XF...

May have been local issue only. Reinstalled and now working as intended.

Manual file clean-up of mg and rm addons results in [ERROR] Current hashes file cannot be determined. Steps to reproduce: Install new 2.3.0 RC4 upgrade to RC5 and post-upgrade Run in CLI php cmd.php xf:file-clean-up XFMG php cmd.php xf:file-clean-up XFRM