1.1.3

• WordPress accepts delivery URLs with or without www and publishes at the site's configured address.
• Selecting a Custom HTML field highlights it in the layout preview on optimized pages. Previously saved whole-block mappings highlight their section when it can be identified.

1.1.2

Selecting a Custom HTML field now highlights its text, link, or image in the mapping preview. Click the preview to select the matching field in the editor, even when two questions use identical text.

Selecting an answer opens its FAQ section. Selecting a structured data field clears the previous highlight and explains that the value has no visible element on the page.

1.1.1

• Map individual headings, text, links, images and FAQ entries inside Gutenberg Custom HTML blocks while preserving the surrounding layout and styling. To use the new fields on an existing template, choose Capture a fresh layout.
• Choose which JSON-LD values to publish by giving each one a Custom purpose and writing guidance. Generated pages omit unmapped schema values.
• Use distinct WordPress permalink paths to route a NOVA page type to different destinations, such as Pages and a custom post type.

1.1.0

WordPress installations that share a NOVA site ID can now share their publishing layouts. Create the mappings on one installation, then use Layouts → Share layouts between installations to export the approved revisions and import them on the others.

• Receiving installations can publish and send receipts while the main installation manages mappings and defaults. Older revisions remain available for queued deliveries.
• The importer checks local image references and identifies any file that needs to be matched. Layout sharing supports the WordPress editor, Gutenberg, Elementor, Flatsome and Enfold.
• Fixed title-only drafts when WPML created translated copies of a featured image. The writer now identifies the correct attachment and completes the body and featured image on the same page.

1.0.7

Adds Themeco Cornerstone support for mapping, previewing and publishing WordPress Pages and Posts. Deliveries can create or update content from a saved layout, including headings, body text, buttons, links and images.

1.0.6

Save and sync a layout directly from Content rules in step 3. The same screen shows whether the posting service confirmed the default and lets you retry sync or explicitly replace another default.

In step 2, search or browse in Reference item, then choose Use this existing page. Selecting the same example for the same destination reopens your mapping. Choose Capture a fresh layout when you want to start over from the example.

New Elementor layouts start with recognized page design settings selected. Use Select all, Deselect all, or change individual settings. Existing layouts keep their selections. The editor also removes the sample-draft controls and hides the built-in WordPress footnotes field from new mappings.

1.0.5

In step 3 of a fixed layout, open Editorial custom fields to map ACF text, textarea, WYSIWYG, URL and email fields or registered WordPress REST strings. Each selected field can have its own instructions. Omitting an optional field preserves its existing value.

WPML and Polylang write each language to its native post. TranslatePress and Weglot serve the fitted values on the localized view of the published original. WPML also links a single translation that arrived before its original.

We verified creation and independent updates on isolated staging with all four providers, including the actual rendered ACF and WordPress meta values on both language URLs. Verification · Field types and setup

1.0.4

WordPress now publishes NOVA deliveries using the article’s language and the multilingual plugin’s public URL. A delivery for one language can proceed while another language’s receipt is pending, provided the two deliveries target different pages.

• WPML and Polylang: Create a native post in the requested language, link siblings that share a NOVA URL ID, and update each independently. A translation can arrive before the site’s primary-language article.
• TranslatePress and Weglot: Apply mapped content to the localized view of an existing, published NOVA original. Send the original for the same URL ID first. A translated delivery does not create a second native post.

Verified on isolated WordPress staging with WPML 4.9.5, Polylang 3.8.5, TranslatePress 3.3.7 with Personal, and Weglot 6.4.3. Test details and supported fields and configurations.

WordPress can fetch this update from the dashboard without GitHub credentials. For manual installation, choose nova-wordpress-plugin-1.0.4.zip below.

1.0.3

Elementor layouts containing a Loop Carousel or Loop Grid can now sync while keeping the widget’s query and its saved card design. The plugin verifies that the selected template is a published, password-free Elementor Loop Item on the same WordPress site.

If this reference previously blocked a mapping, open the layout and choose Sync saved revision after updating. For a layout targeting Pages, choose a Posting user who can create and edit Pages and, when publishing live, publish Pages.

The release was tested locally. The regression test reproduces the carousel failure from 1.0.2, checks that replacing a mapped heading preserves the carousel settings, and exercises the saved revision’s sync and default confirmation with a simulated posting service.

1.0.2

Compatible delivery starts automatically once the WordPress connection is configured. Manage pauses in NOVA. If an installation was paused or disabled only in WordPress and needs to stay paused, pause it in NOVA before upgrading.

• Select the WordPress user for new posts. The first suggestion is the eligible site member with the most published posts, pages and editorial custom posts. Updates keep the existing byline.
• Site-only routing and excluded paths are together under Multi-site WordPress, below Save NOVA connection. The Modules screen now lists NOVA Blog CPT, NOVA Service CPT and WooCommerce Rich Text.
• Layouts go straight from field mapping to Save & review. Saving still checks the source revision and syncs the mapping and default with posting-service. If sync fails, WordPress retains the local revision and offers a retry.

All 93 local suites passed. WordPress staging verified native draft creation and update, and the revised connection form passed all 50 connection checks there. Mapping sync, default selection and outage recovery were exercised with a simulated posting-service endpoint.

Sites on 1.0.1 can update from the WordPress dashboard. If you already installed the earlier 1.0.2 and want the revised form, upload the ZIP below and choose Replace current with uploaded. The version number has not changed.