Product Page not working in Magento PWA venia theme local setup? - magento2

I successfully installed venia on my local system. I connected the backend URL with Magento 2.4.4, Homepage and list page working fine. But, the Product page is not working. When I click on the product page it shows like the below image. Any solution to resolve this issue? Please let me know if any.
Thanks.

try "yarn run build" or "npm run build" then "yarn/npm start"

First thing you have to do is turn on developer mode; command:
php bin/magento deploy:mode:set developer
Then, after that, check the debug log
path of error log:
magento root dir/var/log/debug.log
If there is any error show to you then we will be able to help you till we don't know the error and can't give any solution.

Related

Magento 2.2.4: "Sorry, no quotes are available for this order at this time"

The checkout was working smoothly and I've checked the test orders in admin panel. While during the maintenance I clean up the cache and upgrade the static content.
Right after unexpectedly, I am getting message at the time of checkout "Sorry, no quotes are available for this order at this time". I have configured UPS shipping method under configuration.
You can also replicate it, by accessing the website at https://awscales.com
I have also tried cache clean, re-index but no luck. I am unable to figure out the possible reason of this message.
My environment setup is:
OS: Ubuntu (VERSION-16.04.4)
PHP: 7.0.33-0ubuntu0.16.04.5
Zend: Engine v3.0.0
Magento: 2.2.4 (changed to developer mode)
While I access admin panel and open 'Sales > Shipping Method' tab from 'Store > Configuration', I noticed that the page is not working at all. The 'Save' button is also disabled.
In browser console I saw the following error:
TypeError: $(...).phpConfigEditor is not a function
I am clueless, please help.

Ionic Cloud: Getting Error Registry returned 404 for Get

I keep getting this error in my output when trying to package iOS through Ionic cloud "Error: Registry returned 404 for GET on https://registry.npmjs.org/[MyAppName]". I've followed a few other forum posts that I could find to no avail. Any help would be much appreciated!
in package.json you have [MyAppName] as package or something like that, which when trying to fetch from npmjs.com its not there since you havent publish it, post package.json to check it.
I was using [MyAppName] as a placeholder for my physical app name; for the post. The issue turned out to be the Cordova plugins directory.
To resolve I ran:
ionic state clear --plugins
This, however, resulted in only partial removal of the plugins. I further had to manually delete the rest. Finally I ran:
ionic state restore --plugins
I can build successfully now.

Mbstring extension installation on godaddy server

Call to undefined function mb_convert_encoding(). How to install
mbstring extension installation on godaddy server?
I have found the solution. We need to complete the following steps:
1.Login to your server WHM as root
2.Search EasyApache or go to Software menu after that EasyApache
3. you can see there are some profile. click on customize profile default profile.
4. click on continue to second step
5. On “Step 2,” click on “Exhaustive Options”
6. Under PHP, check the checkbox for MBString
7. Proceed with Build & Compile Process
Make sure you wait for the build to complete.
I'm updating this thread as I went through a painful day trying to get this resolved. The mbstring extension is used by Magento (I needed it for 1.9) and without it installed, the checkout process will fail, with the shopping cart failing to take the user to the 'Thanks for your order screen' (although the order is sometimes created on the back-end successfully). It was also creating an issue when hitting the 'Send Email' button on the Admin panel on an Order, producing a 500 error.
In my log files, I was seeing the following error:
PHP Fatal error: Call to undefined function mb_convert_encoding() in
/home/yoursite/public_html/lib/Pelago/Emogrifier.php on line 556
Searching for this error gave results that suggested I needed to enable the mbstring extension on the server, but with a GoDaddy hosted virtual server, I ran into a wall of frustration with the package not being found via the php install search, and their tech support unable to assist. The above solution worked, although I will clarify the instructions below for the current WHM panel (Jan 2019):
Login to your server WHM as root.
Search EasyApache or go to the Software menu on the left and select 'EasyApache 4'.
You will see a list of profiles and at the top of the list, 'Currently Installed Packages'. Select the 'Customize' button.
Select the 'PHP Extensions' link or keep hitting 'Next' until you reach the page.
In the search box, type 'string', you will see 'php56-php-mbstring' and 'php70-php-mbstring'; move the grey slider on the right to install each.
Continue to the 'Review' tab. Here you can simply hit 'Provision' to install the extension. You can also save these options as a custom profile if you'd like.
After the build has completed, the extension should be available on all your domains.
Hopefully this will save someone some time trying to figure this out!

Magento2 error: We're sorry, an error has occurred while generating this email

I am getting below error in magento 2 local system:
We're sorry, an error has occurred while generating this email.
It is not showing me the sample data installed in catalog. Please help me out to get solution of this problem.
Regards,
Rakesh Kumar
The first thing you need to do is go to your .htaccess file. Uncomment
SetEnv MAGE_MODE developer
The error message is 90% of the time misleading and most likely you have an xml parsing issue. Either way turning on the developer environment and clearing the cache will pull the error.
Without seeing your error log it'd be hard to give an exact diagnosis. Some users will say sendmail will fix this error but generally this is because the error is trying to be emailed to you and that is because you are not in the correct developing environment to debug the issue. This could be because you are in default or production mode which is not ideal for fixing issue.
The sendmail module is meant to allow a site to operate and if any issues do occur with the site then the developer can be notified and hopefully the error hasn't caused a full site rendering issue. This way a site can still operate unbeknown to users and the issue can be resolved by a qualified developer behind the scenes.
This error is quite misleading. In my case an error in MySql query was causing this.
You should enable developer mode the get the exact error.
php ./bin/magento deploy:mode:set developer
In My case issue get solved by giving permissions to directory pub/media/catalog/product/
Enable developer mode using command line php bin/magento deploy:mode:set developer
Clear cache using command line php bin/magento cache:flush
Reload the frontend page
After reloading the page the message will change to
Error filtering template: Unable to write file into directory \C:/xampp/htdocs/Magento/pub/media/catalog/product\cache\f073062f50e48eb0f0998593e568d857/m/b. Access forbidden.
Follow this link to fix Magento 2: Unable to write file into directory. Access forbidden
Clear cache
Reload the frontend page again
If you see another message after enabling developer mode you can search for it
In my case it was missing php-gd extension on my machine.
This was on my exception log (magento_root/var/log/exception.log):
main.CRITICAL: exception 'Exception' with message 'Required PHP extension 'gd' was not loaded.' in /var/www/html/magento2/vendor/magento/framework/Image/Adapter/Gd2.php:620
Solved by installing php-gd library on my Ubuntu machine with the following command:
sudo apt-get install php-gd
If you want to install for php5.6 then you may run:
sudo apt-get install php5.6-gd
This can be for any error occurred in the page. The notice is different. The notice is given when system tries to send error email to administrator and failed while in Production mode.
For actual error one should enable developer mode and enable display error in app/bootstrap.php and checking error logs. It can be any error like php or mysql.
ini_set('display_errors', 1);
Thanks
Please check your /var/log/exception.log
This is issue raised because your product does not upload. so check your database or upload your sample database again .Let me know what error in exception.log

How to diagnose metro app deployment errors?

When trying to debug a Metro project from VS, I came across this error:
DEP0700 : Registration of the app failed. Another user has already installed a packaged version of this app. An unpackaged version cannot replace this. The conflicting package is PACKAGENAME and it was published by CN=some Guid. (0x80073cf9)
But I have already uninstalled the app from the Start page, also, I can confirm that there is no entry left in Add/Remove program.
And since the access to the "%PROGRAMFILES%\WindowsApps" folder where the app files reside in is blocked, so I have no way to see if the app is still there.
However, I can still find many 'PACKAGENAME' occurances in the registry.
How to diagnose this? How to get rid of the "packaged version" so I can start debugging from VS?
Try installing the app from the windows store again, and then uninstall it from the start page. It appears that when Visual Studio does the uninstall it doesn't do it right.
1) Go to your Package.appxmanifest file in your solution
2) Go to the identity tag.
<Identity Name="xxxxxxx-yyyy-zzzz-tttt-bbbbbbbbbbbbb"
Publisher="CN=bigbob"
Version="1.0.0.0" />
3) Change the value of the Identity Name (Ex from ...bbbbb to ...bbbbc)
4) Rebuild and run
Source:
http://www.sempf.net/post/MetroUIAnother-user-has-already-installed-an-unpackaged-version-of-this-application.aspx
Are you sure you didn't just unpin the app? Try doing a search for it and see if it is still there.
I find a solution to the problem. It's said it is a "staged package" that does not show up in my start page so I can not uninstall it in normal way. I follow the steps, and successfully get rid of that "un-uninstallable" :) package.
This blog post was helpful, although after an hour or so of troubleshooting it turns out that I had indeed installed the package under another user account. After switching accounts and uninstalling from the start screen it worked fine.