this is a port of an older twitter plugin that I am just trying to get to work with PG > 3.0, I have this working fine on my IDE, so I wanted to share with others, for some reason when I try and do the install via NPM it errors. I have re-read the file system structure and plugin.xml specification, and cannot see any errors.
I even changed the ID of the plugin from CDVPluginTwitter incase the prefix was throwing an error, however I still get
path.js:360
throw new TypeError('Arguments to path.join must be strings');
^
TypeError: Arguments to path.join must be strings
at path.js:360:15
at Array.filter (native)
at Object.exports.join (path.js:358:36)
at /usr/local/lib/node_modules/phonegap/node_modules/cordova/node_modules/plugman/src/util/plugins.js:72:39
at /usr/local/lib/node_modules/phonegap/node_modules/cordova/node_modules/shelljs/shell.js:1707:7
at ChildProcess.exithandler (child_process.js:635:7)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:735:16)
at Socket.<anonymous> (child_process.js:948:11)
at Socket.EventEmitter.emit (events.js:95:17)
The Git is located here, https://github.com/ednasgoldfishuk/CDVPluginTwitter/tree/master
Any ideas?
It was missing the finishing </plugin> tag in plugin.xml, Github has been updated and now is confirmed installable on PhoneGap 3.0 +
Related
I have looked at several answers suggested to a similar issue but nothing worked in my case.
FYI, this is my first project in Laravel 7, working fine on my Mac.
I have deployed the project on my server following this article.
When running the project on the web, I get the following error :
Fatal error: Uncaught RuntimeException: A facade root has not been set. in /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php:258
Stack trace: #0 /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(425): Illuminate\Support\Facades\Facade::__callStatic('replaceNamespac...', Array) #1 /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(402): Illuminate\Foundation\Exceptions\Handler->registerErrorViewPaths() #2 /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(313): Illuminate\Foundation\Exceptions\Handler->renderHttpException(Object(Symfony\Component\HttpKernel\Exception\HttpException)) #3 /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/Handler.php(210): Illuminate\Foundation\Exceptions\Handler->prepareResponse(Object(Illuminate\Http\Request), Object(Symfony\Component\HttpKernel\Exception\HttpExcepti in /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php on line 258
How can I fix it?
I finally found a solution that worked in my case.
delete the folder vendor
run composer update
run php artisan config:cache
run php artisan config:clear
Home page now displays but the routes do not work...
If the solution from #Paul Godard doesn't work, it could be a psr/log issue as mine.
My composer update added psr/log v2.0.0, which requires php8. However, my application is on php7.4
That gave me the exact error output like in the description
Fatal error: Uncaught RuntimeException: A facade root has not been set. in /usr/www/users/utopiqwvpw/vendor/laravel/framework/src/Illuminate/Support/Facades/Facade.php:258
My solution was to specify in composer.json that I'm using "psr/log": "^1.1.0"
Then run composer update
I got that error when my config folder was deleted by mistake. So after recovering the config folder. My project worked fine. You have to check if any folder is removed on which project is depending. Recover or copy it. It will work fine then.
Currently getting this error when i try to run eslint locally:
Error: Cannot find module 'escope'
at Function.Module._resolveFilename (module.js:455:15)
at monkeypatch (/Users/pablorincon/Documents/SSENSE/micro-services/ws-website/services/ui-website/node_modules/babel-eslint/index.js:53:26)
at Object.exports.parse (/Users/pablorincon/Documents/SSENSE/micro-services/ws-website/services/ui-website/node_modules/babel-eslint/index.js:358:5)
at parse (/Users/pablorincon/Documents/SSENSE/micro-services/ws-website/services/ui-website/node_modules/eslint/lib/linter.js:671:23)
at Linter.verify (/Users/pablorincon/Documents/SSENSE/micro-services/ws-website/services/ui-website/node_modules/eslint/lib/linter.js:806:27)
at processText (/Users/pablorincon/Documents/SSENSE/micro-services/ws-website/services/ui-website/node_modules/eslint/lib/cli-engine.js:278:31)
at processFile (/Users/pablorincon/Documents/SSENSE/micro-services/ws-website/services/ui-website/node_modules/eslint/lib/cli-engine.js:320:18)
at executeOnFile (/Users/pablorincon/Documents/SSENSE/micro-services/ws-website/services/ui-website/node_modules/eslint/lib/cli-engine.js:655:25)
at fileList.forEach.fileInfo (/Users/pablorincon/Documents/SSENSE/micro-services/ws-website/services/ui-website/node_modules/eslint/lib/cli-engine.js:693:13)
at Array.forEach (native)
What's weird is that im using the same linting configuration with another project, and i had no issues at all.
I'm using:
babel-eslint#7.1.1
eslint#4.0.0-beta.0
Any ideas ?
Even though I had same package.json, babel-eslint was set as "7.1.1" in one and "^7.1.1" in the other.
Basically ESLint v4 uses a new fork of escope, which was then updated on version 7.2.3 of babel-eslint.
So, adding the little ^ to my configuration fixed my problem.
I am following the GitHub instructions to contribute to the Visual Studio Code (vscode) project. The instructions I am following are here:
https://github.com/Microsoft/vscode/wiki/How-to-Contribute
I am on Windows 10 and therefore following the Windows-specific instructions.
When I run 'npm run watch' after fulfilling the pre-requisites, I get over 1700 errors when it attempts to build.
Sample errors:
[16:56:59] Finished 'clean-client' after 3.78 s
[16:56:59] Starting 'watch-client'...
[16:57:25] Error:E:/src/git/vscode/extensions/css/server/src/languageModelCache.ts(22,21): Cannot find name 'Date'.
[16:57:25] Error: E:/src/git/vscode/extensions/css/server/src/languageModelCache.ts(23,15): Cannot find name 'Object'.
[16:57:25] Error: E:/src/git/vscode/extensions/css/server/src/languageModelCache.ts(40,31): Cannot find name 'Date'.
[16:57:25] Error: E:/src/git/vscode/extensions/css/server/src/languageModelCache.ts(44,80): Cannot find name 'Date'.
[16:57:25] Error: E:/src/git/vscode/extensions/css/server/src/languageModelCache.ts(50,22): Cannot find name 'Number'.
The full error list is here:
http://pastebin.com/wJgEQ18m
I am trying to find out how to troubleshoot and correct these errors. So far I have not found anything online to point me to what I did wrong in setting things up.
It turns out this was caused by a bug in the gulp-tsb project, which was just fixed with the commit below.
https://github.com/jrieken/gulp-tsb/commit/ea84a0a16a631410071ae96336ac9f3842ec41b0
Upgrading to the new gulp and typescript tools fixed the problem.
While running $ sails lift command , I am getting this error.
info: Starting app...
error: Trying to use unknown adapter, "sailspostgresql", in model `adminintro`.
error: Are you sure that adapter is installed in this Sails app?
error: If you wrote a custom adapter with identity="sailspostgresql", it should be in this app's adapters directory.
error: Otherwise, if you're trying to use an adapter named `sailspostgresql`, please run `npm install sails-sailspostgresql#0.10.x`
Please help me out guys ...
Got the answer ... It was unicode mistake . I have copy n pasted the code for local.js from one of my coworker's pdf file. So when I pasted that code in my local.js "-" was replaced with some unicode http://www.fileformat.info/info/unicode/char/00AD/index.htm .. and that was causing this issue..
Maybe I am making a fundamental error, but I assume you have to install the Import / Export plugin on IP3.9 to make the zip file before you import it to the new ip4.1 site ?
The plugin will not install in IP3.9 there is an error "plugin.ini doesn't exist"
The Import / Export plugin is not in the IP3.x format
ip_plugins/group_name/plugin_name/files
so I do not see how it can be installed.
If I try exporting data from IP4.1 I get the following error message
Error:
Fatal error: Call to undefined method Ip\Page::getType() in /var/www/ip41/Plugin/ImportExport/ManagerExport.php on line 207
I am probably doing something stupid, but I cannot see what
Alan
For v3.x version you must download a 3.x branch of the plugin - https://github.com/impresspages-plugins/ImportExport/tree/3.x
For the error in v4.1 open an issue on GitHub - https://github.com/impresspages-plugins/ImportExport/issues
I hope it does make sense now.