Developer
  • Projects
  • Docs
  • Blog
  • Forum
  • Builds
  • BLENDER.ORG

    • Download

      Get the latest Blender, older versions, or experimental builds.

    • What's New

      Stay up-to-date with the new features in the latest Blender releases.

    LEARNING & RESOURCES

    • Blender Studio

      Access production assets and knowledge from the open movies.

    • Manual

      Documentation on the usage and features in Blender.

    DEVELOPMENT

    • Developers Blog

      Latest development updates, by Blender developers.

    • Documentation

      Guidelines, release notes and development docs.

    • Benchmark

      A platform to collect and share results of the Blender Benchmark.

    • Blender Conference

      The yearly event that brings the community together.

    DONATE

    • Development Fund

      Support core development with a monthly contribution.

    • One-time Donations

      Perform a single donation with more payment options available.

Logo
Explore
Products
Blender User Manual Developer Documentation
Blender Benchmark
Blender Studio Tools Flamenco Watchtower
Modules
Animation & Rigging Asset System Core Grease Pencil Modeling Nodes & Physics Pipeline & I/O Platforms & Builds Python API & Text Editor Sculpt, Paint & Texture Triaging User Interface VFX & Video
Rendering
Render & Cycles Viewport & EEVEE
Report a Bug Paste Code Help
Sign In
archive/phabricator
1
0
Fork 0
You've already forked phabricator
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity
Files
aa3b2ec5dcd0ba91e36d5a0b59f37f27ec78b57c
phabricator/resources/sql/autopatches/20141007.fundmerchant.sql

3 lines
80 B
MySQL
Raw Normal View History

Adjust payment workflows to deal with merchants and configurable providers in Phortune Summary: Ref T2787. Builds on D10649 by rebining existing objects (carts, charges, etc) to merchantPHIDs and providerPHIDs instead of an implicit global merchant and weird global artifacts (providerType / providerKey). Basically: - When you create something that users can pay for, you specify a merchant to control where the payment goes. - Accounts are install-wide, but payment methods are bound to merchants. This seems to do a reasonable job of balancing usability and technical concerns. - Replace a bunch of weird links between objects with standard PHIDs. - Improve "add payment method" flow. Test Plan: Went through the Fund flow with Stripe and WePay, funding an initiative. Reviewers: btrahan Reviewed By: btrahan Subscribers: epriestley Maniphest Tasks: T2787 Differential Revision: https://secure.phabricator.com/D10652
2014-10-07 14:41:59 -07:00
ALTER TABLE {$NAMESPACE}_fund.fund_initiative
ADD merchantPHID VARBINARY(64);
Reference in New Issue Copy Permalink
Powered by Gitea Page: 155ms Template: 1ms
English
Bahasa Indonesia Deutsch English Español Français Gaeilge Italiano Latviešu Magyar nyelv Nederlands Polski Português de Portugal Português do Brasil Suomi Svenska Türkçe Čeština Ελληνικά Български Русский Українська فارسی മലയാളം 日本語 简体中文 繁體中文(台灣) 繁體中文(香港) 한국어
Licenses API