AjaxControlToolKit AjaxFileUpload, upload files without an extension - ajaxcontroltoolkit

Using the AjaxControlToolKit AjaxFileUpload control (v18.1.1), how can I allow files without an extension to be uploaded?
Currently, any file without an extension throws an error. I know there is a default whitelist and the ability to add allowed extensions in the web.config, but it's not clear how to allow files without an extension.

As of v18.1.1, the AjaxFileUpload does not allow uploading of files without an extension in its current state.

Related

custom vscode extension not working over ssh

I created a vscode extension for the first time..I used LSP(language server protocol) and having both client and server bundled as one extension.
The extension has highlighting and autocomplete features for a custom file type. I packaged it using vsce I got a VSIX file. I installed the extension in my vscode using the .vsix file.
The extension works when i am working on local files.
However, i connected to a remote VM using the ms-vscode-remote.remote-ssh extension such that I can view the remote files in vscode, but here my created extension is not working. I can't even see the file type i created.
Any help is appreciated. Is there some specific setting I need to put in my package.json
For your extension to properly work remotely, either installed on host or on the remote, you have to follow a few guidelines, and yes, there are some settings that you may take care of on package.json.
The first and more complete source of information is Supporting Remote Development and GitHub Codespaces API documentation. It describes the architecture, settings, how to debug, common problems and so on. There is also the Extension Host page, where it describes the Preferred extension location topic, which tells you how to configure your extension to work on the correct location.
Based on your description (a LSP related extension) I understand your extension should be a Workspace Extension. This means that you should have this on your package.json:
"extensionKind": [
"workspace"
]
The Commons Problem section describes how you can evaluate and fix Incorrect execution location. To debug using SSH follow these instructions.
Also, remember that while working with remotes, you rely on local paths anymore. Instead you must always deal with Uri, whenever possible.
I guess after reviewing your settings, based on the docs related above, you should be able to detect what is happening on your extension and fix it. Give debug a try, it will be much easier to detect issues than installing the vsix and look for erros in Console.
Hope this helps

vscode extension development: svelte content not loading in webview after building the vscode extension

I am building a vscode extension by using svelte for webview. I am following https://youtu.be/a5DX5pQ9p5M. But the deployment of extension is not mentioned in the tutorial .
So i am following https://code.visualstudio.com/api/working-with-extensions/publishing-extension.
So after packaging the extension with vsce package and installing the extension the extension doesn't load svelte content but when running in developer mode everything works fine.
I tried creating the package extension multiple Times but still didn't work.
Check if all necessarily files are included via:
vsce ls
(You can also open packaged extensions, they are just ZIP-archives with a different extension.)
If they are not (e.g. src is excluded by default), you probably can create a .vscodeignore file and manually specify what to exclude.
Running extension problems can be inspected via Help > Toggle Developer Tools, usually you will find some errors in the console.
I do not know if debugging forces the extension to load, but if so, make sure you have set the correct activationEvents.

How do I prevent the .dccache file from being created?

vscode keeps adding a file named .dccache. How can I prevent this?
It messes up the github diffs and I keep on having to add .dccache to the .gitignore for several different projects.
I can't find anything about why .dccache is being created in the first place
It can also be created by the Snyk extension.
I have the same file, I believe this is being created from DeepCode: https://www.deepcode.ai/
This is a code analysis tool to try to find issues. Check if you installed the DeepCode extension in VSCode if you want to get rid of this file, otherwise ignoring it should be fine.
The DeepCode plugins or the CLI is using this file to create a cache for the source code bundles send to the analysis engine. Without this cache, the collection and upload would be very time-consuming.
As it only serves as a caching mechanism, you can exclude it from git uploads and ignore it otherwise.
Snyk extention has a Help&Feedback tab, on the FAQ there is a 'Add custom .dcignore file to your workspace'.
Sometimes git ignore doesn't work for me
I used this file: https://github.com/DeepCodeAI/dcignore/blob/master/full.dcignore.js
just create .dcignore and copy all contents to that. I manually add .dccache and .dcignore just in case.
I had the same issue and when I disabled Snyk extension on VS code editor is disappeared, if you don't have Snyk installed and still have .dccache appearing every now and them, just keep an eye on the other extensions, disable each one at a time and see which one is creating the .dccache file

TYPO3 form - Editing of form.yaml files not possible in the backend

I need to edit the configuration files of the TYPO3 form extension on the webserver. As I have no access via FTP I need to edit the files in the TYPO3 backend. The problem is, I am not allowed to edit files with the extension .form.yaml.
In the install tool I added
[SYS][textfile_ext] = txt,html,htm,css,inc,php,php3,tmpl,js,sql,yaml,form.yaml,form
Now I can edit files with the extension yaml but no files with the extension form.yaml
Is there another configuration option I have to set to be able to edit the form.yaml files?
Is it possible to change the standard extension of my configuration files from .form.yaml to .yaml?
I am using TYPO3 8.7.30 and form 8.7.30.
As Bernd already said, since TYPO3 8 editing of .form.yaml files is not allowed in the backend for security reasons.
I wanted the editing to allow backend users the definition of different upload folders.
But different upload folders can also be defined in the central .yamlconfiguration file (TYPO3 8 form - Define several file upload folders).
So there is no need to enable editing of .form.yaml files for backend users.

TYPO3 Extension: I changed my extension folder name and now TYPO3 throws an error message

So today my extension_builder overwrote my entire TCAs while saving, so I did something stupid: I changed the folder name of my extension via winscp and uploaded the backupfolder of my extension I made yesterday. Now I get the error message
Oops, an error occurred!
TYPO3 Fatal Error: Extension key "icingaconfgen" is NOT loaded!
I know the error could be fixed with changing the state of the extension in the PackageStates.php to inactive, but the problem is: The extension doesn't appear in this file. Interesting enough the foldername I changed my old old extension folder to ("x") appears in the file as inactive though. What should I do now?
I assume you meant the extension key. This key is used in differnt files of an extension.
If you rename an extension folder the old key still is used in some files. TYPO3 analyses all extensions and joined (active) parts into cached files, so be careful as what is active executed and what is stored on the disk can differ (always clear all caches - there are a lot of caches!)
One part of your problem may occur of two folders with the usage of the same extension key. here especially the foder you renamed, as there the foldername and the internal extension key do not match.
TLDR:
NEVER rename an extension folder inside of typo3conf/ext/.
If you want to backup an extension move it to e.g. typo3conf/ext.bak/.
Always clear all caches after such a manipulation. (With newer versions of TYPO3 it is at least typo3temp/Cache/Code/, but also have a look at typo3temp/autoload/ and the internal caches tables in the database.)
If there is no non-existent extension listed in your PackageStates.php you should be fine after clearing TYPO3s cache.
Go to the install tool and do it under "important actions".
Or remove the contents of the typo3temp folder.