Cause: It is hard to learn.
Why: When asking for how to do, the answar is "Use this module" or a link to a guide for Drupal 5 or 6, or simular.
comparison:
I am driving in my car and can´t find the way, i stop to ask where to find that street.
If Drupal, the answar is: Get in your car and drive.
Those who know Drupal, are they afraid, that others will learn?
I need to build a site which will keep track of website projects. I'd like a resource library for each project to store assets/docs and a system by which if either me or my other developer makes a code change we can log it which will then trigger an email to the other of us to check and tick a 'code change tested' box just so no mistakes are made without the other one of us catching them (this has come about from a bitter experience).
I don't want anything quite as big as open atrium - just basic workflow, file manager and task manager.
This could just be me, but I just tried to upload a tar.gz 7.0 file and got the following error when I tried to upload it to my server:
VIRUS DETECTED(PHP.EXPLOIT.CVE_2011_4153-2 Found)
I downloaded the Zip file and it went through fine. either my servers AV is jacked up or we have a virus in the install bits. Not sure who to contact about this, so I thought I would throw it out there.
Sorry to post here but this forum is obviously well-trafficked.
I'm looking for the Drupal sites implemented for the most impressive sounding companies or brands ( particularly those likely to be well-known in Europe ).
I am also looking for examples of large scale multi-site ( as in Drupal multi-site ) implementations within companies or without.
And also sites designed to handle very high peak loads.
Id love to have my mind changed on this, but I personally dont see any place for github or other version control for the types of sites that I make and maintain.
Im a bit of a version control newbie but I do use it at my job, where I do mainly front end coding. I use drupal for freelance projects that I do outside of work. I use a fair few contributed modules but I dont create my own modules or write extensive php or javascript. As most of my changes are therefore in the database I cant really use the diff feature of version control.
I also dont make sites with any hardcoded links. With the pathologic module, when I move my site all I have to do with flush the cache and all the paths update to what they should be. This means I can duplicate the site's files and database (changing the database name) and keep working on the new one, leaving the old one as a backup. I find this is a good way to make backups as they are working sites. So if I run into an issue down the line I can 'go back in time' and see if this problem always existed or if it was caused more recently and so must be due to a change ive made.