Sitecheck URL is invalid

94 Posts

William A Reply #11, 8 years, 1 month ago

So i am trying to get modx up and running on homestead (laravel). And i am getting this issue with sitecheck as well.

It's an nginx server. I guess my problems has more to do with that than modx/sitecheck. But i thought i'd just mention it here to see if someone have tried getting modx to run on Laravel Homestead. I get the modx 500 error screen, and can't reach the manager either.

If someone has an idea, i welcome it. If i stole the thread, i am sorry.

/w

--------------------------------------
www.williamastrom.se

24,544 Posts

BobRay Reply #12, 8 years, 1 month ago

MODX cloud is on nginx, so it's certainly possible. Is this a new install of MODX or a moved site?

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

94 Posts

William A Reply #13, 8 years ago

Quote from: BobRay at Mar 08, 2016, 12:35 AM

MODX cloud is on nginx, so it's certainly possible. Is this a new install of MODX or a moved site?

I use laravel homstead, and i curl the latest modx version, unzip it and run setup. I get to this page http://modx.app/setup/index.php?action=complete and it shows me the modx 500 error indicating it could be permission issues. I have tried setting folders to 755 and files to 644 however, and nothing.

/w

--------------------------------------
www.williamastrom.se

94 Posts

William A Reply #14, 8 years ago

From the nginx log:

2016/04/13 08:51:49 [error] 25683#25683: *365 FastCGI sent in stderr: "PHP message: PHP Notice: Undefined index: primary in /home/vagrant/Code/modx.dev/public/core/xpdo/om/mysql/xpdomanager.class.php on line 462
PHP message: PHP Notice: Undefined index: unique in /home/vagrant/Code/modx.dev/public/core/xpdo/om/mysql/xpdomanager.class.php on line 462" while reading response header from upstream, client: 192.168.10.1, server: modx.app, request: "GET /setup/index.php?action=install HTTP/1.1", upstream: "fastcgi://unix:/var/run/php/php7.0-fpm.sock:", host: "modx.app", referrer: "http://modx.app/setup/index.php?action=summary"

--------------------------------------
www.williamastrom.se

24,544 Posts

BobRay Reply #15, 8 years ago

Is there anything useful in the MODX Error log (in core/cache/logs)?

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 #16, 8 years ago

Hi Bob

I'm glad I found this very recent thread…
I have just come across this this morning…

Despite 'Verbose Output' and 'Attempts to fix errors' unchecked the
following results page seems very sparse to me…

These Tests Do Not Require MODX
____________________________________________________________________

Looking for MODX root directory

$configFile = /home/*******/core/config/config.inc.php
 
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

MODX_ASSETS_URL: (/assets/) is invalid
______________________________________________________________________

Correct URLs before continuing

Ending SiteCheck

Also the results are not formatted…
ie no colour coding on the outcome or anything else.
Are these issues you may have come across before?
That said, the site and manager do indeed seem to be functioning correctly otherwise.

My server is running PHP 5.5

Any pointers would be appreciated

Many Thanks
Chris

24,544 Posts

BobRay Reply #17, 8 years ago

Are you using the current version of SiteCheck (1.0.7)? You can tell by the name of the zip file.

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 #18, 8 years ago

Yes I am Bob.
So does that list look too short to you?
And should the css always kick in on the test results page?
Nothing in the error log...

24,544 Posts

BobRay Reply #19, 8 years ago

Because of the way SC runs, the CSS is often missing in the case of an early error.

It's definitely too short, though.

Try this, in the file core\components\sitecheck\model\sitecheck\pathcheck.class.php find these two lines (around line 313):

    $msg = $this->modx->lexicon('sitecheck_correct_urls');
    $this->helpers->quit($msg);

Comment out the second line:

    $msg = $this->modx->lexicon('sitecheck_correct_urls');
    // $this->helpers->quit($msg);

Save the file, then clear the site cache.

See if that gets you past the error.

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 #20, 8 years ago

That sorted it Bob.
Thank You.

The only error I'm still getting now is this…

MODX_ASSETS_URL: (/assets/) is invalid

I've tried your suggestion from a previous post on the subject
by replacing:

$this->helpers->output(8, $key . ": (" .
   $url . ') ' .
   $this->modx->lexicon('sitecheck_is_invalid'),
   false, true, 'sc_red sc_block sc_indent2');
$this->totalConfigErrors++;
$this->totalErrors++;
$urlsOk = false;

with

$this->helpers->output(8, $key . ": (" .
   $url . ') ' .
   $this->modx->lexicon('sitecheck_is_invalid') . 
   ' Status: ' . $status
   , false, true, 'sc_red sc_block sc_indent2');
$this->totalConfigErrors++;
$this->totalErrors++;
$urlsOk = false;

...but without success.

Is this an error that absolutely needs correcting or can I simply let it lie?

Many Thanks