Post installation

Hi!

I have some categories with some pages in side. But sometimes there is an empty article with n/a that appears out of nothing. There is no title, no node id, or something else. Anyone a idea?

This is the html I get:


......a correct displayed page.

Hi all

I have had trouble with unusual characters in my articles - probably down to issues in my TinyMCE editor - and unfortunately I now have a whole series of errors in my large number of articles. What would be the most convenient way to search and replace eg "’" for an apostrophe?

I am using MySQL and PhpMyAdmin, but if there is a module that might assist, that'd be great.

Thanks :)

I want to create my index page in Drupal to look like this:
http://www.cottagestocastles.com/

What does it take to build a front page like this?

This is something that has been puzzling me over the past year or so, when we lost all our Google rankings due to a (suspected) algorithm update affecting relatively new websites. After my first experimental installation, all my sites now run Drupal and I never regretted this decision.

The problem is that each page needs to be represented by a single URL and not by multiple ones. This problem exists for all new sites and some may not consider this important, however one of my sites has suffered dearly over the past year. The examples below can help better understand what I am trying to say here.

Homepage

The homepage can be accessed at http://www.example.com, but also http://www.example.com/node. Even though I can't figure out where does Google discovers this (as no links to http://www.example.com/node exist), the issue is that you get a penalty for having this page available using two URLs.

The solution to this is to add a 301 redirect to your .htaccess file which sends all hits to http://www.example.com/node to http://www.example.com.

Taxonomy Pages

On sites with many stories on taxonomy pages which span across multiple pages each additional page is a duplicate. The reason for this is that each (next) page has the same and taxonomy description (which is different if you have nodewords module). It does not matter what the links on the page say.

Hello!

I am using the Drupal core Search, and I need to display the results by catergory (wikipage, blogpost, image) when i use the general search form field (when not using the checkboxes) have been looking to display the results by category, when i search for all.

Through admin, I can only order by date, comments, views or relevance and I've been studying the module code to see if I can modify the SQL queries in any way but to no avail. Is there anyway to catergorise the results? thanks! :)

Over at http://drupal.org/node/88568 I've been researching a way to allow non-admin users to set a node's "athored on" creation date to something other than the current date of submission— basically allowing a non-admin to backdate a node. This can of course be done by checking the box at "access control -> node module -> administer nodes", but that apparently also allows any user (with that permission set) to modify any other user's nodes as well, which is def not what I need. i only want these users to be able to modify their own nodes (not global node admin).

Since i'm not at all familiar with PHP, I thought I could get around it by using something similar to the Actions module's "Touch node creation date" action, except my action would be "Set authored on date" (or similar) and I'd have it fire whenever a particular node type (below) was created.

So does anyone how I could relativey easily create an Action (to be used with the Workflow module) to automatically set a node's "athored on date" to a non-admin, user-supplied field? For instance, I used CCK to create a new node type, and used the standard categories menu to add the following vocabularies to that node type:

• Production Day
• Production Month
• Production Year

Now non-admin users won't actually see the "authored on" option when creating this new node type, either. So what I'd like to do is, when a non-admin user creates this new node instance and click's submit, the Workflow action would automatically set that node's hidden "authored on date" to the concatenation of my custom date fields (which the non-admin can see).