Page 1 of 1

from Cumulus to CumulusMX: a comprehensive and complete guide is required

Posted: Sun 15 Sep 2019 9:54 am
by Simbor
Hi Guys,

Right now, I want to congratulate and thank those who, without any obligation or remuneration, have committed themselves in the past like now, to create and support this magnificent software. Times change and challenges continue to improve it and make it work better.
Since 2008, thanks to Steve and his Cumulus, I started recording and disseminating the weather data for my area.

With regret I had to change system: from a normal PC running all day to a raspy .... and this is causing me several problems, still partially unresolved.
I believe that, given the remarkable upgrade that MX offers, it is essential to have a clear and comprehensive guide to a typical installation.
If this is (or almost) for the raspy side, the same cannot be said for the server side.

After having done many tests without success, I purchased a web space instead of a free one, which served me for all these years without any problems. But evidently the problem was not even that.

Currently my server configuration is this:
Screenshot at Sep 15 11-17-51.png
Screenshot at Sep 15 11-18-41.png

I edited the graphSetting.php file:

Code: Select all

$GRAPH['jsonloc']        = '/meteo/';  // NOTE: This is the *server* operating system path to the file, so unless you have added
                                      // the web folder to your PHP path, it will be something like "/home/<userid>/www/"
$GRAPH['jpgraphloc']     = '/meteo/images/jpgraph/'; // NOTE: Same path type as json above
I edited the file:

Code: Select all


I edited the gauges.js file:

Code: Select all

imgPathURL        : 'meteo/images/',             //*** Change this to the relative path for your 'Trend' graph images
oldGauges         : 'meteo/gauges.htm',       //*** Change this to the relative path for your 'old' gauges page.

showPopupData     : true,                   //Pop-up data displayed
I edited the file at line 2266 about

Code: Select all

    function GetAndStream($aImage,$aCacheFileName) {
        if( $this->Isvalid($aCacheFileName) ) {
            return true;
        else {
            return false;
I put the files in the JSON folder ( into the images folder
(including the .htaccess file)
Screenshot at Sep 15 11-30-25.png

I have verified that the server is running GD.
Currently there is php 7.3.9

Now on (new web space)

I have tried various combinations of relative paths on file modifications; I tried (not knowing where to put it) to move all the files related to the JSON folder

the site runs, the weather data is visible and updated correctly.
- the graphs (trend.htm) there is no way to see them
- the gauges are not visible

Where am I doing wrong ????
It's driving me crazy.
:bash: :oops:

Reading several 3D, I realized that the biggest problem is precisely these two aspects.
for this reason, a guide or, at least, a typical server-side installation scheme and, possibly, the basic configurations (on interface: internet setting-> Web / FTP settings and Extra web files) necessary for the operation would be very helpful of graphics and gauges page.

Many thanks to those who want to give me help

Re: from Cumulus to CumulusMX: a comprehensive and complete guide is required

Posted: Sun 15 Sep 2019 2:51 pm
by water01
I can see both the gauges and the graphs.

Have you tried clearing the cache of your browser?

Re: from Cumulus to CumulusMX: a comprehensive and complete guide is required

Posted: Sun 15 Sep 2019 3:18 pm
by Simbor
Hi Water ...
no ... my stubbornness in trying to understand and try, has yielded something.
The LIB and JS folders were not in the right place.

What confused me for many days is that I didn't immediately understand that some passages described in the posts, were used to put different graphics and gauges.
 Considering the fact that I didn't see them on my site, I thought they were steps and changes to be made. Instead they are just modifications to MX, which alone works very well.

The fact remains that, in my opinion, we need a step-by-step guide that can provide guidelines, exhaustive and explanatory. A kind of 'typical installation', then those who feel it, can make improvements and changes.
I'm certainly not a programmer, but I understand something about code .... nevertheless, I got lost in a 'glass of water'.