olefredrik / FoundationPress

FoundationPress is a WordPress starter theme based on Foundation 6 by Zurb
https://foundationpress.olefredrik.com
MIT License
2.71k stars 869 forks source link

Browsersync issue #1141

Closed matbathome closed 6 years ago

matbathome commented 6 years ago

I posted to gitter.im/olefredrik/FoundationPress yesterday but didn't get a response. I'm sure my issue is a newbie issue.

I created a Wordpress site on my computer. I loaded FoundationPress as a theme. I then did npm start in the terminal, which seemed to be working. I get this:

foundationpress@2.10.4 start /Users/mattbrown/Documents/Websites/www.icemelt.dev/wp-content/themes/FoundationPress gulp

[16:53:10] Requiring external module babel-register [16:53:12] Loading config file... [16:53:12] config.yml exists, loading config.yml [16:53:12] Using gulpfile ~/Documents/Websites/www.icemelt.dev/wp-content/themes/FoundationPress/gulpfile.babel.js [16:53:12] Starting 'default'... [16:53:12] Starting 'build'... [16:53:12] Starting 'clean'... [16:53:12] Finished 'clean' after 14 ms [16:53:12] Starting 'sass'... [16:53:15] Finished 'sass' after 2.39 s [16:53:15] Starting 'javascript'... [16:53:20] Version: webpack 2.7.0 Asset Size Chunks Chunk Names app.js 406 kB 0 [emitted] [big] app [16:53:20] Finished 'javascript' after 5.79 s [16:53:20] Starting 'images'... [16:53:21] Finished 'images' after 199 ms [16:53:21] Starting 'copy'... [16:53:21] Finished 'copy' after 50 ms [16:53:21] Finished 'build' after 8.45 s [16:53:21] Starting 'server'... [16:53:21] Finished 'server' after 51 ms [16:53:21] Starting 'watch'... [Browsersync] Proxying: http://localhost:3000 [Browsersync] Access URLs:

   Local: http://localhost:3000
External: http://192.168.55.129:3000

      UI: http://localhost:8080

UI External: http://192.168.55.129:8080

The issue is that Browsersync doesn't load a page.

I expected Browsersync to load a page.

The page just stays blank, and it looks like the page is trying to load, but nothing happens.

Please List the Following:

JPOak commented 6 years ago

@matbathome You need to put http://icemelt.dev or http://www.icemelt.dev in your config file.

matbathome commented 6 years ago

that fixed it.