New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When running in a subdirectory, CP has the wrong link to create a page #977

sarahkyler opened this Issue Sep 22, 2016 · 5 comments


None yet
5 participants

sarahkyler commented Sep 22, 2016

Expected behaviour

Click the button, select the fieldset, go to create the page

Actual behaviour

After selecting the fieldset, the create link is missing the /sub/ part of the url.
So instead of:**sub**/cp/pages/create?fieldset=fieldset
It tries to go to:
and subsequently fails.

The rest of the site and CP are completely functional with the subdirectory setup. (except editing pages, but that's another issue: #937 )

Server configuration

Operating system:
CentOS release 6.8 (Final)
Linux 4.6.5-x86_64-linode71

Web server:
Apache 2.2.31

PHP version:
PHP 5.6.25

Statamic version:
(has existed in previous versions though)

Updated from an older Statamic or fresh install:

List of installed addons:

I apologize if this is a duplicate issue, searching gave me nothing.


This comment has been minimized.


jackmcdade commented Sep 26, 2016

Did you set your site_root in your index.php file?

$site_root = '/**sub**/';

This comment has been minimized.

sarahkyler commented Sep 26, 2016

Yes, the index.php, .htaccess and control panel settings are all set up correctly. It's just this one link that doesn't work.


This comment has been minimized.

jcohlmeyer commented Nov 9, 2016

I am also experiencing this issue and in addition edit page links do not work unless I set /site/settings/system.yaml locales url to / but this breaks the front-end of the site ...



This comment has been minimized.

mattrock1 commented Nov 9, 2016

I'm experiencing the issue here as well.


This comment has been minimized.


jasonvarga commented Nov 9, 2016

Fixed for the next release.

@jasonvarga jasonvarga closed this Nov 18, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment