Drupal 6.x

Hi,

I'm looking for a Drupal developer in Sydney with good experience in OpenAtrium, PHP, MYSQL to fix our slow intranet site built on OpenAtrium 1.0 Beta. This site is running very slow and we are not sure what is causing this. The environment setting is:
• Web server: Apache/2.2.14 (Ubuntu)
• Database: MySQL v5.1.41
• PHP v 5.3.2-­‐1
• Open Atrium v1.0 Beta8
• Drupal v6.16

I'm the end user of a small website (see www.billherring.info). I'm in need of a cost-effective backend manager to handle occasional code writing and other troubleshooting issues as they arise. I have technical questions I may have from time to time. I've had good success in the past on this forum getting a "handyman" and may need to do so again. I would like to find a personable, down-to-earth person to be responsive when I need him/her. I don't anticipate needing much help but need someone in my corner when I do.

Hi

I am looking for drupal themer from India.

Please try to contact me so that i can discuss about the project.

Thanks
Drupalsign

Hi there,

I noticed my site is outdated (Drupal 6.19).

I was wondering if I need to upgrade to Drupal 6.34 first before I upgrade to the newest 7.34.
Or can I just go ahead and upgrade to 7.34?

Is there anything I should keep in consideration so I don't do this wrong?
Any links as to where can I start off with Drupal 6.19 to upgrade it to 7.34?

Thank you much in advance!

I imported content with Feeds and everything works fine except nodes (calendar event) are created but not visible. I need to open every single node and just save them.
Does someone ad this problem (and solution) for this? Or any idea how to massively open/save nodes?

Thanks for any ideas!

We've got a page in Drupal 6 Views 2 that displays organization contact information, mostly custom fields except for the Contact Display Name. Every so often (more and more lately, seems pretty random, sometimes more than once a day) the view breaks and it only displays the Contact Display Name. Clearing caches restores the view. I initially thought it occurred after a Drupal update but apparently this is not the case, and I don't know what triggers it.