Drupal 7.x

Hi
I am trying to create a new theme based on Omega 960 for Drupal 7. For the menus I am trying to use a variation of the sliding doors technique to include one level of submenus. You can see the site at www.letsgoagile.com

Hi,

We are looking to move an existing site to Drupal 7. I've been reading Drupal 7 Module Development and came across the Chapter 6 where it is apparent developers can create their own entities.

Objective

We have a need to implement a Wiki with Drupal, and we need the content from the Wiki to be searchable in Drupal. We would like to understand what the best practices are for such an implementation.

Background

We have a corporate Intranet site where a variety of different people will be entering and updating content. Content access will be limited based on the user's role. (For example, Engineering will not be able to access the Sales portion of the Wiki.)

Options

We are currently aware of a couple of different options for implementing/interfacing a Wiki with Drupal.

1. Implement MediaWiki and the "MediaWiki Auth Bridge" module. This will allow users to log into Drupal and still post and read content in MediaWiki. The downsides of this appear to be that 1) the theming will be completely separate in MediaWiki (since it is a different program), 2) the content will not be stored within Drupal (though we could make MediaWiki share a DB with Drupal), and 3) the Wiki pages will not be searchable within Drupal without the use of an external search engine like Apache SOLR. Are these assumptions correct?

Hello, I am developing my first module module in Drupal 7.

module name is "testposter".

Code of .info file is below

**********************************************************
name = Test Poster
description = "Details of testposter module "
core= 7.x
files[] = testposter.module

configure = admin/config/testposter
**********************************************************

After activating this module when I click on Configure link for this module it redirect me to admin/config but not on admin/config/testposter

Running Centos 5.5 and latest PHP 5.3.4, and trying to install Drupal 7 pre-release which apparently requires XML/DOM

PHPInfo() shows in the "Configure Command" portion "......'--without-mysql' '--without-gd' '--disable-dom' '--disable-dba'". From this I would presume that DOM is disabled. Cannot find any disable line in php.ini or elsewhere that refers to DOM. Is there an easy way to re-enable DOM? Thanks

Hello all,

My company's website is www.bciincorporated.com. Its a small company Im fairly new and since I'm young, motivated, hardworking, and quick (at least they seem to believe so!) I was elected to learn about SEO and start helping the website build pagerank. We have use Drupal I believe it is the newest version (not sure how to verify Drupal was implace when I got here) I have used drupal to add alot of the hardware and software pages in the past and was able to do so quickly which is probably one of the reasons I was promoted to take on SEO and what not. We also use Fatcow.

Here is the issue
The old URL is www.barcodeadvantage.com both sites exist. the old URL takes you to the new content but does not redirect. And guess what it gets worse the non www version for both URL's exisits also and does not redirect and shows new content. If I make changes or add new pages and content it is also created for all URL types. I was informed this hurts SEO.

I know if i google "site:bciincorporated.com" i get 1,100 results - which means 1,100 indexed pages correct? (website.grader.com shows 789 pages indexed by google)
"Site:barcodeadvantage.com" returns 295 results.
I believe the actual site only has under 200 pages (not sure exactly) So in I guess what is happening is google is index all these differnt URL and the site is losing bigtime in SEO.