By stpaultim on

Having trouble understanding what is going on. I am lead to believe, that Drupal 7 by default is set to provide for auto population of "machine names" when creating content types. In a recent install, this was working as expected for me.

However, I recently installed a updated version of Drupal 7 and this is not happening.

I'm mostly concerned, because of other problems I'm having with fields that MIGHT POSSIBLY be connected. See: http://drupal.org/node/1603682

I currently trying to figure out the particular circumstances under which this behavior happens, but am hoping that someone else might have a clue.

Thanks in advance for any help.

⋅ Categories: Drupal 7.x

Comments

stpaultim’s picture

stpaultim commented

Ok, I think the problem is a difference between my development installations using Aquia Dev Desktop and my production sites on a server at:

http://www.webhostinghub.com/

Here are two screenshots. The first is of "manage fields" for Product Display Content Type on my local Aquia Dev Desktop installation.

http://www.lexlake.com/tim/one.jpg

This second is the same page on the remote host.

http://www.lexlake.com/tim/two.jpg

Any reason to expect this kind of difference between the two installations?

Tim

ayesh’s picture

ayesh commented

If you turned off JavaScript executing in your browser you will see that both sites are now working same.

Can you make sure that this happens when caching is disabled?(and after flaring cache)

What's new and changing in PHP 8.4

stpaultim’s picture

stpaultim commented

I'm using firefox and turned of JavaScript, which did make both sites act like image two.jpg I believe that the correct behavior is what is seen in image one.jpg .

How do I disable caching?

I believe that whatever is causing the above problem, is also causing this problem:

http://drupal.org/node/1603682

stpaultim’s picture

stpaultim commented

After struggling for an entire day to understand this problem. I simply set-up a new account with a hosting service listed on Drupal.Org.

Was able to install Drupal 7 cleanly and quickly and problem disappeared.

Apparently, this problem was related to the specific set-up of the web host I was using.