If probably goes without saying, but we are Drupal experts and not GDPR lawyers. We have tried our best to outline our understanding of the new requirements and how this impacts Drupal sites - this page does not in any way constitute legal advice.
Drupal's batch API processing is awesome and offers two great benefits: -
Building a batch routine in a custom module requires a minimum of 4 function including the batch function call: -
So this is strictly Drupal, but it's a useful post which will hopefully help others who may have this problem.
I use PHPStore or Aptana Studio 3 for developing in Drupal. Aptana is a great IDE in my opinion. Occasionally it gets into a mess and hangs every time I launch it and Windows reports and Aptana Studio 3 is not responding - very annoying.
The simple fix is to remove the .markers file from the project which could be causing the issue. This file (as far as I know) contains break points, so you'd need to re-add them to your project.
Again, this is really a note to myself, but here is a query to import CSV data on the server: -
LOAD DATA LOCAL
INFILE '<path_to_file>'
INTO TABLE `<table_name>` FIELDS
TERMINATED BY ',' LINES TERMINATED BY '\n'
IGNORE 1 LINESN.B. You have to make sure the structure is already in place.
Here are a couple of useful tips for making development and debugging easier. I've written this primarily as a note for myself but maybe it's prove useful to others as well.
To force PHP to display any errors in Drupal on screen instead of just 500 server error pages add these lines: -
ini_set('error_reporting', E_ALL);
ini_set('display_errors', 'stdout');
To up the memory limit add this line: -
ini_set('memory_limit', '64M');
Today I needed to apply a CSS class and a "usemap" attribute to an imagefield in Drupal. So I created my MY-FIELD-IDENTIFIER.tpl.php file (based upon field.tpl.php) and made a couple of minor changes: -
Today I was presented with a problem. Data wasn't being saved to one particular field in a Drupal custom module's table. Looking into the client's custom module code everything looked OK. Looking at MySQL the table matched OK too.
