Captive Portal File Manager leaving broken symlinks
-
I'm using snapshot pfSense-2.1-RC0-2g-i386-nanobsd-20130630-0822.img.gz
Files uploaded with the Captive Portal File Manager are written to /var/db/cpelements/ and a symlink will be placed at /usr/local/captiveportal/
Deleting files via the Captive Portal File Manager will delete the file at /var/db/cpelements/, but not the symlink at /usr/local/captiveportal/, leaving a broken link
-
Should be fixed on newer snapshots.
Thank you for reporting. -
I'm having trouble with making changes to a second captive portal instance clobbering all the files in /var/db/cpelements but leaving all the symlinks in /usr/local/captiveportal.
Are there supposed to be different namespaces for each instance?
-
Hrm you using the same filenames?
-
No. When I bring up a second portal and save it. All the files in /var/db/cpelements that are not listed in the second portal's file manager are deleted, with the symlinks in /usr/local/captiveportal remaining. This appears to be fixed in the July 4 build. (Was using July 1).
-
Yeah i fixed the issues you mentioned just 2 days before.
For same filename you might have issues and i have to give a look for that.
