This forum is for module development and code related questions, not general module support. For general support, use the Post installation forum.

image.module woes: migrated site to new server, can't upload images

The problem: preview or submitting an image upload produces no image - also no php errer. Log says

404 error: images/tmp/tmpthumb_d5d3d1889c7b5aede36427dcd5558b76.jpg not found

The html on the preview page contains the following broken link to the image:

<img  class="image" src="http://www.kerryturner.com/?1840124573" />

Path to convert is correct, all image directories have 777 permissions.

The funny thing is, I developed this site on another server and migrated it to the production server. The code can't be *that* broken since I've already uploaded 100 images on the other server with the same scripts.


What php settings should I check? Is there anything else I forgot? I thought I knew this module.

Mailhandler +4.5

Just wondering how the upgrade from 4.4 mailhandler to 4.5 mailhandler is going, if it will be released soon or anything?

Same with listhandler!

Upgrading module to 4.5?

Hi Everyone,
Quick question, ages ago I developed a simple module for 4.3 and it has been running since. Just for fun I loaded the module into a 4.5 install and tried to access it. Whereas before the module worked fine, now i get a 'page not found' error. Any ideas? Has the way Drupal calls the modules changed?

Thanks in advance,

Geoffrey

Adding audio file support?

Greetings!

I'm planning to convert a mostly static HTML site to run under Drupal 4.5. This site has hundreds of hours of audio in MP3 format. Right now it's all speech (Bible teaching) and no music (yet). I was rather impressed at what could be done with Drupal without any coding. Right now, I'm just typing in links to the MP3 and associated M3U playlist into the body of the node. However, it would be preferable to have special support for audio files so they can be attached to a node and meta information displayed.

To do this, I need a way to associate an MP3/Ogg Vorbis/Speex file with a node such that it has a download link for the file and also a listen/streaming link pointing to an associated .M3U playlist file. Initially associating just one file and it's playlist will be adequate but in the future I'll need the ability to associate two or three files with the same node. These files would be variations in format of the same audio, i.e. an MP3 and a Speex file or an MP3 and an Ogg Vorbis file or possible two MP3 files with different bit rates.

automatic email updates for forums thread and topic comments

Does anyone know how to automatically notify thread participants of new responses by email ?
This would be for forum threads or topic comments.

I noticed that many users don't get to respond to comments because they never receive emails when additional forum comments are made.

This feature is found on Vbullitin and PHPBB. Since Drupal is such a community centric tool, I think we should get the capability working.

Where would be the best place to add this function ? or does something like this exist already ?

Taxonomy Permissions idea

This is my idea (mockup only) for taxonomy permissions:

http://www.construct3d.com/temp/taxperm.htm

The basic idea is to keep it simple and usable, whilst still allowing flexibility.

The select options are:

  1. inherit
  2. no access
  3. read only
  4. read/write

inherit is the default, so permissions are automatically inherited from the term's parent, but can be overridden easily when required. This saves having to explicitly set each term's permissions, especially if the taxonomy tree is large.

no access means those taxonomy vocabularies and terms are not shown anywhere (including menus) and if a user were to type a valid URL, they'd get the usual access denied page. Would this require modifications to the core menu system?

Given that Drupal now supports multiple roles per user, user-level permissions could be accomplished with the same interface. For example, if the admin wanted a single user to have access to a particular term, simply create a new role, assign the user to that role and then allocate the relevant permissions.

Similarly with node-level permissions, if the admin wanted a role to have access to a particular node, simply create a new parent term for that node and assign the relevant role permissions.

In this way one interface could serve all three purposes.

Pages

Subscribe with RSS Subscribe to RSS - Module development and code questions