Cart page error with Porto theme

diegozanotti commented 3 years ago

Preconditions (*)

Magento 2.3.6 in developer mode
Porto theme 3.2.6
Paypal and Stripe checkout methods
PHP 7.3 and Debian 4.9.246-2 (dedicated virtual machine)
website: https://www.00up.app/magento2/

Steps to reproduce (*)

Go to catalog
Add product to cart (one or more)
Click on shopping bag top right
Open mini cart
Click on bottom button (view or edit cart) - "Visualizza e modifica il carrello"

Expected result (*)

Display cart page (checkout/cart/)

Actual result (*)

Cart page return error (checkout/cart/)

1 exception(s): Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'argument': The attribute 'name' is required but missing. Line: 1219

Element 'argument': Not all fields of key identity-constraint 'blockReferenceActionArgumentName' evaluate to a node. Line: 1219

Exception #0 (Magento\Framework\Config\Dom\ValidationException): Element 'argument': The attribute 'name' is required but missing. Line: 1219

Element 'argument': Not all fields of key identity-constraint 'blockReferenceActionArgumentName' evaluate to a node. Line: 1219

#1 Magento\Framework\Config\Dom->__construct('createObject('Magento\Framewor...', array('create('Magento\Framewor...', array('xml' => ' '/var/www/vhosts/...', 'validationState' => &Magento\Framework\App\Arguments\ValidationState#00000000797756090000000074da638e#)) called at [vendor/magento/framework/ObjectManager/ObjectManager.php:56]
#4 Magento\Framework\ObjectManager\ObjectManager->create('Magento\Framewor...', array('xml' => ' '/var/www/vhosts/...', 'validationState' => &Magento\Framework\App\Arguments\ValidationState#00000000797756090000000074da638e#)) called at [vendor/magento/framework/Config/DomFactory.php:43]
#5 Magento\Framework\Config\DomFactory->createDom(array('xml' => ' '/var/www/vhosts/...', 'validationState' => &Magento\Framework\App\Arguments\ValidationState#00000000797756090000000074da638e#)) called at [vendor/magento/framework/View/Model/Layout/Update/Validator.php:141]
#6 Magento\Framework\View\Model\Layout\Update\Validator->isValid('_validateMergedLayout('LAYOUT_frontend_...', '\n   load(array()) called at [generated/code/Magento/Framework/View/Model/Layout/Merge/Interceptor.php:206]
#9 Magento\Framework\View\Model\Layout\Merge\Interceptor->load() called at [vendor/magento/framework/View/Layout/Builder.php:86]
#10 Magento\Framework\View\Layout\Builder->loadLayoutUpdates() called at [vendor/magento/framework/View/Layout/Builder.php:63]
#11 Magento\Framework\View\Layout\Builder->build() called at [vendor/magento/framework/View/Page/Config.php:224]
#12 Magento\Framework\View\Page\Config->build() called at [vendor/magento/framework/View/Page/Config.php:247]
#13 Magento\Framework\View\Page\Config->getTitle() called at [vendor/magento/module-checkout/Controller/Cart/Index.php:57]
#14 Magento\Checkout\Controller\Cart\Index->execute() called at [vendor/magento/framework/Interception/Interceptor.php:58]
#15 Magento\Checkout\Controller\Cart\Index\Interceptor->___callParent('execute', array()) called at [vendor/magento/framework/Interception/Interceptor.php:138]
#16 Magento\Checkout\Controller\Cart\Index\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153]
#17 Magento\Checkout\Controller\Cart\Index\Interceptor->___callPlugins('execute', array(), array(array('amazon_login_car...'))) called at [generated/code/Magento/Checkout/Controller/Cart/Index/Interceptor.php:26]
#18 Magento\Checkout\Controller\Cart\Index\Interceptor->execute() called at [vendor/magento/framework/App/Action/Action.php:108]
#19 Magento\Framework\App\Action\Action->dispatch(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#) called at [vendor/magento/framework/Interception/Interceptor.php:58]
#20 Magento\Checkout\Controller\Cart\Index\Interceptor->___callParent('dispatch', array(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#)) called at [vendor/magento/framework/Interception/Interceptor.php:138]
#21 Magento\Checkout\Controller\Cart\Index\Interceptor->Magento\Framework\Interception\{closure}(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#) called at [vendor/magento/framework/Interception/Interceptor.php:153]
#22 Magento\Checkout\Controller\Cart\Index\Interceptor->___callPlugins('dispatch', array(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#), array(array('designLoader', 'customerNotifica...', 'catalog_app_acti...', 'tax-app-action-d...', 'weee-app-action-...', 'storeCheck', 'contextPlugin', 'customer-app-act...', 'multishipping_cl...'))) called at [generated/code/Magento/Checkout/Controller/Cart/Index/Interceptor.php:39]
#23 Magento\Checkout\Controller\Cart\Index\Interceptor->dispatch(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#) called at [vendor/magento/framework/App/FrontController.php:186]
#24 Magento\Framework\App\FrontController->processRequest(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#, &Magento\Checkout\Controller\Cart\Index\Interceptor#00000000797754280000000074da638e#) called at [vendor/magento/framework/App/FrontController.php:118]
#25 Magento\Framework\App\FrontController->dispatch(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#) called at [vendor/magento/framework/Interception/Interceptor.php:58]
#26 Magento\Framework\App\FrontController\Interceptor->___callParent('dispatch', array(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#)) called at [vendor/magento/framework/Interception/Interceptor.php:138]
#27 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#) called at [vendor/magento/module-store/App/FrontController/Plugin/RequestPreprocessor.php:99]
#28 Magento\Store\App\FrontController\Plugin\RequestPreprocessor->aroundDispatch(&Magento\Framework\App\FrontController\Interceptor#00000000797756660000000074da638e#, &Closure#00000000797756450000000074da638e#, &Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#) called at [vendor/magento/framework/Interception/Interceptor.php:135]
#29 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#) called at [vendor/magento/module-page-cache/Model/App/FrontController/BuiltinPlugin.php:73]
#30 Magento\PageCache\Model\App\FrontController\BuiltinPlugin->aroundDispatch(&Magento\Framework\App\FrontController\Interceptor#00000000797756660000000074da638e#, &Closure#00000000797756450000000074da638e#, &Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#) called at [vendor/magento/framework/Interception/Interceptor.php:135]
#31 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#) called at [vendor/magento/framework/Interception/Interceptor.php:153]
#32 Magento\Framework\App\FrontController\Interceptor->___callPlugins('dispatch', array(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#), NULL) called at [generated/code/Magento/Framework/App/FrontController/Interceptor.php:26]
#33 Magento\Framework\App\FrontController\Interceptor->dispatch(&Magento\Framework\App\Request\Http#000000007977572c0000000074da638e#) called at [vendor/magento/framework/App/Http.php:116]
#34 Magento\Framework\App\Http->launch() called at [generated/code/Magento/Framework/App/Http/Interceptor.php:24]
#35 Magento\Framework\App\Http\Interceptor->launch() called at [vendor/magento/framework/App/Bootstrap.php:261]
#36 Magento\Framework\App\Bootstrap->run(&Magento\Framework\App\Http\Interceptor#00000000797757d60000000074da638e#) called at [index.php:39]

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

[x] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
[ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
[ ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
[ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
[ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

m2-assistant[bot] commented 3 years ago

Hi @diegozanotti. Thank you for your report. To help us process this issue please make sure that you provided the following information:

Summary of the issue
Information on your environment
Steps to reproduce
Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

Join Magento Community Engineering Slack and ask your questions in #github channel.

:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

:movie_camera: You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

mrtuvn commented 3 years ago

Seem this problem related to porto theme and not from magento Some layout of your theme rely on argument tag but it's missing name attribute (this is required) Search in entire your theme files and locate the missing attribute name in tag argument

diegozanotti commented 3 years ago

Seem this problem related to porto theme and not from magento Some layout of your theme rely on argument tag but it's missing name attribute (this is required) Search in entire your theme files and locate the missing attribute name in tag argument

Thank you for your fast reply! Unfortunately I'm new in Magento, can you please suggest me how to check and fix it?

mrtuvn commented 3 years ago

You should search all tag argument in XML files in your porto scope theme to indicates missing required name one

diegozanotti commented 3 years ago

Ok, will try, thank you very much!

diegozanotti commented 3 years ago

You should search all tag argument in XML files in your porto scope theme to indicates missing required name one

I have tried to set LUMA theme instead PORTO, and have the same error, so should be not Porto theme error...

mrtuvn commented 3 years ago

What about switch to blank theme ?

diegozanotti commented 3 years ago

Yes I have tried with blank theme too... same error

mrtuvn commented 3 years ago

Maybe cause from layout modules. Try disable all modules custom not related to magento that you have. It's hard to tell you without see direct code. You should re-test with sample instance. Clean install without any customise or extra module.

m2-assistant[bot] commented 3 years ago

Hi @krishprakash. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
[ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop branch
Details
- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
[ ] 5. Add label Issue: Confirmed once verification is complete.
[ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

krishprakash commented 3 years ago

Hi @diegozanotti. Thank you for your report. GitHub issue tracker is intended for Magento core technical issues only Kindly refer community forum or Magento stack exchange for general discuss about this topic

magento / magento2