date_deploy.module
| Project: | Deployment |
| Version: | 6.x-1.x-dev |
| Component: | deploy.module |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I created a new Story node and added it to a "test" deployment plan. Both servers are running virtual on my computer and have identical implementations (except for virtual URL names). Even though this story node does not have a CCK date field, it seems the date_deploy.module may be causing an error during the push attempt? The node does show up in the "test" deployment plan. But when attempting to push, the following error is returned and it does not show up on the target server:
warning: First parameter must either be an object or the name of an existing class in C:\Users\Dave\Documents\Recruiters World\Web\RW Drupal Local\modules\deploy\modules\date_deploy\date_deploy.module on line 45.
The environment is Drupal 6.12, Services 6.x-0.14, and Deployment 6.x-1.x-dev. All of the module activation options under Services and Deployment are selected.
Don't know if this is a bug or configuration issue. Please advise. Would really like to utilize a module like this.
#1
All of the enabled modules that implement hook_node_deploy() will answer when that hook fires, regardless of whether that is strictly necessary or not (in cases where it is not, they just don't do anything.) As far as this issue, there is a typo in date_deploy.module which was causing your issue and I have committed a fix. It will be in the next dev release sometime in the next 12 hours, or you can pull it from CVS.
Thanks for the report!
#2
Thanks much, heyrocker, especially for the quick response. I'll look for the update.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.