Crystaldawn.net

I have been busy for the last 6 months or so and havent really been checking on the site. I've noticed that the demos dont work at the moment so I will check into why those are down.

EDIT: Got it all fixed up. It was just a simple permissions problem when I updated apache a couple months back.

UPDATE: This has now been fixed. The auto google key service is back online now. Google thought they would be sneaky and try to break Curl browsers from accessing the key generation API but I've coded a workaround for their sneakieness and it works once again.

The previous method to create google keys has recently changed and my google key generation service doesnt work at the moment because of this recent change. I am updating my service API and it should be working again sometime today. So for now, you have to manually put in your google keys for new installs until the autogeneration api is back up.

Some more pieces of the PHP version of phpGoogleStore Locator have been released. There are now 5 new modules that will eventually be used to put together the Drupal version of PGSL. Currently they dont make up the PGSL installation just yet, but they are still very useful on their own. These are:

Queryable Variables a replacement storage system for Drupal's variable_get/set/del functions. Very powerful, very flexible. This is the storage engine that PGSL will use rather than using it's own tables. This project was part of the original PGSL that was used in the Settings portion.

Parsing API is another extremely powerful module that has become very popular over at drupal.org. It allows module developers to parse things easily using readable code. It provides many functions such as before(), between(), after(), etc. This project was built using the PGSL geocoding engine, PGSL drupal will use this module to duh, do it's geocoding ;)

Module Template System is a template system for Drupal modules. It allows drupal modules to define their own templates that can then be overriden in any themes directory. Drupal 5 lacked the ability for modules to define their own templates so I wiped this up based on the PGSL 3.0 template system. This module is only available for Drupal 5 and thus the drupal 5 version of PGSL will use it. The drupal 6 and 7 versions of PGSL will use the built Drupal template system since those versions of Drupal allow modules to define their own template files.

Drupal Function Override is a SUPER powerful module that I developed to allow COMPLETE control over Drupal. The Drupal hooks system is great, but sometimes it just doesnt allow you to dig deep enough. Using this module we can even re-write how the hooks themselves function. This module has amazing capabilities and will probably be used in PGSL Drupal somehow. I used this module to give Drupal jQuery a compatibility mode so that mootools modules could be built for Drupal. Before this module existed, it was NOT possible to write mootools modules because they would conflict with the built in jQuery installation which was developed WITHOUT using jQuery compatibility mode, a HUGE mistake that Drupal made and was not and will not be corrected in the 4/5/6 versions. The only Drupal version that has jQuery compatibility mode is Drupal 7.

jQuery Compatibility Mode is a module that allows you to install Mootools or any other JS library app for that matter, right along side built in jQuery apps/modules. If you had tried this before without using this module, your jQuery apps/modules would simply not function at all and give JS errors. I will probably use this to add some snazzy mootool applications to Drupal and then use those in PGSL Drupal.

The Drupal version of PGSL is taking a while to produce because I am piece mealing it out into separate modules as I have free time, but it's progress is still moving forward.