NS Products

We here at Never Settle are always looking for new ways to improve our products and we love hearing from you!

How can we improve our products and make them better for you? That’s where we can use your help!

If there are features that our products do not currently support but you think would be a huge added value for you and lots of other people, then please share them here with us.

Before posting your idea, here are a few tips that will help make your request stand out and succeed:

Look to see if someone else has suggested the same idea, or something very similar. Many ideas are being submitted and it’s very possible that another request already exists. In that case, add your vote to the existing request.

Be as descriptive as possible. What does the feature do? Where would it be located? Who would use it? How does this improve the overall experience of the product?

Please note, this is NOT a place to get support or ask questions about how the plugin works. If you need help, please visit our help desk. If you use one of out free plugins, you can post in that specific plugin forum on WordPress.org.

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

When an admin closes an idea you've voted on, you'll get your votes back from that idea.

You can remove your votes from an open idea you support.

To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".

Enter your idea

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

Let NS Cloner duplicate sites when our users signs up to a site with PaidMembershipsPro and their Add-on "Member Network Sites".
It would be great if it could be possible to assign a certain template to a subscription level, so if a user signs up to the "silver-plan" they will get a clone of "template 2", and the "gold-plan" could duplicate "template 3".

There are theme thumbnails for Registration Template selections, but no descriptors. The Registration Templates we are offering have specialized configurations for particular use cases - it would be great to note these tailored uses in the Registration Template form.

First, love NS Cloner. Often users on my network don't want to verify so I wind up being the owner of the site and I can't loose myself from it. Allowing the admin email to be set on-clone would be a God-send. Just the way the default add-new site screen has. It then could trigger the default notifications and so on..

There are some companies such as WPMUdev and also Infinite WP that provide this "copy" service where you can copy one page from one site to others in a multisite environment, but to be honest I would trust you with it more than with them.

Many thanks! This is the second time very recently that this idea has crossed our radar. With our new V3 architecture I don’t think it would be too hard to add to the existing Content add-on, or even a new add-on if we starting thinking of additional features to combine with it.

If I were to clone everything into a location on Amazon S3 or my local development using XAMPP then it would make sense to also be able to overwrite everything, which would in essence create a backup without incremental capability. I would love that! This could either mean for all sites in a multisite or just single sites. This would be VERY exciting if I could do that.

Thanks! We have talked about this exact idea internally. Our current thought about the approach we might take is to have a Cloner archive format that would include the Cloner settings + the resulting data in a single file. Instead of executing the instructions with the data it would store both. Then to “restore” the archive, you point the Cloner at the archive, it reads the settings and plays back the execution with the data in the file as if it had cloned a live site in that network (whether or not it was actually there). The physical files are probably the biggest sticking point on the entire thing as that could lead to enormous archive files depending on the total size of the site(s) backed up. Anyway, we’re brainstorming that idea through. Input is much appreciated, especially if you have better ideas on implementation approach. But this kind of feedback is super valuable to us – we want to prioritize what we build based on what everyone finds the most useful.

Thanks! We have talked about this exact idea internally. Our current thought about the approach we might take is to have a Cloner archive format that would include the Cloner settings + the resulting data in a single file. Instead of executing the instructions with the data it would store both. Then to “restore” the archive, you point the Cloner at the archive, it reads the settings and plays back the execution with the data in the file as if it had cloned a live site in that network (whether or not it was actually there). The physical files are probably the biggest sticking point on the entire thing as that could lead to enormous archive files depending on the total size of the site(s) backed up. Anyway, we’re brainstorming that idea through. Input is much appreciated, especially if you have better ideas on implementation approach. But this kind of…