URL Rewrites are not generated after product import - magento2

I am trying to import products into my store however the rewrites are not generated in the database at all so the long default url remains. Anyone faced this issue and solved it before without using an external module?
The URL key is correctly set at the product page.
incorrect url

You can use faonni module indexer which will create URL rewrite for your products category and cms pages.
After installing the extension you can run indexer commands as follows.
php bin/magento indexer:reindex category_url_rewrite
php bin/magento indexer:reindex product_url_rewrite
php bin/magento indexer:reindex cms_page_url_rewrite

The issue is with the importer. When there are no images available however they are defined in the feed file the importer will stop processing further information. For example it won't create the rewrites in the database and won't process stock related information. Won't create the relevant stock related records in the database neither. Database tables impacted ( the ones I actually found so far ):
url_rewrite
cataloginventory_stock_status
cataloginventory_stock_item

Related

TYPO3 DDEV installation upload to server

I have a local ddev based TYPO3 site. If I want to upload it on my apache server there is some path issues with the resource files like JS,CSS and images.
This is the path for the css file on my local server... this works perfect:
typo3conf/ext/sitepackage/Resources/Public/Dist/Css/main.css
On my apache server following path gives a 404 error
/typo3conf/ext/sitepackage/Resources/Public/Dist/Css/main.css
Is there a way to change the base path of the production environment?
This article describes your issue probably.
The main issue if you want to keep the old structure is to use
"typo3/cms-composer-installers": "^2.0 || ^3.0"
without version 4.
Else the whole structure is created differently.
Nevertheless you might be able to repair the current state by using paths like this:
EXT:sitepackage/...
as soon as you use typo3conf/ext directly it won't work.
Certainly you could create symlinks but that's likely not the best approach.

Magento 2 cannot delete module bceause ClassReader.php class not found

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";

TYPO3 Service Unavailable (503)

I installed a copy of a TYPO3 project. So, I'm using an existing TYPO3 database.
When running the home page of the site, I get the 'standard error':
Service Unavailable (503)
The page is not configured! [type=0][]. This means that there is no TypoScript object of type PAGE with typeNum=0 configured.
More information regarding this error might be available online.
which refers to following site: https://wiki.typo3.org/Exception/CMS/1294587217
But when I modify the setup of the template of the root as given in the link. I get an empty page with "HELLO WORLD" and the whole website is gone.
The old root setup code was:
config.contentObjectExceptionHandler = 0
page.meta.description.data = page:description
page.meta.keywords.data = page:keywords
How can I solve this problem without losing the rest of the website? Using TYPO3 8.7
Addition to the db install I also copied the extension folders to the typo3conf/ext folder and edited the PackageStates.php with the path to the extensions.
I see the extensions in the extensions tab the status is 'local'.
1st: make sure you have the correct configuration of all domains (as it is a copy it can not run with the same domain, otherwise you will switch between servers unpredictably.
2nd: enter list mode and look for multiple template records in your web root page. Multiple records will result in ignoring all but one record. maybe you just edit the wrong one. Normally the content is not lost but only inaccessible for the moment.
3rd: have you activated all the extensions which are active in the source installation? especially any site extension, which probably include the configuration for the TypoScript page object.
4th: you can use the TSOB (TypoScript Object Browser) and the template analyzer to view the active or resulting typoscript.

Unable to get content for 'frontend/Magento/blank/en_US/css/source/lib/_lib.less'

When I compile static with php bin/magento setup:static-content:deploy, I'm getting the following errors:
Unable to get content for 'frontend/Magento/blank/en_US/css/source/lib/_lib.less'
Unable to get content for 'frontend/Magento/luma/en_US/css/source/lib/_lib.less'
I was also facing the same issue. Then I went through the comments from different people on GitHub here. After that I was able to fix by recovering the folder "lib/web/css" or whole "lib/web" under root directory.
Lastly run the command and there was no error :
bin/magento setup:static-content:deploy en_US -f
Based on your setup version you can take it from here : https://github.com/magento/magento2/tree/2.3/lib
Your Magento probably was poorly updated, you might be able to fix it by getting a new composer installation in the same version and replacing your lib folder with a clean lib folder from the native installation.

In Magento after installing extension Admin panel in unable to load

As I have assigned to work on magento, according to our requirement i tried to install Arabic extension for magento. The extension got successfully installed. Later on refreshing the admin panel, it shows the URL not found. The Stores FrontEnd CMS home page is loading, But when Iclick on any products, it shows again URL not found..
How can i solve this...
When diagnosing things like this, try the following..
Delete (or move to another folder) files in /var/www/var/cache
Delete (or move to another folder) files in /tmp
From a shell, run
/var/www/shell$ php indexer.php --reindexall
You've just manually cleared your caches and re indexed your data.
See if your system comes back to life.
For me I was redirected to wrong URL from MagentoConnect after installation of extension.
My admin URL: <-hostname->/index.php/admin
Redirected To: <-hostname->/admin
I had same issue when I added extension manually. I could find the issue when checked via shell command and it returned missing table error. This is issue happened when I installed module manually.