Hi Florian,
you are right. This is something we need.
Frank
On 28.05.2012, at 11:59, Florian Hülsmann f...@cbix.de wrote:
s/doesn't work/isn't provided yet/
I meant if a newer version of an app is uploaded to the repo, the OC admin
has to remove the old version completely and can't
What exactly doesn´t work?
On 28.05.2012, at 00:02, Florian Hülsmann f...@cbix.de wrote:
Additionally upgrading apps to a newer version doesn't work.
Florian
Am 27.05.2012 23:34, schrieb Michael Gapczynski:
On Sunday, May 27, 2012 01:43:11 PM Florian Rüchel wrote:
I would prefer a
s/doesn't work/isn't provided yet/
I meant if a newer version of an app is uploaded to the repo, the OC
admin has to remove the old version completely and can't simply click an
Upgrade button in the apps list, right?
My proposal is to let the developer add more information into the app's
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
On Sunday, May 27, 2012 01:43:11 PM Florian Rüchel wrote:
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.
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
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
