search

TelemundoDigitalUnit / NBC_Docker

0 stars 1 forks source link

Viewing Microsites on Local Error #10

Open dchianese opened 4 years ago

dchianese commented 4 years ago

When I go to my local microsite page I am getting this wpcom_vip_load_plugin: Unable to load plugin wordpress-fieldmanager; the plugin was not found in the plugin directories (/var/www/html/wp-content/plugins)

nbcsteveb commented 4 years ago

Hey @dchianese,

Can you try running this command from the <NBC_Docker Repo>/wp-container-microsites/wp-content folder.

git submodule init && git submodule sync --recursive && git submodule update --recursive ;

That should bring in all the submodules and plugins for you.

dchianese commented 4 years ago

When I run that command I get `Cloning into '/Users/a206107261/repos/wordpress/wp-container-microsites/wp-content/plugins/ad-layers'... ssh: Could not resolve hostname github.com: nodename nor servname provided, or not known fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists. fatal: clone of 'git@github.com:alleyinteractive/ad-layers.git' into submodule path '/Users/a206107261/repos/wordpress/wp-container-microsites/wp-content/plugins/ad-layers' failed Failed to clone 'plugins/ad-layers'. Retry scheduled Cloning into '/Users/a206107261/repos/wordpress/wp-container-microsites/wp-content/plugins/ad-layers'... ssh: Could not resolve hostname github.com: nodename nor servname provided, or not known fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists. fatal: clone of 'git@github.com:alleyinteractive/ad-layers.git' into submodule path '/Users/a206107261/repos/wordpress/wp-container-microsites/wp-content/plugins/ad-layers' failed Failed to clone 'plugins/ad-layers' a second time, aborting `

nbcsteveb commented 4 years ago

Could not resolve hostname github.com: nodename nor servname provided, or not known fatal

These are proxy issues.

Please make sure your $http_proxy and $https_proxy environment variables are properly set.

You can also try jumping off the proxy to run the update command.

dchianese commented 4 years ago

Same error

tnspinks commented 4 years ago

I'm also getting this error 😢