Error installing symfony CMF - symfony

I am trying to get symfony cmf up and running. After encountering a few problems during install, i'm stuck at this error message:
Catchable fatal error: Argument 1 passed to Symfony\Cmf\Component\Routing\ContentAwareGenerator::getBestLocaleRoute() must be an instance of Symfony\Component\Routing\Route, instance of Doctrine\ODM\PHPCR\Document\Generic given, called in D:\wamp\www\QHCMF\vendor\symfony-cmf\routing\Symfony\Cmf\Component\Routing\ContentAwareGenerator.php on line 86 and defined in D:\wamp\www\QHCMF\vendor\symfony-cmf\routing\Symfony\Cmf\Component\Routing\ContentAwareGenerator.php on line 98
I'm a novice and I have no clue what to make of this. I have looked at the ContentAwareGenerator.php but it was of no help to me.

You get a Generic document when no specific document is at that position in the content repository. PHPCR being a tree, there sometimes are nodes added in between so that a child node can have a parent. Those nodes do not map to any document, in which case the Generic document is used.
If you simply installed the sandbox from git and followed all the steps in order, this should not happen. You first set up the repository, then load the fixtures. If this is what you did, please open an issue at https://github.com/symfony-cmf/cmf-sandbox

Related

Bit.dev error creating a component dur to package mismatch

I have an issue and it wont let me create a component because of mismatch versions, I tried deleting vue-loader, vue-template-compiler node modules. Deleting #vue/compiler-sf an reinstalling etc and i always get the same message.
new components
(use "bit tag --all [version]" to lock a version with all your changes)
> test-test ... issues found
error found while parsing the file (edit the file and fix the parsing error):
src/components/testTest.vue ->
Vue packages version mismatch:
vue#3.2.31 (C:\Users\Alex 2019\AppData\Roaming\npm\node_modules\vue\index.js)
vue-template-compiler#2.7.13 (C:\Users\Alex 2019\AppData\Roaming\npm\node_modules\bit-bin\node_modules\vue-template-compiler\package.json)
This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using vue-loader#>=10.0, simply update vue-template-compiler.
If you are using vue-loader#<10.0 or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

why sanity start failed to compile in my nextjs app?

as a beginner i'm trying to follow up with a tutorial that uses sanity for backend , the problem is that when it come to the step to start sanity , so many errors are showing up here is the first one that i think is the major one that blocks the compilation
Error in ./schemas/schema.js (part:#sanity/base/schema)
Module build failed: Error: [BABEL]: Cannot find module 'C:\Users\ghars\tiktik-a
pp\sanity-backend\node_modules\#babel\helper-plugin-utils\lib\index.js'. Please
verify that the package.json has a valid "main" entry (While processing: C:\User
s\ghars\tiktik-app\sanity-backend\node_modules\#babel\plugin-proposal-class-prop
erties\lib\index.js)
i've searched about this and i think that sanity have a problem when it comes to node version 17 that i'm using , is there any solution without passing back to node 16 ?

Uploading manifest file failing

After making some changes in a JSON manifest file, I was trying to update it following the Amazon documentation:
ask smapi update-skill-manifest -g development -s amzn1.ask.skill.xxxx --manifest "skillManifest.json" --debug
I kept getting this error:
The error was not pointing to what the error was but my guess was that it was related to the parameters, but that was strange as I was following the documentation to letter.
I then tried, instead of passing the json file, to cat the content of the file, which would be either:
For Powershell: --manifest "$(type skillmanifest.json)"
For Linux: --manifest "$(cat skillmanifest.json)"
I still kept getting the same error.
Firstly, for debugging and getting a more accurate error, I checked my ASK-CLi version, which was outdated.
After updating ASK to the latest version I was still getting the same error.
At that point it started including an error object, which was saying:
When looking into Parsing error due to invalid body. and INVALID_REQUEST_PARAMETER through the error codes, it just said the body of the request cannot be parsed.
After research and playing around, the problem was the manifest parameter, changing it to "file:FILENAME" solved the issue:
--manifest "file:skillmanifest.json"
The documentation is not stating this but it seems necessary for it to go through.
I hope this helps someone out there avoid spending a full day troubleshooting.

Getting this error when compiling in theos

This is the error here:
http://i.imgur.com/tDwiXod.jpg
Any ideas? I have no idea what the error means
It seems like your theos tool is either not installed correctly or not in the path it expects it to be or your environment variable that points to it is not set correctly. You are also trying to compile as root which is problematic. You should be compiling as 'mobile' user and only use root while installing theos.
Type "echo $THEOS" (without quotes) to see if that environment variable is even set. It should point to somewhere like /opt/theos

Grunt Warning 6

Our automated build process incorporates a grunt task that periodically (more times than I'd like) generates a 6 return code.
According to the grunt web page 6 is a "Warning". Well okay, a warning for what? It's breaking our build since we would only pass on a 0 exit case. I'm looking at wrapping this in a script so I can catch this warning condition and generate a success exit code, though without any idea what the Warning might be I'm hesitant. It appears to work when I get this exit condition but would like a better understanding on what it may be.
Any ideas?
So this turned out to be an issue with grunt-contrib-less. I didn't recognize the associated less compiler error in our build log:
[39mnon_object_property_loadError: Cannot read property 'rules' of undefined in ../../XXXX/styles/modules/SomeLessFile.less on line null, column 0: [31m
Once I found this line a google search quickly found this in GitHub:
And have updated the grunt-contrib-less package. So far so good.
check http://gruntjs.com/api/grunt.fail:
If --stack is specified on the command-line and an error object was
specified, a stack trace will be logged.
Or try to run "grunt --verbose --force"

Resources