Conflicting configuration warnings on admin page

[jnfrmarks]

Steps to reproduce

1. Install 8.1
2. Do not set a cacheing model
3. Go to admin page

Expected behaviour

The only message about cacheing should be that it's not configured

Actual behaviour

I see messages about the APCu version and that cacheing is not configured. I'm thinking that we shouldn't be checking the version if it's not configured.

Server configuration

Ubuntu 14.04
PHP 5.5.9
ownCloud Enterprise Edition 8.1 alpha 2 (testing)

[ghost]

Hi,

isn't it so that APCu was disabled because of the old version and then the second message appears because there is no other memory cache configured?

[jnfrmarks]

I was thinking: why are we checking the APCu version if it's not even configured?

[DeepDiver1975]

Well - the list of warnings might cause confusion - but technically speaking they are correct.

1. APCu was detected with a wrong version -> warning is reported and not used
2. Because no other memcache was detected -> warning because performance will not be optimal

[jnfrmarks]

I agree that they are technically correct. I am just questioning if we should be displaying 1 if no memcache is configured. If we're ok with this, then we can close this issue.

[DeepDiver1975]

well removing either of these messages can result in confusion as well.

But this is more a UX/tech writer topic @jancborchardt @carlaschroder THX

[jancborchardt]

It seems like yeah, if no memory cache is configured, then we don’t need the APCu message.

[DeepDiver1975]

well and then you turn APCu on -> what shall happen?

APCu is broken and you have still no mem cache

[jnfrmarks]

Then I should get a message saying that APCu is the wrong version.

My issue is we're checking something that isn't yet configured and providing an error to the user on that. We should only be checking it if it's configured.

For instance, when I configured the memcache to XCache, I do not get the APCu error (as expected). If you're saying that we should check it regardless of if memcache is configured in config.php then I would have expected the same warning when XCache was configured.

[jancborchardt]

Yup, as @jnfrmarks said. Ideally the APCu warning should also mention that it’s for caching.

[DeepDiver1975]

Ideally the APCu warning should also mention that it’s for caching.

well - let's add a documentation link to it just like we did with the "no mem cache" warning

[carlaschroder]

OPCache replaces APC in PHP 5.5, and is included so you don't have to install it separately. http://php.net/manual/en/opcache.installation.php I think this may be more than a documentation issue.

[ghost]

Not exactly as also written here: owncloud-archive/documentation#1056 (comment)

APC is opcode cache and data store
APCu is only data store
OPcache is only opcode cache

So OPCache only replaces one part of APC and APCu is still needed if OPCache is installed.

But i still think the problem described here is because the old/unsupported APCu version got disabled by ownCloud and then the second message also appears because no other cache is installed. To fix this you need either:

1. Update APCu to 4.0.6 later -> both messages disappear
2. Install another cache like XCache -> The "no cache" message disappears but the APCu version stays (as you can also enable two cache modules side-by-side AFAIK, no matter if they are compatible or not).

[carlaschroder]

See how y'all like this one owncloud-archive/documentation#1099

[jnfrmarks]

Doc looks ok to me.

Can we close this one? @carlaschroder @jancborchardt @DeepDiver1975