1

Hi Matthew, to answer your questions:

1. Yes. Currently the only way is to export your WordPress database in phpMyAdmin, and import it into Injader.

2. No. The URL structure is: view.php/article/212/article-title. At the moment I'm not planning to allow different URLs, it is possible, but there are a couple of things I wanted to avoid. Firstly, defaulting to non-optimised links. Secondly, allowing people to customise the URL structure after they have added content to their site, as it would either break all their links, or result in a performance-hungry and complex redirect solution. (Think of what happens if you go to SEO links and then go back. It won't work.)

Now, if I were to work in a year-month-day option and provide support for a server-based redirect so we can lose the reference to view.php, that may be workable.

3. As you say, it's a custom editor.

4. Injader has both areas and tags. Areas provide a physical location for each article - for instance, this article is stored under Forums - Help Forum. You can have a hierarchy of areas on your site. The top-level areas generate the navigation bar at the top, and the areas beneath can be displayed as a list of links or you can change the HTML to display them differently. Areas have to be created by an admin.

Tags are much the same as WordPress, I believe. They are not in any kind of hierarchy, and can be used to find similar content.

Hope this helps, let me know if you have any other questions.

2

Actually, I too am curious about why the choice of <br><br> instead of <p> in the WYSIWYG editor. It's how the editor for Community Server works, too, so I'm sure there's a logical rationale behind it... ??

3

The main reason for <br><br> is because of things like lists, headers and tables and how to get <p></p> tags to sit around these without invalidating the source.

In the past I tried keeping every paragraph in <p></p> tags but what happens is you end up with a lot of empty <p></p> tags in the code. Also, it's a lot harder to not mess with people's source code if you add <p> tags, because if they take them out I'd have to add them in.

I think that if Injader used <p></p> instead of <br><br> then we'd run into a lot more source errors than we do now. Perhaps we could think about changing it in the future, but I think it's going to be a trade-off. Especially when you look at the mess of code that IE generates...

4

That does make sense. When you look at the source for a lot of things (Google Docs leap to mind, too) there are certainly a lot of <p>&nbsp;</p> things going on. And I hadn't thought about the problem of tables etc... See, I knew there had to be a reason! In any case, I quite often just type HTML anyway... it's faster for us old folks!

5

Hi Ben, thanks for the responses.

I haven't yet had time to explore Injader properly, but from what I can see, it's sufficiently different from Wordpress that I would have a lot of work ahead to convert my particular project over, which relies on a lot of WP plugins.

I have been rebuilding my portfolio site using Wordpress for the last few months but after the problems that were introduced in WP2.5 I wasn't too happy to continue with it. However, I've done so much work that it's now too much for me to try and convert it to another system, so I'll keep it on WP for now. Not ideal, but I have to be practical about it.

Anyway, this means that I'll probably wait to look at Injader once I have a blog type project that requires a build from scratch.

Regarding the <br> thing... perhaps you might consider using one of the open source editors? TinyMCE is pretty good these days and it would save you re-inventing the wheel?

6

No worries, Matthew. That's a fair point - using Injader to build a new site is going to be a lot easier than migrating an existing site. Both can work, but switching systems is never a small task.

You make a good point about TinyMCE. The only reason I added a custom editor was because at the time, it was a commercial CMS. Now that it's open source, this kind of thing becomes a reality. The only thing I will have to figure out is what to do with site images - currently there's a handy button that will allow you to easily insert an existing image from the AdminCP with one click.

I'll check out TinyMCE for possible inclusion in a future version of Injader. Thanks!

7

That's incredibly fast service, Ben - I see you've just released an update that includes TinyMCE editor, already! Looking forward to trying it out...

8

Thanks for the update here, Jen - I forgot to mention it in this thread. Can you guess that I was very impressed with TinyMCE?

I need to change the default font - it's very small - I'll do that for 2.0.2.