# NC 15.0.0, versions do not appear

**URL:** <https://help.nextcloud.com/t/nc-15-0-0-versions-do-not-appear/44200>\
**Category:** ℹ️ Support\
**Tags:** nc15, files-versions-app\
**Created:** [December 31, 2018, 11:11am UTC](https://help.nextcloud.com/t/nc-15-0-0-versions-do-not-appear/44200 "2018-12-31T11:11:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cyril](https://help.nextcloud.com/user_avatar/help.nextcloud.com/cyril/32/2664_2.png) [@Cyril](https://help.nextcloud.com/u/Cyril)\
**Post date:** [December 31, 2018, 11:11am UTC](https://help.nextcloud.com/t/nc-15-0-0-versions-do-not-appear/44200/1 "2018-12-31T11:11:29Z")

</div>

Nextcloud version _(eg, 12.0.2)_:15.0.0.10  
Operating system and version _(eg, Ubuntu 17.04)_: linux (shared hosting)  
Apache or nginx version _(eg, Apache 2.4.25)_: Apache 2.4.37  
PHP version _(eg, 7.1)_: 7.2

The issue you are facing:  
Using the web interface, I cannot see/restore previous versions of my files. I know they exist, since I can see them in nextcloud-data/username/files\_versions folder, but when I click on “Versions” from the “details” screen of a particular file, nothing happens.

Using Firefox debugging console, I get the following message (similar in Chrome console) at the exact moment I click on “Versions”:

```auto
    **`TypeError: this.sync is not a function** core.js:2101:14
fetch https://XXX/core/vendor/core.js:2101:14
nextPage https://XXX/index.php/js/files_versions/merged.js:270:4
setFileInfo https://XXX/index.php/js/files_versions/merged.js:360:5
selectTab https://XXX/index.php/js/files/merged-index.js:9972:4
_onClickTab https://XXX/index.php/js/files/merged-index.js:9876:4
_onClickTab self-hosted:975:17 
dispatch https://XXX/core/vendor/core.js:3:6414
add/r.handle https://XXX/core/vendor/core.js:3:3224

```

Is this the first time you’ve seen this error? _(Y/N)_: Y, I know that versioning used to work since I have used it in the past. I do not remember if I have used it successfully after the 15.0.0 upgrade.

Steps to replicate it:

1. Create a file
2. Make a change so a new version is created
3. In the web interface, click on Details -\> Versions

The output of your Nextcloud log in **Admin \> Logging** :  
Nothing relevant

The output of your config.php file in `/path/to/nextcloud` (make sure you remove any identifiable information!):

```auto
<?php
$CONFIG = array (
  'instanceid' => 'XXX',
  'passwordsalt' => 'XXX',
  'secret' => 'XXX',
  'trusted_domains' => 
  array (
    0 => 'XXX',
  ),
  'datadirectory' => '/home/secondes/nextcloud-data',
  'overwrite.cli.url' => 'XXX',
  'dbtype' => 'mysql',
  'version' => '15.0.0.10',
  'dbname' => 'XXX',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'dbuser' => 'XXX',
  'dbpassword' => 'XXX',
  'logtimezone' => 'UTC',
  'installed' => true,
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'debug' => false,
  'updater.secret' => 'XXX',
  'maintenance' => false,
  'enable_certificate_management' => false,
  'mail_from_address' => 'nextcloud',
  'mail_smtpmode' => 'smtp',
  'mail_domain' => 'XXX',
  'theme' => '',
  'loglevel' => 2,
  'updater.release.channel' => 'stable',
  'versions_retention_obligation' => 'auto',
  'mail_smtphost' => 'XXX',
  'mail_smtpport' => '465',
  'mail_smtpauth' => 1,
  'mail_smtpname' => 'XXX',
  'mail_smtppassword' => 'XXX',
  'mail_smtpsecure' => 'ssl',
);
```

---

<div class="post-metadata">

**Author:** ![stratege1401](https://help.nextcloud.com/user_avatar/help.nextcloud.com/stratege1401/32/7570_2.png) [@stratege1401](https://help.nextcloud.com/u/stratege1401)\
**Post date:** [January 1, 2019, 7:18pm UTC](https://help.nextcloud.com/t/nc-15-0-0-versions-do-not-appear/44200/2 "2019-01-01T19:18:14Z")

</div>

this may be a real bug.

Better post it on githuh [https://github.com/nextcloud/server/issues](https://github.com/nextcloud/server/issues)

---

<div class="post-metadata">

**Author:** ![Cyril](https://help.nextcloud.com/user_avatar/help.nextcloud.com/cyril/32/2664_2.png) [@Cyril](https://help.nextcloud.com/u/Cyril)\
**Post date:** [January 3, 2019, 5:29pm UTC](https://help.nextcloud.com/t/nc-15-0-0-versions-do-not-appear/44200/3 "2019-01-03T17:29:08Z")

</div>

Thanks for the suggestion, I filed a bug report on Github.  
After a lot of tries, I finally discovered that, at least in my particular situation, **disabling the Comments application breaks the versioning app** as described above. Enabling again the Comments application restored the functionality as expected.  
Problem solved on my side, but I would be interested in knowing whether this is a general bug or only with my configuration 😕

EDIT: Actually, I can reproduce this on [demo.nextcloud.com](http://demo.nextcloud.com), so it seems it is a genuine bug

---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 4, 2024, 8:38am UTC](https://help.nextcloud.com/t/nc-15-0-0-versions-do-not-appear/44200/4 "2024-12-04T08:38:14Z")

</div>



---

<div class="post-metadata">

**Author:** ![wwe](https://help.nextcloud.com/user_avatar/help.nextcloud.com/wwe/32/72963_2.png) [@wwe](https://help.nextcloud.com/u/wwe)\
**Post date:** [December 9, 2024, 3:52pm UTC](https://help.nextcloud.com/t/nc-15-0-0-versions-do-not-appear/44200/5 "2024-12-09T15:52:14Z")

</div>


