Error when using custom DB
See original GitHub issueI just came across the npm package today. I set it up with MongoDB and made a test command for it. When the giveaway ended, instead of picking a winner it gave me this error:
(node:22344) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received type
boolean (false)
Anyone know why this is happening?
Issue Analytics
- State:
- Created 3 years ago
- Comments:9
Top Results From Across the Web
Troubleshoot Custom Databases - Auth0
You can use return errors resulting from your custom database connection for troubleshooting purposes. We will also cover some basic troubleshooting steps ...
Read more >How to Add a Custom Database Error Page in ... - WPBeginner
A simple tutorial that shows you how to customize your error establishing database connection or other database error pages in WordPress.
Read more >Support custom error messages from custom DB scripts #234
Is it working for all custom-db scripts? I followed your PR and use this code in my login script: return callback(new ValidationError('custom- ...
Read more >Custom Database Error Page - CSS-Tricks
Put a file called “db-error.php” directly inside your /wp-content/ folder and WordPress will automatically use that when there is a database ...
Read more >Scheduled jobs are failing with the error 'Cannot upload any ...
This error is presented when the CUSTOM database is full. Diagnosing The Problem. The CUSTOM and DATAMART database both contribute to this quota ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you so much for the help! I’m going to close this issue. Have a very nice day!
Oh, I forgot I actually fixed this error for someone a time ago, I just didn’t recognize it. Remove
storage: false
from your manager options, it’s what causes the error It will be removed from the examples in the next release.