We changed our privacy policy. Read more.
15

Take a look at PDOException SQLSTATE[HY000] [2002] No such file or directory Check your "host" setting in Magento 1: /app/etc/local.xml Magento 2: /app/etc/env.php Try changing it from "localhost" to "127.0.0.1"


14

There is a known Issue After Upgrading to CE 1.8.1 that affects you only if you do not follow the recommended procedure to upgrade to a new environment as discussed in Getting Ready For Your Upgrade. Symptom: After completing the upgrade, when you log in to the Admin Panel and click System > Configuration, a fatal error similar to the following displays in ...


12

If you see an error like this it is a complete application failure - which will actually be logged by corresponding number to /var/report/ (Per comments) if this dir doesn't exist try to set 777 perms recursively on var a la chmod -R 777 var/


12

Is this a known issue with Magento 1.9 ? No. What steps do I need to perform the stop these from occurring? Fix your corehack. This can't happen: app/code/core/Mage/Core/Model/Session/Abstract/Varien.php:87 // session cookie params $cookieParams = array( 'lifetime' => $cookie->getLifetime(), 'path' => $cookie-&...


9

I reckon there's several types of errors that can be triggered by the deployment. First you can see that Exception are handled directly in the execution in Magento/Deploy/Console/Command/DeployStaticContentCommand.php: catch (\Exception $e) { $output->writeln('<error>' . $e->getMessage() . '</error>>'); if ($output-&...


9

Magento can increase the memory for processing a large amount of data by using memory engines instead of InnoDB. The algorithm increases the memory value for the max_heap_table_size and tmp_table_size MySQL parameters. When the allocated memory size for a temporary table will be greater than 20% of innodb_buffer_pool_size, the error message is written to ...


8

1. After Magento Installation, you should set the developer mode by this command php bin/magento deploy:mode:set developer By setting Developer Mode, Errors are displayed in the browser and can be seen by users. 2. You can check the errors for var/log and var/reports folder Errors that get in var/reports are more detailed. 3. This will display PHP ...


6

See /app/code/core/Mage/Review/Block/Helper and find the function getSummaryHtml. It has a third parameter $displayIfNoReviews Please pass in a true or false if you want it to output the summary even if no reviews exist. <?php echo $this->getLayout()->createBlock('review/helper')->getSummaryHtml($product, 'short', true); ?>


6

Replace Exception $e to \Exception $e Final Code public function uploadFile($scope) { try { $uploader = $this->_fileUploaderFactory->create(['fileId' => $scope]); $uploader->setAllowRenameFiles(true); $uploader->setFilesDispersion(true); $uploader->setAllowCreateFolders(true); if ($uploader-&...


5

If you are using the SCP extension, you should be able to find the line: Mage::log("cpid: ". $cpid); in the file: /app/code/community/OrganicInternet/SimpleConfigurableProducts/Catalog/Model/Product/Type/Simple.php You can comment it out to prevent the log file from filling up. It doesn't appear to do anything when the extension is configured and ...


5

Remove % from 'Image Watermark Opacity, Percent'. Just put in a number, like 15.


5

By default Error reporting are possible in frontend using developer mode. Run command, Using Developer mode, you can directly check error in frontend browser if any error are occur, php bin/magento deploy:mode:set developer Changes in file, Go To pub folder of root and rename at below path, pub/erros/local.xml.sample to local.xml Now go to app/...


5

Go to your server MySQL settings file (my.ini) Search for innodb_buffer_pool_size and increase this value.


4

delete /var/.update_error.flag The above solution worked for me.


4

Had the same issue with var/page_cache not writable. OP's answer pointed me in the right direction. Rather than disabling SELinux completely, need to update SELinux security context for following directories: chcon -R --type httpd_sys_rw_content_t <your Magento install dir>/app/etc chcon -R --type httpd_sys_rw_content_t <your Magento install ...


3

It looks like the extension Webinse_DailyDeals created an attribute deal_update_days. When you remove an extension, any changes it made to the database are still there. Unfortunately this attribute depends on a class of the extension and now that the extension is uninstalled you get this error because the class cannot be found anymore. You have to manually ...


3

It sounds like the fault is with permissions of the folder and the files within. Sometimes when Magento create a folder it doesn't add the correct permissions to that folder "As in user / owner permissions" not just 777. You need to: Login via SSH as root and type the following chown accountuser.accountuser /home/accountuser/public_html/var/report ...


3

If you want to see these errors directly on the page, add SetEnv MAGE_IS_DEVELOPER_MODE true to the top of your .htaccess file. You will get the full error directly through the browser, instead of having to get the file from var/report. Note:: Remove SetEnv MAGE_IS_DEVELOPER_MODE true from .htaccess before you go live! The most concise and ...


3

You can often see errors within your less by viewing the css file that is generated on your development environment. This doesn't quite answer the question but will hopefully be helpful to someone.


3

turn this foreach ($items as $itemCart) { $tab[$itemCart->getUdropshipVendor()] += $itemCart->getPrice() * $itemCart->getQty(); } into this foreach ($items as $itemCart) { $vendor = $itemCart->getUdropshipVendor(); if (!isset($tab[$vendor])) { $tab[$vendor] = 0; } $tab[$vendor] += $itemCart->getPrice() * $...


3

try below command to disabled maintenance mode: php bin/magento maintenance:enable php bin/magento maintenance:disable php bin/magento maintenance:status Please check this link. http://devdocs.magento.com/guides/v2.0/install-gde/install/cli/install-cli-subcommands-maint.html


3

This error due to undefined return type. you cannot defined array as return type. If I am not wrong then you want to return it as associative array so check below code. You need to define it like below /** * Get Slides * * @return \Vendor\Module\Api\Data\KeyValueInterface[] */ public function getSlides(); Please Check, in your case there will be ...


2

(This should probably be a comment to your question.) You are trying to put an array in a column that expects longtext. If you can reproduce this notice and thus know what is saved during that request, you will probably see it saved the text 'Array' somewhere, instead of the expected piece of text. If you know that, you can probably figure out how it got ...


2

You have a section commented out in a layout xml file but it's not closed. A comment starts with <!-- and ends with with -->. It should be pretty easy to track down. Search the contents of your theme's layout folder for "wePrefer_150x60" and you'll find your open ended comment that's throwing the error.


2

Please post the entire contents of the file from /var/report as it probably has the actual error message at the top. But to help you start looking into the problem, reformatted for easy reading, this is the query that is failing: SELECT `t_d`.`entity_id`, `t_d`.`attribute_id`, `t_d`.`value` AS `default_value`, `t_s`.`value` AS `store_value`,...


2

Something went wrong, so the table wasn't created. And because you can't be sure this is the only problem, get your backup and start from the beginning. Sorry, too stupid to read an error message. You are right. Then it might be, that you request the page two times, so the install script runs two times. You can try to just remove everything from the script ...


2

The problem isn't the upgrade procedure, if you skip some versions (i.e. from 1.7 to 1.9). The cause is, that in versions above 1.7 the path to GoogleCheckout is written with lower c, ERR (3): Warning: include(Mage/Googlecheckout/Helper/Data.php): failed to open stream: No such file or directory in /chroot/home/path/to/html/lib/Varien/Autoload.php on line ...


2

Find this file in /your/magentodir/var/.update_error.flag and remove it. Execute following commands cd <your Magento install dir> rm var/.update_error.flag


2

Please check adminhtml/menu.xml to find (Ves_All::ves_all) you should define a child with id="Ves_All::ves_all).


2

Magento 2.3.3 Commerce. It was related with optimize parameter for me. composer dump-autoload --optimize I noticed it needed to run the command with optimize twice php7.2 /usr/local/bin/composer dump-autoload --no-dev -o Generating optimized autoload files php7.2 bin/magento setup:di:compile Class Magento\Framework\App\ResourceConnection\Proxy does not ...


Only top voted, non community-wiki answers of a minimum length are eligible