I use my personal server as a guinnea pig to push my server administrative skills to the edge and help bleed as much performance out of Drupal. So not even an hour and a half ago I signed up for New Relic and installed their monitoring daemon on my server. And I'm in love. The installation was ridiculously easy that even a novice who is scared of the terminal could pull it off.
I have just migrated my website from WordPress to Drupal, so if you run across any bugs I apologize while I get the kinks figured out. I discovered the hard way Disqus comments do not migrate well, even if its just across platforms and no URL changes.
Drupal Commerce is an amazing open source ecommerce solution; with its foundation in Drupal it can easily contend with the big cookie-cutter ecommerce solution companies. Except for one area - reporting. Drupal Commerce and reporting seem to have missed each other while its growth skyrocketed. I mean, there are ways to build reports and show your store's revenue...just nothing "perfect," in my mind. Let's start with this: Drupal commerce orders have a creation date and updated date.
Free shipping offers are a huge request in Drupal Commerce. Here is how you can use one shipping calculation rule to provide free shipping without making new shipping services or modifying existing ones. Typically tutorials have you create a new "Free shipping" flat rate service that checks if the order is greater than XX and have your other services check if the order is less than XX. That's neat, but sucks if you or your client is just trying to offer a sweet deal for a month.
We've all been there - create this awesome responsive design for a client's website and then you have to try and slap a Facebook Like Box in there..somehow..without breaking your responsive work. Sucks, doesn't it? But it doesn't have to. Using a little jQuery you can cause the Facebook Like Box to re-render on window load or resize allowing it to become responsive versus hardcoded.
Google AdWords provides a tracking code that allows you to keep track of how well your ads are performing - if someone clicks an ad and ends up at the conversion code, the ad was technically a success. Typically you would use this in e-commerce and track order completions.
Facebook Album 2.0.4 has just been released and fixes quite a few issues, hopefully resolving a lot of the little things that were wrong with the plugin.
Missing Thumbnails. There was an issue with smaller images and not having the same number of thumbnails as larger images, which means the plugin was trying to display an imaginary image source.
My Facebook Album for WordPress has one major issue: performance. Each time a the plugin is loaded it polls the Facebook API for a response to parse the photos feed. I am going to integrate the caching method WordPress's RSS widgets use for caching Facebook's API response. By default the cache will set to one day, but I will be sure to add a setting that allows adjustment.
Secondly I want to localize the plugin since there is such a wide variety of users from different countries. I'm going to start localizing the plugin based off of the demographics analytics of the plugin's page.
Web developers have a lot of their plate - not only do we build custom solutions for a specific purpose, but we have to ensure that solution works in every way possible. That means it has to work properly in Internet Explorer, FireFox, Chrome, Opera, and Safari, and that each user has the same experience regardless operating system, screen resolution, and internet connection. Oh! Then through in the thousands of mobile devices. That makes website troubleshooting a large and difficult task.
I'll share a few tips and tricks I've learned to streamline the process.