Import folders to Cookbook

First, I love this app!! I enjoy cooking and it keeps me wonderfully organized and helps me share recipes with my family.

Unfortunately, I had to reinstall NC. I copied my old recipe folders into my new Recipes folder. They don’t show in the app - is there something I need to do to import them or make them visible to the app?

Thanks for the app and your help.

The recipes need to get reindexed. This happens every now and then, but can also be triggered from the settings menu.

If you had the cookbook app not open prior to restoring, it might have selected another folder for storing the recipes than you might want. You normally can select the folder in the settings. It will reindex in the new folder automatically.

Currently, there was a recent bug report from last night that switching of the folder was not possible with Cookbook 0.11.0 on NC28. I just inform you, this is not yet confirmed but would be fixed soon.

Depending on the number of recipes in the folder, reindexing might take some time. Be patient, you might need to trigger multiple times in case it times out.

1 Like

Thank you. I moved the folders in and triggered a rescan several times, waited, but all to no avail.

What did work, however, was to create a recipe with the same name. Say ok when told a duplicate exists and then load all recipes Then a rescan read the new folder(s).

Thanks for your help.


The method described in this post did work for me too. Thx!

But I needed to do this for every Receipe, quite annoying :confused:

@finco1 @peterge do you have the recipe archives still?

I would be interested to have them to test if I can reproduce it in the dev instance. Also I would need to know ideally the version of NC and cookbook you use(ed).


PS: I can send you a NC link to put the files (or zipped folder). First do not delete them if possible and give me a short hint.

Thanks again

These were the files I did import yesterday, using the manual method suggested by finco1.

I did migrate them from
a nextcloud instance with 28.0.4 and cookbook 0.11.0
to a nextcloud instance with 29.0.0 and cookbook 0.11.0.

I guess these are the infos u asked for or do you need to know anything else?

Hello and thank you for your support!

So, you had issues with these 15 recipes? I will try importing them here in my dev instance as you did and see what happens. Maybe I can get the reason for the problem and fix is soon.

I no longer have the archive. I just replaced the old recipes with new copies.

1 Like

I tried it now multiple times but without success (in the sense that it worked out of the box as expected). I can try one more thing but this requires a bit more time to set up.

To make it simpler for me to debug things: How fast is the NC instance in general on your machine (is it by chance a Raspberry pi or such)?

If not, I can only add some debugging code that might help (was on the agenda anyways) and push out a 0.11.1 (also on the agenda for the near future).

My vps where NC is running in a docker ct has these specs:

Its a VPS hosted at netcup, no pi or such.

Would any other logs help you? I can provide them of course.

CB is still not reachable:

Internal Server Error

The server was unable to complete your request.

If this happens again, please send the technical details below to the server administrator.

More details can be found in the server log.

Technical details

  • Remote Address:
  • Request ID: M4pcm6Dmglo28QjJx9av

Did you remove the, .sh and .txt files? Maybe those are causing problems on my side…

Yes, I did remove them. Unfortunately, I am on the road ATM. Could you try that once for me?

I tried it on my dev instance with all files. No problem was detected. It took here milliseconds to switch the recipe folder.

So you have full control over the server @peterge? If yes, you could enable device mode temporarily (in the config.php), try the request once more and stop debugging again. This should print more details and a stack trace on the 500 server error page. With that, we might be able to get now insight on what is going on.


And, just to verify: You did not keep the .git folder in the same location, did you?

Ye i have full control. How do I enable device mode? searching for device mode nextcloud just brings this Manage connected browsers and devices — Nextcloud latest User Manual latest documentation

i did have the .git folder and the in the Recipes folder, i just cloned my repo and mv * to Recepies/

But even after deleting .git and the other files ()md, txt & sh) its still showing the error, even after restarting the container and reenabling the app:

Sorry, I meant debug mode. Just set 'debug' => true in the config.php.

now the page shows this trace when i open cookbook:

Internal Server Error

The server was unable to complete your request.

If this happens again, please send the technical details below to the server administrator.

More details can be found in the server log.
Technical details

    Remote Address:
    Request ID: x3OT6JEzKuX7eeIUwn5f
    Type: OCP\Files\GenericFileException
    Code: 0
    File: /app/www/public/lib/private/Files/Node/File.php
    Line: 56


#0 /config/www/nextcloud/apps/cookbook/lib/Service/DbCacheService.php(143): OC\Files\Node\File->getContent()
#1 /config/www/nextcloud/apps/cookbook/lib/Service/DbCacheService.php(124): OCA\Cookbook\Service\DbCacheService->parseJSONFile()
#2 /config/www/nextcloud/apps/cookbook/lib/Service/DbCacheService.php(69): OCA\Cookbook\Service\DbCacheService->parseJSONFiles()
#3 /config/www/nextcloud/apps/cookbook/lib/Service/DbCacheService.php(406): OCA\Cookbook\Service\DbCacheService->updateCache()
#4 /config/www/nextcloud/apps/cookbook/lib/Service/DbCacheService.php(395): OCA\Cookbook\Service\DbCacheService->checkSearchIndexUpdate()
#5 /config/www/nextcloud/apps/cookbook/lib/Controller/MainController.php(56): OCA\Cookbook\Service\DbCacheService->triggerCheck()
#6 /app/www/public/lib/private/AppFramework/Http/Dispatcher.php(232): OCA\Cookbook\Controller\MainController->index()
#7 /app/www/public/lib/private/AppFramework/Http/Dispatcher.php(138): OC\AppFramework\Http\Dispatcher->executeController()
#8 /app/www/public/lib/private/AppFramework/App.php(184): OC\AppFramework\Http\Dispatcher->dispatch()
#9 /app/www/public/lib/private/Route/Router.php(338): OC\AppFramework\App::main()
#10 /app/www/public/lib/base.php(1050): OC\Route\Router->match()
#11 /app/www/public/index.php(49): OC::handleRequest()
#12 {main}

OK, nice to see that!

By chance, I yesterday merged a PR to make the DbCacheService more robust and cover the getContent method that causes the trouble in your case. This will not solve the underlying problem but should at least create a log entry in the NC logs (typically data/nextcloud.log) with the offending file name.

My guess is a permission issue but once we have the file name, this will be simpler to identify.

The next release will be done soon. I wanted to push out a beta release eventually in the next 2 days. I think there are only 2 issues left right now.


kk, watched the repo to keep track when the release is published

1 Like