Error: Attempted to load class "vmCustomPlugin" from the global namespace on

[Alexb65]

Hi all

Version svn 13-12-2023

When accessing any Joomla content (non VM page) we have the following error:

Attempted to load class "vmCustomPlugin" from the global namespace.
Did you forget a "use" statement?

Symfony\Component\ErrorHandler\Error\ ClassNotFoundError
in /var/www/virtual/bauoutlet.shop/web/plugins/vmcustom/specification/specification.php (line 23)

     * See /administrator/components/com_virtuemart/COPYRIGHT.php for copyright notices and details.
     *
     * http://virtuemart.org
     */
    class plgVmCustomSpecification extends vmCustomPlugin {

Disabling the three vmcustom plugins everything works fine

[vvasiakpl]

It seems like there might be an issue with the "vmCustomPlugin" class within the Joomla content. The error message indicates that there's a problem with loading this class from the global namespace.

The error suggests that there might be a missing "use" statement or an issue with the class itself. One way to troubleshoot this is to ensure that the "vmCustomPlugin" class is properly defined and accessible within the context where it's being used.

Here are some steps you might consider:

1. Check Namespace and Use Statements:
Ensure that the namespace and use statements are correctly set up in the file where the class `plgVmCustomSpecification` is defined.

2. Class Inclusion and File Path:
Double-check the file path and the inclusion of the file containing the `vmCustomPlugin` class. Ensure it's properly included or autoloaded in your Joomla setup.

3. Class Definition:
Verify the definition of the `vmCustomPlugin` class. It should be accessible and correctly defined within your Joomla environment.

4. Review Recent Changes:
Check if there have been recent updates or changes made to Joomla, VirtueMart, or any related plugins around the time this error started occurring. Sometimes, conflicts arise due to updates or changes in code.

5. Error Logs:
Review your error logs for any additional details. Sometimes, there might be additional information that could pinpoint the root cause more accurately.

6. Disable and Enable Plugins:
Since disabling the vmCustom plugins resolves the issue, you might want to re-enable them one at a time to identify which specific plugin is causing the conflict.