Magento1.9 : An error occurred while processing this directive
I Configure Sub domain Unfortunetley I got this error
[an error occurred while processing this directive]
I don't Know What is the problem on it. Front end it's opening but it show's this error Backend it redirect to Live Backend.
I don't know it's related to server error or Magento Error can any one please guide me on this?
magento-1.9
add a comment |
I Configure Sub domain Unfortunetley I got this error
[an error occurred while processing this directive]
I don't Know What is the problem on it. Front end it's opening but it show's this error Backend it redirect to Live Backend.
I don't know it's related to server error or Magento Error can any one please guide me on this?
magento-1.9
add a comment |
I Configure Sub domain Unfortunetley I got this error
[an error occurred while processing this directive]
I don't Know What is the problem on it. Front end it's opening but it show's this error Backend it redirect to Live Backend.
I don't know it's related to server error or Magento Error can any one please guide me on this?
magento-1.9
I Configure Sub domain Unfortunetley I got this error
[an error occurred while processing this directive]
I don't Know What is the problem on it. Front end it's opening but it show's this error Backend it redirect to Live Backend.
I don't know it's related to server error or Magento Error can any one please guide me on this?
magento-1.9
magento-1.9
edited 20 mins ago
Amit Naraniwal
61239
61239
asked Mar 7 '16 at 19:54
user31402
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Step 1: Enable Error Printing in PHP OR Enable DEVELOPER_MODE
In order to find out the bug, enable errors for your PHP.
From http://www.phpfunctionalism.com/config/error-reporting/:
ini_set('display_errors',1);
error_reporting(E_ALL|E_STRICT);
If that doesn't work, edit php.ini (see http://php.net/manual/en/errorfunc.configuration.php) and set:
display_errors=1
If you don't know where your php.ini is located use:
<?php phpinfo(); ?>
And locate "configuration file (php.ini) path".
Step 2: Debug your Apache / Web Server Log
If you still don't get any errors in PHP, the problem has to be with web server:
If you are using Apache, locate access.log
and error.log
and see if they contain messages related to this issue.
Hint: tail -f xxx.log
allows you to track changes in a log in real-time (very useful for debugging).
Step 3: Check directory and file permission
Directory permission must be 755 other permissions like (752, 753, 756, and 777) cause limitation and will not work..
File permission must be 644 other permissions like (642, 643, 646 and 647) cause limitation and will not work..
I tried all no solution
– user31402
Mar 8 '16 at 6:08
Checked apache log?
– Rohit Kundale
Mar 8 '16 at 6:10
It's server error or Magento error
– user31402
Mar 8 '16 at 6:11
Where to check in var folder i didn't find
– user31402
Mar 8 '16 at 6:12
It's web server error. Do you have access to server error log? Check my second step
– Rohit Kundale
Mar 8 '16 at 6:14
|
show 4 more comments
You should check that the
magentosourcedirectory/var/tmp
folder exists in the Magento root directory and that the web user has permissions to write in it.
hope this will work for you.
No temp folder on that Location
– user31402
Mar 8 '16 at 6:22
Please create one and then assign appropriate permissions so web server user can write
– liyakat
Mar 8 '16 at 6:37
add a comment |
You can solve this error by just one PHP script.
Download it by this site:- https://wpbloggerbasic.com/special-guide/an-error-occurred-while-processing-this-directive/
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f105115%2fmagento1-9-an-error-occurred-while-processing-this-directive%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Step 1: Enable Error Printing in PHP OR Enable DEVELOPER_MODE
In order to find out the bug, enable errors for your PHP.
From http://www.phpfunctionalism.com/config/error-reporting/:
ini_set('display_errors',1);
error_reporting(E_ALL|E_STRICT);
If that doesn't work, edit php.ini (see http://php.net/manual/en/errorfunc.configuration.php) and set:
display_errors=1
If you don't know where your php.ini is located use:
<?php phpinfo(); ?>
And locate "configuration file (php.ini) path".
Step 2: Debug your Apache / Web Server Log
If you still don't get any errors in PHP, the problem has to be with web server:
If you are using Apache, locate access.log
and error.log
and see if they contain messages related to this issue.
Hint: tail -f xxx.log
allows you to track changes in a log in real-time (very useful for debugging).
Step 3: Check directory and file permission
Directory permission must be 755 other permissions like (752, 753, 756, and 777) cause limitation and will not work..
File permission must be 644 other permissions like (642, 643, 646 and 647) cause limitation and will not work..
I tried all no solution
– user31402
Mar 8 '16 at 6:08
Checked apache log?
– Rohit Kundale
Mar 8 '16 at 6:10
It's server error or Magento error
– user31402
Mar 8 '16 at 6:11
Where to check in var folder i didn't find
– user31402
Mar 8 '16 at 6:12
It's web server error. Do you have access to server error log? Check my second step
– Rohit Kundale
Mar 8 '16 at 6:14
|
show 4 more comments
Step 1: Enable Error Printing in PHP OR Enable DEVELOPER_MODE
In order to find out the bug, enable errors for your PHP.
From http://www.phpfunctionalism.com/config/error-reporting/:
ini_set('display_errors',1);
error_reporting(E_ALL|E_STRICT);
If that doesn't work, edit php.ini (see http://php.net/manual/en/errorfunc.configuration.php) and set:
display_errors=1
If you don't know where your php.ini is located use:
<?php phpinfo(); ?>
And locate "configuration file (php.ini) path".
Step 2: Debug your Apache / Web Server Log
If you still don't get any errors in PHP, the problem has to be with web server:
If you are using Apache, locate access.log
and error.log
and see if they contain messages related to this issue.
Hint: tail -f xxx.log
allows you to track changes in a log in real-time (very useful for debugging).
Step 3: Check directory and file permission
Directory permission must be 755 other permissions like (752, 753, 756, and 777) cause limitation and will not work..
File permission must be 644 other permissions like (642, 643, 646 and 647) cause limitation and will not work..
I tried all no solution
– user31402
Mar 8 '16 at 6:08
Checked apache log?
– Rohit Kundale
Mar 8 '16 at 6:10
It's server error or Magento error
– user31402
Mar 8 '16 at 6:11
Where to check in var folder i didn't find
– user31402
Mar 8 '16 at 6:12
It's web server error. Do you have access to server error log? Check my second step
– Rohit Kundale
Mar 8 '16 at 6:14
|
show 4 more comments
Step 1: Enable Error Printing in PHP OR Enable DEVELOPER_MODE
In order to find out the bug, enable errors for your PHP.
From http://www.phpfunctionalism.com/config/error-reporting/:
ini_set('display_errors',1);
error_reporting(E_ALL|E_STRICT);
If that doesn't work, edit php.ini (see http://php.net/manual/en/errorfunc.configuration.php) and set:
display_errors=1
If you don't know where your php.ini is located use:
<?php phpinfo(); ?>
And locate "configuration file (php.ini) path".
Step 2: Debug your Apache / Web Server Log
If you still don't get any errors in PHP, the problem has to be with web server:
If you are using Apache, locate access.log
and error.log
and see if they contain messages related to this issue.
Hint: tail -f xxx.log
allows you to track changes in a log in real-time (very useful for debugging).
Step 3: Check directory and file permission
Directory permission must be 755 other permissions like (752, 753, 756, and 777) cause limitation and will not work..
File permission must be 644 other permissions like (642, 643, 646 and 647) cause limitation and will not work..
Step 1: Enable Error Printing in PHP OR Enable DEVELOPER_MODE
In order to find out the bug, enable errors for your PHP.
From http://www.phpfunctionalism.com/config/error-reporting/:
ini_set('display_errors',1);
error_reporting(E_ALL|E_STRICT);
If that doesn't work, edit php.ini (see http://php.net/manual/en/errorfunc.configuration.php) and set:
display_errors=1
If you don't know where your php.ini is located use:
<?php phpinfo(); ?>
And locate "configuration file (php.ini) path".
Step 2: Debug your Apache / Web Server Log
If you still don't get any errors in PHP, the problem has to be with web server:
If you are using Apache, locate access.log
and error.log
and see if they contain messages related to this issue.
Hint: tail -f xxx.log
allows you to track changes in a log in real-time (very useful for debugging).
Step 3: Check directory and file permission
Directory permission must be 755 other permissions like (752, 753, 756, and 777) cause limitation and will not work..
File permission must be 644 other permissions like (642, 643, 646 and 647) cause limitation and will not work..
edited Mar 8 '16 at 5:48
answered Mar 8 '16 at 5:29
Rohit KundaleRohit Kundale
2,88111327
2,88111327
I tried all no solution
– user31402
Mar 8 '16 at 6:08
Checked apache log?
– Rohit Kundale
Mar 8 '16 at 6:10
It's server error or Magento error
– user31402
Mar 8 '16 at 6:11
Where to check in var folder i didn't find
– user31402
Mar 8 '16 at 6:12
It's web server error. Do you have access to server error log? Check my second step
– Rohit Kundale
Mar 8 '16 at 6:14
|
show 4 more comments
I tried all no solution
– user31402
Mar 8 '16 at 6:08
Checked apache log?
– Rohit Kundale
Mar 8 '16 at 6:10
It's server error or Magento error
– user31402
Mar 8 '16 at 6:11
Where to check in var folder i didn't find
– user31402
Mar 8 '16 at 6:12
It's web server error. Do you have access to server error log? Check my second step
– Rohit Kundale
Mar 8 '16 at 6:14
I tried all no solution
– user31402
Mar 8 '16 at 6:08
I tried all no solution
– user31402
Mar 8 '16 at 6:08
Checked apache log?
– Rohit Kundale
Mar 8 '16 at 6:10
Checked apache log?
– Rohit Kundale
Mar 8 '16 at 6:10
It's server error or Magento error
– user31402
Mar 8 '16 at 6:11
It's server error or Magento error
– user31402
Mar 8 '16 at 6:11
Where to check in var folder i didn't find
– user31402
Mar 8 '16 at 6:12
Where to check in var folder i didn't find
– user31402
Mar 8 '16 at 6:12
It's web server error. Do you have access to server error log? Check my second step
– Rohit Kundale
Mar 8 '16 at 6:14
It's web server error. Do you have access to server error log? Check my second step
– Rohit Kundale
Mar 8 '16 at 6:14
|
show 4 more comments
You should check that the
magentosourcedirectory/var/tmp
folder exists in the Magento root directory and that the web user has permissions to write in it.
hope this will work for you.
No temp folder on that Location
– user31402
Mar 8 '16 at 6:22
Please create one and then assign appropriate permissions so web server user can write
– liyakat
Mar 8 '16 at 6:37
add a comment |
You should check that the
magentosourcedirectory/var/tmp
folder exists in the Magento root directory and that the web user has permissions to write in it.
hope this will work for you.
No temp folder on that Location
– user31402
Mar 8 '16 at 6:22
Please create one and then assign appropriate permissions so web server user can write
– liyakat
Mar 8 '16 at 6:37
add a comment |
You should check that the
magentosourcedirectory/var/tmp
folder exists in the Magento root directory and that the web user has permissions to write in it.
hope this will work for you.
You should check that the
magentosourcedirectory/var/tmp
folder exists in the Magento root directory and that the web user has permissions to write in it.
hope this will work for you.
answered Mar 8 '16 at 6:14
liyakatliyakat
3,60061933
3,60061933
No temp folder on that Location
– user31402
Mar 8 '16 at 6:22
Please create one and then assign appropriate permissions so web server user can write
– liyakat
Mar 8 '16 at 6:37
add a comment |
No temp folder on that Location
– user31402
Mar 8 '16 at 6:22
Please create one and then assign appropriate permissions so web server user can write
– liyakat
Mar 8 '16 at 6:37
No temp folder on that Location
– user31402
Mar 8 '16 at 6:22
No temp folder on that Location
– user31402
Mar 8 '16 at 6:22
Please create one and then assign appropriate permissions so web server user can write
– liyakat
Mar 8 '16 at 6:37
Please create one and then assign appropriate permissions so web server user can write
– liyakat
Mar 8 '16 at 6:37
add a comment |
You can solve this error by just one PHP script.
Download it by this site:- https://wpbloggerbasic.com/special-guide/an-error-occurred-while-processing-this-directive/
add a comment |
You can solve this error by just one PHP script.
Download it by this site:- https://wpbloggerbasic.com/special-guide/an-error-occurred-while-processing-this-directive/
add a comment |
You can solve this error by just one PHP script.
Download it by this site:- https://wpbloggerbasic.com/special-guide/an-error-occurred-while-processing-this-directive/
You can solve this error by just one PHP script.
Download it by this site:- https://wpbloggerbasic.com/special-guide/an-error-occurred-while-processing-this-directive/
answered Feb 2 at 13:15
ayush singhayush singh
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f105115%2fmagento1-9-an-error-occurred-while-processing-this-directive%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown