See the Mailing lists or Drupal Issue queue. There are also various working groups on groups.drupal.org

Cron Error with Duplicate entry

I am using Drupal: 4.4.1 on Linux2.4.20 . I customized the notify module.

Full path issue

Hello,

I need to create a module which will upload a ZIP file into files/images directory unpack it and do some other strange things :) Here is a problem I've encountered with:

I'm using $file = file_check_upload('image_file'); and $file = file_save_upload('image_file', $path); functions for upload, where 'image_file' is a name of file upload input and $path stores 'files/images' directory. Then, I use $zip = zip_open($filename); where $filename must be a FULL file name.

Filter on blocks and mission statement stops simple code

I don't think this feature is needed, and in fact its just an annoyance because people who run a drupal site should at least learn not to paste random code from the net into their site. Advance css code is especially needed for nice formatting of the sections of your site that appear on every page, and as a result css like text-align and margin being blocked is very annoying. Can we have this changed before the next release?

Why isn't SESSIONS emptied?

Why doesn't the SESSIONS table ever get emptied? It seems that, if left to its own devices, the SESSIONS table would keep growing and growing. Surely that's bad? Shouldn't all the "old" sessions be removed on every cron cycle?

Personally, I manually empty my SESSIONS table every week or so (I make sure no users are logged on before I empty the table).

(If this turns out to be a bug then I'll submit a proper issue... but I wanted to discuss it here in the forum first in case it's not a bug)

Thanks,
Jack

form_render problem when themeing elements?

In trying to theme a textfield element, I noticed that while my theme was being invoked at

$content = theme($elements['#theme'], $elements);

but the standard output from theme_textfield was reaching the browser.

form_render invokes the theme, but as $elements['#printed'] hasn't been set, form_render then invokes the standard theme for the element type

  if (!isset($elements['#printed'])) {
    $content = theme(($elements['#type']) ? $elements['#type']: 'markup', $elements);
    $elements['#printed'] = TRUE;
  }

Adding $element['#printed'] = TRUE after the element is themed seems unpredictable: if $elements['type'] is form, then the form element does not get rendered. I've special-cased that, and pages appear to be working (and looking at theme_form it's obvious why) but this seems strange.

I was about to file this as a bug, but decided to check if I am misunderstanding how element themeing is supposed to function. The Forms API Reference is ... vague ... on the matter. I could see having to set #printed in the theme function, but the way themes are invoked makes this impossible.

node

Is there a way to get rid of the node:
yourname.com/node/2323

?

Or at least change the node name to something else? because with url changer won't work.

thanks. :)

Pages

Subscribe with RSS Subscribe to RSS - Deprecated - Drupal core