Dador wrote: ↑Sat 11 Nov 2023 1:20 pm
I started using custom logs 2 days ago. It went relatively smoothly, but since then I haven't had any charts. I thought maybe there had to be a minimum amount of time for this to happen (for me it was 48 hours), but I was checking the website for the code today and the browser prompted
Code: Select all
Failed to load resource: https://pogodarybnik.pl/customlogsRecentdata.json? the server responded with a status of 404 ()
From this I understand that the module is looking for the customlogsRecentdata.json file in the main directory, but I have all the cutils files in the /CU directory. My path should look like this:
Code: Select all
https://pogodarybnik.pl/CU/customlogsRecentdata.json?
Would adding
Code: Select all
cumulusutils.ini -> CustomLogs -> FTPDirectory=
solve the problem?
Great you use the CustomLogs module
OK, your datafile is in the CU directory (I checked). Apparently you defined that as the uploading directory for the CUtils modules but you run the modules from one level up: your webroot is
https://pogodarybnik.pl/ this separation of modules and website directory has never been done before: the CUtils files should be in the webroot. I assume you don't want that but I ask you: would that really be an issue?
What we now have is a
'kind of inverse use' of
CumulusRealTimeLocation (which is used if the CMX datafiles are outside the CUtils directory structure). If you wish to stay with the CU directory for the modules, I'll have to think on how to deal with this.
The issue can now only be solved by moving all files to the webroot and run from there (effectively removing CU from the path)
Your suggested solution for adding another directory may work but through another parameter specifically for module use.