[SOLVED ]Running Console Loads Front-End

[aComAdi]

Hi,

We use RockMigrations (an older version) to run migrations for our various modules on client sites. We execute the migrations using the Tracy Console, which works for nearly 100 websites.

However, intermittently, we encounter a problem when attempting to run scripts in the console. Instead of executing the script, the console either loads the front-end of the website into the output panel or, in one case, even opens the front-end in the current browser window, causing us to leave the CMS.

We have attempted to identify the issue:

1. It does not appear to be server-related, as some of these sites run on our own shared server with identical settings (Fast-CGI, PHP 7.3 or 7.4).
2. It does not seem to be related to the ProcessWire version (3.0.240).
   1. We have disabled finished.php, init.php, and ready.php with no change.
   2. It does not seem to be related to the config files of ProcessWire (which can differ in structure between various versions).
   3. We have disabled markup regions to rule them out.
3. We have completely deleted Tracy and reinstalled it.
   1. Tracy settings are 'standard', i.e., out of the box.
4. This issue has occurred on installations where the console previously worked, but after an update (both ProcessWire and Tracy), it stopped working.
   1. Tracy: 4.26.34
   2. PW: 3.0.240

Notably, on the affected sites, this issue occurs even when running no script (i.e., it’s not the script causing the problem).

Could you please provide guidance or a solution to resolve this issue?

Thank you for your assistance.

Is there any setting that we are missing? Or what else could be the cause of this behavior? It keeps us from updating our moduls, we have to update them manually respectively.

Any help/tip is appreciated.

[aComAdi]

Never mind. After looking at the instances where it happens from a different light, we have figured it out. It's redirects in the root of the site. The sites all have preceeding brand selection sites. My bad.

[aComAdi]

OK. So it's not solved per se. I reopened the ticket.

When we create new sites for existing clients, we usually install those in a subfolder, e.g.:

/new2024/

So far this has never been a problem. But it seems with  Tracy v4.26.34 we can now not run the console commands anymore, because it will load the existing site in the root folder. I tried renaming index.html in the root folder, but then I just get a 404 error.

Is there a setting in config or Tracy settings which I can use to ensure, the commands are run from the subfolder (/new2024/), where Processwire lives?

 

[adrian]

Hi @aComAdi - sorry for the issues you've been having, but thanks for narrowing things down. I think it's likely this commit: https://github.com/adrianbj/TracyDebugger/commit/4b35ecddfb184cd7a04c3614fb40ac72d0a62874 to fix this issue: https://github.com/adrianbj/TracyDebugger/issues/96

I have never set up a site in a subfolder in such a way that an AJAX call to "/" doesn't work as expected, so I can't really test this, but I think the latest version should fix things for you.

@Jonathan Lahijani - can you please make sure this new version doesn't affect the issue you had with bootstrapped files?

 

[aComAdi]

Hi Adrian,

4.26.35 did seem to have resoved this issue. Tested it on one of the affected sites successfully. Thanks a lot for the very fast turnaround.

[adrian]

On a side note, I would really recommend you upgrade your PHP version - 7.x hasn't had security updates for quite some time now!

[Jonathan Lahijani]

On 7/31/2024 at 10:26 AM, adrian said:

@Jonathan Lahijani - can you please make sure this new version doesn't affect the issue you had with bootstrapped files?

@adrian No issues with latest version.