I am sure this is a common scenario and many people may have encountered this: anonymous users enter info in a form; after a couple of steps it gets to the point where only log on users can access (let's say, log on to check out). Before log on, form values in multi steps store fine in anonymous stage. But after log on, all form values are lost.
How can I get around this and carry the form values from anonymous stage to log on stage? As now, I suppose setting session variables, not the form api (even with #multistep be true), is a viable way. Correct me if I am wrong.
Is there a way to force the install hook for a module to run again?
Since I've added a custom module, I've added some code to the install hook. I disable the module and re-enable it again, however the code in the install hook doesn't get run. It ran the very first time I installed the module.
I would like to modify the "website" link that appears in the OG group menu so that when you click on it, the url opens in a new window.
I found a possible solution using phptemplate http://drupal.org/node/75192#comment-144123, but I was wondering if there was another way, using, say, hook_link or hook_filter? Another way other than modifying the OG code that creates the link.
I'm using the sucker fish code for the drop down menu's at supplychain.com
The problem is that on the secondary pages (not the homepage), if you click something on the page (could be anything from white space to a dead link), and hover over more than one drop down category, all of the categories stick and stay expanded.
I'm building a $node object in my module with some custom values including setting some CCK fields that I've defined for my content type...when I do a node_submit and then a node_save, everything is storing correctly except for the CCK values, they don't seem to be set at all. Is there something else I need to do to make the CCK custom fields store into the appropriate DB table?
I created a module for CiviCRM and I have an update hook that inserts records in the CiviCRM database.
After I enable the module. I run the update.php script. When I click update my update hook runs and the tables are populated, however the update hook gets run more than once; 8 times to be specific.
As a result I get an error of the nature 'record already exists'.
Has anyone had an issue where the code in their update hook is getting run many times over again?