Not able to edit Weathermaps after upgrade to 0.98

[krislee]

Good afternoon,

I've run into a bit of problem after upgrading from Weathermaps 0.97a to 0.98 that I hope you can help with.

I'm not able to edit any existing maps in the online editor since the upgrade. When I go to the editor I can't see any of the existing maps to choose from. The maps are still running and updating fine and I can manually edit the text files in the \cacti\plugins\weathermap\configs\ folder.

Edit: - I can't create new maps or new maps based on existing maps. I can however, create a new map by using File Explorer and copy/pasting/renaming the 'simple.conf'. I can edit these new maps with the editor as they appear in the list.

I've searched the forum and checked the manual but I'm still stuck, so any help would be appreciated.

In case it helps, I'm running this on Windows XP and:

Cacti Version 0.8.8a
Cacti OS win32
SNMP Version NET-SNMP version: 5.5
RRDTool Version RRDTool 1.2.x

PHP Information
PHP Version 5.2.14
PHP OS WINNT
PHP uname Windows NT xxxxxxx 5.1 build 2600
PHP SNMP Installed
max_execution_time 30
memory_limit 128M

Regards,

Kris.

[Howie]

This sounds like file permissions. Can the user that runs your webserver create files in the configs directory?

(the editor should actually complain about the directory being read-only on the green file-picker screen, hopefully)

Oh, wait - are your files names *.conf? At some point relatively recently the editor was restricted to only load *.conf files as part of sanitising its input.

(YUUMMMM, so much ancient software! I hope it's not publicly available )

[krislee]

Hi Howie,

The web server is Apache and is on the same machine. I'll check on the rights the cacti user has for creating files, but there's no error message in the editor about read-only. I checked again and noticed that I can create a brand new file and one based on another map, as long as I specified the .conf as part of the file name! They appear in the list fine.

The filenames are all .conf.

I've actually worked round this by creating new files by hand in File Explorer and copying the configs from the old files to the new ones.

No, it's not public facing I'm a bit of a s/w numpty and when I've tried upgrading the various bits of software for Cacti in the past I've managed to break everything. I find that the support and documentation is more Linux orientated than Windows, so I've left it as it is . Looks like I 'll need to work it all out now that Cacti v1 is out...

I think I'm actually sorted with this for now, without actually solving the problem. Thanks for your help.

Cheers,

Kris.