Read the statement by Michael Teeuw here.
http request
-
I’m using that code in php
$xml = simplexml_load_file('XML/status1.xml'); echo "<br>--------------<br>XML parsing <br>--------------<br>"; $result = array(); foreach($xml->children() as $child){ $result[$child->getName()] = trim($child);
-
have a look in here https://forum.magicmirror.builders/topic/240/soccer-standings i had also problems with cors so i used the request module in my node_helper to fix it
-
I copied the xml file on a synology web server, same behaviour status :0
-
Thanks @strawberry-3-141 - I’ll take a look and see if there are any changes I can make.
-
I took contact with the provider, he advices me to use x-device techno?
-
@acdacd2 said in http request:
some errors with nom install
pi@raspberrypi:~/MagicMirror/modules/default/MMM-HTTPRequestDisplay $ npm install
npm WARN enoent ENOENT: no such file or directory, open ‘/home/pi/MagicMirror/modules/package.json’
npm WARN enoent ENOENT: no such file or directory, open ‘/home/pi/MagicMirror/modules/node_modules/node_helper/package.json’
npm WARN modules No description
npm WARN modules No repository field.
npm WARN modules No README data
npm WARN modules No license field.I’m having this same error with a module… What am I doing wrong… any hints much appreciated
-
Does that module actually require an
'npm install'
to be run? Don’t blindly run commands that you don’t know are actually necessary. You need to ask the author of that module how to properly install it, what the steps are, what’s needed, etc., etc. I know nothing of that module.Edited to add: running an
'npm install'
is generally only required if the specific module needs any additional node dependencies installed. However, the author would make this known. If it doesn’t say that anywhere, do not assume you have to do it yourself. You may end up causing more harm to your installation than good. -
I’ve updated the ReadMe appropriately for this module, and this is available on the github page.
There are a few outstanding issues I need to address such as the calls to external domains (and a few other underlying issues), but I’m in the USA until the 6th of August and I won’t have time to address those issues until I return home.
Once the module is copied to the Modules folder, and the relevant config changes have been made, you shouldn’t need to “npm install” anything. You should simply be able to launch the MM software. No installations should be necessary. Be sure to read the Readme carefully, but if you can be more specific about the steps you have taken I can help you further.
-
Sorry. Wasn’t clear. I’m having this same issue with another module.
Am I correct that your http module isn’t working correctly yet?
Been trying to get it to work. Should solve a lot of my module needs. Home automation statuses and data from import.io.
Can’t wait 😃
Enjoy the holiday.
-
There appears to be a cross domain issue with the module. I’m currently travelling and I’m going to make it a top priority when I return to repair it. In addition, I have a very cool module upcoming :)
I’ll get the fix done as soon as I can guys. Sorry for the wait.
In the meantime if you have access to the server side clients of your request, please look into making requests accepted from any source as a temporary fix.