Shared to Reseller hosting issues

1

Hi Folks

I’ve recently upgraded my shared hosting account to a resellers account.
Unfortunately my host has encountered problems with the migration bit.
The splitting of the core and public files has resulted in real issues my end.
There was much back and forth during which time…
All my sites went down
I temporarily reverted to the shared platform
Each site was again re-allocated its dedicated CPanel on the reseller platform.

All well and good on the front end now.
But now I’ve lost access to the backends.
When I attempt to run ‘setup’ I get as far as the ‘Installation Summary’ page which shows the bottom three entries thus:

Checking if /home/user/public_html/mysite/ directory is writable: Failed!

Checking if /home/user/public_html/mysite/manager/ directory is writable: Failed!

Checking if /home/user/public_html/mysite/connectors/ directory is writable: Failed!

I have checked permissions and core paths. All appear good.

I found this article from 2011, but decided against acting on it on account of its age and assumption that that particular bug would have been crushed by now.

In fact, on further reading, it indeed has been.(addendum)

When I run ‘test_config.php’ I get

Incorrect path to core

which seems obvious and yet is a mystery.

re Reseller platform:
It appears my host has adopted public_html as the root for each sub account
ie
home/site-name1/public_html/assets, connectors, cgi-bin, manager
home/site-name2/public_html/assets, connectors, cgi-bin, manager
home/site-name3/public_html/assets, connectors, cgi-bin, manager

Re previous shared platform:
Each site had its differentiating container folder
ie
public_html/site-name1/assets, connectors, cgi-bin, manager
public_html/site-name2/assets, connectors, cgi-bin, manager
public_html/site-name3/assets, connectors, cgi-bin, manager

so when on the resellers platform, in effect does away with a folder…
specifically the container folder.

I don’t know if this is common practice with hosting or even significant,
but it seems paths are at the heart of this problem.

My host is still onto it, but I was hoping (in the nicest possible way) others have encountered a similar situation.
Any pointers would be useful I’m sure.

Many Thanks

My setup:
Mac High Sierra 10.13.6
PHP 7.4.2
MySql 5.7.26

2

You mention that the path to the accessible part of each site is home/site-name/public_html/.

If the core is still being stored outside the main site directory what is the path to the core folder for each site?

These docs might help:


Have you cleared the cache on each of the sites?

3

Hi Andy

Yes, cleared all the caches.

the path to the core folder is
home/sitename/core

but where the path and site name folders were set up in the shared account
as follows:
public_html/amazon.com/assets, connectors, cgi-bin, manager

the reseller platform is set up thus:
home/amazon/public_html/assets, connectors, cgi-bin, manager

Think it’s sorted now!
It appears after much careful fine-tooth combing and almost going blind, that the one click migration
(judging by the timestamp record of the various site migrations…one per minute…sometimes two) automation didn’t take into account at all the split folder nature of Modx security.
That, couple with truncated folder names for the dedicated CPanels left me adrift for hours.
To boot my host simply didn’t read my series of small pamphlets of my findings and suggestions of what the next step might be.
I knew (well kinda) it was a path issue.
Basically there were remnants of the old paths interspersed all over the place.
The four config files all required amending.
However once I resolved one, it was just then a case of side-by-side comparison tweaking.
I looked at the two articles you suggested and there were one or two hints that helped me on my way for sure.
I didn’t help that I was so unfamiliar with a resellers account setup.
I was expecting something a bit more self-explanatory if I’m being honest.
But there we are.
We live and (hopefully) learn!

Many thanks

1 Like
4

I’m glad to hear you have it all working. Thank you for reporting back with your findings.