I've been mulling this over for awhile, especially with Drupal 7's new database abstractions, and having Fields in core. When you're building a new web application with Drupal and an existing database, when should you use Nodes as the basis of your site? I have a database that I already keep information in, so I don't *need* nodes, but nodes have some nice features (especially the "revision"). Is it common practice to integrate legacy databases into Drupal as nodes, or as their own system of modules?
I'm playing around with the D7 Field API and wondering how conditions, ordering and grouping (if possible) with fields will work.I read the documentation, but couldn't find anything except some appearances of "fieldCondition" and "entityCondition" which sound like the right direction, but didn't really help me.
Can somebody point me the right way?
I have just installed this module to add some tags to my articles.
There are a lot of choice; but I cannot find any information about this module especially how to use it.
Could you recommend a source in which I can find information about nodewords especially users who do not know what is its features. For example, I do not have much information about some words like Abstract, Canonical URL, Copyright, Revisit after, Robots.
For some of them, I know what is it; but I do not know how it work or how much is it important etc
I have used Drupal in my native language. I downloaded translation package. I've used it;
But especially for extensions, there are some texts which have not translated yet.
I have two choices for them.
Translate Interface
Downloading and editing PO Files
Is there any difference between Translate Interface and PO Files?
If so, what is the difference?
Which one I should use?
This was made for D6, how do you do that on D7 since in D7, Views Relationship Groups menu drop down doesn't have a "Content" option; the node option there only shows author field as reference.
Anyone care to describe the steps for D7 or rewrite it.