More onion drupal development blog
Usually when you try to uninstall a field-based module you're confronted with the following error message:
[module] is a required module and can't be disabled. Reason: Field type(s) in use - see Field list
In this blogpost I'm showing you how to uninstall such a module anyway (deleting all the stored data).
This week I've finally found the core of several issues that I've had in the past. Are you using install-profiles or features? Then this bug is likely to have affected you too.
Recently I came in a situation where I wanted to extend all entities of a specific type (payment) to reliably provide (and store) an additional property. At first glance this seems like a no brainer: simply use hook_entity_* to save/update/load the property to or from the database and that should do it. Turns out it isn't … and there is a lot to learn about how entities work in D7.
Lets take a look at a specific example.
A few weeks ago we've released our first public open-source version of Campaignion. It's a tool that helps non-profits and NGOs with online campaigning, fundraising and digital marketing. In this blopgost we'll explain some of the technical background and how it works.
As the title suggests we have Drupal hosted behind a reverse proxy. Usually this doesn't matter a lot, but there are few things like IP-blocking or oauth that need to know some data about original request. Namely that's: The client-IP, whether the request was issued via HTTPS and the server port. Here is how to achieve that.