An issue arose where we had no option but to rename our post creation plugin. It is now called CSV 2 POST.
WordPress CSV Importer here on WordPress.org will now be a data importer only, no post creation. Anyone who knows WordPress CSV Importer prior to this change, will find the plugin they knew within CSV 2 POST. So essentially we re-branded a copy of WordPress CSV Importer and then downgraded WordPress CSV Importer. We don’t want two plugins the exact same and we will now focus on data management when it comes to WordPress CSV Importer.
CSV 2 POST is the advanced data import and post creation plugin from here on. http://www.csv2post.com is also the main domain for the post creation plugin and [ link redacted ] cannot be used due to it including the WordPress trademark “wordpress” obviously.
So yes, big changes and it all happened today. CSV 2 POST has been uploaded and the website which currently shows “WordPress CSV Importer” on it. Is about to get changed too CSV 2 POST.
In the long run this is all for the best. Thank you for your patience.
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 WordPress.org
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]
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
It only violates if it is in use as a parent domain.
That’s not correct and that redacted URL does not 301 redirect to anything. It leaves the user on that site.
If you want to handle this correctly then make sure you have a blanket redirection for all visitors to that site.
<IfModule mod_rewrite.c> RewriteEngine on RewriteRule (.*) http://new-url-here/ [R=301,L] </IfModule>
Until you do that then you are not following the rules. Please make that simple change now.
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 WordPress.org where they can download it or GitHub repo where they can get involved.
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.
Edit: See what happens when we lightning reply? 😀 Much thanks for taking care of this!
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.
Pardon me while I get a little less formal:
Dude. I trust that you have good intentions. Seriously, I do get that. 😉
But now do the right thing and fix your site. It’s less then 5 minutes work and *POOF!* you’re in compliance. Problem solved! Easy peazy and as you’re using Git I know you know how to fix this.
- The topic ‘WordPress CSV Importer Changes To CSV 2 POST’ is closed to new replies.