magento2.3 – Sorry, something went wrong. You can find out more in the error log

magento2.3 – Sorry, something went wrong. You can find out more in the error log – Magento Stack Exchange

magento2.3 – 2. Assigning multiple drop ship vendors for a single SKU in Magento 2.4.2

  1. Assigning multiple drop ship vendors for a single SKU:

What would be best way to have an item record store “Drop Ship Vendor Information” for that specific SKU or SKU Variant (i.e. product comes in two sizes: small and large. Size Small via drop ship supplier 1 and size large via drop ship supplier 2). In addition, we will connect to the drop ship vendors via EDI to obtain up-to-date costs and QTY Available (aka stock availability).

For instance, each SKU should have an option to add a minimum of 4 drop ship vendors:

Vendor 1 Name Vendor 1 SKU Vendor 1 Cost Vender 1 QTY Available

Vendor 2 Name Vendor 2 SKU Vendor 2 Cost Vender 2 QTY Available

Vendor 3 Name Vendor 3 SKU Vendor 3 Cost Vender 3 QTY Available

Vendor 4 Name Vendor 4 SKU Vendor 4 Cost Vender 4 QTY Available

This way, our system and our customer service agents are able to know which vendor or vendors have this item. I need to have this info on the Magento item record since my CS agents won’t have to our ERP system.

This is how it’s done now with our NetSuite ERP (from the item record):

NOTE: Not all Drop Ship vendors use the same SKU (Code) for the same exact item, therefore, it’s important to have SKU for each vendor.

Any suggestions, please?

magento2.3 – Composer can’t install any module due to “Your requirements could not be resolved to an installable set of packages”

Running 2.3.6
When I try to install any module via composer I get the following error:

 ()$ COMPOSER_MEMORY_LIMIT=-1 composer require stripe/stripe-php:^7
Warning from https://repo.packagist.org: You are using an outdated version of Composer. Composer 2 is now available and you should upgrade. See https://getcomposer.org/2
./composer.json has been updated
Loading composer repositories with package information
Warning from https://repo.packagist.org: You are using an outdated version of Composer. Composer 2 is now available and you should upgrade. See https://getcomposer.org/2
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: remove magento/product-community-edition 2.3.6
    - Conclusion: don't install magento/product-community-edition 2.3.6
    - Installation request for magento/product-community-edition 2.3.6 -> satisfiable by magento/product-community-edition(2.3.6).
    - Installation request for veriteworks/cookiefix ^3.0 -> satisfiable by veriteworks/cookiefix(3.0.0).
    - Conclusion: don't install magento/framework 102.0.6-p1
    - magento/product-community-edition 2.3.6 requires laminas/laminas-code ~3.3.0 -> satisfiable by laminas/laminas-code(3.3.2, 3.3.0, 3.3.1).
    - Can only install one of: laminas/laminas-code(3.4.1, 3.3.0).
    - Can only install one of: laminas/laminas-code(3.4.1, 3.3.1).
    - Can only install one of: laminas/laminas-code(3.4.1, 3.3.2).
    - Can only install one of: laminas/laminas-code(3.4.1, 3.3.2).
    - Can only install one of: laminas/laminas-code(3.4.1, 3.3.2).
    - Conclusion: install magento/framework 102.0.6-p1|install laminas/laminas-code 3.4.1


Installation failed, reverting ./composer.json to its original content.

What is composer telling me to do?

Is it possible i made a mess since few days ago (before that I think
everything was working fine) and then I launched “composer
dump-autoload -o” for some reason?

Edit:
i ran same command and got different error

     composer require stripe/stripe-php:^7
The "magento/magento-composer-installer" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
The "dealerdirect/phpcodesniffer-composer-installer" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
The "magento/inventory-composer-installer" plugin was skipped because it requires a Plugin API version ("^1.1") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
The "laminas/laminas-dependency-plugin" plugin was skipped because it requires a Plugin API version ("^1.1") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
The "magento/composer-root-update-plugin" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
./composer.json has been updated
The "magento/magento-composer-installer" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
The "dealerdirect/phpcodesniffer-composer-installer" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
The "magento/inventory-composer-installer" plugin was skipped because it requires a Plugin API version ("^1.1") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
The "laminas/laminas-dependency-plugin" plugin was skipped because it requires a Plugin API version ("^1.1") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
The "magento/composer-root-update-plugin" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
Running composer update stripe/stripe-php
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - magento/composer-root-update-plugin is locked to version 1.0.0 and an update of this package was not requested.
    - magento/composer-root-update-plugin 1.0.0 requires composer-plugin-api ^1.0 -> found composer-plugin-api(2.0.0) but it does not match the constraint.
  Problem 2
    - Root composer.json requires veriteworks/cookiefix ^3.0 -> satisfiable by veriteworks/cookiefix(3.0.0).
    - veriteworks/cookiefix 3.0.0 requires magento/framework ~102.0.6-p1||~103.0.1 -> found magento/framework(102.0.6-p1, 103.0.1, 103.0.1-p1, 103.0.2) but the package is fixed to 102.0.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
  Problem 3
    - dealerdirect/phpcodesniffer-composer-installer is locked to version v0.5.0 and an update of this package was not requested.
    - dealerdirect/phpcodesniffer-composer-installer v0.5.0 requires composer-plugin-api ^1.0 -> found composer-plugin-api(2.0.0) but it does not match the constraint.
  Problem 4
    - laminas/laminas-dependency-plugin 1.0.4 requires composer-plugin-api ^1.1 -> found composer-plugin-api(2.0.0) but it does not match the constraint.
    - magento/product-community-edition 2.3.6 requires laminas/laminas-dependency-plugin ^1.0 -> satisfiable by laminas/laminas-dependency-plugin(1.0.4).
    - magento/product-community-edition is locked to version 2.3.6 and an update of this package was not requested.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

You are using Composer 2, which some of your plugins seem to be incompatible with. Make sure you update your plugins or report a plugin-issue to ask them to support Composer 2.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

magento2.3 – Create a ResourceModel based on 3rd Party API Call from Magento

I am working on integrating a 3rd Party API into Magento. I’d like to use an Admin Grid with a Data Source that comes from a 3rd party API. So Essentially the Flow work like this…
User Loads into admin page with grid -> grid has data source specified to resource model -> resource model calls 3rd party api to get data -> data is returned to resource model(not sure if its supposed to be resource model or collection or factory in this scenario) -> data is bind through the resource model to the grid.

If there’s any additional information needed please let me know. I’m not sure what all information might be helpful.

magento2.3 – entity_type_code_entity table is empty in magento2

I am trying to insert data into the EAV tables, but my main entity table isn’t saving any data but the value tables data is inserted.
My Entity Type code is vinay_employee, my table vinay_employee_entity has three columns entity_id employee_name and employee_email. Data is not inserting into vinay_employee_entity when i am calling save() function but other values tables like vinay_employee_entity_datetime get their data.

Model/EmployeeData.php

namespace VinayEmployeeModel;

use MagentoFrameworkDataObjectIdentityInterface;
use MagentoFrameworkPricingSaleableInterface;
use VinayEmployeeApiDataEmployeeInterface;
use MagentoFrameworkApiAttributeValueFactory;

class EmployeeData extends MagentoFrameworkModelAbstractModel{

    const ENTITY = "vinay_employee";

    protected function _construct() {
        $this->_init('VinayEmployeeModelResourceModelEmployeeData');
    }
}

ResourceModel/EmployeeData.php

namespace VinayEmployeeModelResourceModel;

class EmployeeData extends MagentoEavModelEntityAbstractEntity{
    
    protected function _construct()
    {
        $this->_read = 'vinay_employee_read';
        $this->_write = 'vinay_employee_write';
    }
    
    public function getEntityType() {
        if(empty($this->_type)) {
            $this->setType(VinayEmployeeModelEmployeeData::ENTITY);
        }

        return parent::getEntityType();
    } 
}

Controller/Adminhtml/Emp/Save.php

namespace VinayEmployeeControllerAdminhtmlEmp;

class Save extends VinayEmployeeControllerAdminhtmlEmpAbstractAction {

    //put your code here

    private $connection;
    private $employeeDataFactory;
    private $employee, $employeeDataFactoryResource, $registry;

    public function __construct(
            MagentoBackendAppActionContext $context,
            MagentoFrameworkRegistry $registry,
            MagentoFrameworkAppResourceConnection $resourceConnection,
            VinayEmployeeModelResourceModelEmployeeDataFactory $employeeDataFactoryResource,
            VinayEmployeeModelEmployeeDataFactory $employeeDataFactory) {
        $this->connection = $resourceConnection->getConnection();
        parent::__construct($context);
        $this->employee = $employeeDataFactory;
        $this->registry= $registry;
        $this->employeeDataFactoryResource = $employeeDataFactoryResource;
    }

    public function execute() {
        $postObj = $this->getRequest()->getPostValue();
        echo "<pre>";
        $employeeModel = $this->employee->create(("employee_name", "employee_email"));
        $result = $employeeModel->setData($postObj)->save();
        print_r($result->getData());
        die();
        $this->employeeDataFactoryResource->create()->save($employeeModel);
        return $this->_redirect("employee/emp/index");
    }
}

$result

Array
(
    (form_key) => HSR4TCVPyzs6r6Wi
    (employee_name) => vinn
    (employee_email) => viin
    (employee_address) => ddsdds
    (is_permanent) => 0
    (joined_at) => 2021-04-15 10:02:35
    (vinaykharayat11) => ssdsd
    (parent_id) => 0
    (created_at) => 2021-04-15 04:32:37
    (updated_at) => 2021-04-15 04:32:37
    (entity_id) => 37
)

magento2.3 – Override Extension (/vendor) in app/frontend

I’m trying to override a layout .phtml file for a 3rd party extension which is located in /var/vendor_name/extension.
As I understand, I should not be modifying the /vendor files, but this extension has no files located in the app/code or app/frontend.

The file I’m trying to override is located in <magento_root>/vendor/vendor_name/module_name/view/frontend/templates/product/view/list.phtml

I read through the following thread but I’m not sure how to apply it in my situation Magento 2: How to Override File in Vendor Folder

Please let me know if more information needed.

Thanks

magento2.3 – Session destroyed in N genius payment gateway magento 2.3

I have created a N Genius hosted session payment gateway module for my project in magento 2.3 version. I have used an iframe to show the 3d secure form in this module. After the 3d secure submit i am setting some value in the checkout session for later use. Payment and order are placed successfully on the first try and from the next time, its not working because the data that i have saved in the session is not getting in the 3d response controller file. The sessions are getting destroyed and i have tried with customer session also, but no luck. Url i have checked, request and response use the same https url. Anyone have faced such issue? any idea about this?

magento2.3 – Display stock status on product detail page

for total quantity

$objectManager = MagentoFrameworkAppObjectManager::getInstance();
$StockState = $objectManager->get('MagentoCatalogInventoryApiStockStateInterface');
echo $StockState->getStockQty($product->getId(), $product->getStore()->getWebsiteId());

and if you want to get status

$stockItem = $objectManager->get('MagentoCatalogInventoryModelStockStockItemRepository');
$productId =1; // YOUR PRODUCT ID
$productStock = $stockItem->get($productId);
$data_p = $productStock->getData();
echo $data_p('is_in_stock'); //1 in stock 0 for out of stock


magento2.3 – Magento 2.3.4?How to change the cronjob frequency?

Try the following way:

  1. Create a module where the sequence should be Amazon_Payment. E.g:

    <module name="Vendor_AmzPayment">
        <sequence>
            <module name="Amazon_Payment"/>
        </sequence>
    </module>
  1. Create crontab.xml. Modify schedule tag. E.g:

    <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Cron:etc/crontab.xsd">
        <group id="default">
            <job name="amazon_payments_process_queued_refunds" instance="AmazonPaymentCronProcessAmazonRefunds" method="execute">
                <schedule>*/15 * * * *</schedule>
            </job>
        </group>
    </config>

magento2.3 – Magento 2.3.3 + elasticsearch 6 – empty catalog. Elasticsearch adds WHERE (NULL) to product collection

I have elasticsearch 6.8 and M2.3.3.
On the both category and search pages Magento display:

We can't find products matching the selection.

(MYSQL engine works correctly)

Reindex and cache are refreshed. I also added 2 patches:
https://github.com/magento/magento2/issues/27112#issuecomment-748916677

https://devdocs.magento.com/guides/v2.3/release-notes/release-notes-2-3-3-open-source.html#apply-the-catalog-pagination-issue-on-elasticsearch-6x-patch-to-resolve-a-critical-search-result-pagination-issue

Elasticseach is configured properly:

curl -X GET http://elasticsearch:9200/test_product_1_v15/_search?q=sergei

{"took":7,"timed_out":false,"_shards":{"total":5,"successful":5,"skipped":0,"failed":0},"hits":{"total":1,"max_score":4.255225,"hits":({"_index":"test_product_1_v15","_type":"document","_id":"246","_score":4.255225,"_source":{"store_id":"1","sku":"Sergey","status":"1","status_value":"Enabled","visibility":"4","name":"Sergey","category_ids":(2,52,84,125),"position_category_2":"0","name_category_2":"Test Category","position_category_52":"0","name_category_52":"Test Category 2","position_category_84":"0","name_category_84":"Test Category 3","position_category_125":"0","name_category_125":"Test","price_4_1":"80.000000","price_0_1":"100.000000","price_1_1":"100.000000","price_2_1":"100.000000","price_3_1":"100.000000","price_5_1":"100.000000","price_6_1":"100.000000"}})}}

Here is the final SQL query from list.phtml – it contains strange condition WHERE (NULL)

SELECT `e`.*, `price_index`.`price`, `price_index`.`tax_class_id`, `price_index`.`final_price`, IF(price_index.tier_price IS NOT NULL, LEAST(price_index.min_price, price_index.tier_price), price_index.min_price) AS `minimal_price`, `price_index`.`min_price`, `price_index`.`max_price`, `price_index`.`tier_price`, IFNULL(review_summary.reviews_count, 0) AS `reviews_count`, IFNULL(review_summary.rating_summary, 0) AS `rating_summary` FROM `catalog_product_entity` AS `e`
 INNER JOIN `catalog_product_index_price` AS `price_index` ON price_index.entity_id = e.entity_id AND price_index.website_id = '1' AND price_index.customer_group_id = 0
 LEFT JOIN `review_entity_summary` AS `review_summary` ON e.entity_id = review_summary.entity_pk_value AND review_summary.store_id = 1 AND review_summary.entity_type = (SELECT `review_entity`.`entity_id` FROM `review_entity` WHERE (entity_code = 'product')) WHERE (NULL)

Without this condition all seems fine.

I logged collection in this method (I suppose it’s elasticsearch output(?)): MagentoElasticsearchModelLayerCategoryItemCollectionProvider::getCollection()

and WHERE (NULL) already here:

SELECT `e`.* FROM `catalog_product_entity` AS `e` WHERE (NULL)

Any ideas why elastic search adds this condition and how can I rightly discard it?

If elastic search (magento extension) adds NULL because the answer from elastic search is empty, how can I debug it in magento?

DreamProxies - Cheapest USA Elite Private Proxies 100 Private Proxies 200 Private Proxies 400 Private Proxies 1000 Private Proxies 2000 Private Proxies ExtraProxies.com - Buy Cheap Private Proxies Buy 50 Private Proxies Buy 100 Private Proxies Buy 200 Private Proxies Buy 500 Private Proxies Buy 1000 Private Proxies Buy 2000 Private Proxies ProxiesLive Proxies-free.com New Proxy Lists Every Day Proxies123