Drupal 6.x

Hi,

I am looking for a module (an input filter) that allows to embed content from a CCK field into another node (e.g. node body, or another CCK field that runs through input filters). I do know for sure that there was such a module a couple of years ago, but I can not find it.

What I need is similar to the 'image_filter' module: target the source with a certain syntax (like [image:184 option_foo]), just working with image fields and other field types.

Thanks for any pointers!

I'm getting the following error from boost

Boost Can not write to file-system
Directory /home/barcelona/public_html/cache credentials - Permissions: 0755. Owner 502. Group 502.
Your credentials - Group ID: 502. User ID: 502. Current script owner: barcelona.

As I understand it those permissions & credentials are all as they should be. Why else would boost not be able to write?

• Advisory ID: DRUPAL-SA-CONTRIB-2014-128
• Project: OG Menu (third-party module)
• Version: 6.x, 7.x
• Date: 2014-December-17
• Security risk: 14/25 ( Moderately Critical) AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:All
• Vulnerability: Access bypass, Information Disclosure

I'm afraid this is a 'can you help identify a module' type question. Sorry if this is the wrong forum for this type of inquiry...

I use a Drupal 6 site and we have AddThis enabled for social sharing, ie. a toolbar that displays on the side of each node through which users can share the node to Twitter, Facebook, LinkedIn etc.

Hi everyone, I have been looking for a solution for a small problem I have with one of the Drupal sites I manage and the problem is related with blocknode block, I do have banners and those banners should redirect users to an external link, the issue is that when I click on the banner, it opens up a new tab with the website I want to redirect users and the same tab too! (My site, were the banners are located). To better understand the problem, please try yourself clicking on the left side banner (the white one) at:

There are a lot of D6 and even D5 sites in the wild which can't necessarily be upgraded in a timely manner. Historically, Drupal is not famous for creating workable upgrade paths from one point release to the next for various reasons, not the least of which being the drastic differences in how core is written and the contrib environment that grows up around these changes. This adds considerable expense to upgrading an old site, because you essentially have to spec the whole thing out fresh, build, deal with migration, and finally go through user training all over again.