rbplugins
Forum Replies Created
-
Yes, this is controlled by the duplication profile you are using.
In the profile settings, open the Elements to Copy section and enable the option “All Post Meta” (or make sure the needed meta options are enabled there). This allows the plugin to copy all custom metadata attached to the post. Also, please double-check that you are duplicating the post with the correct profile where this setting is enabled.
When All Post Meta is active, the plugin will correctly copy:
– ACF custom fields
– Custom taxonomies registered via ACF or manually
– Any other custom metadata attached to the postForum: Plugins
In reply to: [Disable Comments] Custom post types commentsWhen you disable comments globally with the plugin, it applies not only to posts and pages, but also to all custom post types that support comments.
In other words, comments are turned off everywhere across the site, regardless of the content type.
Forum: Plugins
In reply to: [Disable Comments] Global disableGood question.
When comments are disabled globally using the plugin, existing comments are not deleted from the database. The plugin simply hides all existing comments on the frontend and in the admin area, and prevents new comments from being added.
So if you ever re-enable comments later, your old comments will still be there, nothing is permanently removed.
Forum: Plugins
In reply to: [Disable Comments] Allow Notes?Thanks a lot for the kind words, really happy to hear you’re using the plugin across your sites!
You’re also 100% right about what’s happening: in WordPress 6.9 the new Notes feature stores data via the comments system, so when comments are disabled “Everywhere”, WordPress blocks saving Notes and shows the “Comments are disabled” message.
Good news: this is exactly the kind of edge case we want to handle better.
We need to run a few tests on WP 6.9 (including FSE sites) to confirm the safest way to allow Notes without unintentionally re-enabling normal comments. But yes, we can look into adding an option like “Allow WordPress Notes” while keeping regular comments disabled everywhere else.
Also, just so you know: we’re actively working on the next Disable Comments RB release with a more advanced configuration layer (including things like WP-CLI support, multisite support, and more flexible rules). The plan is to have a simple Basic mode (current behavior) and an Advanced mode where exclusions like this are easier to manage.
If you can share your setup details (WP 6.9 exact version, which theme, and whether Notes are used on posts/pages or site-wide), that would help us reproduce it faster.
Forum: Plugins
In reply to: [Forms Rb] Order form fields with product name and quantityYes, absolutely.
Forms RB can be used as a simple order form. You can create fields such as Product Name, Quantity, and any other required details, then mark them as required in the form settings.
This way, visitors must fill in the necessary information before submitting the form, making it perfectly suitable for basic order requests or inquiries.
Forum: Plugins
In reply to: [Forms Rb] Multiple contact formsYes, it’s absolutely possible.
You can create multiple forms in Forms RB, each with its own set of fields, labels, and settings. Every form has its own shortcode, so you can easily place different forms on different pages, posts, or widgets.
Just create a new form, configure the fields as you need, copy the generated shortcode, and paste it into any page where you want that specific form to appear.
This should work, and it’s usually a profile setting issue.
Please check the duplication profile you’re using:
– Go to Duplicate Post RB -> Profiles and open the profile used for duplication
– In Elements to copy, make sure Attachments / Media is enabled
– Also enable Taxonomies / Categories (so folder/category assignments are copied as well)The plugin supports copying attachments even when they are organized in nested media categories, but only if those elements are enabled in the active profile.
Also, please double-check that your duplication action is actually using the same profile (bulk duplication and quick actions can sometimes use a default profile if not selected).
We do have a dedicated WP-CLI guide here:
https://rbplugins.com/docs/duplicate-post-rb/wp-cli-duplication/To duplicate posts via WP-CLI using a specific profile, you can use:
wp rb-duplicate-post duplicate 123 --profile=2And yes, you can duplicate multiple posts at once by passing IDs separated by commas:
wp rb-duplicate-post duplicate 12,32,43 --profile=2Where
--profile=2is the duplication profile ID you want to apply to all provided posts.Yes, the duplication history does store information about how metadata was copied, including ACF fields and taxonomies, as long as this is configured correctly.
Here’s how it works:
– You can create a custom duplication profile and give it a clear name (for example, “ACF Metadata Duplication”).
– This profile name is saved and displayed in the duplication history, so you can later see exactly which profile and settings were used during the copy operation.
In the profile settings, make sure to enable “All Metadata” and select the required custom taxonomies in the “Elements to copy” tab. This ensures that ACF fields and taxonomy data are duplicated correctly.This setup makes it much easier to audit copy operations, especially when working with complex content structures that rely on ACF and custom taxonomies.
If you’d like, we can help you fine-tune a profile specifically for your ACF-based workflow.
In the current version of Duplicate Post RB, the plugin does support copying custom fields and taxonomies, including ACF fields and custom taxonomies, when duplicating posts or pages. This means that all metadata linked to supported post types can be duplicated correctly.
However, full support for ACF Custom Post Types (CPTs), such as Projects or Services created entirely via ACF, is not yet available in the current release. At the moment, duplication works reliably for standard post types and their metadata, but ACF-defined CPTs are still limited.
That said, we’re actively working on the next update, which will introduce full support for ACF content, including custom post types, their fields, and related taxonomies.
If you’d like, feel free to share your specific ACF setup – it can help us ensure the upcoming implementation fully covers real-world use cases like yours.
When the “Copy attachments” option is enabled, attachments are physically duplicated in the Media Library, they are not just linked to the original files. Each duplicated post gets its own copy of the attachment files, which works correctly even during bulk post duplication.
Regarding categories and structure:
– Duplicate Post RB gives you full control via duplication profiles.
– If you enable category/taxonomy copying together with attachment copying, then attachments will be duplicated across all categories associated with the post, including nested (child) categories.
– The plugin correctly preserves the relationship between the post, its taxonomies, and the copied attachments.This makes the feature especially useful when you need fully independent copies of posts and media – for example, when creating templates, localized content, or large batches of duplicated posts.
If you want, we can help you fine-tune a duplication profile that best fits your workflow.
When you duplicate posts in bulk or individually, the history is stored per each duplicated post, not just as a single bulk action.
Here’s how it works:
- Each post or page has its own duplication history widget.
- You can see this widget when editing the post in both the Classic Editor and Gutenberg.
- The history is available regardless of whether the post was duplicated individually or via bulk duplication.
For every duplicated post, the widget shows:
- Date and time when the duplication happened
- Title of the original post/page, including a direct link to it
- Name of the duplication profile used, with a link to that profile’s settings
This makes it easy to audit copy operations, track content origins, and understand exactly how and when each post was created.
If you’d like, we can also help you design profiles specifically optimized for bulk duplication workflows.
Thanks for the feedback, we’re glad you like the new duplication history feature.
Yes, this is expected behavior. The duplication history starts recording data from version 1.5.7 onward. Copies that were created before updating to this version don’t appear in the history list because that information wasn’t stored at the time.
Going forward, all new duplication actions (both single and bulk) will be tracked automatically and shown in the history widget.
We’re planning to continue extending and improving this feature in future versions, including more details and additional tracking options, so stay tuned! If you have suggestions on what you’d like to see next in the history panel, we’d love to hear them.
Of course, the profile feature is applied both when duplicating posts and when duplicating pages.
Please make sure that you’re selecting the correct profile in the duplication popup before creating the clone. If you have multiple profiles, it’s easy to accidentally run duplication with a different preset than the one you configured.
I’d recommend double-checking:
– That the desired profile is selected in the popup.
– That the fields you want to copy are enabled inside that profile’s settings.If after that some specific fields are still not being copied, let us know which ones and we’ll be happy to investigate further.
To duplicate a parent page together with all its child pages, you simply need to enable the Children option in the Elements to Copy tab inside your duplication profile settings.
Once this option is enabled, the plugin will automatically detect the page hierarchy and duplicate the entire structure, including the parent and all of its child pages. When you run the duplication pages or duplication posts using that profile. This works for both pages and hierarchical post types.
Just make sure you select this profile in the duplication popup before starting the process. After that, everything will be handled automatically.