The new Garland / Minnelli theme (née Themetastic) from Drupal 5.0 is one of the main visible improvements over 4.7. However, not all sites are ready to make the jump to 5.0 as soon as it's ready, which should be very soon now, so why not use Garland on 4.7 ?
The new Drupal-based community site for PHP-GTK is up at http://www.php-gtk.eu.
Technically, this is pretty much a plain Drupal 5.0
Beta 1 Beta 2 RC1 RC2
site, using the new Garland theme without custom changes
besides a much needed fix, and a site-specific
module for things like useful referer counting and the PHP-GTK dev geolocation
A first sight, it looks like the
in Drupal 5.0 is missing an important function: the ability
to theme the page displaying the list of books, normally
found at www.example.com/book
Zend Studio is a convenient environment to code in PHP, even though it is not currently possible to use it for integrated debugging of PHP-GTK code: its php completion and file management, and phpdoc integration make it very useful for the PHP-GTK environment too. However some settings are necessary to ease its use, due to the specific extensions typically used by PHP-GTK programs:
phpw files for applications, and
gladep for Glade files storing UIs.
The official site for PHP-GTK is obviously a natural must for anything related to PHP-GTK 2.
However, its resource pages links indiscriminately to fresh and useful material, and to obsolete intro-level information for the now-defunct PHP-GTK 1.
Here is my selection of current useful resources for PHP-GTK 2, for the developer who already read the advertorials, installed the environment and ran the intro tutorials, and now wants to actually create with the extension.
As many other developers of e-commerce sites using Drupal, I've had to solve the problem of integrating the "front-office" store maintained in the ecommerce module with the back-office data like the actual invoicing matching legal requirements, tax documents, product ordering from suppliers, and so on, and I've had to choose a toolkit for this.
Until recently I had been using Delphi with XML-RPC to upload content and remotely monitor my sites, but I was looking for a cross-platform solution, and one that would preferably have sources available. Using Kylix for other projects and it *does* work, even with SOAP and remote data stores, but the level of support and lack of upgrades from Borland regarding it left me rather skeptical about using it for new projects. And this was not even taking into account the fact the XML-RPC for Delphi and Kylix is a poorly supported Open Source project. So what ?
Having non-HTML-skilled contributors input content on a Drupal site seems to often lead to invalid HTML tag soup being input. And even with seasoned coders, a HTML input error happens sometimes, which can be a problem until someone fixes the post.
So I figured I'd force valid HTML from user input, and here is the proof-of-concept
valid_node module: it will force any node to be saved as a XHTML fragment.
Some months ago, I noticed Arnab's blog note about the importance of the
sequence table, albeit in a multisite context.
This table also needs special care when copying a drupal site: logically enough, its rows contain the name of the prefixed tables for which a sequence is maintained. For instance, this means that, if you defined the source site as using, say,
oldsite_ as a prefix, the name field on the row for the next nid will look like: