When viewing pages on my production site, I noticed that, although the page loaded, the browser was stuck on "Waiting..." or equivalent message.

Switching on some debug, e.g. in FireFox, the Network option of its in-browser Developer, I observed that livereload.js was the last thing that the browser attempted to load, but that its source URL was my local dev, not the URL of the production machine.

Note, at the moment I am not using livereload.js at all, I do not have the module enabled. The livereload.js file comes with the omega theme as I understand it. My assumption is that livereload is optional.

I have been developing the site on my local development environment, inside a VM, provisioned using Vagrant, the Vagrant scripts I'm using are: https://github.com/mikebell/drupaldev-apache
Here, a local address is setup for the site, e.g. site.drupal.dev

I'm going to investigate the mechanisms by which the .info file appeared to have been auto-edited by machine to have a reference to livereload.js locally.

However, I thought I'd post a quick initial note here in case others are having a similar issue, so they know that someone is looking into it. Indeed if you know of this issue and know something about cause and perhaps solution, this would be most welcome, for example, is there something wrong that I am doing here?

Comments

fubhy’s picture

fubhy CreditAttribution: fubhy commented
Status: Active » Fixed

If you don't use livereload, you should disable it in the Development settings.

This is *completely* unrelated to the LiveReload module hosted on drupal.org (in case you were referring to that) because it's part of Omega and whatever you would use to start the livereload daemon (Guard, Grunt, whatever).

If you don't use it at all, just go to the settings and disable it there... However, even if you don't disable it it should not cause *any* problems because in that case all that happens is that the file won't be loaded (because there is no daemon serving it).

therobyouknow’s picture

therobyouknow CreditAttribution: therobyouknow commented

Hi fubhy! Thanks for the advice about disabling livereload in the omega development settings.

I checked and I have the livereload setting currently enabled in admin/appearance/settings/myomegasubtheme

I will turn this off and see if what outcome this has related to my problem.

Is it normal for the .info file for the sub theme to be 'edited' by the code itself to refer to livereload.js
(as said I saw that an entry for a local copy of livereload.js (on my local dev) had appeared in the .info file)

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.