D7 - CCK in Core?

If you're a Drupal developer, you're aware, no doubt, of the coming of D7. One of the exciting changes in D7 is that CCK has been brought into core...somewhat. The changes provide opportunities to do things that were much more difficult to do before, but also, might create a black hole of challenges in the migration space between D6 and D7.

It can be very frustrating to do what seems to be everything needed in order to receive USPS shipping quotes in Ubercart, only to receive There were problems getting a shipping quote. Please verify the delivery and product information and try again. after clicking the button to receive one. Here is a list of the things to verify before throwing anything in frustration!

I was working on a module that uses a query with a few joins to select an appropriate node and then obtain the name of a file attached to it. The file name is then built into a link. Occasionally, clicking on such a link would result in a 404 error. I detest intermittent errors as much as any developer or support tech. It seemed that the common factor with this one was that the files in question had suffixed names, _0, _1 and so on. And therein lies the answer!

Drupal 7 - A Baker's Dozen!

Boiling down the zillion hours of D7 development into a short list of important changes isn't practical, so consider this a starting point rather than a comprehensive list.

In a Drupal view, one of the presentation options for a selected field is to have the field be a link to its node. What if you need the label to also be a link? No problem! Another option is to rewrite the output, so you can manually create the links using HTML, and specify the replacement pattern of [nid] for one. The only problem is that when a field is a link to its node, the URL that appears is the path alias, mydomain.com/my-content, but when using [nid] in a manually constructed link, the resulting URL is mydomain.com/node/##.


Subscribe to RSS - Drupal
©2005-2017 Ayen Designs. Underlying theme by Kiwi Themes.