[PHP] Auto-adding asterisks not working on Enter

[mbomb007]

I see you said the issue is fixed in #1, however, I still have the issue. When I press Enter while in a block comment, no asterisk is added at the start of the new line.

I tried with auto-comment-blocks.singleLineBlockOnEnter set to both true and false. Neither works.

If you can't reproduce the issue, let me know, and I can provide more environment information.

[yCodeTech]

@mbomb007 As I see you've come directly from kevb34ns#40, could you please confirm that the extension by kevb34ns has been uninstalled (or at the very least disabled).

Also is there any errors in the "Window" or "Extension Host" channels in the Output panel? (Use the find/replace feature of the output panel to find all occurrences of ycodetech.)

I'll try reproduce the issue tomorrow, though I have been using it without a problem in my other PHP projects this week. So it could be a potential clash with another extension.

Could you also provide a list of installed/enabled extensions, then I can rule out extension clashes while I'm testing.

[mbomb007]

@mbomb007 As I see you've come directly from kevb34ns#40, could you please confirm that the extension by kevb34ns has been uninstalled (or at the very least disabled).

Yes, I got rid of the other extension first, then restarted Code and installed yours.

Also is there any errors in the "Window" or "Extension Host" channels in the Output panel? (Use the find/replace feature of the output panel to find all occurrences of ycodetech.)

There are no errors. I'm using VS Code with WSL2, so your extension is installed in WSL (Ubuntu). The only item in the Extension Host (Remote) channel for your extension was a startup message:

2025-06-13 08:08:48.631 [info] ExtensionService#_doActivateExtension ycodetech.automatic-comment-blocks, startup: false, activationEvent: 'onLanguage'

I'll try reproduce the issue tomorrow, though I have been using it without a problem in my other PHP projects this week. So it could be a potential clash with another extension.

Could you also provide a list of installed/enabled extensions, then I can rule out extension clashes while I'm testing.

Local

If it isn't followed with (enabled), it's just installed.

alefragnani.bookmarks (enabled)
bmewburn.vscode-intelephense-client
csstools.postcss (enabled)
dbaeumer.vscode-eslint
dmitrydorofeev.empty-indent
eamodio.gitlens
editorconfig.editorconfig
gruntfuggly.todo-tree
m-ender.retinate
ms-vscode-remote.remote-wsl (enabled)
neilbrayfield.php-docblocker (enabled)
owenfarrell.vscode-microtask
sibiraj-s.vscode-scss-formatter
whatwedo.twig (enabled)
xdebug.php-debug

WSL Ubuntu

If it isn't followed with (disabled), it's enabled.

bmewburn.vscode-intelephense-client
dbaeumer.vscode-eslint
dmitrydorofeev.empty-indent
eamodio.gitlens
editorconfig.editorconfig
gruntfuggly.todo-tree
m-ender.retinate
ms-azuretools.vscode-containers
neilbrayfield.php-docblocker
owenfarrell.vscode-microtask (disabled)
sibiraj-s.vscode-scss-formatter
valeryanm.vscode-phpsab
xdebug.php-debug
ycodetech.automatic-comment-blocks

[yCodeTech]

@mbomb007 My tests have concluded that it's working as it should, with all my extensions disabled too in the extension test environment. Copilot assures me there is no Windows-specific code in the extension:

The extension should work identically in WSL2 Ubuntu as it does on Windows, as long as you run it in VS Code (or VS Code Remote - WSL).

So I know it can't be a Linux compatibility issue.

For further debugging, could you please update the extension to the new latest v1.1.7. This update adds a logger to help debugging.

After updating and restarting the extensions, could you share the entire log output from the Auto Comment Blocks channel in the Output panel. Making sure that you also have a PHP file open so that the extension knows to use PHP language configs.

The output will be massive, as it also goes through each installed language configs. It might be easier to use the Save Output As button in the panel's three-dot settings, and then upload the file here.

Also I assume you've recently disabled all extensions except this one, and tried using it?

[mbomb007]

Also I assume you've recently disabled all extensions except this one, and tried using it?

Yes, it didn't work.
Log file has been removed

[yCodeTech]

@mbomb007 Hmm from the log, it looks like the extension couldn't find many language config files, including PHP. so that's why there is no PHP support, since it's now automatic support as long as there is a language file provided by an extension. However, it seems the extension is only getting the installed extensions on WSL2 server. I don't use WSL2 so I can't test its integration.

As yet, I have no idea how to get all installed extensions from WSL2 and Windows. The implementation uses the VScode API, to get the extensions, but clearly it doesn't work cross Windows and WSL2.

However, for this exact purpose, I've already provided a setting in this extension: auto-comment-blocks.multiLineStyleBlocks to add language IDs to enable multi-line comment blocks support for that language, allowing unsupported languages to have comment completion. Please add php to this custom list (which also includes html and blade by default) in your settings. The comment blocks should now work on enter. This also goes for any other "unsupported" languages.

[yCodeTech]

Closing as won't fix, since it's a limitation with the VScode API. If you know of a way to access all extensions (and their language configs) located on the Windows drive from WSL2 (or vice-versa), a PR is always welcome.

[mbomb007]

I added "php" to the list and it still doesn't work.

[mbomb007]

Closing as won't fix, since it's a limitation with the VScode API. If you know of a way to access all extensions (and their language configs) located on the Windows drive from WSL2 (or vice-versa), a PR is always welcome.

The C:\ drive is mounted at /mnt/c if on WSL, so if you know the path on Windows, you can get to it via the mounted drive.

The mount is probably not guaranteed to exist, though.