Sitecheck URL is invalid

24,544 Posts

BobRay Reply #21, 8 years ago

Are you seeing the Status value in the error message now, or at least the word "Status" (you may have to clear the cache)?

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

89 Posts

geordiechris Reply #22, 8 years ago

Yes I have cleared the cache…

and yes I'm seeing the Status value…

ie.

Checking MODX_CONFIG_KEY.inc.php
 
Checking all paths in main config file
 
ALL PATHS OK!
 
Checking all URLs in main config file
 
MODX_ASSETS_URL: (/assets/) is invalid Status: 404

Thanks Bob

24,544 Posts

BobRay Reply #23, 8 years ago

OK, try this at line 245 of the core\components\sitecheck\model\sitecheck\pathcheck.class.php file. Comment out the MODX_ASSETS_URL line as shown below:

     /* Check All URLs in config.inc.php for validity */
     $urls = array(
          'MODX_BASE_URL' => MODX_BASE_URL,
          'MODX_CONNECTORS_URL' => MODX_CONNECTORS_URL,
          'MODX_MANAGER_URL' => MODX_MANAGER_URL,
     //   'MODX_ASSETS_URL' => MODX_ASSETS_URL,
          'MODX_SITE_URL' => MODX_SITE_URL,
     );

That will skip the ASSETS_URL test and should allow the other tests to be performed.

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

89 Posts

geordiechris Reply #24, 7 years, 11 months ago

Apologies for the tardy response…
Worked a treat Bob
Many Thanks

24,544 Posts

BobRay Reply #25, 7 years, 11 months ago

I'm glad that worked for you. I wish I could figure out why the error is reported on some systems. I've never been able to replicate it.

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

463 Posts

chrisandy Reply #26, 7 years, 10 months ago

I've just run into this error whilst moving a site to another server. The site is down with a 500 error. I used site checker and this was the initial output...

Looking for MODX root directory

MODX Root Found!
______________________________________________________________________

Checking MODX_CONFIG_KEY.inc.php

Checking all paths in main config file
ALL PATHS OK!

Checking all URLs in main config file
Warning: strpos(): Offset not contained in string in /home/sites/***************/public_html/core/components/sitecheck/model/sitecheck/pathcheck.class.php on line 595

MODX_BASE_URL: (/) is invalid
Warning: strpos(): Offset not contained in string in /home/sites/***************/public_html/core/components/sitecheck/model/sitecheck/pathcheck.class.php on line 595

MODX_CONNECTORS_URL: (/connectors/) is invalid
Warning: strpos(): Offset not contained in string in /home/sites/***************/public_html/core/components/sitecheck/model/sitecheck/pathcheck.class.php on line 595

MODX_MANAGER_URL: (/manager/) is invalid
Warning: strpos(): Offset not contained in string in /home/sites/***************/public_html/core/components/sitecheck/model/sitecheck/pathcheck.class.php on line 595

MODX_ASSETS_URL: (/assets/) is invalid
Warning: strpos(): Offset not contained in string in /home/sites/***************/public_html/core/components/sitecheck/model/sitecheck/pathcheck.class.php on line 595

MODX_SITE_URL: (http://www.***************/) is invalid

______________________________________________________________________

Correct URLs before continuing

Ending SiteCheck

...so I commented out all those checks and ran it again. This time I got as far as...

Checking Encoding and Collation for all text columns Fatal error: Call to a member function fetch() on a non-object in /home/sites/******/public_html/core/components/sitecheck/model/sitecheck/pathcheck.class.php on line 431

Any ideas would be much appreciated.

Web site design in Nottingham UK by Chris Fickling http://www.chrisficklingdesign.co.uk

24,544 Posts

BobRay Reply #27, 7 years, 10 months ago

This ridiculously complex query above that line is failing:

"SELECT CCSA.character_set_name FROM information_schema.`TABLES` T,
               information_schema.`COLLATION_CHARACTER_SET_APPLICABILITY` CCSA
        WHERE CCSA.collation_name = T.table_collation
          AND T.table_schema = '" . $dbase . "' " . "
          AND T.table_name = '" . $table . "';";

Are you using a MySQL database? If so, what version of MySQL?

Repairing all tables in PhpMyAdmin is worth a try, as is manually deleting all files in the core/cache directory.

You may be able to see other issues if you skip the character set test. You can look in the DB to see if the tables and text fields match the character set in config.inc.php.

FWIW, 500 errors are most often caused by an issue in the .htaccess file or a plugin that's not compatible with the current version of PHP or MODX. A problem with .htaccess (e.g., Rewrite Base) could also explain the invalid paths. PHP directives like php_flag in .htaccess that may work on one host can cause a 500 error on a host that doesn't allow them.

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

463 Posts

chrisandy Reply #28, 7 years, 10 months ago

When a Modx install / migration goes wrong - it's usually my fault. I had...

host:

instead of

host=

...in core/config/config.inc.php

Sitecheck helped me track it down. I'm still getting the path errors in Sitecheck but site is running fine.

Web site design in Nottingham UK by Chris Fickling http://www.chrisficklingdesign.co.uk

24,544 Posts

BobRay Reply #29, 7 years, 10 months ago

I'm glad you got it sorted.

I wish I could track down the cause of the path errors. I can't duplicate the problem.

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

4 Posts

dennis-f Reply #30, 7 years ago

Quote from: BobRay at Jun 12, 2016, 05:15 PM

I'm glad you got it sorted.

I wish I could track down the cause of the path errors. I can't duplicate the problem.

I don't know if this helps but: I have the same error on my remote Server, but locally everything works fine. I have a local vagrant instance with an exact copy of the remote files and remote database (excluding only cache folders). I'm using MODx 2.5.6 btw.