In 20.1 he found out that his site was hacked ? Ah ok . ThxHe just found out.
Version control does not show any unauthorized or unintended changes to the package between 1/9 and 1/20. We will regenerate cached versions of the package today.We need an audit of the download package.
Version control does not show any unauthorized or unintended changes to the package between 1/9 and 1/20. We will regenerate cached versions of the package today.
If you updated your VaultWiki installation between these dates, you may just want to run XenForo's File Health Check to be safe (AdminCP > Tools > Diagnostics > File Health Check).
I think that how you have told your userbase everything about the hack should be commended. Not many businesses follow this openness with their customers. Many could learn a thing or two. I commend you.VaultWiki.org was recently hacked. If you have an account at the site, you will want to read the disclosure: https://www.vaultwiki.org/articles/183/
(released December 24, 2015)
- Style Properties for History Status Colors
- Fixed instant emails for edits to same subscribed page
- Fixed email notifications for feed updates
- Fixed feed entries not removed when feed is deleted
- Fixed E_NOTICE errors still halt install/upgrade with debug off
- Fixed invalid closing tags in wiki prefs
- Fixed array to string conversion editing comments
- Fixed fatal error upgrading to 4.0.6 from 4.0.0 Beta 7
- Fixed can't chmod existing CSS...
(released March 2, 2016)
- Compatibility with [bd] WidgetFramework 2.6+
- missing data in VW4 import
- missing data in VW3 import
- upgrade might skip number of steps from previous upgrade
- tweaked responsive style on some pages
- can't approve moderated discussions
- broken images using FILE for non-images
- add-on upgrade control doesn't redirect to upgrade script
- no available target area for non-normal page when area only accepts that kind
- extra queries when pages...
We use essential cookies to make this site work, and optional cookies to enhance your experience.