No Code Attached Yet bug
avatar Obscerno
Obscerno
11 Jan 2023

Steps to reproduce the issue

  • Set up a login menu item that is a different component from the home menu item.
  • Using the Edge browser, use an extension to add sec-gpc: 1 to headers.
  • Try logging in.

Expected result

You log in normally.

Actual result

You get the error:

0 - Invalid controller: name='user', format=''

System information (as much as possible)

Server:

  • Joomla 3.10
  • LAMP Stack
  • PHP 8.1.12
  • MariaDB 10.6.8

Browser

  • Windows 10 with Edge installed.
  • The user originally encountered the issue with the "Avast Online Security & Privacy" extension installed, but just the header is enough to cause the issue for me.

Additional comments

The issue seems to be that when the form is submitted, the home page menu item controller is used instead of the login menu item controller. That causes issues in getInstance() in BaseController.php, generating a non-existent file path and throwing that error.

I'm not sure whether you'll look at bugs for Joomla 3.10, but it might be worth looking into whether the problem exists for Joomla 4 too.

avatar Obscerno Obscerno - open - 11 Jan 2023
avatar Obscerno Obscerno - change - 11 Jan 2023
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 11 Jan 2023
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 11 Jan 2023
avatar Hackwar Hackwar - change - 23 Feb 2023
Labels Added: bug
avatar Hackwar Hackwar - labeled - 23 Feb 2023
avatar brianteeman
brianteeman - comment - 12 Jul 2023

That header is an experimental feature that is not supported by any of the supported browsers

https://caniuse.com/mdn-http_headers_sec-gpc

avatar alikon alikon - close - 12 Jul 2023
avatar alikon alikon - change - 12 Jul 2023
Status New Closed
Closed_Date 0000-00-00 00:00:00 2023-07-12 07:53:51
Closed_By alikon
avatar Obscerno
Obscerno - comment - 12 Jul 2023

Ah okay. It's unfortunate that users won't be able to log into a Joomla site with the Avast extension, but I suppose you can't support every extension. If it were up to me I'd uninstall it from everyone's browsers but I can't do that, or make them uninstall it either.

Add a Comment

Login with GitHub to post a comment