When you try to set up a local development environment from a drupal dump which includes just the code base and the database without the Drupal files folder you will run into the issue of missing files. Drupal would think that it still has all the files in the Drupal files folder and would create links / process images as usual. This would however lead to a lot of unexpected errors in a lot of unexpected places. If you really do not care about the content in these files and want to recreate the missing files here is how you do this.
If you run into a Drupal 7 site with file system access and you would want to change the password of a user in the system programmatically, here is an easy way to do this.
If you run into a problem with your microphone not working in Skype in Ubuntu 15.04 on a Lenovo B40-70 laptop then this solution would work perfectly fine for you. Even if your laptop or ubuntu versions don't match and you have same symptom then this fix could very likely work for you
If you frequently have to set up git version control system for existing projects then you would very likely run into the problem of having to remove files, which should not have been in git, from git after they were added. Running a git rm will only delete the file from the head and the file would still remain in the repository. This may be alright for small files but this could be troublesome for large files as these would unnecessarily bloat the git repository. But don't worry git being a 'swiss army knife' of version control systems there is a solution to delete files permanently from both your local and remote git repositories.
On one of our recent Drupal projects we came across an issue where the file browse button was not triggering the file selection dialog in IE10 in Windows 8. The problem was diagnosed to be the result of jquery not getting the click event from the button. The site was using jquery 1.44 and this problem is supposed to be fixed in later versions of jquery.
Those of you who have been regularly visiting this site would have started seeing small changes in the site related to how it integrates with social media sites. I have been experimenting on how to increase the interactions between us and the visitors on the site as well as between visitors on the site. This is still a work in progress but I wanted to share with you some of the things I have changed on the site
The first thing that you have to do when you want to improve something is to understand what is it that you are trying to improve. To do that you have to have some way of putting that thing which you are trying to improve into a quantity you can measure and get some kind of numbers on. This is applicable not just for your web traffic or social media marketing efforts but with anything (or rather most things) you do in your business.
In the last year or so we have been in the process of transitioning from a small business to a medium size business. With over 50 people in the rolls it was time we moved away from a bunch of people working with and around a single individual to a more structured organizaiton. As part of this transition we have been looking to change gears on our marketing initiatives. For the first time since we started our business we now have a business development team and we have active business development activities going on.
If you are in the habit of running queries directly on your production database to generate custom reports then you will run into the requirement of having to connect to your Drupal database on the Acquia cloud hosting. One of our clients wanted to do this and this is how we got this working for them.
When you host your Drupal site on the Acquia cloud your site resides on a set of different VPSes that runs Varnish, Apache, MySQL and memcache. Additionally you have your staging server, your development server as well as your production servers - all of them being VPSes.
On one of our recent projects we had an issue where the Drupal site search was not working. There was a search.html file present in the home folder to handle a Google custom search page outside of Drupal. Since the filename was not the same as the drupal search path we did not expect it to be the cause for the Drupal search to not work.