Deprecated - Drupal core

I was tearing my hair out trying to figure out why requests to my main site were getting remapped to my alternate site. This happened after enabling the Gallery module in the alternate site. It appears that module stomped all over my htaccess file:

# BEGIN Url Rewrite section
# (Automatically generated. Do not edit this section)

RewriteEngine On

RewriteBase /baja/

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d [OR]
RewriteCond %{REQUEST_FILENAME} gallery\_remote2\.php
RewriteCond %{REQUEST_FILENAME} !/baja/index\.php$
RewriteRule . - [L]

RewriteCond %{THE_REQUEST} \ /baja/d/([0-9]+)-([0-9]+)/([^\/\?]+)(\?.|\ .)
RewriteCond %{REQUEST_FILENAME} !/baja/index\.php$
RewriteRule . /gallery2/main.php?g2_view=core.DownloadItem&g2_itemId=%1&g$

RewriteCond %{THE_REQUEST} \ /baja/v/([^?]+)(\?.|\ .)
RewriteCond %{REQUEST_FILENAME} !/baja/index\.php$
RewriteRule . /baja/index.php?q=gallery&g2_view=core.ShowItem&g2_path=%1 $

That would explain the problems. So modules are allowed to edit major config files?! Without any indication of which lines go with which modules? Who made the changes? When? Yikes!

I am currently writing a customized theme based on php, and I use drupal_get_form to produce the html for placing the search on my header.

What I don't like is how many div tags come out here. This is the output (formatted for ease) from the drupal_get_form:

<form action="/drupal5/?q=search/node"  method="post" id="search-theme-form">
 <div>
  <div id="search" class="container-inline">
   <div class="form-item">
    <input type="text" maxlength="128" name="search_theme_form_keys" id="edit-search-theme-form-keys"  size="15" value="" title="Enter the terms you wish to search for." class="form-text" />
   </div>
   <input type="submit" name="op" id="edit-submit" value="Search"  class="form-submit" />
   <input type="hidden" name="form_token" id="edit-search-theme-form-form-token" value="6522b80a5f3b4974689e309f883e3d55"  />
   <input type="hidden" name="form_id" id="edit-search-theme-form" value="search_theme_form"  />
  </div>
 </div>
</form>

I am currently writing a customized theme based on php, and I use drupal_get_form to produce the html for placing the search on my header.

What I don't like is how many div tags come out here. This is the output (formatted for ease) from the drupal_get_form:

<form action="/drupal5/?q=search/node"  method="post" id="search-theme-form">
 <div>
  <div id="search" class="container-inline">
   <div class="form-item">
    <input type="text" maxlength="128" name="search_theme_form_keys" id="edit-search-theme-form-keys"  size="15" value="" title="Enter the terms you wish to search for." class="form-text" />
   </div>
   <input type="submit" name="op" id="edit-submit" value="Search"  class="form-submit" />
   <input type="hidden" name="form_token" id="edit-search-theme-form-form-token" value="6522b80a5f3b4974689e309f883e3d55"  />
   <input type="hidden" name="form_id" id="edit-search-theme-form" value="search_theme_form"  />
  </div>
 </div>
</form>

I have an error after upgrading from 5.2 to 5.3. The server is running Apache/PHP5.

There is no error on my test system which is running Apache/PHP4.

The message on the PHP5 server sounds like

warning: array_merge() [function.array-merge]: Argument #1 is not an array in /srv/www/vhosts/oekoportal.net/subdomains/test/httpdocs/includes/menu.inc on line 415.

The line in MENU.INC is

Hello, I am using simplemenu, so I said to myself it would be nice to have 1 admin menu operating, so the clients would not get confused.I think I remember seeing, in Bryght.com's installation they removed the admin menu9from the left side block) thus letting the customer control the site using the simple menu functions. I tried to remove the admin menus by disabling it in the menu options, but this removed the menu items from simple menu(it seems that simple menu just relocates the admin menu options)

Hi,

I apologise if this has been covered before, but I am having trouble finding information on it. If someone could point me in the right direction I would be grateful.

I have been attempting to theme the output of the aggregator module. I have followed instructions at http://drupal.org/node/31598 to override the item listing. I want each item to be listed inside the list item tags. Not a problem, I have done that and got the following in my template file:


/* Function from: http://drupal.org/node/31598 */
function tribe_aggregator_page_item($item) {

$output .= "