Hello,

from the error message it sounds like you cannot use unencrypted FTP, but need to use FTPS or FTPES.

The server administrator or hosting provider should know more.

You're right, Cmd-E should also show the search field.

Did you also press Cmd-F to show the search field?

You can use Edit -> Find -> Use Selection for Find (Cmd-E) to use the selected text for search.

This behavior is not a bug in Textastic, but a limitation of iOS. It is documented in the manual at https://www.textasticapp.com/v7/manual/integration_other_apps/external_files_folders.html

"Opening external folders only works when the files and folders are stored locally on the device. This is typically true for Git clients and the “On my iPad/iPhone” location, but also for apps like Documents by Readdle.

It does not work when folders are stored in the cloud. For cloud providers like iCloud Drive or Microsoft OneDrive, you can only open individual files, not folders."

Note: A future update of Textastic will add support for adding external iCloud Drive folders. 

Hello,

you need to make sure that you use type="module" in the script tag in the html file, like this:

<script src="file2.js" type="module"></script>

Also, it should probably be 

import sum from "./file1.js"; 

in the first line of file2.js.

Thanks for the video! I'll look into it.

I'm aware of a crash that happens to some users when restoring the application state on macOS 10.13.6. It does not seem to happen on 10.14 Mojave.

Please try the following to fix the problem:

• Go to Finder
• Select Go -> Go to Folder…
• Enter "~/Library/Containers/com.textasticapp.textastic-mac/Data/Library/" and press Go
• Delete the folder "Saved Application State"
• Try to launch Textastic

If that doesn't help, you can also try to delete the folder "~/Library/Containers/com.textasticapp.textastic-mac" which will remove all preferences, saved application state, custom syntax definitions, themes and templates. It won't delete your documents.

I'm really sorry for the inconvenience. I'm still trying to figure out what exactly is causing the crash.

Currently not, but I'm actively working on adding this feature in the next major version of Textastic which is going to be a free update for existing users.