Revo 2.2.4-pl Manager broken (JavaScript)

Hi Opengeek, I can confirm that I've been working on getting the correct paths in the config file! Immediately after a successful install it wasn't working (404 error). (additional long story including deleting everything and doing it over several times, and doing standard installs several times, then comparing lots of things)

Some details: the manager is moved out of the incoming web path, and the solution for the config "URL" part seemed to be to create a subdomain pointing to the directory with the manager. The connectors are also relocated on this subdomain URL. This change, applied to the config file allowed the site operation to go from 404 not found, to launching the sign in, which opens the text version of the manager.

Have I made sure -all- the references are correct? As far as I am able to determine, I've made that effort, but I'm new enough I could easily have missed some small detail. I'm assuming first of all I might have missed something. comparing actual paths, to path statements in the config, everything seems correct (paths vs directory tree) and seems to work to a degree since the script is able to navigate the URL through the subdomain and launch the manager - partially.

I will make another pass through every config on the site...

Thanks!

Make sure your connectors directory is on the same subdomain as the manager.

Hi Opengeek, yes the connectors are on the same sub-domain, but a different directory, and is so noted in the paths and the URLs part of the config. file.

I've run into a lot of weird and irregular problems upgrading to 2.2.4 as well... hard to reproduce. One heavy-handed fix of mine was to do a full backup of files + database, then do a clean install of 2.2.4, then copy in the assets I needed, re-install all of the components I needed using the package manager, then import the database from the corrupted version of 2.2.4.

SOLVED! For me anyway... Thanks to another thread and comments by "anso" about where to make changes in the database to the modx_compress_css and modx_compress_js settings. (change from '1' to '0'. It was a question and description by "calamander" that sparked a 'maybe this will work...'

Easily made the changes, forgot to clear cache, site didn't work.
Logged out, cleared the cache manually, logged back in and the manager now works! Finally a working advanced install!!!

This is verification that weeks spent studying the paths in the configs for mistakes was searching in the wrong places for errors that weren't there. Could have used a pointer back then... To a newby the obvious isn't always immediately obvious.

Perhaps the official instructions for the "advanced install" needs a few holes plugged?

Particularly, regarding how to configure complicated paths. It would seem almost mandatory to manually make this change in the database when a complex advanced install is being attempted. Or better yet, add a function during the install to make this setting correctly in the database automatically when required.

The final testing of the install should also test whether or not the manager is able to operate relative to these 'hidden details'.

Just to be clear... I am not complaining! This is some of the most amazing script work I've encountered, and it has "quality" written all over it. I know there are lots of contributions out there that made it what it is. Thanks to all!

Thanks to Opengeek for the info about a requirement for the connectors and the manager to be on the "same" sub-domain! I don't know why that is true yet and the instructions where I read about using sub-domains made no mention of this detail. I accidentally had it right only because I thought that would be easier and probably good enough in the security department. Plus some comments, including one from Bob, indicates quite openly that in Revolution your manager and connectors can be "anywhere"... or did I miss a sentence clarifying this???

On to the fun stuff.
Larrybqd