I would prefer a warning and let the user decide. For example you could create a "compatibility mode", basically disabling the check and any others if it is active. Thus the user knows that certain bugs may be because of incompatibility. You could then provide a list of such incompatible apps so the user can check for new, adapted versions.
Cheers, Florian On 26.05.2012 18:01, Frank Karlitschek wrote: > > I added the check so that only apps that are compatible with the current > version can be installed. Most of the strange ownCloud 4 bugs reported the > last few days are caused because people use incompatible apps. > App developer have to port and test their app and mark them as compatible > with oC 4 before they work. > So this is intended behavior. Similar to browser plugins for example > > Frank > > > On 26.05.2012, at 17:33, Florian Hülsmann <[email protected]> wrote: > >> In lib/installer.php I found this check: >> >> $version=OC_Util::getVersion(); >> if(!isset($info['require']) or >> ($version[0]>$info['require'])){ >> OC_Log::write('core','App can\'t be installed because it is not >> compatible with this version of ownCloud',OC_Log::ERROR); >> ... >> >> Which means that if the <require> tag content in info.xml is below the >> ownCloud version number, the installation fails. So in ownCloud 5 no >> external apps can be installed before having their <require> tag set to a >> number >= 5. Can someone please explain me the intension of this behavior? >> Or did I miss something? >> >> Thanks! >> >> -- >> Florian Hülsmann >> <[email protected]> >> http://cbix.de >> _______________________________________________ >> Owncloud mailing list >> [email protected] >> https://mail.kde.org/mailman/listinfo/owncloud > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
