Magento 2.3.3
I have the module Swissup/Core installed. I had some problems and removed it. After I removed the module, (deleted from composer directory) I can no longer use Magento 2. I get the following when trying to run any commands.
Updating modules:
Class Swissup\Core\Console\Command\ModuleCommand does not exist
In ClassReader.php line 19:
Class Swissup\Core\Console\Command\ModuleCommand does not exist
I checked and there is no attribute created by this module. I checked source_model, frontend_model, backend_model.
I removed all references to the module in composer.json, composer.lock.
I removed all references to it in composer files in vendor directory.
I removed cache, pub/static, generated, and var/cache.
I also did a recursive search across the entire site for any file containing the word swissup or Swissup. None were found.
I also removed the module from the setup table.
I also checked/removed any reference in core_config_data
Still, I cannot use the system and this error persists.
I cleared all composer cache
I also as a test, put invalid credentials in app/etc/env.php to see if the database would cause an issue, but it didn't, I still get this error.
I don't understand, how, if i'm sure by doing a grep in every file a part of Magento and no such reference exists, that this error is raised. There must be some file stored outside of the Magento filesystem. It cannot be a database issue, because the database cannot connect due to me inputting invalid values.
I highly recommend you delete Modules by first running bin/magento module:disable Vendor_Namespace followed by composer remove vendor/package instead of deleting it in the file system.
Do you have a git repository on which you can reset? Does composer install generate any errors?
This can happen if there is the module entry in the setup_module table.
If the module you want to delete is Vendor_Module, then search for the module in setup_module table:
SELECT * FROM setup_module WHERE module = "Vendor_Module";
If you find the module in setup_module table, then you need to remove that from the table:
DELETE FROM setup_module WHERE module = "Vendor_Module";
Related
Using data patch, created one product attribute. I wants to remove that attribute when extension is unstalled. Generally we are using Uninstall.php but my question was that, how can we uninstall it by using data patch?
Thanks in advance.
Create Uninstall. php inside setup directory from module directory.
write your logic over there to remove the attribute.
so when you will run
bin/ magento module:uninstall [MODULE NAME]
then your Uninstall script will run and code will be executed.
After I instaled extension in typo 3 version 4.5 I can't log in to backend, my page is blank and after I try to go on http://mydomain/typo3/install/index.php I get this message :
The Install Tool is locked.
Fix: Create a file typo3conf/ENABLE_INSTALL_TOOL
This file may simply be empty.
For security reasons, it is highly recommended to rename
or delete the file after the operation is finished.
If the file is older than 1 hour TYPO3 has automatically
deleted it, so it needs to be created again.
Installing any extensions in such an old TYPO3 probably will kill your installation, as any modern extension is incompatible to the old sources.
Modern extensions have namespaces, autoloader, use API classes and functions unknown to the old installation, maybe even use PHP7 features unknown to the old PHP which is needed to run those old TYPO3.
now for your cleanup:
For entering the instal-tool do as the message indicates:
create/update that file and then you can enter the install tool.
but in 4.5 you will not get much help to get the system running again.
you must disable the malicious extension:
in the file typo3conf/localconf.php you need to delete the extension key from the list of installed (active) extension. For this you can use any editor. One is build in the InstallTool.
After that you need to remove the cached version of the localconf.php: remove the temp* files in the folder typo3conf/.
Now your system should work again (but still might be unclean).
you should remove the extension (typo3conf/ext/extensionkey).
Maybe there are new tables and fields in the database. Therefore do a database compare in the InstallTool.
I want to intstall the ext "my_redirects". On my local machine it does what it should. But now, on the live site, i got this error:
1: PHP Warning: file_get_contents(/kunden/homepages/28/d574274134/htdocs/update7/typo3/sysext/core/Resources/Private/Sql/Cache/Backend/Typo3DatabaseBackendCache.sql): failed to open stream: No such file or directory in /homepages/28/d574274134/htdocs/update7/typo3_src-7.6.14/typo3/sysext/core/Classes/Cache/Backend/Typo3DatabaseBackend.php line 441
I got a hint to delete the typo3temp/autoload/ files. Then the installation works, but if i after that go into the install tool, i get this error again. Can someone give a hint?
This file is part of the core and must exist. Look into the src-tar/zip file. Maybe the file wasn't transferred to the server.
I don't think it's an autoload issue, because the .sql file is missing, not the PHP class.
Please verify that the sql file does exist. If it's missing, check the hash of your downloaded TYPO3 core. Make sure you compare the correct path on the server.
But I guess you got an access restriction. Maybe bad ownhership of that .sql file? Perhaps you ran into some security problems with file_get_contents() and at least sql files? So please also check your security settings.
I updated an installer file (.ism) for major upgrade in which I made the following changes:
updated product code,
updated package code,
updated versionmin and max in upgrade,
updated product version,
few strings in which old version was mentioned.
Now when I am upgrading my product using this setup, few files get removed automatically.
I did not make any changes in those files in target machine and the same files (no change in content) are in my new setup.
Also I did not add any entry in "RemoveFiles" table to remove them.
Also checked the installation log in which I am just seeing this:
Action 14:14:59: RemoveFiles. Removing files
RemoveFiles: File: CapibilityDemo.htm, Directory: C:\Program Files\Server\Printing\
RemoveFiles: File: HTTP.js, Directory: C:\Program Files\Server\Scripts\OpenLayers\lib\OpenLayers\Protocol\
RemoveFiles: File: Script.js, Directory: C:\Program
Files\Server\Scripts\OpenLayers\lib\OpenLayers\Protocol\
Can anyone please help me in resolving this issue ?
Thanks
Taran
Dynamic components are probably the problem.
This link is someone who was having a similar problem while patching (which is like a minor update)
Basically what is happening is that MSI has determined that the 'old' components have been removed (since they are dynamically generated, the GUIDs change every build). So in your upgrade it is removing the components you 'removed'. However it isn't laying down the new components, likely because it has determined there isn't a need for it to do so. You should examine your MSI file in Orca and look for the files/components that didn't get installed in your upgrade, and then search the install log for that GUID. That should give you a clue as to the next steps.
Also, here is the installshield best practice recommendations for Dynamic file linking.
I created a VOB and a snapshot view that loads it. The VOB is empty and I wanted to add some files to initialize it, but I got errors for all files that I wanted to import. Here is the details.
The VOB is created by this command:
ct mkvob -tag /vobs/sqlite -comment "testing VOB for Sqlite" -public /var/clearcase/vobs/sqlite.vbs
The view is created by this command:
ct mkview -tag sqlite-dev -snapshot /home/clearcase/working/sqlite-dev
The config spec is:
element * CHECKEDOUT
element * /main/LATEST
load /vobs/sqlite
I checked out the "vobs/sqlite".
In the view directory /home/clearcase/working/sqlite-dev, I run clearfsimport to import some files:
clearfsimport -rec /home/clearcase/tmp/sqlite-3.6.23.1/* vobs/sqlite
But I got errors for all files and directories. Fore example, for the file "VERSIONS", I saw errors like:
Creating element "vobs/sqlite/VERSION".
clearfsimport: Error: Unable to lookup "VERSION" in "/vobs/sqlite##/main/CHECKEDOUT": no version selected in configuration specification.
clearfsimport: Error: Unable to access "/vobs/sqlite/VERSION": no version selected in configuration specification.
clearfsimport: Warning: Trouble updating name "VERSION" in snapshot view: error detected by ClearCase subsystem.
A separate update may need to be performed in order to reflect the results of the operation in the snapshot view.
clearfsimport: Warning: Unable to check if new version of "vobs/sqlite/VERSION" is identical.
clearfsimport: Warning: Element "vobs/sqlite/VERSION" is no longer being loaded and will not be updated as part of this operation.
version "/main/1".
Can anybody please point out what I did wrong here? Should I change the config spec somehow?
Updates after I tried VonC's answer.
Thanks for the response. I tried to run clearfsimport again and I saw some different errors:
Validating directory "/home/clearcase/working/sqlite-dev/vobs/sqlite/tool".
clearfsimport: Error: Cannot checkout a directory when directory doesn't exist in the snapshot view.
clearfsimport: Error: Could not checkout directory "/home/clearcase/working/sqlite-dev/vobs/sqlite/tool".
Validating element "/home/clearcase/working/sqlite-dev/vobs/sqlite/VERSION".
clearfsimport: Error: Could not access "/home/clearcase/working/sqlite-dev/vobs/sqlite/VERSION".
clearfsimport: Warning: Trouble importing element "/home/clearcase/working/sqlite-dev/vobs/sqlite/VERSION".
tool is a directory and VERSION is a file. The same error happens to all files/directories.
The CC is installed on Linux, so I cannot try the ClearCase explorer.
I tried the full path but I saw the same errors.
I am running these command as root, I guess "-nset" won't help. I tried adding it but still saw the same error.
Are there other ways to add files if I only want to add them once?
Try the clearfsimport without checkouting the vob first.
Try adding a file to the vob through the ClearCase explorer (just to see if it works)
Try specifying the full path of the vob when clearfsimporting: /home/clearcase/working/sqlite-dev/vobs/sqlite
Note: you can also use a dynamic view for this kind of operation (that avoid any "update view" error regarding the workspace, since a dynamic view has no need to update its -- network managed -- workspace)
See also "How can I use ClearCase to “add to source control …” recursively?" for more on the clearfsimport options: the '-nset' option might also be needed here.