Moving my site to 20i

[mhsuffolk]

I have found 20i's support team very helpful and responsive. I am trying to move my 1.0.9.7 shop over to 20i.
They have given me a temporary URL to test shop with. The shop works perfectly on my current useless hosts package, but I want to ensure it works on 20i before I hit the button.
The temporary URL throws a "Too many redirects" error. 20i's support have tried a few things but are baffled. They want me to contact yourselves. I am convinced it is the configure files that are at fault. Here are both files from both installations. I would be grateful if you could peruse them please and feedback from anybody who has gone through this process with 20i.

Current Host Shop

Code: Select all

// set the level of error reporting
  error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED);  
  
  const HTTP_SERVER = 'https://www.*****.co.uk';
  const COOKIE_OPTIONS = [
    'lifetime' => 0,
    'domain' => 'www.*****.co.uk',
    'path' => '/',
    'samesite' => 'Lax',
  ];
  const DIR_WS_CATALOG = '/';

  const DIR_FS_CATALOG = '/home/*****/public_html/';

  date_default_timezone_set('Europe/London');

  define('DB_SERVER', '127.0.0.1');
  define('DB_SERVER_USERNAME', '*****');
  define('DB_SERVER_PASSWORD', '*****');
  define('DB_DATABASE', '*****');

Current Host Admin

Code: Select all

// set the level of error reporting
  error_reporting(E_ALL);
  
  const HTTP_SERVER = 'https://www.*****.co.uk';
  const COOKIE_OPTIONS = [
    'lifetime' => 0,
    'domain' => 'www.*****.co.uk',
    'path' => '/*****',
    'samesite' => 'Lax',
  ];
  const DIR_FS_DOCUMENT_ROOT = '/home/*****/public_html';
  const DIR_WS_ADMIN = '/*****/';  

  const DIR_FS_ADMIN = DIR_FS_DOCUMENT_ROOT . DIR_WS_ADMIN;
  const DIR_FS_BACKUP = DIR_FS_ADMIN . 'backups/';
  
  const HTTP_CATALOG_SERVER = 'https://www.*****.co.uk';
  const DIR_WS_CATALOG = '/';
  const DIR_FS_CATALOG = DIR_FS_DOCUMENT_ROOT . DIR_WS_CATALOG;
  
  date_default_timezone_set('Europe/London');

  define('DB_SERVER', '127.0.0.1');
  define('DB_SERVER_USERNAME', '*****');
  define('DB_SERVER_PASSWORD', '*****');
  define('DB_DATABASE', '*****');

20i Temporary URL Shop

Code: Select all

// set the level of error reporting
  error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED);  
  
  const HTTP_SERVER = 'https://**********.stackstaging.com';
  const COOKIE_OPTIONS = [
    'lifetime' => 0,
    'domain' => '*********.stackstaging.com',
    'path' => '/',
    'samesite' => 'Lax',
  ];
  const DIR_WS_CATALOG = '/';

  const DIR_FS_CATALOG = '/home/virtual/vps-0583ae/7/********/public_html/';

  date_default_timezone_set('Europe/London');

  define('DB_SERVER', '127.0.0.1');
  define('DB_SERVER_USERNAME', '****');
  define('DB_SERVER_PASSWORD', '*****');
  define('DB_DATABASE', 'phoenix-********');

20i Temporary URL Admin

Code: Select all

// set the level of error reporting
  error_reporting(E_ALL);
  
  const HTTP_SERVER = 'https://*****.stackstaging.com';
  const COOKIE_OPTIONS = [
    'lifetime' => 0,
    'domain' => '*****.stackstaging.com'
    'path' => '/*****',
    'samesite' => 'Lax',
  ];
  const DIR_FS_DOCUMENT_ROOT = '/home/virtual/vps-0583ae/7/*****/public_html';
  const DIR_WS_ADMIN = '/*****/';  

  const DIR_FS_ADMIN = DIR_FS_DOCUMENT_ROOT . DIR_WS_ADMIN;
  const DIR_FS_BACKUP = DIR_FS_ADMIN . 'backups/';
  
  const HTTP_CATALOG_SERVER = 'https://*****.stackstaging.com';
  const DIR_WS_CATALOG = '/';
  const DIR_FS_CATALOG = DIR_FS_DOCUMENT_ROOT . DIR_WS_CATALOG;
  
  date_default_timezone_set('Europe/London');

  define('DB_SERVER', '127.0.0.1');
  define('DB_SERVER_USERNAME', '*****');
  define('DB_SERVER_PASSWORD', '*****');
  define('DB_DATABASE', 'phoenix-*****');

[burt]

Check the .htaccess file URLs in the staging site.
Check that there is nothing in there that still refers to the live site.

I note you have some type of URL rewriter in the live site.
I am not familiar with the mechanics of this particular URL re-writer, but it might do something in the htacces

[ecartz]

I don't think it is possible to have a URL rewriter without doing something in .htaccess or httpd.conf

If you continue to have problems, I would find it reasonable if you would PM me the configure.php files from the temporary shop with the DB_ entries removed but the other **** stuff unredacted. Or if you prefer, burt would probably find it reasonable as well (but you may want to ask him first).

Either way, you should also include the .htaccess from the root of the shop. If you can find configuration for the URL rewriter (perhaps in the module configuration?), that might help too.

You might ask 20i support for the logs showing the redirect loop. For example, that might look like

example.com 301
example.com/ 301
example.com/index.php 301
www.example.com/index.php 301
example.com 301

There's probably timestamps and other information as well. I call that a loop because it starts and ends with the same URL.

[mhsuffolk]

Success!!!
Thank you for your suggestions and offers.
What I did. 20i has Phoenix in their quick installs. So I installed a new copy and used the configure files from that as templates to amend mine. This line existed in my admin config which is not in the new version, perhaps that was the issue.

Code: Select all

const DIR_FS_ADMIN = DIR_FS_DOCUMENT_ROOT . DIR_WS_ADMIN;

My htaccess had a section forcing http to https, I think that might also have been an issue.
There are several lines in the htaccess relating to the URL rewriter but they were not the issue and still work fine.
I must endorse 20i for their speedy and attentive support even though I had to work out the problem myself.

[burt]

TY for coming back with the answer, this will be useful for future similar queries when more move to 20i.