As a web developer and CTO with over 15 years of experience, I am passionate about building profitable small SaaS products and pursuing Go-to-Market strategy for them. My areas of expertise include high performance, networking technology and APIs, SRE, automation using Puppeteer.js, web scraping, and SQL databases.
When you have core "image" field on your node type and you want to output "title" (or "alt") of this image just under the image thumbnail as text - you can use imagecaptionformatter module for that. But only in the case when you don't need another image formatter in place
When you create Drupal code for 7 years, it's easy to mistakenly assume that you know everything regarding such basic things as theme_preprocess_node() and drupal_get_form() functions. And that is a wrong feeling. Today I've discovered that you shouldn't mix these functions! The bug description: I was
We are now developing big Drupal 7 project where users have profiles with lots of fields. They also have a node tied to them ("My story") which is created during registration. Initially, these were "edit my profile" and "edit my story" links which were leading to a huge forms where
uc_file module that allows selling files in Ubercart is definitely not perfect in terms of API, but it is a nice piece of functionality. We've just finished creating one e-book store which has product-import feature. Each product has multiple formats (pdf, epub, rtf) - some products can have pdf+
In Drupal 7, it's easy to show calendar (ui.datepicker) date selector to user. (it's not hard in Drupal 6, too - but in d6 you need to enable http://drupal.org/project/jquery_ui to get the calendar, I think) You just write several lines of js code, and
In Drupal 7, the direct access to entity fields (CCK in d6) is different. In Drupal 6 you write: field_yourfield[0]['value']; ?> in Drupal 7 you have to write: field_yourfield[LANGUAGE_NONE][0]['value']; ?> (this is a way suggested by
