Solution to MAGENTO 500 server error

Directory and file permissions

Some hosts are installed.Magento displays error 500,If you confirm that the host supports all components of magento, the permission may be related to the directory and file.

Cause: There are a lot of hosts out there that don't allow permissions of 777 for directories or 666

Files now. This makes things "Group" writable which is a security risk. This isn't a MySQL, htaccess, or

Anything else issue, it has to do with suphp stuff and is a little unavoidable.

Some hosts do not allow Group writing for security purposes. Therefore, the default permission directories 775 and file 664 cannot be installed and run after magento is uploaded.

.

Modify the permissions of all subdirectories and files under the magento directory to 755 and 644.
(The downtownhost host is one of them. I have encountered such a problem. I can check the error log in cpanel to find the cause)

If the host supports SSH, perform the following operations:
Enter the ssh terminal and magento installation directory, and enter the command (note that the semicolon should not be missed. maxdepth 1 indicates the current directory. During actual operations, you must specify
Maxdepth 10, so that all subdirectories and files can be modified)

Modify file permissions: find-maxdepth 10-type f-exec chmod 644 {};

Modify directory permissions: find-maxdepth 10-type d-exec chmod 755 {};

This method does not solve the problem that occurs during the installation process. I fixed this problem by setting folder permission 775 and file permission 755.

The. htaccess rule causes

The final cause is the. htaccess rule in the default installation package. During installation, we only need to change the. htaccess file name to ensure normal installation.

If magento needs to be pseudo-static, you can select the apache rw module during installation or log on to magento to enable the pseudo-static function. Here, we will remind you to install magento.

What causes the class? I have read the htaccess rules in the official installation package because several rules control or disable some apache parameters (for example, disable security mode ). For the sake of space security and stability, carefree hosts prohibit users from parsing php. INI files or apache configurations through. htaccess rules. This error is not prompted when Magento rules are installed on independent servers, VPS, or spaces that are not strictly managed by space security mechanisms.

Magento solution to 500 error when modifying user information

Symptom:

When a user modifies his/her personal information, the page is blank. View the log and an error is found:

PHP Fatal error: Call to a member function setAttribute () on a non-object in .. /app/code/core/Mage/Eav/Model/Attribute/Data. php on line 80, referer :...

Solution:

Execute this statement to find all the attributes with blank fronted_input, and change fronted_input to any valid values (text, select, etc ):

SELECT * FROM 'eav _ attribute' where attribute_id in (select attribute_id from customer_eav_a