WordPress.org
Get WordPress

Plugin Directory

Changeset 2727503


Ignore:
Timestamp:
05/20/2022 05:14:23 PM (3 years ago)
Author:
minnpost
Message:

update trunk to git 09e401ecfcf4889ea73a7e77947eac53a866cff8

Location:
object-sync-for-salesforce/trunk
Files:
3 edited

Legend:

Unmodified
Added
Removed

  • object-sync-for-salesforce/trunk/README.md

    r2727501 r2727503  
    7272Related to the mapping of custom fields, but raising its own distinct questions and problems that can make this plugin more complicated, is the issue of mapping between required fields in WordPress or Salesforce.
    7373
    74 #### How WordPress handles meta fields
     74**How WordPress handles meta fields**
    7575
    7676This plugin runs on WordPress' core actions for user, post, comment, attachment, and term objects, which run when those objects are created or deleted. This plugin also runs on WordPress' meta actions for those objects. The way WordPress works is that these actions don't happen together, so metadata is generally not part of the core action's dataset.
    7777
    78 #### How this affects required fields
     78**How this affects required fields**
    7979
    8080The way these actions work means that if a field is required in Salesforce, it needs to be sent as part of the first, core WordPress action associated with the WordPress object. If it is only added as part of the second action, the metadata, it will not be sent and the Salesforce operation will fail.

  • object-sync-for-salesforce/trunk/readme.txt

    r2727501 r2727503  
    4242Related to the mapping of custom fields, but raising its own distinct questions and problems that can make this plugin more complicated, is the issue of mapping between required fields in WordPress or Salesforce.
    4343
    44 #### How WordPress handles meta fields
     44**How WordPress handles meta fields**
    4545
    4646This plugin runs on WordPress' core actions for user, post, comment, attachment, and term objects, which run when those objects are created or deleted. This plugin also runs on WordPress' meta actions for those objects. The way WordPress works is that these actions don't happen together, so metadata is generally not part of the core action's dataset.
    4747
    48 #### How this affects required fields
     48**How this affects required fields**
    4949
    5050The way these actions work means that if a field is required in Salesforce, it needs to be sent as part of the first, core WordPress action associated with the WordPress object. If it is only added as part of the second action, the metadata, it will not be sent and the Salesforce operation will fail.

  • object-sync-for-salesforce/trunk/vendor/composer/installed.php

    r2727501 r2727503  
    66        'install_path' => __DIR__ . '/../../',
    77        'aliases' => array(),
    8         'reference' => '2495c7588b1e4ed6b60bc5abdeba3ca96ceccfe9',
     8        'reference' => '09e401ecfcf4889ea73a7e77947eac53a866cff8',
    99        'name' => 'minnpost/object-sync-for-salesforce',
    1010        'dev' => false,
    … …  
    2828            'install_path' => __DIR__ . '/../../',
    2929            'aliases' => array(),
    30             'reference' => '2495c7588b1e4ed6b60bc5abdeba3ca96ceccfe9',
     30            'reference' => '09e401ecfcf4889ea73a7e77947eac53a866cff8',
    3131            'dev_requirement' => false,
    3232        ),
Note: See TracChangeset for help on using the changeset viewer.