Resolved Combining fields on export

Hello,

You don't need that patch because 6.0.1 came out after that patch, so it is included in the release. It can even mean you now have older code than what is in 6.0.1.

As for your export, you can set the Amazon DE color to unpublished because you don't want it exported but it will need to be there to be combined.

Other than that I don't see anything wrong with your setup. Now I have rewritten the rules a little bit for 6.1.0 to make them more flexible. So there are no longer template rules, all rules are directly linked to their fields. If you are interested I can send you a pre-release. The only thing you would need to change then is to assign the rule to the Amazone DE title field.

Ok thanks! Yes I'm interested in the pre-release of 6.1.0.

Thanks for helping out.

Hi,

I was just about to make a new topic about fieldcombine rule, but I found this one.
I did rule as described here, however it seems it doesn't work (no combination is done).

So there are no longer template rules, all rules are directly linked to their fields

As I understand there will be no more "runTemplateRule" function? That's sad, because while using template rule I had possibility to access other fields, for example I did my own template rule plugin with scenerio "if some field value = test, then make all other fields values = ''. This was before 6.0.1 I guess. Will this be possible while there will be only field rules? Also will I need to assign one rule to all exported fields?

Best regards,
Chris

Hello Chris,

Let me first say there is no fire

Will this be possible while there will be only field rules? Also will I need to assign one rule to all exported fields?

Let me give you a little background info. In the current situation both the field rules and template fields are ran at the same place. Only difference is that first the field rules are run and then the template rules. Kinda stupid but I guess I had an idea at the time. So instead of running them like that, they now run one after the other based on the ordering on the rules page.

You still have the possibility to access the other fields as the whole fields object is passed on in the runRule function as well. Any rule you create yourself, you can assign it to any field as you can always access all fields. In this case you would assign it to a field the rule is related to.

Does that answer your question?

Hi,

it looks even better, in my template rule I had to find field which I want to check/process, now I'll already have field choosen as the field rule is assigned to field, right? :woohoo:

Best regards,
Chris

Hello Chris,

This is the signature of the runRule function:

/**

	 * Run the rule.

	 *

	 * @param   string            $plugin    The ID of the plugin.

	 * @param   array             $settings  The plugin settings set for the field.

	 * @param   array             $field     The field being process.

	 * @param   CsviHelperFields  $fields    A CsviHelperFields object.

	 * @param   string            $action    Which action is performed.

	 *

	 * @return  void.

	 *

	 * @since   6.0

	 */

	public function runRule($plugin, $settings, $field, CsviHelperFields $fields, $action)

as you can see you get both the field currently being processed and a list of all the fields assigned to this template.