node path of custom content type redirects to front page

By d8v15 on 6 May 2016 at 23:47 UTC

I've been looking for even the slightest solution for 3 days but nothing.

After creating a new content type with no issue, I then create a node from that type. This also has no issue.

But when I try to access that content path by clicking the link in the content admin list (or accessing url directlty), the page 302 redirects to the home page - ive tried as admin and anonymous using pathauto, clean urls, and default query string urls. I cant find a cause or solution. Searching online - i find nothing.

I've attempted to create additional new content types. no issue until i access the node content path with the same fate.

If i create a node from an existing custom content path, everything works fine.

Help appreciated.

Comments

Is rewrite_module is enabled

arulraj commented 7 May 2016 at 02:45

Is rewrite_module is enabled in apache?

Rewrite is enabled.

d8v15 commented 7 May 2016 at 15:17

Rewrite is enabled.

Anyone? I mentioned that the

d8v15 commented 7 May 2016 at 20:03

Anyone? I mentioned that the issue is for new nodes created from a new content type. If i create a node from an existing (custom) content type, the node path works. Please advise.

Are you using aliased paths

Sam Moore

he/him

Sandy Hook, CT

commented 10 May 2016 at 17:02

~~This topic really doesn't belong in the Upgrading Drupal forum - perhaps Post Installation would get you more answers.~~

Are you using aliased paths or the node number (/node/nid)?
Also, are you sure these are 302 redirects? If so, you'll need to figure out where they're coming from; perhaps an error in your .htaccess?

============================
Resonetrics: Better Tools for Building Brands
http://resonetrics.com
http://technologyformarketers.com
http://kittenassociates.org
http://www.linkedin.com/in/sammooreatresonetrics

The issue happened during

d8v15 commented 10 May 2016 at 14:10

The issue happened during upgrade to 7.43

node number path is being used.

I was able to track down that drupal_goto is being called (which explains the 302 redirect - as this is default).

I installed a plugin that blocks on redirect. When I go to the node number path for the content, I see the content title only. At the bottom of this I see the page is attempting to redirect. Is there a field issue?

Any new content type I create

d8v15 commented 10 May 2016 at 18:25

Any new content type I create - then add content for, I get this error.

Any existing content type I had - that I add content for, it works fine.

Useless...

d8v15 commented 26 May 2016 at 17:07

Useless...

I seem to have found the issue - there is a page_manager module associated with url /node/%node under the pages tab.

In here you will find rules stating e.g. which content types to show.

Realistically, this redirect could be called from anywhere including code. I assumed the drupal redirect function was being used as the redirect was using 302.

For anyone else that comes across this issue ..