FlashFXP Forums - 'Add ioFTPD Scripts' page problems

FlashFXP Forums (https://oss.azurewebsites.net/forum/)

- Suggestions and Feedback (https://oss.azurewebsites.net/forum/flashfxp/suggestions-and-feedback/)

- - 'Add ioFTPD Scripts' page problems (https://oss.azurewebsites.net/forum/flashfxp/suggestions-and-feedback/10291-add-ioftpd-scripts-page-problems.html)

'Add ioFTPD Scripts' page problems

Edit a script' file.
Add this as changelog:

Quote:

Added getnfo.php; clicking on any news in your RSS reader will load the NFO from that dir, if any.
Make sure you edit getnfo.php and change the UserId to use to open NFO files (I used '11').

Hit Update button.

Result:
Error: Invalid File Changelog.

1. Why is this changelog invalid ?
A more descriptive message would help.

2. The page presented with this error is the script details edit page, and not the file details edit page i was on before clicking 'Update'.

---

3. Sometimes, scripts' Long Descriptions are also rejected with a similar error.

Example:

Quote:

The script will deny the command if the user / group they\'re trying to see is not in any of their admingroup(s).

---

4. When creating a new script, when the Long Description or Changelog is invalid, the page that is presented contains extra slashes (\\ instead of \ in all fields, etc.) ...

5. ... and the following fields are missing the values previously entered:
'Categories' and 'Foundation'.
('File' is also missing, but that's normal.)

---

6. Files' Comments and Changelog should probably be allowed to be blank. 1 file & 1 version scripts don't really require a fle comment and a file changelog.

Also, on this page: https://secure.inicom.net/pages/en.i...cripts.php?s=4
DLs: 117 36 34 32 53 29 19 32 30 27 ...
This is either not ordered correctly, or presenting the wrong numbers.

Quote:

Originally Posted by Mouton

Result:
Error: Invalid File Changelog.

1. Why is this changelog invalid ?
A more descriptive message would help.

If the change log contains apostrophes (and perhaps other characters), it's considered "invalid". I guess it hasn't been fixed yet.

http://www.inicom.net/forum/showthread.php?t=15217

Thanks guys...keep the bug reports coming :) We'll get these fixed ASAP

Mouton, you are right, both issues are beign addressed and will be fixed on the new scripts engine that we will upload this upcoming week.

Thanks for the input.