Possible Bug Pro 6.3.7 - Can't load Pro

Beta
#1

I have a site which needs to run in it’s own folder but display from the root domain.

This is possible in WordPress by setting the WordPress Address (URL) to a different location to the Site Address (URL).

In this way the WordPress files are stored in a folder but the site runs through the root.

Just set up a new site to do this as we are replacing portions of a web based application with a WordPress front-end.

Everything is working as expected however loading cornerstone fails as it loads it from the root rather than the folder.

image
image993×176 7.81 KB

Trying to load Cornerstone results in the below:

image
image906×466 11.6 KB

#2

Looks like user error on my end. Seems like adding something to the custom path in the Cornerstone settings makes it work.

The custom path seems a bit odd they. I first tried adding the path to my WordPress install which didn’t work but adding any random name into the “custom path” did the trick.

By default it showed a placeholder “cornerstone” in the path. After I simply typed out cornerstone into the custom path Cornerstone started working on the site.

Not sure if that is how it is meant to work but at least it is work.

I am also able to remove this from the custom path and Cornerstone is working without the path so not really sure what is going on.

#3

Sounds similar to a permalink saving issue. Did you have anything custom in .htaccess? What is your permalink structure for this site? Cornerstone in general can have issues if your homepage isn’t WordPress, or you have fancy routing. So I’d like to have that addressed better.

1 Like
#4

@charlie can you tell me more about the permalink saving issue please as I have a persistent reoccurring permalink issue with just one of my Pro sites. thought it was hosting related but interested to find out if this is related?

#5

The htaccess has the default WordPress rules + a bunch of stuff from the legacy site. (Don’t think it will affect the WordPress rewrites though or at least it doesn’t seem to impact anything in the wp-admin or front-end.) Initially I attempted to resave the permalinks a fews times which didn’t seem to help. After I save a “path” in the cornerstone settings then things started working however after I removed the name I saved Cornerstone continued to work.

The name “path” is a bit misleading though as you can’t actually add a path in there. It just allows you to edit the name that appears in the path when you use cornerstone.

The WordPress install is completely new / fresh install. The primary home page is WordPress. I have the WordPress index.php in the root with the require changed to point to the folder WordPress is in.

require dirname( __FILE__ ) . '/wp/wp-blog-header.php';

Besides the above it is essentially a fresh install. Everything seems to be OK now.

#6

@scotbaston Is the permalink issue with loading the Cornerstone App? If so it’s possible. What do you mean by reoccurring? How does the issue go away? By permalink saving, I mean that when saving a permalink it usually triggers WordPress to make updates to links elsewhere. Even if nothing changed.

I can definitely look at changing the setting to be an actual path too. Thanks for bringing this up!

1 Like