right bottom corner of a block in IE

sorry for bad english :)

Mistake at display of the right bottom corner of a block in IE.

Use this code in css to prevent it:

.block .content .w2 {
/*background: url(down-bl.png) no-repeat 0% 100%;
position: relative;
padding: 5px 5px 6px 5px;
left: -2px;
top: 0px;
*/
background: url(down-bl.png) no-repeat 0% 100%;
position: relative;
left: -2px;
padding: 10px;
overflow: hidden;
height: 100%;
overflow: visible;
}

Drupal.org missing "submitted by" line?

Am I just imagining it or is the "submitted by" line missing from nodes on drupal.org?

It also seems to make the node text flow awkwardly around the terms list. The "submitted by" line shows up fine on comments still though.

trying to understand patches and compatibility

i was looking at the documentation for patches here:

http://drupal.org/node/22568

can someone explain, if you see a patch for a module has been fixed and the last message says 'applied'; where was it applied to?

for example, the event module has things that were fixed recently,
http://drupal.org/project/issues/event

Drupal Developer Releases

Drupal Developer Releases

Though I've only been working with Drupal for about two months, I do have nearly ten years experience developing and testing (mostly web based) applications professionally.

When I recently took a contract to build a complete website in a short period of time, I began researching CMSs (which I've never before used). After about two weeks I narrowed the field down to Drupal, Mambo and TikiWiki. After more in depth research into these three solutions, it was obvious that Drupal was the most developer friendly and "least hacked" of the three, and I began to use it.

Because version 4.7 is soon to be released, I decided it would be wise to build my site based on the latest code. Since there are no development releases, I simply did what I assume most others do and used the CVS HEAD branch. This worked fine for a few weeks until about last week when I came across an apparent incompatibility with PHP5 and some of the code in one of the core modules. Since my Drupal base was derived from a non-tagged set of code, I now have no real way of reverting to a 'working version' as I have no idea when this incompatibility was introduced. Now I could stop all that I'm doing and investigate it, but that's not a very efficient way to work. In fact, I generally would never build upon a dynamic code base, but since that's all that was available for post 4.6.3 code, I didn't have another option. I'd like to propose the idea of developer releases for Drupal. I'm sure most of you know what I'm talking about already, but the idea is that relatively stable code bases that are not yet ready for the final release can be tagged so that testers and developers have reference points to work with.

drupal module can't "call home" (notify drupal.org)

Drupal module can not notify drupal.org this time.

I've set "Drupal XML-RPC server" (at drupal module settings page) to http://www.drupal.org/xmlrpc.php

I see the following errors in log:

Failed to notify www.drupal.org at /xmlrpc.php: Didn't receive 200 OK from remote server. (HTTP/1.1 301 Moved Permanently).

What's wrong?

Patch submitters and developers list

Hi everybody!

I don't know if this is the right place for this,
maybe admins can move this to the right place.

I'm the maintainer of the video.module.
Last days I get a wondeful contribution by LukeLast
which sent me patches for adding a lot of new features
to my module.

Then I sayd him to get a cvs and commit the changes.
Then this was the reply.

Pages

Subscribe with RSS Subscribe to RSS - Deprecated - Drupal.org infrastructure