Jump to content

Fix errors


Recommended Posts

  • 3 weeks later...

Hi...

 

I am getting following error & also my site is not working.

 

Required parameters: OK

Optional parameters: Please fix the following error(s)

  • register_globals
  • magicquotes

 

Can anyone help.

 

Thanks in advance

Link to comment
Share on other sites

You host would have to change them. If you are on shared hosting more than likely they won't. The magic quotes is not really a problem. I am pretty sure you can turn register globals off with a php.ini file. you might try googling it.

Link to comment
Share on other sites

Thanks for reply.

 

I am getting white screen error.

I moved my site from one server to another.

When i run it on my local pc it works great but in server in front-end it just doesn't show anything but white screen.

i have set @ini_set('display_errors', 'E_ALL'); to show error in config file but no luck...

 

Can you help me please?

I have upgraded PS 1.4.8 to PS 1.5.1.7

 

Thanks

Link to comment
Share on other sites

I have done a lot of customization. I'll lost all OR fix them again. That is why right now i don't want to consider this option.

This is frustration error. I must be able to see errors at least. Black screen is a mess.

 

Thanks for your help mate.

Link to comment
Share on other sites

I also see a white screen (display errors is off probably). Just in case - possible way to turn off register globals and magic quotes in .htaccess file (it works on my shared hosting, info taken from the support FAQ section):

{I had to add these lines to my .htaccess, maybe it will work for you}

 

# turn off register globals and magic quotes

# PHP 4, Apache 1.

<IfModule mod_php4.c>

php_value magic_quotes_gpc 0

php_value register_globals 0

php_value session.auto_start 0

</IfModule>

 

# PHP 4, Apache 2.

<IfModule sapi_apache2.c>

php_value magic_quotes_gpc 0

php_value register_globals 0

php_value session.auto_start 0

</IfModule>

 

# PHP 5, Apache 1 and 2.

<IfModule mod_php5.c>

php_value magic_quotes_gpc 0

php_value register_globals 0

php_value session.auto_start 0

</IfModule>

Link to comment
Share on other sites

error_log just displays errors which were produced in previous server.

It means error log is not being updated

 

It's also possible that your PS files/folders do not have proper CHMOD permissions. In my experience, when I moved PS folders the permissions for some folders and files had been reset automatically. This resulted in a white screen similar to yours, after enabling the PHP display errors - the site returned error 500 (internal server error). Then I restored the permissions and the problem was solved

Link to comment
Share on other sites

Hi jberezhnoy

 

I added following code in htaccess file but no change?

 

# PHP 5, Apache 1 and 2.

<IfModule mod_php5.c>

php_value magic_quotes_gpc 0

php_value register_globals 0

php_value session.auto_start 0

</IfModule>

 

What should be the right file permissions?

Link to comment
Share on other sites

It has a 500 internal server error. Did you adjust the config file when you moved it to a live server?

 

Yes. i have corrected config file that is why i can use backend.

If it is config error it must be same for backend and front-end

Link to comment
Share on other sites

Hi jberezhnoy

 

I added following code in htaccess file but no change?

 

# PHP 5, Apache 1 and 2.

<IfModule mod_php5.c>

php_value magic_quotes_gpc 0

php_value register_globals 0

php_value session.auto_start 0

</IfModule>

 

What should be the right file permissions?

 

Hi,

after you've added the above to .htaccess your back-office should remove the error message re magic quotes/global register (only if this trick worked), if not - you may try to find help from your hosting provider (and check their FAQ section if it exists).

 

By default the CHMOD permissions for folders is 755 (rwx r-x r-x), for files 644 (rw- r-- r--), for .htaccess file I have - rw- rwx rwx

PrestaShop can require writing permissions for specific folders, but if your problem is really with permissions default CHMOD permissions should help to start the website (later you can adjust them for PrestaShop needs)

 

P.S. do not forget to set CHMOD 755 for your PSfolder: http://yourdomain.fi/presta/

Edited by jberezhnoy (see edit history)
Link to comment
Share on other sites

Yes Bro. i already have changed this line. But i can't see any error.

When i turn it on i was able to see one file permission error in backend which i corrected then.

But no error at all in front-end...

 

1) maybe try to use another theme (the PS 1.5 default one). When I try to browse your site and enter some URLs (e.g. index.html), the site redirects me to ../index.php?controller=404 This probably means that CMS is actually in a working state, but there are other problems (theme related?). By the way from which version you have upgraded to 1.5.X ?

2) create another folder on this website, download PS 1.5.17 (or which one you are using) or even better 1.5.2 and install it using another DB (or another prefix) and check if it works with the default settings. then maybe you (or we) could be able to understand the problem roots (if it's with permissions or other stuff)

Edited by jberezhnoy (see edit history)
Link to comment
Share on other sites

Yes. this i think is best idea. i must first try fresh install.

Thanks mate.

 

I'll tell if i am successful or not

 

sure but I would try to switch to default theme first. your site seems to be operational. e.g. I do not receive page not found if i go to

presta/index.php?controller=contact

but server returns no no content (possibly DB is empty or corrupted?)

 

In any case - good luck and share your news ))

Link to comment
Share on other sites

Yes. these type of problems can come. But in prevoius server i must encounter such errors.

Even default theme never works.

Same error blank screen.

 

other suggestions:

1) in BO try to load modules page, if it loads - then try to disable any non-native modules. if the modules tab does not load it can return an error indicating which modules are not working

2) try to rebuild cache with different options ()

Link to comment
Share on other sites

×
×
  • Create New...