@faustwp/cli@2.0.0

Major Changes

• c163fa5: BREAKING: Removed telemetry CLI commands for faust telemetry enable/disable/status for managing and viewing telemetry opt-in status. Telemetry functionality has been moved to the Faust WordPress plugin. Sites that previously opted in from CLI will no longer send telemetry data unless someone opts in from the WordPress side.

Patch Changes

• c163fa5: Adds block_editor_utils and experimental_app_router to telemetry events.

@faustwp/block-editor-utils@0.1.0

Minor Changes

• 8dcda28: Add support for RichText control fields.

  Add a source and selector in your block attributes string field:

  ...
  "attributes": {
  		"richText": {
  			"type": "string",
  			"source": "html",
  			"selector": ".rich-text",
  			"default": "Hello World"
  		}
  	}

  Then in your component definition make sure the selector specifier matches the component you want to render as rich text:

  <div
    style={styles}
    className="rich-text"
    dangerouslySetInnerHTML={{ __html: attributes.richText }}
  />

  Once the blocks are synced you will be able to use it as a RichText field.

Patch Changes

• 66c1e24: Publish Readme to NPM

@faustwp/wordpress-plugin@1.1.2

Patch Changes

• 78a061a: Fixed a bug that caused links to files in wp-content to be rewritten to the Faust Front-end site URL when they should not have been.
• 2559958: Bug Fix: Fixed missing call to autosave when using Post/Page previews.
• 75f5c80: Fixed a bug where links were rewritten to the Faust Front-end Site URL when using the post editor, resulting in those rewritten links being saved to the post content and guid fields when they shouldn't be. These links are now saved with the URL pointing to the WP site, as they should be. They are still rewritten at runtime to link to the Front-end Site URL when appropriate.

@faustwp/experimental-app-router@0.2.2

Patch Changes

• 626207b: Added: New util for fetching data on the client side. In a client component (use client), you can now use Apollo's useQuery to fetch data once your application is wrapped with the <FaustProvider> component. This new component is available via:

  import { FaustProvider } from '@faustwp/experimental-app-router/ssr';

@faustwp/cli@1.2.1

Patch Changes

• c75ab2b: Bug: Quote blockset "output-path" to prevent issues with space in paths.

@faustwp/experimental-app-router@0.2.1

Patch Changes

• 6276c80: Fix broken build from 0.2.0

@faustwp/experimental-app-router@0.2.0

Minor Changes

• 6e43598: BREAKING: Updated the following peer dependencies to new required minimums:

  • @apollo/experimental-nextjs-app-support: 0.4.1 -> 0.5.0
  • next: 12.1.6 -> 14.0.0
  • react: 17.0.2 -> 18.0.0
  • react-dom: 17.0.2 -> 18.0.0

• 6e43598: BREAKING: This package now requires Node 18+

@faustwp/wordpress-plugin@1.1.1

Patch Changes

• b2c0fd3: Updated the settings page to improve descriptions and documentation links.

@faustwp/wordpress-plugin@1.1.0

Minor Changes

• c29f83d: Add blockset command in @faust/cli and faustwp plugin.

  Add your blocks inside wp-blocks folder. Then run faust blockset to compile and upload the blocks into WordPress. Blocks will be available in the editor.

• d3d30aa: Added support for authenticated WPGraphQL introspection queries using FAUST_SECRET_KEY. It is no longer required to enable "Public Introspection" in WPGraphQL.

@faustwp/core@1.2.0

Patch Changes

• 3722ab3: Fix x-using header not appearing when i18n options are set in next.config.js