Move to another Server, same domainname

English forums
21

At least I could install Oxid version 4.8.7 and overwrite all files.
Now I get a red marker that permissions are not OK.
/log - /export - /out/pictures - /tmp
all have 777 recursive set

What more should I do? put the whole shop on 777?

Regards,
Jan

22

Never put the whole shop on 777.
Instead do the following to check correct permissions (they are depending on your server system and addons like suhosion):

In Oxid go to core/oxsysrequirements:
Locate ‘public function ckeckServerPermissions’ and add around line 374 ‘echo $sPathToCheck’.
Code Snippet:
…
$sPathToCheck = next( $aPathsToCheck );
}
// next line shows in Admin Systemhealth the path to possible access rights problems
echo $sPathToCheck;
return $iModStat;
}
Then you can see permission issues in Admin > Service > Systemhealth but only one at a time. So you have check again and again while solving issues step by step.

23

Thanks for the help.

That did not work out, I did not see a directory, after I deleted all data in /tmp I als0 lost all CSS getting just plain html for no obvious reason.

Seems I can install again . . . ., overwrite again etc. etc.

I am getting tired . . .

Regards,
Jan

24

To install any Oxid-Version on my root servers, I set folder/file access rights under Debian with shell scripts, where pathes need to be adjusted to the shop-version of course:

  1. Before Installation:

#!/bin/bash
shop=shop499
theme=azure

SETS PERMISSIONS BEFORE SHOP INSTALLATION

changing directory

cd /home/$shop/www
chmod 777 .htaccess
chmod 777 config.inc.php
chmod -R 777 export
chmod 777 log
chmod 777 tmp
chmod -R 777 out/
cd /home/$shop/www/out
chmod -R 777 media
chmod -R 777 pictures

c h a n g e d i r e c t o r y - uncomment/comment out according to shop version

cd /home/$shop/www/application/
chmod -R 777 views/
cd /home/$shop/www/out/$theme
chmod -R 777 src

  1. After Installation:

#!/bin/bash
shop=shop499
theme=flow

RESET PERMISSIONS AFTER SHOP INSTALLATION

c h a n g e d i r e c t o r y

cd /home/$shop/www
chmod -R 644 .htaccess
chmod -R 644 config.inc.php
chmod -R 777 export
chmod 777 log
chmod 644 log/.htaccess
chmod 777 tmp
chmod 644 tmp/.htaccess

c h a n g e d i r e c t o r y next section commented out w/Debian, keeps 777

cd /home/$shop/www/out
chmod -R 777 media
chmod -R 777 pictures

c h a n g e d i r e c t o r y according to shop version

cd /home/$shop/www/application/
chmod -R 755 views
cd /home/$shop/www/out/$theme
chmod -R 777 src

NOTE: Some statements are redundant in step 1 and 2 for post ex adjustments - e.g. if you need to run script 2 only.

25

Thanks Earlybird,

my main desktop is linux so I know my way with bash, use it on the server as well for setting permissions.

For now it will have to wait, there are other customers that need to get service.

Kind regards,
Jan

26

I found this in german
forum.oxid-esales.com/showthread.php?t=27094

So I changed the server-settings to apache-handler / mod_php and see in phpinfo that mod_rewrite is loaded.
Oxid however does not see it . . .

Regards,
Jan

27

I have found the cause.

If you have an ubuntu-server then:

install apache mod_php

in php.ini find:

disable_functions = pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl

Comment this out:

;disable_functions = pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl

Thanks to another opensource project where this is being checked, I found that the moment the functions are no longer disabled, Oxid started as it should.

Regards,
Jan