Closed (won't fix)
Project:
Subscriptions
Version:
7.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
14 Aug 2013 at 16:18 UTC
Updated:
27 Aug 2013 at 12:24 UTC
Jump to comment: Most recent file
Comments
Comment #1
shaneonabike commentedOk it turns out that this was my fault actually. When I created the custom module I copied code for the hook_subscriptions call in the 'fields' section.
What's interesting though is that having defined identical fields to subscriptions_content the code ended up creating an array for the variable $data_function (see patch). I realized that in some circumstances maybe folks would want to define the same variables but add their own data_function to deal with some element of changes happening?
Here's a patch... let me know if you want to scrap it but it might at least alleviate others having this issue.
Comment #2
shaneonabike commentedBTW I recognize this is an edge-case but actually by adding this you'll extend the API a bit (har har)
Comment #4
salvisThank you for following through with this.
Please learn and adopt the http://drupal.org/coding-standards. This may seem nit-picky at first, but in the end everyone benefits from uniform code.
I've started to write comments for your patch...
... but in the end I'm not convinced that it's a good idea.
We could argue to go to arrays for all the data returned from hook_subscriptions(), but without a demonstrated need and successful implementation, it's just stale code that is never executed.
I doubt your code would have performed as expected, even with this patch.
Please clean up #2014867-10: Subscriptions causing cron to run endlessly.
Comment #5
shaneonabike commentedCould be an edge case like I said. I'm happy just to ditch this anyway. I'll try to find some time to work on fixing up coding standards before I post other stuff.