Ryan Bayne

I would like to reply to the question put forward for further clarity…

Why is there not a check after step 1???

These plugins require all settings and configuration to be saved prior to post creation. The notice is regarding post creation itself which is performed last. There is no possible check that can be done early, not without guessing or making assumptions.

Other importers guess the users needs and wishes. CSV 2 POST does not. It is a plugin for professionals who want to take full control over the websites they build. However in response to people struggling with such an advanced plugin we decided to stop providing so many features and reduce the interface down to what most plugins offer. Sometimes more is not good and that we do understand. We hope you try our next version.

I’ll finish by confirming what Zara basically said. The notice may mean very little but I do admit it seems more serious than it is and that it needed changed. Which it was about a week back and will be delivered in the next version. We are on the ball ??

The notice could indicate one custom field for one post out of 100,000 posts was not saved successfully. These things happen and unlike many CSV importers we do not avoid alerting the user just to brush issues under the rug. Hell knows how many auto-blogged websites out there have some un-finished posts that the owner will never notice due to the massive amount of posts blogged. This is what we wish to avoid and deliver more accuracy/quality.

I am sorry if you feel you had bad experience but we are here to help you continue your need for auto-blogging.

Sorry I didn’t realize. It had been done but I think we updated the .htaccess when we re-developed the site.

That is done now thank you.

Sorry correct terminology is top-level domain name. Sorry about posting the domain here which I realize its not proper but I was trying to explain our intentions.

I may have failed to express that the domain is no longer made public. Any traffic (which will be very little) will come from accidental entry or anyone who does happen to know the domain name from when it was initially launched. To help clear up any existing use and knowledge of it spreading we decided this plugin will not have its own website with the idea of sending all traffic to somewhere that helps the community i.e. either www.ads-software.com where they can download it or GitHub repo where they can get involved.

It only violates if it is in use as a parent domain. Otherwise its fine and can be used to forward traffic.

It was mentioned above but now…

and [ link redacted ] ca

We are being asked to re-release “WordPress CSV Importer” as a different type of importer from CSV 2 POST and put it on GitHub public repository.

It is something we are considering. This suits us because we won’t setup a website. [ link redacted see below ] which we are not allowed to use as a parent/main domain can be used to forward traffic to either the repo or to the plugins page here on www.ads-software.com

What a journey but we’ll get it all sorted out and provide another plugin with an approach in high demand. Mainly it will have the tools for migrating other CMS into WordPress. Something CSV 2 POST will never provide as it is focusing on general data management. Maybe by default some of the data tools CSV 2 POST gets will allow migration but if it happens the functions won’t be designed to work with specific CMS.

[Moderator note: Please see the WordPress Foundation Trademark Policy regarding your domain name]

Still toying with this idea. Hard one.

A lot of users find the sandbox area too complex. But they warm up to it and eventually say…wow. What we need to do is push them through the Quick Start screen, let them warm up that way. Then introduce them to a sandbox approach.

Do we remove the sandbox area or just hide and offer option to display it?

Lets not make any sudden decisions on this.