Hi, Just to inform users about a possible issue that is created by MW as it has hijacked the `composer.json` in MW 1.25.
Yesterday after upgrading MW to version 1.25alpha via git and me not having realized that the `composer.json` was replaced by a bare MW version (the original was created manually and contained information about all the installed extensions) and while running `composer update` I made things worst because Composer interpreted the empty file as a request to delete all previous installed extensions. While for a normal user the replacement/deletion should not matter much, personally I felt annoyed with MW because some of my work went down the drain just because someone decide to deploy a bare `composer.json`. Lessen learned, if you do development work don't trust MW and copy anything to a safe place before you press the enter button. PS: I was able to recover some of my work from a 6-month old backup. [0] https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/314 Cheers ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
