Needs work
Project:
Ubercart Product Power Tools
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
20 Jan 2011 at 16:51 UTC
Updated:
15 Nov 2018 at 03:39 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
djdevinSorry, I meant uc_product_power_tools_NODETYPE
Comment #2
yaoweizhen commented+1
Comment #3
tr commentedProvide a patch and I'll add this in to the module. New features need to go into the Drupal 7 version first.
Comment #4
djdevinCool, can actually just keep the schema on second thought. I will try to find some time to do it.
Comment #5
djdevinHere is a patch for features integration. It is rolled against 6.x-1.x-dev (need it for a project) but I believe it should apply to any version with minor tweaks.
Comment #6
socialnicheguru commentedI enabled the patch
I can see the uc power tools option in features
NO STRONGARM VARIABLES
i do not see any variables in strongarm that I can download and enable
"Power Tools" Status is not available for export
I can download it as part of the feature
I see the settings in the features module
but when I enable the feature, no variables are set :(
Edit - I am on Drupal 6.22
There is a "uc_product_enable_nodes" strong-arm variable. is this the one that I have to include to enable my particular content type?
Can I include this in each product feature that I create? Will they conflict because they all will share this variable?
Comment #7
djdevinThis won't show up as strongarm - it's from the schema, it should show up as 'UC Product Power Tools' in your list.
Comment #8
tr commentedStrongarm exports system variables. This module doesn't use system variables for settings. http://drupal.org/node/1198864
Comment #9
socialnicheguru commentedSo I thought that if I included product power tools via the patch that all values previously entered would be maintained.
however when I enable the feature on a new site none of the values are present.
Comment #10
socialnicheguru commentedDid you mean to return '$pipe', an empty array, in the following code in your patch?
Comment #11
socialnicheguru commentedI figured out why the patch wasn't working for me.
Every time i enable the feature, I have to revert changes. Once I do that, then the settings are there.
Comment #12
socialnicheguru commentedWhenever I use manage class to create a product
I then use product power tools to modify the settings.
Whenever I enable a feature with product power tools, the settings are always overriden to FALSE. Please see attachment.
can anyone help with this? Is there a setting that I missed somewhere?
thanks!
Comment #13
djdevinAre you saying your post in #11 didn't work? That diff means the feature is overridden, and needs to be reverted for the changes to be made. I suppose we can make a change to automatically revert changes if there isn't a record for it already.
Comment #14
socialnicheguru commentedIt finally did.
But every time I enable the feature on a new site and goto the features page, it is overridden. I don't know why.
I would think that if I enable a feature for the first time on a site that all of my settings would automatically take.
Comment #15
djdevinIt should. Give me some time to work on it and I'll make sure that works.
Comment #16
djdevinThis one should be better, I forgot to add the _rebuild() hook which was probably causing the records not to create on first enable.
Comment #17
socialnicheguru commentedCan this be ported to D7 if need be? I haven't actually tried it to see if it is an issue.
Comment #18
djdevinNot tested, but I think it should work as-is.
Comment #19
djdevinJust saw there was a new release, cool.
We still use this patch and it works in D6 & D7.
Comment #20
stefan.r commentedThanks. Can anyone else review this so we can get it to RTBC?
Comment #21
stefan.r commentedThanks. Can anyone else review this so we can get it to RTBC?
Comment #22
djdevinComment #24
tr commentedI turned testing on for this module. I don't know why it wasn't on before. The two test failures are not related to this patch.
If you'll fix the 8 new coding standards problems added by this patch I'll commit it. (see the list at https://www.drupal.org/pift-ci-job/1121837) No need to fix the existing coding standards problems, just don't add any new ones!