This forum is for less technical discussions about the Drupal project, not for support questions.

can drupal incorporate into our current website?

our store is currently using Shopsite. all pages are rendered in PHP. Shopsite is an ecommerce software which lacks features such as comments, ratings or votes. these are the things i would like to have.

is it possible that i could have some kind of php snippets included in my pages?

any suggestion or input is greatly appricated.

question on etiquette re: "Assigned to"

What does it mean to the Drupal community if I follow up on a bug or feature request and choose to "assign" the issue to myself?

My own interpretation is that this means that I'm submitting a patch that addresses the issue and I will continue to follow up and modify my patch based on feedback for other users. However, I also notice that most of the uses who show up as "Assigned to" have access to commit changes to CVS for core or that particular module.

Drupal Integration with Democracy In Action

Hi -

I'm looking for information or examples on integration between Drupal and Democracy In Action's Campaign Advocacy tool.

Specifically we want to know if anyone has developed a module or something else to transfer data about user actions on DIA back into Drupal.

Another way of framing it potentially (I'm really new to this) Is there an API spitting back who did what from DIA to Drupal?

Any help, experience, examples would be greatly appreciated.

Thanks!

Linda Setchell

PHPTemplate vs Smarty

Hi - I'm new to Drupal and don't mean to start a war over this.

Curious to hear opinions of why use one or the other of these template engines.

Performance, logical organization of templates, and ease of maintenance are my primary considerations.

Thanks
Graham

We can do better than this...

As a software engineer, I find it very odd, when someone logs a bug, for someone else to say, "Well, gee, I don't experience that, so you must be wrong." Software bugs are like that -- if they happened all the time for everyone, it's likely the developer would have found it first. Bugs usually result from boundary conditions -- circumstances which occur infrequently because they represent some kind of extreme -- and by definition, most of us drive down the middle of the road.

The next level of inappropriateness is to try to decide democratically whether a bug is actually a bug. So people keep piling on -- "I don't see that, either" -- until someone declares victory, because only one or two people actually see the problem, whereas a whole raft of people don't. People who drive down the middle of the road will always outnumber the pedestrians on the shoulder.

The final mistake is to change the state of a bug to a support request, or shift it to someone else's project, because you don't experience it -- especially when anecdotes of similar buggy behavior keep cropping up. It's like pulling the batteries out of a carbon monoxide detector because it's annoying, and it only goes off occasionally.

These things happen here all the time. As users, we are told incessantly (but appropriately) to search the database before filing a bug or support request. What one often finds when searching is not one thread on the subject, but many. Very often, those threads are curtailed by people who autocratically declare the issue dead, "because I don't experience the problem, and I have been using this for a long time." A short time later, someone else sees the same problem, and running across the closed issue, opens another one.

Segmentation Fault with 4.7

Hi all,

since I upgraded to Drupal 4.7 one month ago, my system go screwed 2 times with an Apache "exit signal Segmentation fault".

I´ve searched the forum for help, but seems that no one have a solution to this issue.

http://drupal.org/search/node/child+pid+exit+signal+Segmentation+fault+%...

From the wikipedia:

Pages

Subscribe with RSS Subscribe to RSS - General discussion