I have written an importer for blogCFC, it is not 100% finished but it works. There are 3 things that it currently doesn’t do, but I am working on these.
It loses all code syntax highlighting, but I have created a default for this for now.
Images are currently not support, but I am working on this as well.
blogCFC supports related entries. This is currently not supported.
I had to make some changes to allow for this importer to work locally. Would have been nice if it just picked it up thoughJ
How do you want these files? Let me know how I can give you these files.
As for related entries, can you submit a ticket for this, so we can prioritize it. I think the actual code to make this work is easy, but the UI for it is the hard part or the time consuming part, as there could potentially be tons of content, so paging is needed, selection, unselection, etc.
As for picking up the importers, that is a nice idea as well. You can do a pull request via github.
Cool, I am not good with github but I’ll give it a go.
I didn’t realise you had raised a ticket for blogCFC importer.
Now the one thing that I did not make any assumptions on, most people I think will setup a user in ContentBox as per the user that they would currently be using in blogCFC. So I made sure that I do a check for the user existing before creation. That way it will attach all too that author.
I am still working on the images stuff, having issues with regex.
As for related posts, yeah I think something like posts->comments would work. So like you have comments for a post then related posts if there is any with the same functionality as comments, like paging etc.
So I am not too worried, but it would be a damn handy thing too have. Only because I already use it on my blog.
Yea, I think it would be a good feature, so yes please create a ticket for it. What I am not looking forward to is the UI for it now. The backed is really easy it is just another many to many to itself with no cascade, but the UI needs to be intuitive as there could potentially be lots of content and you need a way to choose the related content somehow and then manage it once persisted. So as of now, maybe I am being lazy about it
Yea, first fork it, this creates the repo in your account.
Next, do you fixes, additions, ideas, or whatever, then commit and push to your repo in github. Once you feel something is ready to be pushed to ContentBox then make a pull request. and it will send me a request to merge your repo changes into mine. Super easy for me to add new stuff based on the community.