Ghost/apps/portal
Michael Barrett d406d2ba6a
🐛 Fixed incorrect subscription status text when subscription is comped (#18369)
refs https://github.com/TryGhost/Product/issues/3963

The subscription status text was incorrect when a subscription was
comped and a member had multiple subscriptions (i.e a cancelled sub and
a comped sub). This was because the methods used to determine the status
of a subscription only took into account the status of the first
subscription associated with a member.
2023-09-27 08:46:55 +01:00
..
src 🐛 Fixed incorrect subscription status text when subscription is comped (#18369) 2023-09-27 08:46:55 +01:00
.env Moved Portal to apps/ 2023-06-16 13:37:58 +02:00
.env.development.local.example Moved Portal to apps/ 2023-06-16 13:37:58 +02:00
.eslintignore Moved Portal to apps/ 2023-06-16 13:37:58 +02:00
.yarnrc Prevented git tags from being created for apps 2023-07-10 13:09:28 +02:00
jsconfig.json Moved Portal to apps/ 2023-06-16 13:37:58 +02:00
package.json Update dependency @vitejs/plugin-react to v4.1.0 2023-09-27 09:36:39 +02:00
README.md Added checks for subscription to multiple newsletter through custom sign up form (#17994) 2023-09-07 18:27:32 +01:00
vite.config.js Moved Portal to apps/ 2023-06-16 13:37:58 +02:00

Portal

npm version

Drop-in script to make the bulk of Ghost membership features work on any theme.

Usage

Ghost automatically injects Portal script on all sites running Ghost 4 or higher.

Alternatively, Portal can be enabled on non-ghost pages directly by inserting the below script on the page.

<script defer src="https://unpkg.com/@tryghost/portal@latest/umd/portal.min.js" data-ghost="https://mymemberssite.com"></script>

The data-ghost attribute expects the URL for your Ghost site, which is the only input Portal needs to work with your site's membership data via Ghost APIs.

Custom trigger button

By default, the script adds a default floating trigger button on the bottom right of your page which is used to trigger the popup on screen.

Its possible to add custom trigger button of your own by adding data attribute data-portal to any HTML tag on page, and also specify a specific page to open from it by using it as data-portal=signup.

The script also adds custom class names to this element for open and close state of popup - gh-portal-open and gh-portal-close, allowing devs to update its UI based on popup state.

Refer the docs to read about ways in which Portal can be customized for your site.

Basic Setup

This section is mostly relevant for core team only for active Portal development. Always use the unpkg link for testing/using latest released portal script.

  • Run yarn start:dev to start Portal in development mode
  • Open http://localhost:3000 to view it in the browser.
  • To use the local Portal script in a local Ghost site
    • Update config.local.json in Ghost repo to add "portal" config pointing to local dev server url as instructed on terminal.
    • By default, this uses port 5368 for loading local Portal script on Ghost site. It's also possible to specify a custom port when running the script using - --port=xxxx.

Available Scripts

In the project directory, you can also run:

yarn start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

Start the portal server when developing Ghost by running Ghost (in root folder) via yarn dev --all or yarn dev --portal. This will host the portal JavaScript files, and makes sure that Ghost uses these locally hosted assets instead of the ones from the CDN.

yarn build

Creates the production single minified bundle for external use in umd/portal.min.js.

yarn test

Launches the test runner in the interactive watch mode.

Publish

Run yarn ship to publish new version of script.

yarn ship is an alias for npm publish

(Core team only)