-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install process went fine, no errors, but the chrome extension is lot loading. #10
Comments
When you start elementor a temporary protractor config file is created. If you look at the log you will see something like this: Creating protractor configuration file
Starting protractor
Running command: [node /home/andres/.nvm/v0.11.16/lib/node_modules/elementor/node_modules/protractor-elementor/lib/cli.js --elementExplorer true --debuggerServerPort 6969 /tmp/protractor-conf115316-11669-10le421] Where The configuration file looks like this: exports.config = {
seleniumAddress: 'http://localhost:4444/wd/hub',
capabilities: {
browserName: 'chrome',
chromeOptions: {
args: [
'--load-extension=/home/andres/.nvm/v0.11.16/lib/node_modules/elementor/extension'
]
}
}
}; Can you send me the text of your configuration file? Maybe there is a space in the path and chrome cannot find the extension. |
exports.config = { seleniumAddress: 'http://localhost:4444/wd/hub', capabilities: { '--load-extension=C:\Users\derrickfink\AppData\Roaming\npm\node_modules\elementor\extension' |
I think I found a solution. I don't have my laptop with me (using my wife's laptop). I will get it fixed soon. |
I've found but am unable to load the manifest.json file Failed to load extension from: ~ I also can't find the Chrome Automation Extension. |
There was a problem in the path of the file for the extension. It looked like this: c:\path\to\extension Now the path uses forward slash: C:/path/to/extension I tested it on Windows 7. Let me know if it works for you. I just pushed a new version: 1.0.8 |
Thanks! |
The text was updated successfully, but these errors were encountered: