Newly created content types have broken field links in admin [#1906738]

Hi,

The field management links (e.g. edit and delete operations, widget and field type links) and the redirects to field related pages (e.g. "Save and Add Fields" on content type creation) all seem to be set as "//field..." rather than "/field...", causing it to fail when clicked or redirected. This also effects the links on the "Comment Fields" tab.

For example the Field Type link for a field called "field_policy_short_body" looks like: <a id="edit-fields-field-policy-short-body-type" class="ext" title="Edit field settings." href="//fields/field_policy_short_body/field-settings" target="_blank">Long text and summary</a>

If you save a form that should redirect to the field page, such as adding a new content type and selecting "Save and Add Fields", the redirect takes you to www.example.org/fields. However any changes made go through correctly and the content types are usable.

Oddly this issue is only affecting newly created content types and not the existing ones. The newly created content types also don't show up in the Views content type list, however they do show up for users when they go to add content.

I'm currently looking back through snapshot backups to try and locate when this became an issue, however the last update carried out was to 7.17.

I've disabled pathauto, sub-pathauto and global redirect to test whether those were having an effect on it, with no luck.

Caches are disabled and have been cleared out manually (including the APC cache).

Comments

Comment #0.0

Hephaestus CreditAttribution: Hephaestus commented 3 February 2013 at 16:59

Issue summary:

View changes

Fixing code display.

Comment #0.1

Hephaestus CreditAttribution: Hephaestus commented 3 February 2013 at 17:01

Issue summary:

View changes

Spelling.

Comment #1

swentel CreditAttribution: swentel commented 22 February 2013 at 18:46

Component:	field system	» field_ui.module
Status:	Active	» Postponed (maintainer needs more info)

This works fine on latest drupal core. There must be some module or maybe a setting in settings.php fiddling with this. Can you try reproduce it on a plain install ?

Comment #2

Hephaestus CreditAttribution: Hephaestus commented 25 February 2013 at 15:54

Status:

Postponed (maintainer needs more info)

» Closed (cannot reproduce)

(Un)fortunately the problem has resolved itself, on all copies of the site including ones that haven't been touched since the issue became apparent. The only thing I can think of that would effect all sites is the APC cache timing out. I had assumed that the "Clear Cache" button in the admin panel cleared this, as Drush "cache-clear" is unable to clear the user cache if it uses APC, but perhaps not.

Comment #3

Exploratus CreditAttribution: Exploratus commented 14 September 2013 at 02:21

I am currently having this EXACT problem with new content types..

Using Drupal 7.22

Comment #4

Exploratus CreditAttribution: Exploratus commented 14 September 2013 at 02:21

Version:	7.17	» 7.22
Status:	Closed (cannot reproduce)	» Active

Setting to active. Maybe someone else has the same problem?

Comment #5

caspervoogt CreditAttribution: caspervoogt commented 23 October 2013 at 22:11

For me, this is APC-related.

I run APC and the APC module. My settings.php file contains:

$conf['cache_backends'][] = 'sites/all/modules/apc/drupal_apc_cache.inc';
$conf['cache_class_cache'] = 'DrupalAPCCache';
$conf['cache_class_cache_bootstrap'] = 'DrupalAPCCache';
$conf['apc_show_debug'] = TRUE; // Remove the slashes to use debug mode.

Commenting out these lines solved the issue with the field links on the content type for me.

See https://drupal.org/node/2087121. I think that is the same issue. Suggest discussion continue there.